Ralf

[Ralf]

Try to run the game windowed. There is some conflict with the Rockstar overlay. Running the game windowed can help, but you still might have to try a few times if you are unlucky.

[Ralf]

Normally setting the resolution automatically shouldn’t cause any issues at all, but if for some reason it does, you can disable that on first launch on the DirectVR page of the vorpX menu. Afterwards select a common 4:3 resolution in the game options manually.

The catch is that this way you can’t select resolutions higher than your desktop res like the auto resolution can. So if you want to manually set a resolution larger than that, you have to add it first in the graphics driver control panel.

[Ralf]

Hating or loving are not the right categories in terms of adding options to the menu. Otherwise the menu wouldn’t look like it does. The menu just has to stay usable, hence not every single parameter can be an option.

Anyway, I’ll definitely experiment with the HUD, just can’t say yet what will come out of that.

On a sidenote: The HUD is probably what benefits most from enabling DLSS in the game’s graphics options. DLSS at ‘Auto’ allows you to go one or two notches higher in terms of resolution, which doesn’t change the lens distortion, but hugely improves readability of the scanner UI.

[Ralf]

@ hasnaat_k

That sounds as if something is severely off. You shouldn’t really have to tinker with the settings in the menu aside from changing the resolution for performance/quality tweaking. Leave all other settings alone. Head tracking should work out of the box.

If you happen to have other mods installed, remove them. Mods that affect the game camera in any way may break head tracking with the VR mod.

Best uninstall the VR mod, then (if necessary) remove all other mods and afterwards reinstall the VR mod.

The version number shown in the game window should be alpha 6b

@ drowhunter:

I’m not much of a fan of the floating HUD approach myself TBH, always find that severely annoying if some native VR game does that. But I’ll tinker a bit with a rubberband approach where the HUD follows your head with some inertia. No promises, but that sounds as if it could be kind of nice and would elegantly solve any issues with glancing into corners.

That aside: I have played so many hours of Cyberpunk myself that I wonder what exactly you can’t see by glancing into the corners. Sure, stuff in the edges is somewhat blurry, but no matter what headset I use, getting information I quickly need like the health status or where I am on the minimap is no problem at all by glncing into corners. And for the (very) few times where a closer look is required, there is indeed EdgePeek.

That said, the rubberband approach still sounds worth a shot. Best of both worlds.

[Ralf]

Great. Have fun (again).

@ Demuse, jools92:

Thanks for the feedback. And also for your detailed troubleshoot infos!

@ Demuse:

If you happen to have the regular vorpX and occasionally use user profiles you like, consider donating a few bucks to the profile authors. Some of them have donation infos in their profile descriptions.

[Ralf]

That can happen if you moved the game to another drive. Try to browse to the actual Cyberpunk install folder manually if the installer can’t figure it out automatically.

[Ralf]

@ all

I was finally able to reproduce the issue with Zel1984’s method of switching to and from the map screen, yay! Not always, but often enough to give me an idea of what it might be related to: when the game switches back from the menu/map screen, vorpX has to reinitialize some depth buffer stuff for Z3D and I’m fairly certain that’s where the problem begins that shortly after results in the crash. Something must have changed with patch 1.5 that triggers this issue.

Fortunately this depth buffer init is entirely unnecessary while alternate frame 3d (‘DirectVR’ in the menu) is used, so as a workaround for now I just skip it unless Z3D is actually enabled. Due to the issue’s random behavior I’m not 100% sure yet whether that was really it, but reasonably confident. Please let me know whether the new version does the trick for you.

CAVEAT: For now do not switch to Z3D! The workaround is only active with DirectVR 3D. I’ll take a closer look at the actual depth init issue next week.

Download

Make sure that the version shows alpha 6b in the game window after installing. Some seem to occasionally get outdated files due to caching by their browser/internet provider or whomever.

[Ralf]

Awesome. Glad you got it sorted.

[Ralf]

Weird that I can’t replicate that here no matter how hard I try.

If anyone of you happens to have the regular vorpX (I think you do Zel1984?), could you please create a trouble shoot data archive in the config app? Won’t contain any mod specific information, but some data about your system that might be useful for me.

Please send that to support(at)vorpx(dot)com as an e-mail attachment.

[Ralf]

@ 3oxis :

Thanks! You’re welcome.

@ Jools92 :

Got your trouble shoot data. Nothing obvious in the logs unfortunately, but I’ll check next week whether your config and save files maybe help to shed some light on the matter.

[Ralf]

There has been a Cyberpunk update today that broke compatibility with the modding framework that the VR mod is based on. You have to update the mod to make it work again:

Cyberpunk VR Update Thread

[Ralf]

OK, thanks. That’s valuable information. What I need now are a few things that might help me to reproduce the problem:

1. Your Cyberpunk config file:
C:\Users\[Username]\AppData\Local\CD Projekt Red\Cyberpunk 2077\Usersettings.json

2. The vorpX log file directly after you encountered a crash
C:\Users\[Username]\AppData\Local\temp\vorpx.log

if you can’t see the AppData folder, enable “Show hidden files” in Windows Explorer.

3. A savegame with this issue (one is enough) and the user.gls file from:
C:\Users\[Username]\Saved Games\CD Projekt Red\Cyberpunk 2077

4. The entire cyber_engine_tweaks folder (has to be the entire folder!) from
[CP2077]\bin\x64\plugins

Please pack these into a ZIP file and send it to support(at)vorpx(dot)com as an e-mail attachment. With some luck that will help me to reproduce the problem.

[Ralf]

You can temporarily disable/enable the mod by moving vpxCP2077.asi from [CP2077]\bin\x64\plugins to your desktop and back.

As far as the issue is concerned:

First and foremost: please try without any changes in the mod settings aside from potentially changing the resolution. There is no need to tinker with settings, the mod works as intended without any changes in the settings menu.

That aside:

If that doesn’t help, it would be great if for testing purposes you could start a new game with no other mod installed than the VR mod and check whether the issue also occurs with that new game, especially if you had other mods installed before, Most importantly: please let me know whether that helps or not.

I’m totally in the dark as far as this issue is concerned and unfortunately haven’t gotten any feedback in that respect so far. Since the issue popped up out of the blue after the 1.5 patch without any actual changes to the mod aside from some gesture related fixes, it’s possible that the issue isn’t actually triggered by the mod, but by a corrupted savegame, e.g. from some pre 1.5 mod that stored settings in the savegame that the patch 1.5 doesn’t like.

Long story short: To help you I need your help.

[Ralf]

The file on the server is the correct one, but if you just downloaded the file very recently, your bowser, internet provider or whoever may still have cached the older one.

Try with a different browser if possible or with your phone via a mobile connection.

Alternatively just installing the latest version of the CET modding framework should also do the trick this time. That’s what today’s Cyberpunk patch actually broke, not the mod itself.

https://wiki.redmodding.org/cyber-engine-tweaks/getting-started

[Ralf]

A new version with support for today’s Cyberpunk hotfix is now available:

Download

[Author]

Posts