I was wondering, is an Oculus user profile required to use Vireio in "Oculus Rift (All Variants)" mode ? Currently it causes games to crash on startup (I tried with Portal 1 & 2 and Skyrim).

Browsing through the forums, it seems Vireio uses the Oculus SDK for this particular rendering mode. I have the Oculus 0.5 runtime installed, but since I don't own an Oculus, and don't know anyone who does, I can't create a profile.

I'm streaming my screen to my phone, got headtracking to work fine, etc, but the "DIY Rift" rendering mode looks horrible with my headset. I need to customize the various rendering options (barrel distortion, etc), but it seems it's only available in the Oculus rendering mode.

Progress... I managed to overcome the Oculus user profile thing !
All you need to do is create this file: C:\Users\<your user>\AppData\Local\Oculus\ProfileDB.json, and put double brackets {} in it. That's all, Oculus doesn't care about missing data in it and defaults everything else. Neat.
(Actually, a Google search on ProfileDB.json can bring up some examples of what is supposed to be in this file, but putting valid data into ProfileDB doesn't prevent the next crash)

Yeah, games still crash on startup though. However this time the logs don't say much:

Hmmm, no error message or anything. Game launches, black screen, and crash. Happens with both Perception 2 and 3 (although 3 has an extra error message saying it cannot init OculusTrack, since VP3 doesn't allow you to select tracking mode when using Oculus Rift rendering)

I hope one of the devs here has time to have a look at this... Not being able to use Vireio with a DIY headset is pretty annoying.