CurlSnout
Well-known member
How does one see the loaded modules list?
Last edited:
Problem UNABLE to get off the pad using Orbiter 2024 - ???
- Thread starter CurlSnout
- Start date
CurlSnout
Well-known member
GLS
Well-known member
A zlib* function is called at/near the CTD... I don't have a theory that explains this, but it seems something to explore.
*) The zlib library has compression and decompression functions, and is used by Orbiter to decompress the big texture/elevation archives.
*) The zlib library has compression and decompression functions, and is used by Orbiter to decompress the big texture/elevation archives.
n72.75
Seize the means of computation
- Joined
- Mar 21, 2008
- Messages
- 2,872
- Reaction score
- 1,714
- Points
- 128
- Location
- Saco, ME
- Website
- mwhume.space
- Preferred Pronouns
- he/him
Given, that this fixed it. It seems like the cause could likely be Windows serving up the wrong zlib.
I believe https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer
can show which DLLs which process is using.
BINGO! It works! 
What a relief...
I can see in the VS debugger that Orbiter.exe loaded zlib from
(In one of my previous posts, I said that the stack pointer shifts 16 bytes up after zlib's)
For what it's worth, the latest version of
Thank you @francisdrake
What a relief...I can see in the VS debugger that Orbiter.exe loaded zlib from
C:\Windows\SysWOW64\Zlib.dll which is version 1.01.2.0 on my machine, from 1998. So I guess that version has some compatibility issues.(In one of my previous posts, I said that the stack pointer shifts 16 bytes up after zlib's
uncompress function returns, corrupting the return address to ReadData. Now that the proper zlib.dll is loaded, that shift doesn't happen. Also, the reason I didn't see a difference when changing the zlib version is because Windows was not even loading those versions )For what it's worth, the latest version of
zlib, v1.3.1, also seems to work on my machine. But I'll leave it to the rest of the development team to properly test that.Thank you @francisdrake
Last edited:
GLS
Well-known member
I'm not following the latest changes in github, so maybe this is history already, but I hope this zlib issue is solved "at the source" so users don't have move dlls around.
GLS
Well-known member
And maybe post this as a "known issue", with the fix, in the Orbiter download page, so people know this might happen and how to fix it.
Similar threads
