Forum Replies Created
-
Posts
-
@ ghoulworld:
Install the latest vorpX beta. It comes with the full feature set of the standalone mod.
@ mateusz:
You could create a custom resolution in the nVidia GPU driver settings app, disable auto resolution in the vorpX menu and then set the created auto resolution.
@ Destroy:
That sounds wrong. Try to reset the game’s graphics settings to medium and go from there. With a 4090 you should get much better results. The CPU shouldn’t be much of a bottleneck either.
You can use motion controllers as gamepad with vorpX. The latest beta also comes with controller gestures. Shor demo video in the post below:
Make sure to install the beta and let it install the additional components. The profile now comes with all extra features of the standalone mod. Alternatively use the standalone mod and pause vorpX while playing Cyberpunk.
I only have the Steam and the GOG version here, but never heard of any Epic specific issues. So it’s pretty unlikely that there are any.
In regard to launch crashes:
First please reset the game’s graphics details to default before installing the mod.
If that does not help, browse to C:\Users\[Your User]\AppData\Local\NVIDIA\DXCache, select all files and delete them. Some can’t be deleted because they are in use, skip those.
Note that the AppData folder is a hidden folder, enable ‘Show hidden files’ in Windows Explorer to see it.
Make sure that the game runs in the foreground by clicking into its window with the mouse, just in case. If it’s not running in the forground there may be input glitches. That should also help with any potential ‘motion controller not working’ issues.
Also try to disconnect potentially unused fightsticks ot anything similar you may have connected to see whether they get in the way.
Please see my reply to when you asked the very same question four posts above. Or alternatively to when you asked it for the first time a few days ago.
Use your motion controllers. Make sure to check the gestures in the tutorial. So much better even seated.
2023/10/05
Version alpha 9b is available. Adds compatibility with Cyberpunk 2077 2.01. No other changes.
If you changed any settings in the vorpX menu, please first reset everything to default. Afterwards please make sure to follow the performance related hints in the huge instructions panel that gets displayed in the launch environment.
You asked that before already. The mod works with CP 2077 2.0, with or without Phantom Liberty, so the only building block is installing the mod. Alternatively you can use the vorpX beta, which auto downloads the updated extra components when you launch the game.
Please note that patch 2.01, which apparently gets released later today, will probably break the mod again. Stick to 2.0 by disabling auto updates in Steam/GOG until a new CET for 2.01 becomes available.
Should work out of the box without the need for any changes on the vorpX end.
Since the Quest 3 will probably become the most popular headset in next one or two years I still preordered one too to make sure it really does. So in the unlikely case of any Quest 3 specific issues things will get fixed ASAP.
You may have to press a trigger/button to activate motion controllers ingame, nothing else.
Don’t touch anything in the vorpX menu aside from the resolution and potentially the framerate cap. If you have a fast PC you may to want to set it to ‘small delay’ instead of the default 66%. That will allow the game to run at the full refresh rate of your headset if you don’t overdo with the graphics details.
Everything else you really need to know gets displayed in the headset when you launch the game. No need for an external readme. Check the huge instructions panel on the right and the info panels that are displayed when you go through the tutorial.
The general features are listed in the aformentioned instructions panel. As far as less obvious features are concerned the most important one is probably VR optimized vehicle and weapon (aiming down sights) cameras, i.e. the mod adjusts the default camera positions etc. based on gameplay context. Aiming down sights even comes with actual motion controller aiming.
Nope, no frame generation. But if you have a very fast GPU, you can try to disable the frame cap in the settings menu or set it to ‘small delay’. With a 4090 for example you can achieve native 90/90 (72/72 on Quest 2) even with a bit of raytracing (and standard DLSS). Framerate can be checked with ALT+F.
I’d still recommend to disable raytracing though and instead bumping up the resolution as high as your PC allows. Higher overall benefit.