Search results

See my additional reply, it was without the MFDs from the start. Forgot that I deleted the blocks in the scenario last night.

Another detail is this happen with the MDUs turned completely off, no MFD blocks in the scenario, only the VC block.

Another day, another crash, this time here: https://www.dropbox.com/scl/fi/nuqk6ca77j25yqsqwt07c/VS_debugger_D3D9Client4.jpg?rlkey=k77oknl6j0xgw7dagjgpfu7ke&dl=0 Details are: Unpaused, 0.1x time accel, exterior camera view, pre-launch at T-8:47.8, mission STS-109, so OV-102 8th mod, PLB liner...

Another crash, this time on the pad, while paused, same error as earlier though: https://www.dropbox.com/scl/fi/p37tmzmmr59n48i4sf2b8/Orbiter_D3D9Client_SSV_error_paused.jpg?rlkey=jbu2h7hd2m994u6ja4qdzzr5j&dl=0 Line 299 of DrawAPI.h is the end of the following bit code: inline FVECTOR3...

Well, so far both SLS Core Stages and ICPS's have been flawless. The hydrogen leaks are a Ground Support Equipment (GSE) problem, not a flight hardware problem. The helium problem encountered with the Artemis-1 ICPS was that a ground-side seal got blown into the ICPS helium system and prevented...

Not it wasn't. That was never the plan. SLS never had that capability, it was always short hence the requirement of the Gateway Station in NHRO for Orion to dock to. Gateway would serve as hibernation point for Orion while the crew went to the lunar surface and back again in the HLS lander...

Click the Advanced button and make sure Full Scene is selected under Reflections and Custom camera settings.

And here's another: https://www.dropbox.com/scl/fi/h8z4o15rtlsfeor861yz5/VS_debugger_D3D9Client3.jpg?rlkey=gb4pok5qptbiugqipwp6iqv7w&dl=0 https://www.dropbox.com/scl/fi/4mjp8vzc8j1blkphy30i1/VS_debugger_D3D9Client3A.jpg?rlkey=7kyabmtv628jjewn0oux37by2&dl=0...

Different error this time: https://www.dropbox.com/scl/fi/9gdftg0fn7d615z6il3cj/VS_debugger_D3D9Client2.jpg?rlkey=ugxl3e0zrrrm74rwljhk26wnu&dl=0 https://www.dropbox.com/scl/fi/9gdftg0fn7d615z6il3cj/VS_debugger_D3D9Client2.jpg?rlkey=ugxl3e0zrrrm74rwljhk26wnu&dl=0...

Here's the call stack window: https://www.dropbox.com/scl/fi/duza1hyfaj6uhmi7g8qh5/VS_debugger_D3D9Client_call_stack.jpg?rlkey=e856kn4fqs28p604gpf8x8oiv&dl=0

How do I check for that?

CTD and caught by the debugger: https://www.dropbox.com/scl/fi/ejrfentjpfaftfvllywbx/VS_dubugger_SSV_CTD_Run3.jpg?rlkey=ygolvlkq3rafv886f8irn6h8q&dl=0

That yielded complete success in the build phase I've replaced the original release files with the newly built debug versions.

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.