Please update this advice.

[bjj]

All that is necessary to run with a fake ("null") HMD is the step where you enable the null driver. That should always be done in your user settings (not the default settings). This is mentioned down at the bottom, but should get better billing.

If you just want to run with no HMD at all (not even a fake one) you just need "requireHmd": false.

There's no need to "force" the driver (which means the null driver would take precedence over any real HMD). This setting causes users to think their HMD is broken later when they have forgotten they forced this setting. The normal driver priority mechanism will let their real HMD override the null one.

There's no need to set "activateMultipleDrivers" just to run without an HMD. The only reason to set that is if you want to mix multiple tracking systems (for example, you want the null HMD and some real physical peripherals). This option is mostly harmless to have on if you don't want it, but it will use more system resources because it will load every driver in your system just to see if they ever have any devices plug in. In the article as written, this setting is basically cancelling out forcing the disabled null driver (which would normally be a dead end) because it essentially un-forces the driver by loading everything else.

[sidenimjay]

Is there any way to turn off the visualization of the HMD ? Initially it did not have a virtual screen, but for the last 2 days it has been persistent

Thanks in advance!