Forum Replies Created
-
Posts
-
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/installingWorks fine for me. Just checked with a Reverb G2.
Please double check whether Windows Mixed Reality is your OpenXR runtime. The WMR portal will complain on launch if it’s not. Unfortunately SteamVR tries to make itself the system’s OpenXR runtime on each launch, which is complete nonsense for Oculus and WMR devices since both have native OpenXR support.
If you have an RTX card, also make sure that all raytracing is disabled in the game options. Otherwise the game would crash when loading a race. Not sure whether raytracing was added later or whether I missed that when doing the profile.
Last but not least: if for some reason you have installed the WMR developer preview runtime, try switching back to the release version.
The updated profile is now online. You can download it on the Cloud Profiles page of the config app.
vorpX can try to force games to a specific monitor. You can configure that in the config app on the General page. Not 100% guaranteed to work, but worth a shot. If that doesn’t work, you have to make the projector a mirror of your primary screen (or the actual primary screen).
There is an SBS 3D output option since quite a while, you can select it in the config app instead of one of the VR output options. Keep in mind though that vorpX was primarily built for VR and VR will stay its main and only focus.
I never tried the game, so I can’t really say anything specific.
The only thing that *might* be useful is checking whether the hook helper was installed as D3D9 hook helper. Since the FSX engine supports both DX9 and DX10 the hook helper might have been installed as DX10+ helper. To check that browse to the game’s install folder and if it contains a file named dxgi.dll (that would be the hook helper acting as DX10+ helper), simply rename it to d3d9.dll.
Also make sure that nothing else is running that also hooks into DirectX, basically anything that can display overlays in games.
Probably just one shader that has to be defined as HUD/menu-shader. Every once in a while a game update breaks that particular shader definition for some reason.
Provided that’s the issue as a workaround you can simply disable 3D in the vorpX menu until the actual game starts.
If you aren’t afraid of tinkering with the shader authoring tool, you could probably fix the issue yourself. You can enable it by checking ‘Show Expert Settings’ and then ‘Enable G3D Shader Authoring’ on the General page of the config app.
Either way I’ll take a look at it myself and upload an updated profile tomorrow.
The ‘G3D FOV Enhancement’ option is unfortunately fairly useless in many modern games since it usually breaks too many things. There seems to be a mod though that let’s you set a higher FOV, better use that instead.
https://www.nexusmods.com/ghostwiretokyo/mods/12
Caveat: from the looks of it it’s an .exe replacement, so the mod will require an update after each game update.
I understand your frustration, unfortunately as far as TrackIR is concerned there isn’t really anything else I can suggest besides following the instructions. That’s all that has to be done under normal circumstances, it’s working that way for years.
If for some reason your setup doesn’t work as intended with TrackIR, you can however disable TrackIR in the game as well as in vorpX and play with mouse emulation tracking instead.
If mapping to gamepad controls behaves odd, try mapping to keyboard/mouse instead. Many games can’t handle simultaneous mouse/gamepad input. Whenever vorpX has to emulate a mouse for head tracking in such a game the only way to make VR controllers work is having them emulate kb/mouse. That’s also why kb/mouse is the default option in most cases.
If you have downloaded an older custom profile from the cloud, please do a full factory reset in the config app (trouble shooting page). The game works out of the box without having to apply any user profile.
If it still crashes with the official profile, please check whether you maybe have an external tool running that hooks into games and could potentially cause a conflict. Pretty much anything that can display overlays over games could be a candidate. The best way to troubleshoot this would be to disable everything you have running in the background.
Not sure if that helps, but the FSX profile is DX9 only, so you would have to make sure to launch Combat Flight Sim 3 in DX9 mode.
The profile that comes with vorpX is OpenGL only. Versions prior to patch 1.29 supported OpenGL by calling ‘wc3.exe’ with the ‘-opengl’ command line option (without the quotes). For 1.29 and above that apparently was changed to ‘-graphicsapi OpenGL2’.
Caveat: I’m not sure wether the profile still works with 1.29+.
BTW: IIRC they also changed rge D3D renderer from D3D8 to D3D9 at some point. No promises, but I’ll check whether maybe a D3D9 profile is possible and let you know in a few days.
Shadows and other effects in modern games are often implemented with deferred rendering techniques that aren’t easily stereoizable. Past 3D drivers like Tridef often had the same glitches (or worse) in such cases. Fallout 4 however should be largely fine though except for some *very* minor issues with character shadows occasionally.
In general make sure to keep the 3D-Strength at realistic levels (in official profiles that means 1.0). With realistic 3D these glitches usually aren’t too bad, only with exaggerated ‘doll-house’ 3D they become too annoying to be bearable.