game crash nov2025 v

[cayuse27]

my game is crashing when i try to start any level, even with no plugins in v 1.8.5
here is an example crash log:

2025-11-28 17:54:32
Myth II Build 471b running under Modern Windows 10.000000 ----------------------------------------------
Loading poweruser.txt... not found.
DEBUG: Updating monolithic tag cache:
Initial count: 17
Number removed: 0
Number added: 0
New count: 17
DEBUG: Adding 13 monolithic tags:
small install
medium install
large install
international small install
international large install
Patch 1.2
Patch 1.3
Patch 1.4
Patch 1.5
bagrada metaserver
Patch 1.8 Interface
Myth II Interface (800x600)
Patch Templates
Scanning for software devices...
Found 1 to use
Scanning for Direct3D devices...
Found 1 to use
Scanning for DirectX 11 devices...
Found adapter: NVIDIA GeForce RTX 4080
Found 1 to use
Scanning for 3Dfx devices...
Found 0 to use
Scanning for OpenGL devices...
Found 1 to use
NVIDIA GeForce RTX 4080/PCIe/SSE2 | NVIDIA Corporation | OpenGL 4.6
Initializing sound with DirectSound...
Initialized for DirectSound3D using COM
DirectSound initialized successfully.
Warning: Unable to find cutscene 'prologue.smk'.
Running DirectX 11 at 1920 x 1080 (VSync ON)
Starting mesh "Salvation"...
Using 1.8.5 gameplay...
Myth Crashed: EXCEPTION_ACCESS_VIOLATION
Attempting Stack Trace...
0 0x004b3e79 _build_mesh_tile_texture + 0x0397 (myth2code\render\render_maps.c:1000)
1 0x0f9706d0 ? + 0x0000 (?:0)
Stack Trace Complete
Recording Buffers Flushed
Saved Recording To 'Crash- 2025-11-28 17.54.46'

[Jon God]

Bizarre, are your drivers up to date? Did you try a different renderer? Trying to narrow down what the issue is.

[cayuse27]

it happens (same error) with DX11 or OGL renderers, with software or D3d it doesn't happen I have nvidia 4070, yes the drivers are up to date. Win11, also up to date.

The game crashes and shows an error as soon as the map loads, after about 2 seconds, it does show the map and players etc, and then crashes.

What's really interesting, is the crashrec actually plays fine, but there are no commands etc, it doesn't run long enough to even select the characters and do anything.

I'm really surprised the playback plays that's odd as heck.

Just to be sure, i installed 184 and 183 and got the same error.

[cayuse27]

ok, i was able to narrow it down a lttle bit, all of the settings in graphics can be on or off, but if either VSync or Max FPS is turned on then i get the crash, other settings don't matter, i can use hires textures and sprites (with plugins etc) but not those two settings.

[Melekor]

The stack trace points to _build_mesh_tile_texture, which does a large stack allocation, so my first theory is stack either overflow, or some kind of interaction with new stack security features in win11. Since the crash is pretty reproducible, can you confirm that _build_mesh_tile_texture is in the trace every time?

Based on this theory, Gemini 3 gave the following troubleshooting steps you could try:

1. Use a tool like CFF Explorer to edit your exe to have a larger SizeOfStackReserve. Try 00200000 instead of the default 00100000. (In CFF explorer, go to Nt Headers > Optional Header)

2. Try Compatibility Mode: Right-click the .exe -> Properties -> Compatibility -> Run this program in compatibility mode for Windows 7 (or XP).

3. Disable Exploit Protection: Go to Windows Security -> App & browser control -> Exploit protection -> Program settings. Add the game exe and disable "Hardware-enforced Stack Protection" and "Data Execution Prevention (DEP)".

Let us know what you tried and if it made a difference.

[Melekor]

You can also try disabling NVidia overlays, windows game bar, etc if you have any of these.

[cayuse27]

I disabled overlays, and added to the stack reserve, but it has the same crash.

grep _build_mesh *txt
myth_crashlog- 2025-11-29 11.32.56.txt: 0 0x004b3e79 _build_mesh_tile_texture + 0x0397 (myth2code\render\render_maps.c:1000)
myth_crashlog- 2025-11-29 11.36.58.txt: 0 0x004b3e79 _build_mesh_tile_texture + 0x0397 (myth2code\render\render_maps.c:1000)
myth_crashlog- 2025-11-29 11.37.11.txt: 0 0x004b3e79 _build_mesh_tile_texture + 0x0397 (myth2code\render\render_maps.c:1000)
myth_crashlog- 2025-11-29 11.42.55.txt: 0 0x004b3e79 _build_mesh_tile_texture + 0x0397 (myth2code\render\render_maps.c:1000)
myth_crashlog- 2025-11-29 11.50.55.txt: 0 0x004b3e79 _build_mesh_tile_texture + 0x0397 (myth2code\render\render_maps.c:1000)
myth_crashlog- 2025-11-29 11.52.00.txt: 0 0x004b3e79 _build_mesh_tile_texture + 0x0397 (myth2code\render\render_maps.c:1000)
myth_crashlog- 2025-11-29 11.58.06.txt: 0 0x004b3e79 _build_mesh_tile_texture + 0x0397 (myth2code\render\render_maps.c:1000)
myth_crashlog- 2025-11-29 12.00.02.txt: 0 0x004b3e79 _build_mesh_tile_texture + 0x0397 (myth2code\render\render_maps.c:1000)
myth_crashlog- 2025-11-29 12.00.29.txt: 0 0x004b3e79 _build_mesh_tile_texture + 0x0397 (myth2code\render\render_maps.c:1000)
myth_crashlog- 2025-11-29 12.01.05.txt: 0 0x004b3e79 _build_mesh_tile_texture + 0x0397 (myth2code\render\render_maps.c:1000)
myth_crashlog- 2025-11-29 12.03.28.txt: 0 0x004b3e79 _build_mesh_tile_texture + 0x0397 (myth2code\render\render_maps.c:1000)
myth_crashlog- 2025-11-29 12.03.49.txt: 0 0x004b3e79 _build_mesh_tile_texture + 0x0397 (myth2code\render\render_maps.c:1000)
myth_crashlog- 2025-11-29 16.00.22.txt: 0 0x004b3e79 _build_mesh_tile_texture + 0x0397 (myth2code\render\render_maps.c:1000)
myth_crashlog- 2025-11-29 16.02.54.txt: 0 0x004b3e79 _build_mesh_tile_texture + 0x0397 (myth2code\render\render_maps.c:1000)
myth_crashlog- 2025-12-04 17.34.29.txt: 0 0x004b3e79 _build_mesh_tile_texture + 0x0397 (myth2code\render\render_maps.c:1000)
myth_crashlog- 2025-12-04 17.41.09.txt: 0 0x004b3e79 _build_mesh_tile_texture + 0x0397 (myth2code\render\render_maps.c:1000)
myth_log.txt: 0 0x004b3e79 _build_mesh_tile_texture + 0x0397 (myth2code\render\render_maps.c:1000)

seems to be in every crash, and yes i tried compatibility mode, a few different operating system options

[Melekor]

Thanks for trying all that. I'm out of ideas so let's go with the nuclear option. I created this special build that will generate a crash dump file that will let me inspect the app's stack memory in a debugger.

https://projectmagma.net/~melekor/tmp/c ... 32Debug.7z

The dump file will probably be around 15 megabytes so but if you 7zip it it should get down to 1-2MB, hopefully small enough to upload here.

[cayuse27]

i tried it and replied directly to the email