Forum Replies Created
-
Posts
-
I think the game was pushed out the door before it was ready for prime-time. It took me several hours just to get the game running on my rtx gpu (had to downgrade my video drivers). I’ve fixed that but vorpx only hooks the game about 10% of the time; usually it flatlines.
So I’ll probably wait until it’s stable enough to actually be playable.
You need to make sure the game starts up in G3D mode. If you start it with Z3D and then switch, the G3D will get messed up.
I already uninstalled the av once but went back because Windows Defender kept complaining about a registry entry but didn’t fix the underlying cause.
I already used solution 2 up to ig-20 but was hoping there was an easier way to address the other 80 possibilities. Maybe I can just turn real-time protection off.
Thanks.
I’m certainly not an expert on the matter, but from what I’ve read, the latency settings are not very effective when compared to other methods of reducing latency, like capping your framerate to prevent the gpu from getting overloaded.
I’d think that ultra low latency would override the setting for pre-rendered frames. I don’t know why you’d want to run a headset with ultra low latency turned on though.
Since I changed pre-rendered frames from the default value, I get better framerates, practically no stuttering, and can run games at higher resolutions (including 4K, which was impossible before).
Anyway, my cpu/gpu don’t like the default value. Years from now, perhaps decades, when the mythical RTX 3080 emerges from the shadows, I may change it back.
The default nVidia setting for VR pre-rendered frames is 1. That’s generally considered to be stupid and should be changed to “use the 3d application setting”, or at least a value greater than 1. Unless you like stuttering.
In the game bring up the vorpx menu (DEL on your keyboard or Left Stick Click on your controller), then hit the right bumper (r1) a few times to get to the input settings. On this tab, you can override the x-box controller fully or partially, or not at all. On this tab you can also change the keys the controller is mapped to by clicking “change gamepad settings”. These keys are only used if the controller has been overridden.
Setting the keys is kind of a pain in the butt because you have to take your headset on and off, but that can be avoided by running the game in generic desktop mode and setting the keys there, before going back to the headset. Make sure you click on “okay and save” after you’ve remapped the keys.
I’d think that the mapping was wasd for movement by default, but I haven’t played the game in awhile, and oftentimes I just run a game in cinema mode with the xbox override turned off because I don’t like the keyboard prompts that display.
To avoid the frustrations I’ve experienced in the past, I’d recommend that you pull the 2nd gpu out of the box. Disabling the gpu doesn’t always work. If removal is too much of an issue, you can try uninstalling the drivers on the second gpu and turn it into a generic vga device.
Oculus doesn’t support multi-gpu configurations, and Windows 10 and the Nvidia drivers seem to fight over whose in charge of the devices. You can try a lot of things including purging and re-installing your nvidia drivers in safe mode, but it’s easier to just pull the adapter out to see if it’s the real problem. If it’s not, then you know to look elsewhere.
It works okay with an xbox 360 controller and Rift S. You can change the vorpx override in input settings, or change the controller mapping. How you want to do it depends upon the mode you’re playing in. If playing in cinema mode try turning off the xbox override; for immersive mode you need the gamepad to emulate the keyboard in order for head tracking to work, so you want the override turned on.
In Windows graphics settings, assign OVRServer_x64.exe, OculusClient.exe, and OculusDash.exe to the gpu you want to use for VR. Also assign any games that you want to run in the headset to the same gpu. You may want to add SteamVR and Virtual Desktop in there as well to be thorough. Reboot, say a prayer to the mighty multi-gpu god while the OS is loading, and keep your fingers crossed. If all else fails disable the gpu you don’t want to use in device manager, at least temporarily until you sort everything out.
The vorpx driver cpu usage is normal – they run at real-time priority for reasons Ralf can better explain than me.
Just a note: vorpx does not get involved in gpu selection – that’s entirely up to your system and how it is configured. Vorpx will hook, or attempt to hook, games running on the wrong gpu – they’ll either crash or you’ll get an infinite loading screen in the headset.
You need to make sure the game you’re running is executing on the gpu connected to the headset. Having more than one gpu is a pain in the butt. I’ve made it work correctly most of the time, but problems occasionally pop up, most frequently a game launches on the wrong gpu despite power and performance settings. Hitting win-shift-control-b fixes it sometimes, sometimes I have to reboot.