Search Results for '2077'

[thebunnyrules]

Hi Ralf, I know this has been discussed before and I know there is a bug related to cdpr engine/texture funkyness when zoom is set above .8.

Thing is, some of us have really low fov HMD that are 90° and loosing 20% of that leaves us with 72° and some really immersion breaking bars.

Personally I would rather take a risk with the texture glitches rather than loose all that fov.

I have 2 suggestions:

Suggestion 1: add an option to disable the limit with a strong warning popup saying “engine will glitch if you zoom past 80% – you’re on your own if you disable the limit.”

Suggestion 2: for those with higher fov HMD: an alternative to going for 100% zoom would be replacing the black bars with a more rounded shaped border that simulates the view in a lower fov HMD (a shape somewhere between the right angles of a square and the curviness of a oval).

I realize this is a free mod, that you’re maintaining in your free time but maybe you can consider these suggestions the next time you’re updating the mod.

Thanks you for this wonderful mod!

[Boblekobold]

And because it was the title of the topic : I think on my hardware (RTX4090) it’s more impressive than Cyberpunk 2077 (the last time I tried a few years ago at least), like a lot of other games.

It’s true G3D, with rich outdoors environments and detailed giant and hairy mammoths ! ;)

Not as beautiful as Frontier Of Pandora or Metro Exodus, but it’s still something to experience (if you like 3dof VR as I do)

[Ralf]

26/01/13 | vorpX 25.1.5 has been released

Another maintenance update. Addresses a couple of input glitches, comes with a rewritten host-exit that better handles exit crashes with Meta’s OpenXR since a recent Meta Link update, makes alternative hooking usable for more games, fixes a rare DX9 issue, has a bunch of profile fixes/updates and more.

Click here for a list of noteworthy changes

• vorpX: keys wrongly blocked in some DirectInput games (e.g. Fallout 3/NV).
• vorpX: the tracking center hotkey also ensures foreground and input focus.
• vorpX: ALT+TAB and back could occasionally confuse key state tracking.
• vorpX: fixed cursor clipping in some older games (e.g. Metro 2033).
• vorpX: headset audio device switching did not work anymore.
• vorpX: D3D9: better unhooked surfaces handling, e.g. Venetica ALT+TAB crash.
• vorpX: improved host exit, cleaner in various games and with Meta OpenXR.
• vorpControl: folder exclude handles symlinks (e.g. latest EA Desktop).
• vorpControl: minimize runtime windows option supports latest Quest Link.
• vorpControl: alternative hooking working for more games.
• Cyberpunk 2077: improved sync between mod-portion and vorpX.
• Tron 2.0: .ini changes weren’t applied anymore since a while.
• Dishonored 2: scalable HUD added.
• Dragon Age Origins: deal with GOG version 2-core lock.
• Dragon Age II: deal with GOG version 2-core lock.
• Farming Simulator 25: Fixed a Z3D issue related to vehicle mirror count.

[excel]

I can get 2077 to crash pretty reliably when using the motion aiming, sometimes it’s fine other times it crashes, enought to where I’m considering just using a gamepad or KB+M which is a shame because it actually works quite well. The game doesn’t seem to crash in VR outside of when motion controls are engaged.

(Quest 3)

[excel]

I have to keep UI scaling at 1 because any smaller setting causes the markers on enemies, loot, vehicles, gigs, etc. to become wrong and “float” around the screen. Would love if this setting could be tweaked so it only affects the relevant UI like abilities, health, minimap etc. as is the best way to play is leave UI at 1 and toggle the edge view when needing to check UI.

[excel]

Works fine with joystick however the motion steering is very bad, V will “jump” the wheel left or right a whole quarter turn or more at the slightest movement making VR steering impossible, I’ve tried various sensitivities and holding the controllers in different orientations and this issue is present in all of them. Aiming weapons with the motion controllers works pretty good!

[excel]

On a Quest 3 I just cannot get the Desktop Viewer to work, the closest I get is a black screen with a stuttering mouse cursor that I can’t control. I’ve tried turning my monitor off and turning off my HDMI soundbar, it still doesn’t work. I’ve tried it using Meta Link and SteamVR and neither function properly. Cyberpunk 2077 more or less works fine so I know the software and my setup is good, it’s just desktop viewer is bugging out.

[Detective_Yoshi]

Hey Vorpxians! Help me complete this list of 3DOF and 6DOF games!

6dof

Bioshock 1 remaster
Bioshock 2 remaster
Bioshock Infinity
Cyberpunk 2077
Dishonored 1 definitive
Fallout 3
Fallout New Vegas

3dof

Deus Ex Human
Deus Ex Mankind
Duke Nukem Forever
Kingdom come deliverance 1

[Ralf]

Both the latest vorpX 25.1.2 and the standalone mod currently are based pretty much on the same code, so whether it’s vorpx 25.1.2 or the standalone mod doesn’t matter. Also no need to update CET, just make sure to use CP 2077 2.31 and the latest vorpX OR standalone mod.

DLSS works fine, just frame generation doesn’t. Graphics settings wise start with medium settings and go from there. Aim for a high resolution over raytracing. Raytracing+DLSS is possible on high end GPUs (4090/5080/5090), on mid tier hardware you’re almost certainly better off without raytracing.

[flamefury42]

What’s the best way to optimize my game for pc build? What settings should I tweak? Also, does the licensed vorpx inject the cyberpunk 2077 from the free version of the mod? I’m just trying to make sure I’m running the latest version from vorpx. I’m up to date. I updated CET and I can get in and run the vr. I’d like to fix the black bars that I see around my screen, do i need dial up my screen resolution in game? It’s also very choppy when I play so I know i have to tweak some things back in my settings. Does Vorpx allow dlss or no? Thank you for any assistance that you can provide me.

[Ralf]

25/09/12 | vorpX 25.1.2 has been released

Another maintenance update with about a dozen noteworthy changes and fixes.

• Head tracking mouse emulation did not work anymore in desktop viewer.
• Messages shown in some games on start could become unresponsive.
• Mod component install with the virtual display failed due to an unclickable prompt.
• Some games did not exit cleanly since vorpX 25.1.0.
• Workaround for 32-bit games that use too much RAM on CPUs with many cores.
• Potential workaround for old games that assign small stack sizes (untested).
• In games with .ini and mem-scan FOV, ini-controls weren’t shown before scanning.
• Avoid more annoying virtual monitor related Quest Link self-restarts.
• Communication between the service and 32-bit vorpControl was broken.
• The service could use an entire CPU core after lock/unlock, standby/resume etc.
• Custom sync selection in the vorpX menu selected different options than shown.
• Trouble shoot data now includes all relevant log files.
• Better service handling in the installer.
• Elder Scrolls Online: HUD shaders updated (again).
• Cyberpunk 2077: mod components updated for CP2077 2.31
• As always numerous smaller fixes and optimizations.

[Ralf]

2025/09/12

A new update is available that adds support for Cyberpunk 2077 2.31 and updates the core components to match the latest vorpX version.

Download link as always in the first post of this thread.

[mvox]

I just started using the mod with everything default and noticed a big black area at the bottom of my view. Looking into it, I saw other people saying the same thing but found no solutions. It looks like it’s an issue with the aspect ratio of the quest 3, which is 1.87 (taller) compared to the other oculus headsets which are at 1.80. I changed the fScreenAspect variable in the Oculus.ini file, so no harm there. But that wasn’t enough, since it produced no change in game. I eventually found the iAspectRatioCorrection variable in the vpxCP2077.user.ini file and set that to zero, and that worked! It looked wonky because of something (maybe fov) but the bar was gone! However, as I opened up the in game vorpx menu it was set back to it’s original value of one instantly (I checked the file again). This instantly caused the black bar to come back. I haven’t been able to test further because of this (need the menu to change fov and stuff to see if this is the real fix) so there may be a better way to change the aspect ratio that I am not aware of, if so let me know.

The fix, I would imagine, would be something like one of these:
1. A config profile for the quest 3 different than the “Meta Quest Link: For Meta Headsets, eg. Quest or Oculus Rift”, that would be exclusively for the quest 3 and would make it work properly.
2. A way to turn off the automatic override of the .ini file when opening the in game vorpx menu. While I am not positive my small adjustments fixed all the issues, the main problem is that I can’t actually adjust the .ini file with current logic.
3. Some other way to change the Aspect ratio in the in game vorpx menu. I saw online references to user profiles or something in your full paid software so it may be possible in that, but not in the free cyberpunk mod.

I am aware that this particular game mod is a free mod, but it sucks to have a popular headset like this unable to be fully immersive due to the black area at the bottom taking significant space.

[djbert]

Ralf wrote:

@ garken

Your symptoms are typical for a CET version mismatch or otherwise not fully loaded mod. Double check that you really have the right CET for your game version and that it’s installed in the right place.

If you are 100% sure both conditions are met, the mod doesn’t work with 2.1 anymore. Unlikely, but not impossible. In that case you have to switch CP2077 2.3, which will work out of the box with the current mod version.

@ djbert

There is a ‘Resolution Quality’ option in the mod’s options menu (DEL key). With your 5090 you should be able to crank it up fairly high. Go has high as you consider OK performance wise with the image quality settings you prefer. No raytracing yields the best possible performance, no DLSS the best possible image sharpness. If you want raytracing you’ll probably need DLSS too though to keep the framerate high enough.

Ralf,

thank you for the input and i have it set up the way you have described. i also have the resolution quality on Ultra as well. i found the smoothness is the best with 120 FPS(set on the meta3), but i cant hold that FPS in busy scenes, and it typically drops to a stable 60 FPS in that situation. still playable but you can notice the difference between the two FPS when it shifts obviously. if i use DLSS, the FPS jumps up some but the image ghosting is a little much to my liking. I found the ghosting amount is due to the faster performing DLSS options and DLAA looks the best, but my FPS drop to 3O-40 FPS if i enable it.

random thought for you. is it possible to use 2 GPUS to process the stereo images? the right and left image on their own GPU? my understanding is the GPU is rendering both images normally, which is going to be taxing no matter what you do. so why not distribute the load? i am spit-balling that would allow some non-VR games to look even better with vorpx or other VR implementations.

[Ralf]

@ garken

Your symptoms are typical for a CET version mismatch or otherwise not fully loaded mod. Double check that you really have the right CET for your game version and that it’s installed in the right place.

If you are 100% sure both conditions are met, the mod doesn’t work with 2.1 anymore. Unlikely, but not impossible. In that case you have to switch CP2077 2.3, which will work out of the box with the current mod version.

@ djbert

There is a ‘Resolution Quality’ option in the mod’s options menu (DEL key). With your 5090 you should be able to crank it up fairly high. Go has high as you consider OK performance wise with the image quality settings you prefer. No raytracing yields the best possible performance, no DLSS the best possible image sharpness. If you want raytracing you’ll probably need DLSS too though to keep the framerate high enough.