Search results

Build failed. Log attached as it's too big to post as raw text.

Now getting this: 1> CMake generation started for configuration: 'windows-x86-debug-windows-x86-debug'. 1> Environment settings: 1> CommandPromptType=Cross 1> DevEnvDir=C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\ 1> ExtensionSdkDir=C:\Program Files...

Still getting the error even with ORBITER_BUILD_XRSOUND off: https://www.dropbox.com/scl/fi/wx9g2qdjbcqzj3vi0vk55/VS_Orbiter2024_source_error_XRSound.jpg?rlkey=hr5hmronzmvna2t9du9keegrv&dl=0

With the GitExtensions problems out of the way, now when I try to build the Orbiter sources, I get this error message: >------ Build started: Project: CMakeLists, Configuration: Debug ------ D:\misc\Orbiter_2024_sources\orbiter\out\build\windows-x64-debug\ninja : error ...

OK, think I manage to get it working by installing Git for Windows.

Yes, and it's the same.

I'm officially stuck. Tried uninstalling and re-installing the damn thing several times now with the same result.

Tried installing GitExtensions and this is the error message I get when trying to use it: https://www.dropbox.com/scl/fi/fq8avd7v9covi7516f4h2/VS_GitExtensions_error.jpg?rlkey=kinn0unzab85pp2vbuto7hrdg&dl=0

So how do I do that. I am very unfamiliar with Git. I have only gotten this far thanks to your instructions.

Got the DirectX SDK installed but now I have this in the log: 1> CMake generation started for configuration: 'windows-x64-asan-windows-x64-asan'. 1> Environment settings: 1> CommandPromptType=Native 1> DevEnvDir=C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\ 1>...

Got this in the log: 1> CMake generation started for configuration: 'windows-x86-debug-windows-x86-debug'. 1> Environment settings: 1> CommandPromptType=Cross 1> DevEnvDir=C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\ 1> ExtensionSdkDir=C:\Program Files...

You mean in the Solution Explorer? When right clicking on CMakeLists.txt, I don't see such an option: https://www.dropbox.com/scl/fi/dc1zaujm7th9cmoqipf31/VS_Orbiter2024_source.jpg?rlkey=un0nd384dfkvguyrexixt95l0&dl=0

Update: Ran another session hoping to get another CTD and was not disappointed! Halfway through the STS-125 OMS-2 burn this time. This time the addresses are different along with where it was trapped, this time in D3D9Client.dll...

Decided to unfreeze the paused debugger and got this immediately after: Unhandled exception at 0x3F097401 in Orbiter.exe: 0xC0000005: Access violation executing location 0x00000000

Only stuff in the installation is Orbiter 2024/Antelope Valley/SSV.

Try this instead: https://www.dropbox.com/scl/fi/ix2i7p9rvdutww6p56erz/VS_dubugger_SSV_CTD.jpg?rlkey=cutfbinocvm9lzzo0mpz1h9vl&dl=0

CTD while VS debugger attached, screenshot attached to this post. Awaiting further instructions.

I always end up with at least the LH2 needing a relief prior to OMS-2 and then a short vacuum inert at MM106 (about of 1 PSI remains after the pre-OMS-2 relief activation).

Are you sure? I've seen the orbiter doing dual propellant purge prior to MM106 if the Engine Manifold pressures are high enough.

Managed to build a debug version of SSV and the CTD is still there at the same point. I'm starting to think that this might have something to do with the automated vacuum inerting as I think the second one is supposed to happen somewhere around the OMS-2 TIG.