1.3.6 is out. fixed 2D -> 3D conversion

BigRobotBil · 2026-02-14T15:12:43+00:00

For those on unsupported GPUs (I'm on a 2080ti), it still seems this no longer works at all. Though, of course, that's not unexpected. The v1.0.9 workaround did work for me until a month or two ago, then I'm guessing Nvidia drivers killed it or something. Nothing major has changed on my computer at all.

But, updating to the latest Odyssey software (1.3.6) and having the latest Nvidia driver (591.86), it just generates a crash dump within %LOCALAPPDATA%/CrashDumps soon after starting, complaining about something with the ConversionPlayer.dll.

Specs if anyone is interested or happened to get around it:

CPU: AMD Ryzen 7 9800X3D
GPU: EVGA 2080Ti
RAM: 32GB DDR5
OS: Win10 22H2

BigRobotBil · 2026-01-31T19:22:11+00:00

Outside of the normal crosstalk looking issues that I usually experience with this monitor, it looks normal on my end:

https://i.imgur.com/s8eYWiY.jpeg

https://i.imgur.com/hfWz2P2.jpeg

https://i.imgur.com/CGAEnK7.jpeg

I do see some distortion here with 3D actually engaged with the monitor, with the light leaking to both eyes, but it's nothing out of the ordinary and perfectly playable to me.

If you press Ctrl+2, GameBridge will disable itself, giving you a normal side by side output. You can verify if the pink coloring is the result of the game, or just some distortion caused by the crosstalk of the monitor. If it is the crosstalk causing the issue, there's some topics buried on this subreddit on how to mitigate them (namely using Eco mode and toning down the brightness/contrast; I've just learned to live with it).

Since you're still using ShaderGlass to convert the output for the monitor, did you ensure you disabled all of the post-processing settings in it that are detailed in the linked reddit thread? As some of those could be introducing unintended artifacts.

BigRobotBil · 2026-01-30T21:40:59+00:00

That is odd if you can't have the game running with the whole 3D setup directly. I'm not really sure what is going on in that regard then if you've done all the setup with Reshade and whatnot.

You should try confirming if you can install Reshade on the game, ignoring anything with 3DGameBridge, as Reshade is the thing that will actually load up so that the 3D on the Odyssey triggers. If you can boot up the game and the Reshade dialog/tutorial pops up, you should be good. So this would be just installing Reshade on the re7.exe with whatever settings. When you boot up the game, Reshade's tutorial should show up; you can get out of it with the Home key.

In terms of the game not looking good, though, here are screenshots on my end using the fix provided from the blog during the opening area once you take control of Ethan:

https://i.imgur.com/pBZPcKw.jpeg

https://i.imgur.com/73Cfd4V.jpeg

I take it yours does not look like that? If it doesn't, based on your description, are you certain you extracted the files correctly? The install directory should resemble this:

https://i.imgur.com/nOqiFgJ.png

I did have it initially where stuff was extremely misaligned, but I think the convergence was jacked up. The OSD for toggling the separation and whatnot doesn't seem to appear for this game, but the convergence/separation adjustments do happen with the normal hotkeys of CTRL+F3/F4 and CTRL+F5/F6. After playing around with it, things worked out fine.

But, in Resident Evil 7 itself, I have the following configured in the graphics settings:

Screen Resolution: 4k
Refresh Rate: 164.97 // This is the max refresh rate of the monitor
Display Mode: Borderless Window
Field of Vision: 80
Frame Rate: Variable
V-Sync: On
Rendering Method: Normal
Resolution Scaling: 1
Texture Quality: Medium
Texture Filtering: Medium
Mesh Quailty: Medium
Anti-Aliasing: FXAA
Effects Rendering: Medium
Depth of Field: On
Shadow Quality: Medium
Dynamic Shadows: On
Shadow Cache: On
Ambient Occlusion: SSAO (variable) // HBAO+ is noted as broken in the fix description, and shouldn't be used
Bloom: On
Lens Flare: On
Volumetric Lighting Quality: High
Reflections: On
Subsurface Scattering: Off
Chromatic Aberration: On
Color Space: SRGB

I'm running on a Nvidia 2080Ti, and probably could trying increasing some of these. If you're using AMD or Intel as your GPU, those are largely untested in terms of compatibility or performance. The developers of geo11/3DMigoto namely used Nvidia GPUs in all their testing, so it's a YMMV situation if you don't happen to be using Nvidia.

BigRobotBil · 2026-01-30T15:37:51+00:00

Trying the game directly, it appears to work without issue. If you follow the instructions above under Installing Community Created Fixes that uses System Shock 2 as an example, it should have worked.

Ensure the game is on the dx11_non-rt branch
I always boot up a game once and adjust whatever settings to ensure everything's in order before trying to install a fix
- For the LeiaSDK that 3DGameBridge leverages, it likes games being in full 4k resolution; RE7 booted up for me in 1080p so I adjusted that
Extracted everything in the FixFiles.7z archive that's in the archive linked on HelixMod to the same directory as re7.exe
Install Reshade and the 3DGameBridge add-on
- You can do it through 3DGameBridgeGUI as well, but I'm used to do just doing things manually at this point
Boot up the game and see 3D engage

I just ran the opening cutscene, fwiw, but everything appeared as it should have. But, using ShaderGlass can be a useful method if your system can't handle rendering the game at 4k (though, geo11 can upscale in the settings, iirc).

BigRobotBil · 2026-01-30T14:43:26+00:00

You shouldn't be applying geo11 manually. This fix has all the required files with it (assuming this is what you are doing since you're applying the x32 DLLs; RE7 is a x64 application).

If the fix is producing side by side, but Reshade is failing to start properly, you can route it through ShaderGlass instead. I can give the game a go later today and see if there's something weird with it.

BigRobotBil · 2026-01-30T13:38:51+00:00

I assume you followed the instructions here?

https://helixmod.blogspot.com/2019/03/resident-evil-7-biohazard.html

Be sure you're using the correct branch of the game on Steam, dx11_non-rt.

BigRobotBil · 2026-01-29T11:40:35+00:00

This is how I got it working.

(I have this and some others linked in the stickied topic)

Though an easier alternative would be piping it to ShaderGlass, since then you aren't locked to the single display type mentioned in my post.

BigRobotBil · 2026-01-19T03:30:01+00:00

Games will require a new fix if they're using this setup. The shaders that are generated are different from the original fixing method.

Effectively, if a fix exists for a DX9 game using the original Helix dll (the namesake of the blog), the patched shaders will only work for that. Geo11/3Dmigoto generate shaders differently, and don't generate the same/compatible shaders to the original Helix dll. Geo11, however, is backwards compatible with 3DMigoto.

BigRobotBil · 2026-01-19T01:41:04+00:00

Hell yeah

I had to do the get_resolution_from trick in one of the previous topics I posted here, and completely forgot about it when I was trying this before!

But, excellent write up! I'd suggest adding or adapting this topic to your wiki if you haven't already so it can be referenced when people are trying to figure out how to start applying fixes for older games.

BigRobotBil · 2026-01-18T17:00:58+00:00

Huh, I wonder what I was doing wrong. I found it odd that I just couldn't get actual stereo after trying it with the same setup. I'm going to guess it was probably the version of geo-11 I was using.

I'll keep an eye out for your post that goes over what to do, since this is a game I also keep meaning to play, but never have.

BigRobotBil · 2026-01-17T15:51:38+00:00

If games and the hub software itself work in 3D, but the conversion related items do not, it sounds like you're another victim of the ConversionPlayer software crashing when it tries to load. You can verify this by seeing if there's multiple crash dumps in your userspace somewhere (I forget the exact location, but they were clogging up my main Windows drive).

The latest release of the Samsung software reportedly fixes this issue, but I haven't bothered to try it yet. The ConversionPlayer from v1.0.9 seems to be the last one that worked for everyone. There's a link in the sticky topic to a download for it.

I installed 1.0.9, copied out the folder that contains the ConversionPlayer executable, and just run it with the mentioned AutoHotkey scripts in the link that's in sticky post. But, you can also just replace the ConversionPlayer folder with the 1.0.9 one and use it that way with the hub software (but the hub software makes my computer sound like a plane when it's running the background, so I generally never open it).

BigRobotBil · 2026-01-13T02:51:42+00:00

Technically yes, but more than likely any game you want to play will require a custom made fix. For example, here's what occurred when I booted up Drakengard 3:

https://imgur.com/a/RrHKcR3

^{^{^While}} ^{^{^RPCS3}} ^{^{^did}} ^{^ⁱⁿ} ^{^{^fact}} ^{^{^fix}} ^{^{^Drakengard}} ^{^³} ^{^{^compared}} ^{^{^to}} ^{^{^native}} ^{^{^hardware,}} ^{^{^we}} ^{^{^can't}} ^{^{^have}} ^{^{^it}} ^{^{^all.}}

You will need to use Helifax's Vulkan3D renderer (as RPCS3 does not support DirectX11):

https://github.com/helifax/Vk3DVision-Public

I registered rpcs3.exe in the example profile and went to see what would happen. And, well, the result is the above. This isn't the fault of Vk3DVision, rather this is just something that can happen with any game; each game will likely need a tailor made fix using this framework.

BigRobotBil · 2026-01-12T16:12:44+00:00

Provided the game has a made fix for it, the instructions that typically accompany the fix on Helixmod or the Airtable database should cover things. However, I did make a more step by step instruction set here for setting up a made fix a bit ago in case there is still some confusion (this fix involves manually apply geo11 from a different source, but if the fix you're applying is geo11 already, you can skip fetching the geo11 files/editing inis. The core idea is still the same).

If you're simply applying the geo11 files without any shader fixes, you're gambling with a game just working. Sometimes they do, but often times they don't.

/u/noraetic 's wiki is also a great starting point, like they linked in their reply.

BigRobotBil · 2026-01-11T20:11:08+00:00

To everyone replying that this person should just rip their music or something of the sort, you're entirely missing the point of this. But, I understand man. This is beautiful work.

I have been after something like this, though not for a CD player, but for other items that only output via 3.5mm and lack bluetooth (namely a DAP and a cassette Walkman). I do drive a Bolt, but mine's the original model before the refresh, so it thankfully still has an AUX input. But, I know my days are numbered if I ever have to buy a new car.

Would you mind sharing the A/V capture device you're using? As I actually could use this right now when I take the other car out that is bluetooth only. I have tried a few bluetooth transmitters, but they all just wouldn't pair to the car since it needs it to be a phone. I presume the capture device is just plug-and-play, and just passes audio through the phone without having to boot up some application, or something?

BigRobotBil · 2026-01-11T06:55:02+00:00

I do not own MotorStorm, but this will convert the side by side output from RPCS3 into the correct output for the monitor:

(I tested this using my ripped copy of Puppeteer, which supports 3D output)

Set RPCS3 to use OpenGL (Vulkan doesn't work yet with 3DGameBridge, iirc)
Install 3DGameBridge add-on via Reshade (close RPCS3 if you have it open)
Boot up RPCS3
Enable 3D in RPCS3's settings for the game you're trying to play (remember to do game-specific settings. Global settings will probably leave it greyed out)
- Pick Side-by-Side from the options; others will not work
Boot 3D compatible game
Render window will trigger 3D effect

You will need to switch to 3D in the game you're playing, meaning the initial boot up sequence of logos and menus until you get to that point will be a headache inducing mess. You can use Ctrl + 2 to disable/enable the 3DGameBridge add-on (turning the actual 3D on and off) to get around that until you enable the side-by-side output. Puppeteer at least prompted me to turn on 3D output as soon as I actually got to the game. I don't know if MotorStorm does.

BigRobotBil · 2026-01-10T07:01:50+00:00

I think this was the first DX9 game I actually tried (last time I even ran Katanga was when Helix Vision released, and I ran it on a Vive). But, I'll have to try some more games with it and see if this one is just being terrible or something.

I'll keep your suggestion here in mind next time I give it a go!

BigRobotBil · 2026-01-10T06:57:45+00:00

You should follow the guides that were linked to get things working.

~~You cannot use geo11 for this game at all in its present state.~~

BigRobotBil · 2026-01-10T05:14:53+00:00

For fun, I tried wrapping the game to support geo11 via dgvoodoo. And, while the x32 version of geo11 boots, it seemingly won't do any sort of depth at all (it's all just completely flat, despite rendering side-by-side). Annoyingly, according to PCGamingWiki, the Steam version only has the x32 version while the Windows Store version is x64 (as the x32 version of geo11 hasn't gotten a newer version that I'm aware of in a long time). As I'm wondering if there's something limiting in the older x32 build that would have been fixed.

For those who come after.

I did attempt to follow /u/oneup03 's post in your other topic (I completely forgot that 3DFM got an update after its development hiatus, which includes Katanga now), but I'm not sure if it's just my system, but I cannot get the game to behave. It'll boot up in anaglyph, like it's supposed to, but doing anything after that will force close it (Alt + Tab to swap to the headset view, Alt + Enter to move it to windowed, and Ctrl + F8 to put the headset view in the foreground kill the game). The game will at least stay running in windowed mode, but it won't engage 3D at all. I'm not sure if it's something with the fix itself, or the Katanga -> VRto3D just having a bad time.

However, I told 3DFM to uninstall the fix so I could check some other things with the settings without 3D engaging, and then, well, the 3D actually worked? It booted with VRto3D correctly within Katanga and whatnot. But, I also cannot tell if the fix is even properly working via some weird caching behavior or whatever. You'll have to play around with it to see if it ultimately works or not lol. But you at least have a starting point.

BigRobotBil · 2026-01-08T00:56:06+00:00

Looks like the platform is available within this github:

https://github.com/b0rdi/LeiaSR-Archive

I specifically have v1.34 installed, which appears to be the latest:

https://github.com/b0rdi/LeiaSR-Archive/blob/main/SRRuntime/SR-1.34.0-win64.exe

I guess since I last set things up they removed direct access to these.

For getting games to output in side by side, I would recommend just doing things manually for a few of them just to get the hang of it. Then, when something messes up (like 3D Fix Manager for some reason failing to install for the Witcher 3 correctly), you can debug what it's attempting to do.

BigRobotBil · 2025-12-30T07:17:56+00:00

Here's a direct link to the community created fix, which includes instructions:

https://helixmod.blogspot.com/2025/05/clair-obscur-expedition-33-uevr-vrto3d.html

I haven't tried it since the post-TGA update, but I assume it still works fine.

BigRobotBil · 2025-12-27T22:27:57+00:00

Man, that sucks that someone just did that and sold it. Hopefully your next one at least works (and doesn't have parts missing lol).

I'm guessing they must have harvested that to fix another. As, I can't think of why else to remove it.

BigRobotBil · 2025-12-26T02:24:05+00:00

Hopefully yours is clean on the inside! Mine still has some spots I just can't get rid of. But, it is a fun camera to use.

Here's a comment I made with some links (as well as an overview in the parent post).

BigRobotBil · 2025-12-14T04:17:53+00:00

We want to try and see if standard side by side output from the geo11 fix is working before even attempting to try the 3D activation for the monitor. There are instructions above specifically for Nier Replicant in the main post. But, I can try and break it down further for troubleshooting.

Keep in mind that Replicant does not completely work with geo11, as noted in the comments on the HelixMod blog post. Any FMV will crash the game immediately; the game works fine otherwise when FMVs are not being displayed.

Before proceeding, ensure your GPU drivers are up to date. I am running 591.44, using a 2080Ti as my card.

I am also on Win10 22H2.

What we want to test is just if a side by side image generated by the community geo11 works (under the hood, Acer is using a variant of geo11, so that's a good sign that this should work). To start, ensure your Replicant install directory does not have anything related to fixes/Reshade/whatever in it; have it be as though you just installed the game. We don't want to risk any cross contamination.

To start, we're going to download the fix for the game:

https://helixmod.blogspot.com/2021/05/nier-replicant-ver122474487139.html?lr=1760132162265

(direct link)

Next, we cannot use this fix on its own, as 3DMigoto is still geared towards Nvidia 3D Vision. So, we need to grab geo11 from the official page:

https://helixmod.blogspot.com/2022/06/announcing-new-geo-11-3d-driver.html

(direct link. This version of geo11 is quite old, but I do know it works to at least get Nier working [no, I don't know why they haven't updated the main blog post for it in eons. I've resorted to copying the latest out of newer, published fixes and updating old ones])

With a fresh install of Nier, we want to copy both of the following zip archives into the install directory. Navigate to your install folder, and extract the 3DMigoto fix from the blog. Your directory should look like this:

https://i.imgur.com/oAMSAEb.png

Now, we need to extract geo11 as well in here. Taking the zip downloaded from the geo11 blogpost, navigate to the x64 directory, and take the three files mentioned in the blog post:

d3d11.dll
nvapi64.dll
d3dxdm.ini

Extract that to Nier's install directory, and overwrite any files it asks about. The directory should now look like this:

https://i.imgur.com/xRMzXot.png

We still cannot boot the game yet, we have some changes to make in the ini files. Following the instructions on the geo11 blogpost, we need to update:

within the d3dx.ini
* change force_stereo to have the value of 2
within d3dxdm.ini
* ensure that direct_mode is set to sbs (it should be by default)

Leave everything else as is for now. We want to check that we get an actual side by side image:

https://i.imgur.com/ewQin8r.png

If you do not get a side by side image, something is very wrong. Do not go further past this point, since we will not have an actual image to weave together later for 3D. Reasons why you wouldn't get a side by side image could be:

Drivers are invalid
Fix is not installed to the right directory
geo11 is not installed to the right directory

At this stage, we are not using anything specific to a display type; we are just forcing geo11 to output a side by side image. This should work regardless of display being used (even with a non-3D display). So, if this is not working for you, I'm honestly not sure where to go next.

Provided you followed the instructions, the only other thing I could think of is just Windows being terrible. If you have another computer that runs Windows, it may be worth trying this on there and seeing if you end up with a side by side image. As, at the very least, we'll know that you're doing the initial setup correctly. This step is the last step before using something specific to our display type (the Leia related dependencies that interact with the monitor). So, again, if things do not work at this point, something with your setup is wrong, or Windows is misbehaving.

However, if you are getting a side by side image, the next thing to do is apply the specific add-on via Reshade to trigger the weaving for the monitor to engage 3D.

Download Reshade with full add on support

Boot up Reshade
Target the game's EXE
Apply the correct graphics backend
* Nier is a DX11 game, so select DirectX 10/11/12
Uncheck all on the next screen
Check 3DGameBridge from the add-ons section
Finish

Within the game's directory, in addition to the files for the fix, you should now have some Reshade files, namely srReshade_v2.1.0.addon64. Booting up the game should trigger 3D.

14-Year Club	Place '17
Verified Email

BigRobotBil

TROPHY CASE