Forum Replies Created
-
Posts
-
@ dborosev : Your issue is WMR exclusive. There is a problem with WMR headsets and the latest SteamVR version. If you happen to still have a Rift/Vive somewhere in a closet, use that instead of your Odyssey and your “not showing in the headset” issue will be gone.
You have to restart the game after switching from Z3D to G3D. There should be a hint recommending that directly below the option in the menu when you change the 3D mode.
Will it VR? Apparently it does. Always nice to see someone liking what you do. Although the really hard work was done by the hundreds of writers, artists, devs etc. at Rockstar, of course.
There seems indeed to be an issue with WMR headsets and the most recent SteamVR version. I just did a few tests with a WMR headset and the latest SteamVR: I get an image in the headset in 1/5 tries or so. Doesn’t matter what API or game, happens with practically everything.
I’m not sure yet whether there is something that be done on vorpX’s end to change that. I’ll do a few more tests next week.
I’ll take care of it. Check back tomorrow for a hotfix.
That said:
I understand that there is a lot to dislike about Windows 10, but as part of the remaining, borderline irrelevant, ~1% of VR users still on Windows 7 (source: Oculus hardware survey) at some point in the not too distant future you will get left behind. This one should be easy enough to fix, but there will be a point where the effort required to still support Windows 7 finally doesn’t make any sense at all anymore.
Oculus stops officially supporting Windows 7 next year and Valve already tells Index users that they should expect “unexpected behavior” on Win 7. In other words, they don’t really care anymore.
Seriously: it’s time to move on. We all have things we grew accustomed to and want to keep as long as we can, but at some point we have to acknowledge that the world around us doesn’t stand still, whether we like it or not.
You probably did that already, but if not, checking SteamVR settings might be worth a shot, especially supersampling settings. vorpX normally prevents unnecessarily large headset render targets automatically, but it can‘t hurt to make sure nothing unreasonable is set in SteamVR in the first place.
It would be nice if you could stop posting everything in multiple places, that gets confusing. One time is enough.
With a 16:9 resolution like suggested by the start message in the upper left corner, FOV should be OK. If not, try to disable automatic settings on the DirectVR page of the vorpX menu and dial in the FOV manually in the game options.
For a sharper image you can run games at higher resolutions. Details in the “Custom Resolutions” section of the help or here.
Please import the “The Outer World [vorpX]” profile from the cloud. Can’t test it here since I have the Windows Store version, but the cloud profile theoretically should fix the Epic Store version not hooking.
The fixed issue that affected the Farming Simulator 2017 shadows might also have affected other D3D11 games, maybe GTA V too. Good to know.
The loading screen image glitches are nothing to be concerned about, just the game writing garbage into the depth buffer while loading.
I’ll do some more tests switching between cutscenes/interactive/UI later. Thanks for the settings file. I sure will try that one.
Desktop viewer: confirmed. Probably due to some last minute injector changes for the Rockstar launcher yesterday. I’ll look into it. Will get fixed ASAP. Thanks for the heads-up.
RDR2: I did another one hour or so test session yesterday after the final 19.3.0 release, incidentally even on a Rift (S). My only issue was that I managed to fail the ‘Polite Society, Valentine Style’ mission four times in a row in incredibly stupid ways. Either by getting stuck with the cart, getting shot by someone I didn’t even see or by riding the cart into a crossing train. Guess I’m not exactly a RDR pro… Plenty of switching between cutscenes and interactive sequences without problems.
I’ll do some more testing later and see how it goes. D3D12 support is so new that I’m not entirely confident yet about its long term stability myself, but so far I didn’t encounter any issues here in that regard. Maybe try switching vorpX to SteamVR mode if you have issues with native Oculus, that will also work with a Rift.
As usual also make sure that Windows, graphics drivers etc. are up to date should that happen to not be that case. If you have changed any graphics settings in the game, using the default preset might also be worth a shot, just in case the issues are related to some feature that isn’t enabled with the default medium settings.
@ dellrifter: You can switch to actual fullscreen mode instead of borderless in the game’s options to avoid stretching with different aspect ratios than your monitor. Alternatively you could select the desired aspect manually in the cinema mode settings if the vorpX cinema screen looks also stretched.
Just in case you tried some manual modding before vorpX: check if you have a leftover d3d12.dll in the game folder, which would cause a conflict with vorpX. For other APIs vorpX shows a warning in such a case, but I might not have added that for d3d12 yet.
vorpX 19.3.0 is back. You should get it when you launch vorpX.
Note that the RDR2 profile defaults to immersive screen mode, which at this point I personally consider the better choice for various reasons.
If you want, you can try FullVR mode with the game’s first person FOV maxed out and a 16:9 resolution. Don’t expect FullVR perfection at this point though. Even maxed out the FOV is relatively low, so relatively huge top/bottom bars are required to account for that. The profile will be resvisited and if possible enhanced over the next weeks/months.
This is largely for those who want to try things as fast as possible.