Forum Replies Created
-
Posts
-
DX12 is currently Z3D only. I’ll check whether that’ll be possible, but for G3D DX11 will be required.
DLSS: I did some pretty extensive DLSS on/off comparisons when I made the Cyberpunk 2077 profile. Obviously faster since it renders at a lower resolution, but it almost always also looks noticably worse, even at the highest quality setting. Clearly the best upscaling technique ever created, but it still doesn’t come close to rendering at native resolution. Good enough on a 4K monitor/TV seen from a distance, but in a VR headset? Not really in my opinion.
Origin, haven’t looked into their new client yet. What you could try is disabling the Origin overlay specifically in the Origin options, although that shouldn‘t really be necessary.
There shouldn‘t really anything special you have to do normally. All textures broken sounds as if something really fundamental is wrong. Do you by chance use 3D-Vision? If so, please double check whether it’s disabled in the nVidia control panel. Might be also worth a try to empty the nVidia shader cache in that case (C:\ProgramData\NVIDIA Corporation\NV_Cache).
Would be great if both of you could send a trouble shoot data archive to support at vorpx com. Considering that the game is supported practically since day one and the forum isn’t exactly overflowing with reports of this issue, it’s probably some weird and rare conflict. With a bit of luck cross checking both your system configurations can give some hint.
@ dborosov: as usual please first and foremost remove any mods and check whether the issue also occurs without. Just as with your keyboard mod last time script hook mods of any kind can cause unpredictable behavior since they may hook into functions that vorpX also hooks.
vorpX handles XBox gamepad input. I’m not really sure how a PS5 gamepad works on Windows, but if you can play the game with a gamepad normally, I would expect that to just work with vorpX too.
The gamepad to mouse/kb emulation can be found on the Input Settings page of the vorpX ingame menu. It gets enabled when you set XBox Gamepad Override to anything else than ‘None’. Button mappings can also be configured from there. For that to work vorpX will have to be able to detect your gamepad as X-Box gamepad.
Not sure why the Touch controllers wouldn’t work TBH, per default they should be set to keyboard/mouse emulation mode. Can you see them in the headset after launching the game? You may have to press a button before they show up.
No way to replicate this here. So nothing else I can recommend besides resetting both the vorpX profile and the game’s graphics settings to default. Also please check whether you maybe have a dxgi.dll or d3d11.dll in the game folder that might have been put there by some mod. If so, please remove them. vorpX should complain in that case usually, but just in case.
Unfortunately both G3D and Z3D don’t work right currently. G3D is left eye only, Z3D has no depth. Requires a code fix, no way to fix this with a profile update. Will work again with the next vorpX version.
Sounds like some weird conflict. Please double and triple and check whether there really are no other overlays active, e.g. from some chat/messenger app. Just in case.
Deleting the game’s D3D12 pipeline cache files is also worth a try. Navigate to [Documents]\Rockstar Games\Red Dead Redemption 2\Settings and delete the two files starting with sga_win32_60.
Afterwards first start the game with vorpX while these cache files don’t exist. If that does not help, start the game without vorpX and load a savegame, so that it recreates the cache file and then try again with vorpX.
If any of this helps with your issue, it would great if you could let me know.
Probably Malwarebytes then that causes the problem. If your IT guy has any questions, he can contact me any time via support at vorpx com.
Please first and foremost try what has been suggested above. Most importantly reset the vorpX profile to default and do the same for the game’s graphics settings. Also please check whether you maybe have some mods installed that might interfere.
I’ll check the game within the next few days and let you know if I can recplicate the issue.
This is a false positive. Can happen shortly after an update, especially with more invasive third party AV programs.
vorpX “injects” other programs, which some av programs may classify as malicious behaviour without really being sure about it. Best to report this as a false positive to your av vendor so they can fix the issue. In the meantime please exclude the vorpX program folder from scanning, typically that would be C:\Program Files\Animation Labs\vorpX.
If you happen to use a third party AV program, consider switching to Windows Defender instead. Windows Defender provides excellent protection without being as invasive as some other AV scanners. Windows Defender gets enabled automatically on Windows 10 when you remove third party AV programs.
No. I’d actually advise against that to make your life easier – and as a side effect also mine. :) Unless you have really good reason to tinker with unstable developer previews (i.e. unless you are a developer), stick to what Microsoft considers ready for general use.
In the OpenXR developer tools there should be a switch that says “Use Latest OpenXR runtime preview”. Slightly Above the motion reprojection options in the dev tools. If you have that on, just set it to off.
BTW: If you enable the developer preview runtime, always expect to get what you asked for: a developer preview that isn’t ready yet for general use.
First keep in mind that for games that don’t have a scanner profile specifically tuned for the game, there is a fairly high chance that although the scanner believes it succeeded, it actually failed.
If it actually succeeded and you have DirectVR head tracking, but the gamepad doesn’t work anymore afterwards, try to disconnect/re-connect it. With some luck that might do the trick.
If not you might be able to use vorpX’s gamepad > mouse/kb mapper instead. It can be enabled by changing the ‘Gamepad Override’ option on the ‘Input’ page to ‘Full’. The key mapping is fully configurable. Alternatively you could use your VR controllers in kb/mouse mode, which is more comfortable to use since that way the current keyboard mapping will be visible in the headset on the rendered controllers.
General hint first: if you haven’t done so already, check the beginners guides in the vorpX help. Worth a read, can help to avoid unnecessary tinkering.
1) RE7 specifically: simply raise the ‘Resolution Scaling’ value in the game’s graphics options. Normally the default value that vorpX sets, which results in roughly 1440p at actual 1080p, shouldn’t look too bad though.
General way for games that don’t have such an option: you can run games at any resolution with vorpX. The higher the resolution, the better the image quality. Check the ‘Customs Resolutions’ thread above for adding additional resolutions to your PC that your monitor does not support normally.
2) Not sure if I really understand the issue. Unless for games where vorpX can directly access a game’s memory for head tracking, it simulates a mouse with head tracking. That’s how things work.
3) Ideally don’t add another tool to the chain. Either use wired Oculus Link or the recently added Oculus Air Link. If for some reason you have to use VD, set vorpX to SteamVR instead of Oculus and enable SteamVR capturing in VD. That’s not real an ideal solution though.