Forum Replies Created
-
Posts
-
The issue is related to the RockStar overlay. Trying several times is your best bet if you are affected by the issue. I’ll take another look at the underlying issue shortly.
Stereo is perfectly fine per default. If you happen to have expert settings enabled and tinkered with the focal offset setting in the vorpX menu, please reset that to default. Tinkering with that setting is the only thing that can potentially cause misaligned stereo 3d as far as vorpX is concerned. The only correct value here is the default (0.0).
I’ll look into that, but no promises. There aren’t many things a VR game should absolutely never do, but binding the player to a moving cutscene camera is one of them. Nothing more uncomfortable and dizzying than that, even for VR veterans. Official VR conversions of flat games like e.g. Hellblade typically handle that in the same manner as the mod.
The system itself is ready to be fully configurable, but the configuration UI doesn’t exist yet, settings are currently hardcoded. The plan is to have the UI ready for the next larger update, just can’t promise that 100%.
Works for me. Did you maybe change the FOV manually? In some games that may break the weapon detection.
Setting the X/Y/Z option to ‘Disabled’ in the OpenTrack’s ‘Output’ settings tab will disable pos tracking.
However, if you have the same issue with an external OpenTrack instance either, i.e. vorpX not doing anything head tracking related at all, there is something severly wrong.
Whenever a new game update gets released that the mod doesn’t cover yet, it displays a message suggesting to install the latest version of the Cyber Engine Tweaks modding framework. CET has to be be updated for each Cyberpunk release, which should usually fix the mod after a Cyberpunk update.
The link below has detailed instructions:
https://wiki.redmodding.org/cyber-engine-tweaks/getting-started/installingEdit:
If you prefer to reinstall the full mod, a new build is now available. Just updating CET following the link above is enough though. Note that I only included the latest CET in the installer, the mod version itself is the same as before, so you’ll still get a version warning.
The latest DLSS version that shipped with patch 1.5 works better than before. It’s still a tradeoff that may or may not be the right thing to do depending on your individual setup, but definitely worth a shot. With a fast GPU DLSS ‘Auto’ will allow to crank the res up to the max, which looks super crisp. The high res compensates for the loss in quality in that case.
Make sure the game runs in the foreground by clicking into its window once. key presses are only registered correctly while games are running in the foreground.
Probably a conflict with some other program that also hooks into games.
If you haven’t done so already, please first try the trouble shooting options that pop up in vorpX’s ‘Attaching To…’ dialog after a minute. Install a hook helper or switching to alternative hooking can often help to resolve hooking issues without having to get to the bottom of the matter.
If that doesn’t help or you don’t see the dialog at all, you have to dig deeper. The pinned trouble shooting post on top of this sub-forum has more details on the matter.
You should be able disable only the positional part of TrackIR in the vorpX menu to deal with your problem.
With TrackIR tracking vorpX launches an instance of OpenTrack, which does the actual headset > TrackIR conversion. If you suspect something is wrong with that, you can launch and configure OpenTrack manually instead. vorpX won’t launch its own instance then.
Please reset everything to default and let VorpX handle FOV and resolution. if you happen to have disabled auto settings, please re-enable that.
If you happen to have any mods installed (especially camera mods) try without. Some mods may affect the FOV.
If you happen to have the game installed under C:\Program Files or any other folder with restricted access, make sure your normal Windows user has write access to the game’s install folder.
Under normal circumstances the FOV is calculated precisely to match the FOV of your headset. Provided vorpX can actually set the FOV there isn’t really any margin for error in case of well known engines like the CryEngine. if you still want to experiment, you can apply a +/- 20° offset on the DirectVR page of the vorpX menu. That’s not necessary though. If you let vorpX do it’s thing, everything is set up correctly.
That’s weird indeed. Might be worth to check whether you have an FPS limit set either in the game’s video options or maybe even globally in the nVidia control panel.
Under normal circumstances it shouldn’t really be a problem with your rig to get 80-90fps at low settings. Please double check whether you really set the game’s details to ‘Low’. Nothing else I can recommend unfortunately.
@ 3oxis:
Couldn’t agree more. Now is not the time, but in a few years I may have a little anecdote to share about the different momentums both mods gained.
@ Hutmacher:
Good that you mention both frame rates are the same. IIRC due to some general Pimax weirdness I set the headset sync per default to synced headset/game fps for Pimax headsets. That’s usually better for Pimax, but will definitely not work well with the alternate frame 3D method the mod uses. Try ‘prefer fps’ instead and then make sure the second number is your headset FPS (usually 90), The first one can be lower, but should ideally be 60 or higher with AFR 3D.