geo-11 Borderlands 3 (STEAM VERSION)

[EpsilonLyrae]

Didn't boot for me at first. Look to a later post in this thread for how to get the fix running again.
Relevant specs:

Windows 10 21H2 (latest updates installed)
RTX 3070 GPU, 516.40 drivers + 3D vision driver installed for DX9 compatibility (was installed by Helixvision)
Primary display: 4k 120hz (also tried 60hz), Gsync Off
VR Headset connected, but off (Valve Index)
Overlay software present (Discord, Steam). I need steam to launch the game, but whether or not Discord is open or its overlay on / off, the results don't change. (Another game I have tested, FFXV, launches and renders in stereoscopic 3d as expected under steam. I do not believe this crash is affected by the Steam overlay, but my results in FFXV are for another topic.)

Game launches in default installed state, no errors. Used "verify integrity" function of steam to validate the install. Game was configured to recommended settings per the 3d fix (Full screen = On, AA = FXAA or Off, I went with FXAA)

Game launches with 3dfix from this link installed: https://helixmod.blogspot.com/2019/10/b ... nds-3.html . Booting the game shows the Help interface that is used by the fix. No 3d is shown (expected behavior) as no 3d driver or device is in use.

Game launches with a default geo-11 install (changing to direct_mode = sbs) , and can render the game in sbs mode without crashing, hanging, stalling, etc. Can play and progress in the game, albeit with visual errors as the game-specific fixes are not present in this state.

Installed in the recommended order: Game specific fix installed FIRST, then contents of the x64 folder of geo-11 copied and pasted on top of the same directory, with the exception of d3dx.ini. Contents of d3dx.ini were edited to reflect recommended settings (force_stereo = 2), d3dxdm was edited to change direct_mode = sbs. The game will crash with one of two errors:

(direct_mode = sbs)

Fatal error!

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION 0x0000000000000000

0x0000000000000000 UnknownFunction []
0x00007ffcb26f1842 d3d11.dll!UnknownFunction []
0x00007ffcb26f45e8 d3d11.dll!UnknownFunction []
0x00007ffcb26ea5b1 d3d11.dll!UnknownFunction []
0x00007ffcb26ee335 d3d11.dll!UnknownFunction []
0x00007ffcb26fe656 d3d11.dll!UnknownFunction []
0x00007ffcb2702968 d3d11.dll!UnknownFunction []
0x00007ffcb26f9b46 d3d11.dll!UnknownFunction []
0x00007ffcb27dc5ed d3d11.dll!UnknownFunction []
0x00007ffcb27d28cd d3d11.dll!UnknownFunction []
0x00007ffcd2548e33 gameoverlayrenderer64.dll!UnknownFunction []
0x00007ff6bc2752e8 Borderlands3.exe!UnknownFunction []
0x00007ff6bc27d0a8 Borderlands3.exe!UnknownFunction []
0x00007ff6bc7050b2 Borderlands3.exe!UnknownFunction []
0x00007ff6bc70609b Borderlands3.exe!UnknownFunction []
0x00007ff6bc706017 Borderlands3.exe!UnknownFunction []
0x00007ff6bc703b16 Borderlands3.exe!UnknownFunction []
0x00007ff6bc8f28af Borderlands3.exe!UnknownFunction []
0x00007ff6bc8f49d1 Borderlands3.exe!UnknownFunction []
0x00007ff6bbdd78f6 Borderlands3.exe!UnknownFunction []
0x00007ff6bbdd7a03 Borderlands3.exe!UnknownFunction []
0x00007ff6bc726a22 Borderlands3.exe!UnknownFunction []
0x00007ff6bc726aa8 Borderlands3.exe!UnknownFunction []
0x00007ff6bbef2b9b Borderlands3.exe!UnknownFunction []
0x00007ff6bbef05d7 Borderlands3.exe!UnknownFunction []
0x00007ffd166c7034 KERNEL32.DLL!UnknownFunction []
0x00007ffd17282651 ntdll.dll!UnknownFunction []

Crash in runnable thread RenderThread 0

(direct_mode = nvidia_dx9). Stereostopic 3d ON or OFF in the Nvidia driver doesn't seem to meaningfully change this error.

LowLevelFatalError [File:Unknown] [Line: 251]
D3DRHI->GetFactory()->CreateSwapChain(DXGIDevice, &SwapChainDesc, SwapChain.GetInitReference()) failed
at t:\OAK-PATCHWIN640-WIN64\main\Engine\Source\Runtime\Windows\D3D11RHI\Private\Windows\WindowsD3D11Viewport.cpp:156
with error 975EEFA0


0x00007ffd14c74fd9 KERNELBASE.dll!UnknownFunction []
0x00007ff6bbee80b4 Borderlands3.exe!UnknownFunction []
0x00007ff6bbeb7ffc Borderlands3.exe!UnknownFunction []
0x00007ff6bbe6344d Borderlands3.exe!UnknownFunction []
0x00007ff6bc28615b Borderlands3.exe!UnknownFunction []
0x00007ff6bc2654f6 Borderlands3.exe!UnknownFunction []
0x00007ff6bc27c0ac Borderlands3.exe!UnknownFunction []
0x00007ff6bc8ea44e Borderlands3.exe!UnknownFunction []
0x00007ff6bc901125 Borderlands3.exe!UnknownFunction []
0x00007ff6bc09d601 Borderlands3.exe!UnknownFunction []
0x00007ff6bcc8a6b1 Borderlands3.exe!UnknownFunction []
0x00007ff6bc8534f3 Borderlands3.exe!UnknownFunction []
0x00007ff6bac88ccf Borderlands3.exe!UnknownFunction []
0x00007ff6bac820fc Borderlands3.exe!UnknownFunction []
0x00007ff6bac8232a Borderlands3.exe!UnknownFunction []
0x00007ff6bac8b9c9 Borderlands3.exe!UnknownFunction []
0x00007ff6be61d94e Borderlands3.exe!UnknownFunction []
0x00007ffd166c7034 KERNEL32.DLL!UnknownFunction []
0x00007ffd17282651 ntdll.dll!UnknownFunction []

Attempts at troubleshooting:
*Enabling or disabling stereoscopic 3d in Nvidia control panel (no effect)
*Different direct_mode settings (nvidia_dx11 [shouldn't work on my config], nvidia_dx9 [still crashes] sbs [still crashes])
*Deleting d3dcompiler_46.dll (game fix includes it, but geo-11 uses d3dcompiler_47.dll). Still crashed. Made a copy of d3dcompiler_47.dll from geo-11 and renamed it to d3dcompiler_46, crashes with the same error.
*Commenting and uncommenting elements of the original d3dx.ini from the game fix. Commenting out include = ShaderFixes\help.ini allows the game to boot, but because the contents of help.ini defines variables and configures shaders, the fix is broken. Commenting out include = ShaderFixes\BL3_fix.ini but allowing help.ini to run still resulted in a crash. Having help.ini disabled is the closest I've come to having BL3 launch with the fix installed + the geo-11 patched dll files in the game directory.

Happy to try other methods of troubleshooting, or provide requested logs. Rolling back to recommended drivers (425.x, 452.x) is not an option for me due to my installed GPU. I've tested at least one other game that works (again, that's for another thread), the issues here seem specific to the combination of my system, geo-11, the BL3 fix, and the game itself.

[3DNovice]

...

[bo3bber]

This line:

Code: Select all

0x00007ffcd2548e33 gameoverlayrenderer64.dll!UnknownFunction []

Is from Steam Overlay, and suggests that it might be causing the crash. Try deleting or moving that file in Steam folder. Also worth trying to disable it, but long time ago we found disabling just hid it, not actual stopped loading it.

Also try upscaling=0 as for dx9 output we need fullscreen in order to see 3D.

[EpsilonLyrae]

I closed steam so that the relevant DLLs would no longer be in use. Then, I launched it again, waited for Steam to fix itself (it notices the dll files are gone and replaces them), then before I launch any games (which would initialize the overlay executable and relevant dll files), I deleted both gameoverlay.dll and gameoverlay64.dll.

direct_mode = sbs gives this result:

Fatal error!

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION 0x0000000000000005

0x0000000000000005 UnknownFunction []
0x00007ffae3451842 d3d11.dll!UnknownFunction []
0x00007ffae34545e8 d3d11.dll!UnknownFunction []
0x00007ffae344a5b1 d3d11.dll!UnknownFunction []
0x00007ffae344e335 d3d11.dll!UnknownFunction []
0x00007ffae345e656 d3d11.dll!UnknownFunction []
0x00007ffae3462968 d3d11.dll!UnknownFunction []
0x00007ffae3459b46 d3d11.dll!UnknownFunction []
0x00007ffae353c5ed d3d11.dll!UnknownFunction []
0x00007ffae35328cd d3d11.dll!UnknownFunction []
0x00007ff687ae52e8 Borderlands3.exe!UnknownFunction []
0x00007ff687aed0a8 Borderlands3.exe!UnknownFunction []
0x00007ff687f750b2 Borderlands3.exe!UnknownFunction []
0x00007ff687f7609b Borderlands3.exe!UnknownFunction []
0x00007ff687f76017 Borderlands3.exe!UnknownFunction []
0x00007ff687f73b16 Borderlands3.exe!UnknownFunction []
0x00007ff6881628af Borderlands3.exe!UnknownFunction []
0x00007ff6881649d1 Borderlands3.exe!UnknownFunction []
0x00007ff6876478f6 Borderlands3.exe!UnknownFunction []
0x00007ff687647a03 Borderlands3.exe!UnknownFunction []
0x00007ff687f96a22 Borderlands3.exe!UnknownFunction []
0x00007ff687f96aa8 Borderlands3.exe!UnknownFunction []
0x00007ff687762b9b Borderlands3.exe!UnknownFunction []
0x00007ff6877605d7 Borderlands3.exe!UnknownFunction []
0x00007ffb5c747034 KERNEL32.DLL!UnknownFunction []
0x00007ffb5e362651 ntdll.dll!UnknownFunction []

Crash in runnable thread RenderThread 0

The steam overlay is no longer listed in the report, but the game is still crashing.

Upscale settings are off or commented out as appropriate.

I changed to direct_mode = dx9.

Fatal error!

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION 0x00000730b8418007

0x00000730b8418007 UnknownFunction []
0x00007ffae3451842 d3d11.dll!UnknownFunction []
0x00007ffae34545e8 d3d11.dll!UnknownFunction []
0x00007ffae344a5b1 d3d11.dll!UnknownFunction []
0x00007ffae344e335 d3d11.dll!UnknownFunction []
0x00007ffae345e656 d3d11.dll!UnknownFunction []
0x00007ffae3462968 d3d11.dll!UnknownFunction []
0x00007ffae3459b46 d3d11.dll!UnknownFunction []
0x00007ffae353cdea d3d11.dll!UnknownFunction []
0x00007ffae353afa7 d3d11.dll!UnknownFunction []
0x00007ff687ae52e8 Borderlands3.exe!UnknownFunction []
0x00007ff687aed0a8 Borderlands3.exe!UnknownFunction []
0x00007ff687f750b2 Borderlands3.exe!UnknownFunction []
0x00007ff687f7609b Borderlands3.exe!UnknownFunction []
0x00007ff687f76017 Borderlands3.exe!UnknownFunction []
0x00007ff687f73b16 Borderlands3.exe!UnknownFunction []
0x00007ff6881628af Borderlands3.exe!UnknownFunction []
0x00007ff6881649d1 Borderlands3.exe!UnknownFunction []
0x00007ff6876478f6 Borderlands3.exe!UnknownFunction []
0x00007ff687647a03 Borderlands3.exe!UnknownFunction []
0x00007ff687f96a22 Borderlands3.exe!UnknownFunction []
0x00007ff687f96aa8 Borderlands3.exe!UnknownFunction []
0x00007ff687762b9b Borderlands3.exe!UnknownFunction []
0x00007ff6877605d7 Borderlands3.exe!UnknownFunction []
0x00007ffb5c747034 KERNEL32.DLL!UnknownFunction []
0x00007ffb5e362651 ntdll.dll!UnknownFunction []

Crash in runnable thread RenderThread

Both no longer report on the steam overlay. It's plausible that I am overlooking a change in the ini files somewhere, but I've successfully launched FFXV (steam version, with overlay enabled).

As mentioned in the original post, the game will launch with the "default" geo-11 configuration (rendering in SBS 3d with none of the game fixes applied), the game will also launch with the fix installed, but the combination of the fix and geo-11 (using the same process I've used for FFXIV and FFXV) results in an error.

[EpsilonLyrae]

Do you by chance have the in-game dx12 option selected? The fix is dx11 only.

Perhaps you might find a useful tidbit in the Borderlands 3 fix thread
viewtopic.php?t=23285

Double checked the DirectX settings to be sure, yep, in DX11

[EpsilonLyrae]

Out of curiosity, I tested another UE4 engine game I own, Dragon Ball FighterZ. I don't feel comfortable enough making a thread on it since I did barebones testing to see if it launched at all, but..

Same specs / configuration, same install process as any other fix I tried (install game, make sure it launches, install game fix, follow instructions in DBFZ fix to launch game without easy anti-cheat enabled, test that the game loads this way, then install geo-11 on top and test again, with force_stereo = 2 and direct_mode = sbs), and DBFZ launched and rendered a side by side image on screen, the same way FFXV and FFXIV do. Can't comment on the quality of the fix or how it appears since I didn't put my headset on, but it does, at a glance, appear to be working. It looks like the UE4 engine used by BL3 is customized to some degree (whereas DBFZ is more likely to be using an out of the box config...), but it's probably the closest game I have to check.

[bo3bber]

Yeah, not sure what's happening there. Set the flags in d3dx.ini to calls=1, debug=1, unbuffered=1, and that will make a debug log I can look at. It does look like it is crashing geo-11, as opposed to the UE4 crash that is fixed by the Schwing hack.

[EpsilonLyrae]

Yeah, not sure what's happening there. Set the flags in d3dx.ini to calls=1, debug=1, unbuffered=1, and that will make a debug log I can look at. It does look like it is crashing geo-11, as opposed to the UE4 crash that is fixed by the Schwing hack.

Sure. Here's d3d11_log.txt and nvapi_log.txt

I took a pass to disable as many PC programs and services as-is practical to reduce the odds that weird overlay or drivers might be causing an issue here- Not a complete one, mind you, since geo-11 has worked on at least 3 other games for me even with most everything I normally have open / in use day to day. I went ahead and left the steam game overlay in there, I think we've established that it isn't the cause of the problem.

[Lysander]

Anyone tried this on a 2080Ti via dx11 to see if the drops are eliminated? If not, I'll check it

[bo3bber]

Code: Select all

HackerDeviceDirectMode::GetImmediateContext(class HackerDeviceDirectMode@000001BCD4C28140) called with:00000081B109E220
WARNING: mHackerContext 000001BCD93E34B0 found to be wrapping 000001BC00000000 instead of 000001BCD30CE530 at HackerDevice::GetImmediateContext!
  returns handle = 000001BCD93E34B0
HackerBuffer::GetType(class HackerBuffer@000001BCD31AD350) 

OK, yeah, that doesn't seem like a good thing. I'll need to look into this more closely, but that's the crash. If the objects are somehow mixed up, that will call routines that don't exist.

[EpsilonLyrae]

Glad I could report something useful. If you want logs of anything on a system level (dxdiag?) or whatever else, or want me to test something, let me know.

[Lysander]

[obsolete post]

[Lysander]

ok, figured it out. The offending files seem to be 2 small text files: help.txt and help_short.txt. Not sure why geo-11 has a problem with them but hopefully that gives Dave some direction

So, apply the original fix, then geo-11, remove the 2 files from the ShaderFixes folder and all should be good. Getting constant 60 in battles on HIGH, at least throughout the beginning

Using Epic store version.

Borderlands3003_100 (2).jpg

Borderlands3002_100 (2).jpg

Borderlands3001_100 (2).jpg

[Lysander]

sorry, dupe post

[EpsilonLyrae]

ok, figured it out. The offending files seem to be 2 small text files: help.txt and help_short.txt. Not sure why geo-11 has a problem with them but hopefully that gives Dave some direction

So, apply the original fix, then geo-11, remove the 2 files from the ShaderFixes folder and all should be good. Getting constant 60 in battles on HIGH, at least throughout the beginning

OK- This inspired me to re-test.

I re-downloaded the game, and installed using my usual process (same process as in the OP)

Then I dove into the shaderfixes folder and renamed those two text files to something else. This seems to have been the problem- Something in geo-11 is struggling on that specific element of the fix. I had my usual that I experience with most games (takes a few tries to launch without a crash, sometimes the emitter doesn't initialize, UE4 games often crash when you try to exit them), but persistence works through most of that.

I am unable to take stereo screenshots using the 3d vision hotkey on my driver setup- I'm not sure if this is a consequence of the GPU I'm using (an RTX 3070), the driver I'm on (516.59), or both. It makes me wonder if other users are having issues with taking screenshots if they're not on a native 3d vision compatible hardware / driver stack.

I didn't have much time to test tonight, but I did at least beat Shiv. Only noticed a couple of things.

The "disable white outline" key only partially removed the white outline around FL4k's beast pet. A weapon that had a screen on it to display clip / ammo counts directly on the gun itself projected light in a manner that resulted in uncomfortable stereo fighting (seems to be a common issue I've experienced with UE4 games that have older fixes). But, the auto-depth function for the crosshair still worked and most other effects you can see in that area of the game still rendered correctly. Minus the light projection error on the gun, this ended up being one of the best looking and seemingly most well-suited to 3d vision games I've played so far, perhaps owed to the art direction of the game and simplistic HUD that generally doesn't overlap with the playable space of the game.

Elements of the fix that display text still seemed to work OK- for example, pressing caps lock to toggle a special high convergence mode generates a message in the lower left side of the screen to tell you that it's on. HUD Depth keys will report what percentage / preset you're on as you cycle through the available options using the appropriate keys. It's specifically something in help.ini and the way it's trying to take the text from help.txt and help_short.txt that's causing the problem.