Forum Replies Created
-
Posts
-
I don’t really think I can help with that beyond what I already wroty above. Sorry.
If you run any gamma profili software on your Windows, try to disable/remove it.
If you want a refund, please send me a mail to support |at| vorpx com. Judging from the rather unusual problems you have on your machine that might be the best solution.
Otherwise I would as a last measure suggest to reinstall Windows to make sure you *REALLY* have a clean Windows install. Then don’t install anything besides the Oculus software and vorpX. If you have an older harddisk somewhere, you could use that for testing purposes without having to kill your current Windows install.
Just in case you didn’t try the most basic thing yet: try to reboot the PC.
Gamma:
There should be a ‘More cinema settings’ button on the main page of the menu, which let’s you adjust the cinema environment if necessary.
The actual game gamma can be adjusted separetly on the image page of the vorpX menu.
One more thing, in case you didn’t try that already: try a full factory reset in the vorpX config app.
After you did that, check whether disabling head tracking in the config app makes any difference.
Also try other VR applications if you did not do that already to check whether the issue occurs generally with your headset or is vorpX specific.
Might also make sense to reinstall the Oculus software and repeat the headset setup.
But it stops every connection out per default
That’s the problem. A more usual firewall setup would be deny incoming/allow outgoing.
Try to disconnect any gamepad/joystick etc. (especially flightsticks/steering wheels) you may have connected to your PC. Alternatively make sure all their axes are centered.
This is no problem with the Windows firewall at default settings.
If the auto update fails for you due to some unusual firewall settings on your machine, you can use the vorpX web installer to install the latest version manually.
This error is returned by the Oculus runtime if it fails to initialize.
The Oculus error code -3001 means: “Couldn’t load LibOVRRT.”
LibOVRRT is the main compopnent of the Oculus runtime. if it cannot be loaded, I would assume that your Oculus software install is broken. Try to reinstall the Oculus software from here: https://www.oculus.com/setup/
The important setting for vorpX is the resolution you run a game with, not the SteamVR supersampling, which only comes into play in a second step when the already rendered game image is sent to the headset. This is quite different from how native apps work.
If you want to raise the image quality, don’t mess with SteamVR, raise the resolution of the game. For many games vorpX can handle that with its DirectVR feature, otherwise you typically want a 4:3 res for FullVR (unless you have a Pimax 5K/8K) and a widescreen res for cinema/immersive screen mode.
I’d also highly recommend to check the ‘Custom Resolutions’ section in the vorpX help that explains how to add resolutions to your PC that it does not support yet.
I’ll take a look at it and see what will be possible.
General hint: If you encounter a situation in a game where G3D has issues that make it hard it play, you can always switch to Z3D (ALT+K) or turn off 3D (ALT+X) temporarily if switching to Z3D still doesn’t help.
In this case you could play with G3D at day and then switch to Z3D at night if I can’t find a solution for the night light glitch. Not perfect, but a good workaround.
I don’t have one yet, but it should work out of the box. Pretty much all software that uses the Oculus runtime should work with the Rift S, vorpX is no exception.
Try to reset the profile to default. There have been no changes to the default zoom level, should be 1.0 per default as always unless a game’s max. FOV requires a lower zoom value.
I looked into it prior to releasing the last update, but due to issues with G3D the profile wasn’t included. Will come at least as Z3D only profile soon if I can’t resolve the G3D problem.
Would probably only make sense for DIY headsets without a SteamVR/Oculus compatible tracker. For headsets that provide tarcking data via SteamVR/Oculus vorpX can do head tracking on its own.
vorpX 19.2.0.1 has been released.
This is a hotfix release that addresses the issues below:
- On Windows 7 some DX11 games could crash with SteamVR.
- Metro Exodus: Shadows are now disabled per default with Geometry 3D for a 50-80% performance boost. If you already have vorpX 19.2.0 installed, either reset the profile to default or switch off shadows manually in the vorpX menu.
- New headset render target size calculation slightly modified.