im using similar setup
i actually just got it to run. using oculus quest w/ link. i ran steamvr and dropped the render settings to 50% and launched game. not sure if this factored in but i also changed the settings in the quality settings.txt from 2 to 1.Are you also using the 21.1.1 diver ? or and older one ?
Are you also on win10 20h2 ?
The main idea is to look for common part (is this a 21.1.1 driver issue, or more a general non radeon support of the engine ? Is this just a win 10 2h02 issue, or just that peculiar version ?).
This may help the dev to get help fixing the issu (reporting to the engine, to the driver manufacturer or microsoft - good luck with the last two)
Edit:
As written in dev note:
* Not compatible with Oculus Quest currently.
I guess the part "Compatible but not tested with Oculus Rift/S." is just wrong and all oculus doesn't work
I really hope that one day, VR development using common norms so one software won't be just compatible with one hardware.
I mean like webbrowser (webpages compatible both gecko/chromium) or directx (implementes by intel/ nvidia or amd) and not like proprietary stuff (cuda, physx, etc... for example)
Yeah I didn't have any sound either, however, on his Twitter or something he had a more updated game shown in a quick video, that had sound and different models or customizable models, the sounds were actually nice too...
I run it through Link, I didn't test Virtual Desktop yet as it costs a bit much in my opinion. Link should be more stable for connection etc. But what happens is: I add the game to my Link library, and I start it, but it says it's loading forever, and when I look on my monitor it started the game with a weird camera angle and no way to control it. If I open it through virtual desktop on Link (the option in Link, not the software) it doesn't allow me to control anything in game, and I can't even change camera angles etc.
