Forum Replies Created
-
Posts
-
I’m on it. Looks like the SteamVR judder fix introduced additional latency. An update for the update will be released later today.
Please check whether you maybe inadvertantly disabled the new ‘Prediction’ option on the display page of the vorpX menu. If so, re-enable it.
If you are using SteamVR, please make sure your SteamVR is up-to-date. Should be 1.1.4. The fix that was necessary due to judder with the latest SteamVR version might have unwanted side effects with older SteamVR versions that do not support Motion Smoothing.
In regard to any potential issue with resolution please create a trouble shoot data archive in the config app and send that to support |at| vorpx com. That will allow me to check whether anything unusual is happening with your headset render target sizes.
In regard to latency try to disable FluidSync (display page of the ingame menu). Be aware though that doing so may introduce flicker/judder if you can’t maintain at least steady 45fps in a game.
The supersampling resolution you have set in SteamVR/Oculus is of no real concern for vorpX. You need to increase the actual resolution a game runs with to increase the image quality. This is very different from how native games work. 1600×1200 or 1920×1440 are usually good resolutions for vorpX.
Make sure to check the Custom Resolutions section in the help or this thread for additional information in this regard.
vorpX 18.3.2 has been released. This is a maintenance release mainly addressing frequent frame judder in SteamVR mode after the latest SteamVR update.
In addition to that some related changes originally intended for vorpX 19.1.0 have been backported to 18.3.2, most notably support for Motion Smoothing (SteamVR), respectively Asynchronous Space Warp (Oculus). vorpX 19.1.0 is still on track for a pre-Christmas release.
Changes/Fixes:
- SteamVR: Fix for frequent judder below 90fps with recent SteamVR versions.
- SteamVR/Oculus: Motion Smoothing/Asynchronous Space Warp support.
- SteamVR: Supersampling <1.0 is now taken into account (only important for Pimax 5k/8k).
- Oculus: Crystal Image setting takes user set super sampling into account.
- D3D11: several multithreading fixes and improvements
- The Witcher: better Geometry 3D profile, Z3D parameters tweaked
- The Witcher 2: G3D did not work anymore, Z3D parameters tweaked
- GTA V: scalable HUD added
Fluid Sync caps the game fps to 45, but in turn make it easier to keep the headset FPS at 90fps. Artificial intermediate frames are created similar to SteamVR’s reprojection to make up for that.
After you created a custom a profile with basic G3D support by copying an existing one you can access advanced shader authoring in the vorpX menu do define shadows, HUD shaders for a scalable HUD etc. or disable effects that don’t work well in stereo.
To unlock these authoring options check “Enable expert settings” and then “G3D Shader Authoring” in the config app. The authoring menu can then be accessed ingame with CTRL+END.
vorpX does not support newer (shader based) OpenGL versions in stereoscopic 3D. With a few exception OpenGL games newer than Doom 3/Quake 4 are 2D only.
There is no way to create a Geometry 3D profile for Rage unless vorpX gets G3D support for newer OpenGL versions, which is unlikely since just a handful of games would benefit from that.
There will be a maintenance update specifically addressing the SteamVR judder issue tomorrow, this issue is too severe to wait for the next regular update.
vorpX 19.1.0 with the DX11 improvements incl. Frostbyte G3D is due (shortly) before Christmas.
If the same issue also occurs with other games, please check whether there might be an injection conflict with some other program on your PC that also hooks into games.
Typical candidates are: virus scanners, any sort of CPU/GPU utility, game recording/streaming software, messengers and generally everything that can show notifications/overlays in games.
The best way to trouble shoot this is to close/uninstall all programs running in the background.
Please check whether maybe your DotNet installation is corrupt. On Windows 10 no additional DotNet install should be required, but who knows. The config app requires DotNet 4.6.2.
Also try to uninstall/reinstall vorpX if you haven’t done so already. Just to make sure the installation isn’t corrupt somehow.Keep the license information when the uninstaller asks about that.
DotNet Repair tool
https://www.microsoft.com/en-us/download/details.aspx?id=30135DotNet 4.6.2 installer:
https://www.microsoft.com/en-us/download/details.aspx?id=53344There seems to be some judder with recent SteamVR versions (probably since Motion Smoothing was introduced) at default settings.
For the time being being please make sure to set “Fluid Sync” to “On” on the display page of the vorpX menu. That will cap the game fps to 45, but in turn make it easier to keep the headset FPS at 90fps. With steady 90fps for the headset rendering the judder should be gone.
You can check the FPS values with ALT+F, should read 45/90 ideally with Fluid Sync on.
An update that addresses this issue one way or the other will follow as soon as possible.