Forum Replies Created
-
Posts
-
Hard to tell, maybe enabling raytraced reflections at your res/settings tips the graphics card over the edge memory wise so that is has to use system RAM. Just guessing though. Just try something slightly more modest and you should be good, probably including raytraced reflections.
“3200×1800, ultra settings” is the answer to your question. Try something slightly more modest. I played for several hours now on a 3080 at 2560×1440 and the settings the game chose automatically for the 3080. No framerate issues at all.
Try the ‘Color Precision’ to ‘High’ fix. Unless you experience yet another depth glitch that should help.
Just to emphasize dborosev’s post: anyone experiencing occasionally garbled depth: please set ‘Color Precision’ to ‘High’ in the game’s graphics options. I’m 99% certain that this will reliably fix the issue.
There will be another hotfix pretty soon that does this automatically on game start.
Changing this setting doesn’t come entirely for free. Provided the GPU monitoring app I use measures correctly it costs about 100MB of GPU memory at 1080p (more on higher resolutions). Probably no big deal, but on lower end graphics cards it might make sense to dial something else back instead that potentially has an impact on GPU memory usage if possible, e.g. shadow resolution.
@ ThinkTwice:
Sure, if you kept the small web installer that you got after the purchase, you can simply use that. If not, no problem either: you can get one here:
http://www.vorpx.com/request-new-download/
@ elocm:
Try to set the ‘Render Scaling’ option to 100 (the default) in the game’s graphics option. That might be necessary to get 3D. Please also note that over large distances (like in reality) there is not a lot of 3D. Stereo vision works at close/medium distances, in VR just as in reality. You should notice a pronounced 3D effect when you switch the camera to external and look at the plane if all is working right.
That will almost certainly be better in many aspects. I just had the profile ready anyway and didn’t want to throw it away.
The biggest factor here is that the game is not made for VR, hands/weapons are often made larger by game devs in first person games to look good on a monitor. Sometimes that can be addressed, sometimes it can’t. I’ll have to dive into the bowels of the game somewhat deeper than I did so far to say whether or not something can be done in this case. A secondary factor is the way vorpX creates 3D for this game, which isn’t entirely accurate (but on the upside twice as fast as rendering everything separately for each eye).
Something like that already exists. There is a gaze based hotkey menu with 16 freely configurable ‘buttons’. You can assign any keyboard shortcut to these ‘buttons’ in the vorpX menu.
To use the menu you simply press (and hold!) shift+mousewheel, look at the ‘button’ you want and release the mousewheel. Seriously couldn’t be more comfortable to execute a keyboard shortcut in VR. Probably the most underused vorpX feature of all times, pretty useful for keyboard heavy games.
The trick for using that from a VR controller would be to sacrifice one controller button by mapping it to shift + mouswheel click.
There is some auto detection built into vorpX that tries to figure out whether Z3D should be on or off by checking how much is going on currently. Unfortunately something like this can’t be 100% reliable all the time since some (many) games render menus and similar screens simply in front of everything else, which basically breaks the workload detection. But for Cyberpunk 2077 it should work most of the time when you switch to the menu.
There also is a hotkey though for turning on/off 3D manually. Per default that’s ALT+X, can be changed to whatever you seem fit in the config app.
Another good, maybe even better, way to achieve what you have in mind is setting the EdgePeek 3D multiplier to 0.0. That way 3D is turned off whenever you switch to EdgePeek.
Maybe that’s just too much. Try to reduce graphics settings until you can reach half your headset’s refresh rate. At that point vorpX will cap the framerate and the GPU wouldn’t be completely overloaded anymore.
Also please try without Virtual Desktop. Better to remove anything from the chain that isn’t strictly necessary. Or does Oculus Link not work for some reason?
Also, just in case you overlooked my earlier reply in that regard: please make sure to have the latest graphics driver installed, both AMD and nVidia had updates for Cyberpunk 2077 yesterday.
And last, but not least, also just in case: no overclocking of any kind. That’s evil in general and it’s even more evil when bringing a PC to its limits by playing a game like this with vorpX.
Just do it like me and play the start multiple times… After that you’ll know everything inside out.
Did you encounter any more issues with garbled depth in the meantime? I checked pretty much the whole game start up until the first mission in the city plus some walking around afterwards two times today. One time in ‘Generic Headset’ mode, one time with an actual headset. Not a single hiccup depth- or otherwise. Seriously beginning to think this might have been resolved by the latest nVidia driver update yesterday, which I didn’t have installed when I made the profile originally.
I just played for an hour straight without any issues. Both nVidia and AMD had graphics driver updates yesterday specifically for the game. Please check whether you have the latest driver installed.
As the very first thing in case of any unusual behavior please revert any changes you made to game files. The max. FOV hack sounds harmless, and I wouldn’t really expect it to cause problems, but who knows.
Also, just in case, a little reminder that routinely belongs into every answer to ‘my games crashes’ posts in this universe: overclocking is evil.
A lot of things only really make sense to be edited from within the game, so that would be of relatively limited use. Not sure what you are editing exactly, but if for example you are working with the shader authoring tool, it can be a big help to do that in ‘Generic Headset’ mode, which shows the output on the desktop.
That’s a lot more comfortable than working on profiles in the headset. You can more or less consider that to be kind of an offline tool. Doesn’t make sense for everything, but makes editing things easier that don’t directly depend on the actual headset.
If you happen to have the “Render Scaling” in the game’s graphics options set to anything else than 1.0, please try to reset it. Let me know if that helps.
If not and you happen to use any unusual setup (output stretched about several monitors or something like that), please also check whether that has an effect.