Documentation of parameters

The experience can be configured via its URL. This allow for customization by anyone while also allowing to share the result back with anyone else. There is no code modification needed, no saving needed. The URL itself becomes the modified experience.

Within that context there are 3 main query parameters to understand, namely username, set and showfile. Specifically :

Note on live documentation of experiments

Most links should work, yes surely some will not work or won't make sense outside of XR or need some interactions.

A lot of the ?set examples (see below) do not show a visual difference as we decided at the end of the 1st quarter to hide a lot of elements to faciliate demonstrations. This unfortunately had the side effect of preventing those examples later on despite them working back then. For example at the end of Q2 ?set_IDenvironment_gltf-model=world-bake.glb does not show the 3D model despite the file being present and showfile working because we are not hiding the element with ID environment. From an experimentation perspective it is arguably not useful to "fix" those historical links as doings will most likely prevent newer ones from working and thus rather unpredictively. It is though important to know that they did work.

Regardless of those technical limitations please do feel free to report links that seem, according to you, not to work as expected. Plenty do provide :
  1. the URL (full including all parameters used),
  2. hardware used, browser used (e.g. Vision Pro with OS version 123 and browser version 456),
  3. date and hour of test (as things are live, maybe something was edited as you tried)
  4. the current behavior (what you expected to see),
  5. the expected behavior (what actually happened),
  6. any supporting materials you think would be useful, e.g. video recording, screenshots, etc.

Parameters

Note that some parameters (e.g. emulatorxr) are only used in conjonction with other parameters. Here emulatorxr with username itself within only a range of values, see below.

Some parameters added after the creation of this documenation (early June 2025) are not documented.

How to populate that list

Ran server side 
grep urlParams.get /transition/webdav/data/fotsave/fot_sloan_companion_public/index.html  | sed "s/.*get//" | sort | uniq

Username values

for username which is itself a just a parameter

Quarter 1

Quarter 2

How to populate that list

Ran server side 
grep username /transition/webdav/data/fotsave/fot_sloan_companion_public/index.html | sed "s/.*== //" | sed "s/) {//" | grep -v dictionaryForCompletion | sort | uniq

emulatexr working with Username values

and for test scenarii only which is with emulatexr parameter

How to populate that list

Ran server side 
head -300 /transition/webdav/data/fotsave/fot_sloan_companion_public/index.html | grep username  | sed "s/.*== //" | sed "s/) {//" |  grep -v dictionaryForCompletion | sort | uniq
there are a quite a few more from Q1 via specifically parametersViaURL because that one https://git.benetou.fr/utopiah/spasca-fot-sloan-q1/src/branch/main/data/index.html#L602 can do a lot, letting anybody changing what is shown or not, how, etc

Set values

Syntax

For example ?set_.pannel_color=red will set to "red" the attribute named "color" for all elements of class name "pannel".

Example of values

Your browser will automatically URI encode your URL, thus one can type position=0 1.4 -1 and get position=0%201.4%20-1

To get a URL to later on use as a parameter value consider using the upload function of the prototype https://companion.benetou.fr which in turns make the resulting file available at https://companion.benetou.fr/filename

Values used

Known problematic ones (usually not a bug, just not visible change)

How to populate that list

Ran client side 
sqlite3 /home/fabien/Prototypes/places.sqlite "select url from moz_places where url like '%?set_%';"  | sort | uniq

See also