After a bit of back and forth I finally got it working, thanks @dnnkeeper ! For you others stumbling in here wondering about the same, Iâll post what I did.
First of all: Localize your Virtual Desktop (VD) folder, specifically the âVirtual Desktop Streamerâ folder. Weâre gonna need the exe path here, so usually itâs
âC:\Program Files\Virtual Desktop Streamer\VirtualDesktop.Streamer.exeâ. Take note of the path.
Second, find your project folder, i.e. âS:\UnityProjects\VRToolkitUnityâ, only the âtopâ path of the folder is needed. Itâs VERY important that the proejct path does NOT contain any white spaces. Even if its enclosed I couldnât getting it to work, so I had to remove any whitespace in the actual folder names in Windows.
Next is the Unity Editor executable, the one installed through the hub. In most cases itâs located like this: âC:\Program Files\Unity\Hub\Editor\2020.1.3f1\Editor\Unity.exeâ
Replace â2020.1.3f1â with the version your specific project uses.
So let inject things here:
Open a cmd window (Windows + R, write âcmdâ, or search for âcommandâ or âcmdâ in Start menu search. so hereâs the kicker: With paths weâve just located paste in this, in this syntax: " â<Unity Editor executable pathâ> -projectpath â<Unity project pathâ.
An example here:
"C:\Program Files\Virtual Desktop Streamer\VirtualDesktop.Streamer.exe" "C:\Program Files\Unity\Hub\Editor\2020.1.3f1\Editor\Unity.exe" -projectpath "S:\UnityProjects\VRToolkitUnity"
Donât forget the " " when pasting in your own paths!
Then Unity starts, if you hit play when VD is active on the Quest, it runs! Even if you start VD after youâve started Unity, it still works!
EDIT: Some reported that adding â-useHub -hubIPC -cloudEnvironment productionâ after the project path cleared up some HMD detection issues.
Project path would then be:
-projectpath "S:\UnityProjects\VRToolkitUnity -useHub -hubIPC -cloudEnvironment production"
Again creds to @dnnkeeper !