Forum Replies Created
-
Posts
-
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.
Please reset everything to default and then just follow the instructions that are displayed in the top/left corner of the game window. The game was extensively tested during the development of the TrackIR integration, it’s working fine for years, and there isn’t really any reason why that wouldn’t work for you.
Under normal circumstances 3D in the cinema environment works perfectly fine, just like it does in any native VR game. If something is off in the cinema environment, please try a full factory reset (config app). If afterwards you still encounter this issue, please check whether you made any canges to your WMR/OpenXR configuration that could possibly have messed things up for you.
No need for OpenTrack. vorpX handles TrackIR itself by launching an own OpenTrack instance. While you theoretically can use an an external OpenTrack, using the internal solution is preferable since that way you don’t have to care about enabling/disabling vorpX’s default head tracking.
If you already tinkered a lot with settings in the vorpX menu, please reset the profile to default and then just make sure that TrackIR is on in the game options as well as in the vorpX menu.
Please follow the instructions displayed in the top/left corner of the game window regarding TrackIR. Enabling TrackIR in the game options provides fully decoupled 1:1 head tracking.
Not sure about the other issue, sorry. The game is working fine for years under normal circumstances. If you happen to have any mods installed, please check whether the issue also occurs without. Same for any tools/utilities you may have running that hooking into DirectX. E.g. CPU/GPU tools, FPS counter and basically anything that can display overlays in games.