CurlSnout
Well-known member
Hello Citizens,
Have been running Orbiter 2016 (and Orbiter 2010 before that and Orbiter 2006 before that) for years without issue. Downloaded/installed Orbiter 2024 and I can't get a single scenario to run. This is 100% vanilla; I haven't attempted to load any addons. The Launchpad comes up (using Orbiter_ng.exe), and I choose D3D9Client for my graphics engine. It recognizes my video card (Nvidia GeForce RTX 3060 Ti) and my resolution is set to 2560 x 1440 (native for my monitor). On the video tab I choose Advanced and ask it to Create symbolic links. I have enabled the XRSound module. I can choose a scenario - say, for example, 'Welcome to Orbiter 2024' in the 2024 directory. When I attempt to run this, the Open Orbiter splash screen comes up, says it's loading (I can see things - Building Shader Programs, Loading Celestial Sphere, Sol:Earth, etc. scrolling by at the bottom left as if they are, in fact, loading), and then I get a CTD. Any/all scenarios give similar result.
Afterwards, Orbiter.log looks like this:
**** Orbiter.log
000000.005: Build Dec 31 2024 [v.602931718]
000000.005: Timer precision: 1e-07 sec
000000.038: Found 0 joystick(s)
000000.236: Module XRSound.dll ........... [Build 241231, API 241231]
000000.239: Loading module XRSound
000000.243: ---------------------------------------------------------------
000000.247: BaseDir : C:\applications\simulations\ORBITER(s)\Orbiter-2024\
000000.250: ConfigDir : C:\applications\simulations\ORBITER(s)\Orbiter-2024\Config\
000000.253: MeshDir : C:\applications\simulations\ORBITER(s)\Orbiter-2024\Meshes\
000000.256: TextureDir : C:\applications\simulations\ORBITER(s)\Orbiter-2024\Textures\
000000.259: HightexDir : C:\applications\simulations\ORBITER(s)\Orbiter-2024\Textures2\
000000.263: ScenarioDir: C:\applications\simulations\ORBITER(s)\Orbiter-2024\Scenarios\
000000.266: ---------------------------------------------------------------
000000.269: D3D9 DLLs : C:\Windows\SYSTEM32\d3d9.dll [v 10.0.22621.4541]
000000.272: : C:\Windows\SYSTEM32\d3dx9_43.dll [v 9.29.952.3111]
000000.277: ---------------------------------------------------------------
000000.281: Module D3D9Client.dll ........ [Build 241231, API 241231]
000000.318: [D3D9] Native Interface
000000.323: [D3D9] DirectX9 Created...
000000.328: [D3D9] Initialize VideoTab...
000000.355: Loading module D3D9Client
000000.361: Module AtlantisConfig.dll .... [Build 241231, API 241231]
000000.365: Loading module AtlantisConfig (legacy interface)
000000.369: Module AtmConfig.dll ......... [Build 241231, API 241231]
000000.373: Loading module AtmConfig (legacy interface)
000000.378: Module DGConfigurator.dll .... [Build 241231, API 241231]
000000.382: Loading module DGConfigurator (legacy interface)
000006.719: Module DX9ExtMFD.dll ......... [Build 241231, API 241231]
000006.726: Loading module DX9ExtMFD (legacy interface)
000011.648:
000011.658: **** Creating simulation session
000011.671: D3D9: [DirectX 9 Initialized]
000011.678: D3D9: 3D-Adapter.............. : NVIDIA GeForce RTX 3060 Ti
000011.683: D3D9: MaxTextureWidth......... : 16384
000011.688: D3D9: MaxTextureHeight........ : 16384
000011.694: D3D9: MaxTextureRepeat........ : 8192
000011.698: D3D9: VolTexAddressCaps....... : 0x3F
000011.703: D3D9: NumSimultaneousRTs...... : 4
000011.708: D3D9: VertexDeclCaps.......... : 0x30F
000011.712: D3D9: MiscCaps................ : 0x2FCEF2
000011.717: D3D9: Separate AlphaBlend..... : Yes
000011.721: D3D9: Shadow Mapping.......... : Yes
000011.725: D3D9: D3DFMT_A16B16G16R16F.... : Yes
000011.729: D3D9: Vertex_A16B16G16R16F.... : Yes
000011.733: D3D9: Vertex_A32B32G32R32F.... : Yes
000011.737: D3D9: Vertex_R16F............. : Yes
000011.742: D3D9: Vertex_R32F............. : Yes
000011.746: D3D9: D3DFMT_A32B32G32R32F.... : Yes
000011.750: D3D9: D3DFMT_D32F_LOCKABLE.... : Yes
000011.754: D3D9: D3DFMT_A2R10G10B10...... : Yes
000011.758: D3D9: D3DFMT_L8............... : Yes
000011.761: D3D9: D3DDTCAPS_DEC3N......... : No
000011.766: D3D9: D3DDTCAPS_FLOAT16_2..... : Yes
000011.770: D3D9: D3DDTCAPS_FLOAT16_4..... : Yes
000011.774: D3D9: Runs under WINE......... : No
000011.777: D3D9: D3D9Build Date.......... : 0
000011.839: D3D9: Available Texture Memory : 4069 MB
000011.845: D3D9: [3DDevice Initialized]
000017.380: Loaded 41057 records from star database
000018.330: D3D9: [D3D9Client Initialized]
000018.427: Module Sun.dll ............... [Build 241231, API 241231]
000018.443: VSOP87(E) Sun: Precision 1.0e-06, Terms 554/6634
000018.457: Module Mercury.dll ........... [Build 241231, API 241231]
000018.464: GRAVITY MODEL: GravityModels\jgmess_160a_sha.tab LOADED, Terms 65/13040
000018.481: VSOP87(B) Mercury: Precision 1.0e-05, Terms 167/7123
000018.507: Module Venus.dll ............. [Build 241231, API 241231]
000018.512: GRAVITY MODEL: GravityModels\mod_shgj120p.a01 LOADED, Terms 65/7380
000018.517: Module VenusAtm2006.dll ...... [Build 241231, API 241231]
000018.520: Loading module VenusAtm2006 (legacy interface)
000018.525: VSOP87(B) Venus: Precision 1.0e-05, Terms 79/1710
000018.548: Module Earth.dll ............. [Build 241231, API 241231]
000018.579: GRAVITY MODEL: GravityModels\egm96_to360.tab LOADED, Terms 65/65340
000018.584: Module EarthAtmJ71G.dll ...... [Build 241231, API 241231]
000018.589: Loading module EarthAtmJ71G (legacy interface)
000018.595: VSOP87(B) Earth: Precision 1.0e-08, Terms 2564/2564
Is it pulling D3D9 DLLs out of C:\Windows\SYSTEM32 (there for Orbiter 2016)? Is that problematic? I do have Orbiter 2016 on this machine (in a completely separate directory) and it is running smoothly.
I have read through the readme.txt file that lives in the root directory. I haven't read the entire User Manual, but I've looked through the first bits to see if I need to download any dependencies. Unsure what I'm missing or what I'm doing wrong or not doing correctly. Any/all help/advice/suggestions appreciated.
Thank you, and good evening,
Sam
Other machine specs:
Desktop PC running Windows 11
intel i7 - 12700K @ 3.6 GHz
32 GB RAM
Nvidia GeForce RTX 3060 Ti (8 GB)
display = Dell U2715H @ 2560 x 1440 (native)
Have been running Orbiter 2016 (and Orbiter 2010 before that and Orbiter 2006 before that) for years without issue. Downloaded/installed Orbiter 2024 and I can't get a single scenario to run. This is 100% vanilla; I haven't attempted to load any addons. The Launchpad comes up (using Orbiter_ng.exe), and I choose D3D9Client for my graphics engine. It recognizes my video card (Nvidia GeForce RTX 3060 Ti) and my resolution is set to 2560 x 1440 (native for my monitor). On the video tab I choose Advanced and ask it to Create symbolic links. I have enabled the XRSound module. I can choose a scenario - say, for example, 'Welcome to Orbiter 2024' in the 2024 directory. When I attempt to run this, the Open Orbiter splash screen comes up, says it's loading (I can see things - Building Shader Programs, Loading Celestial Sphere, Sol:Earth, etc. scrolling by at the bottom left as if they are, in fact, loading), and then I get a CTD. Any/all scenarios give similar result.
Afterwards, Orbiter.log looks like this:
**** Orbiter.log
000000.005: Build Dec 31 2024 [v.602931718]
000000.005: Timer precision: 1e-07 sec
000000.038: Found 0 joystick(s)
000000.236: Module XRSound.dll ........... [Build 241231, API 241231]
000000.239: Loading module XRSound
000000.243: ---------------------------------------------------------------
000000.247: BaseDir : C:\applications\simulations\ORBITER(s)\Orbiter-2024\
000000.250: ConfigDir : C:\applications\simulations\ORBITER(s)\Orbiter-2024\Config\
000000.253: MeshDir : C:\applications\simulations\ORBITER(s)\Orbiter-2024\Meshes\
000000.256: TextureDir : C:\applications\simulations\ORBITER(s)\Orbiter-2024\Textures\
000000.259: HightexDir : C:\applications\simulations\ORBITER(s)\Orbiter-2024\Textures2\
000000.263: ScenarioDir: C:\applications\simulations\ORBITER(s)\Orbiter-2024\Scenarios\
000000.266: ---------------------------------------------------------------
000000.269: D3D9 DLLs : C:\Windows\SYSTEM32\d3d9.dll [v 10.0.22621.4541]
000000.272: : C:\Windows\SYSTEM32\d3dx9_43.dll [v 9.29.952.3111]
000000.277: ---------------------------------------------------------------
000000.281: Module D3D9Client.dll ........ [Build 241231, API 241231]
000000.318: [D3D9] Native Interface
000000.323: [D3D9] DirectX9 Created...
000000.328: [D3D9] Initialize VideoTab...
000000.355: Loading module D3D9Client
000000.361: Module AtlantisConfig.dll .... [Build 241231, API 241231]
000000.365: Loading module AtlantisConfig (legacy interface)
000000.369: Module AtmConfig.dll ......... [Build 241231, API 241231]
000000.373: Loading module AtmConfig (legacy interface)
000000.378: Module DGConfigurator.dll .... [Build 241231, API 241231]
000000.382: Loading module DGConfigurator (legacy interface)
000006.719: Module DX9ExtMFD.dll ......... [Build 241231, API 241231]
000006.726: Loading module DX9ExtMFD (legacy interface)
000011.648:
000011.658: **** Creating simulation session
000011.671: D3D9: [DirectX 9 Initialized]
000011.678: D3D9: 3D-Adapter.............. : NVIDIA GeForce RTX 3060 Ti
000011.683: D3D9: MaxTextureWidth......... : 16384
000011.688: D3D9: MaxTextureHeight........ : 16384
000011.694: D3D9: MaxTextureRepeat........ : 8192
000011.698: D3D9: VolTexAddressCaps....... : 0x3F
000011.703: D3D9: NumSimultaneousRTs...... : 4
000011.708: D3D9: VertexDeclCaps.......... : 0x30F
000011.712: D3D9: MiscCaps................ : 0x2FCEF2
000011.717: D3D9: Separate AlphaBlend..... : Yes
000011.721: D3D9: Shadow Mapping.......... : Yes
000011.725: D3D9: D3DFMT_A16B16G16R16F.... : Yes
000011.729: D3D9: Vertex_A16B16G16R16F.... : Yes
000011.733: D3D9: Vertex_A32B32G32R32F.... : Yes
000011.737: D3D9: Vertex_R16F............. : Yes
000011.742: D3D9: Vertex_R32F............. : Yes
000011.746: D3D9: D3DFMT_A32B32G32R32F.... : Yes
000011.750: D3D9: D3DFMT_D32F_LOCKABLE.... : Yes
000011.754: D3D9: D3DFMT_A2R10G10B10...... : Yes
000011.758: D3D9: D3DFMT_L8............... : Yes
000011.761: D3D9: D3DDTCAPS_DEC3N......... : No
000011.766: D3D9: D3DDTCAPS_FLOAT16_2..... : Yes
000011.770: D3D9: D3DDTCAPS_FLOAT16_4..... : Yes
000011.774: D3D9: Runs under WINE......... : No
000011.777: D3D9: D3D9Build Date.......... : 0
000011.839: D3D9: Available Texture Memory : 4069 MB
000011.845: D3D9: [3DDevice Initialized]
000017.380: Loaded 41057 records from star database
000018.330: D3D9: [D3D9Client Initialized]
000018.427: Module Sun.dll ............... [Build 241231, API 241231]
000018.443: VSOP87(E) Sun: Precision 1.0e-06, Terms 554/6634
000018.457: Module Mercury.dll ........... [Build 241231, API 241231]
000018.464: GRAVITY MODEL: GravityModels\jgmess_160a_sha.tab LOADED, Terms 65/13040
000018.481: VSOP87(B) Mercury: Precision 1.0e-05, Terms 167/7123
000018.507: Module Venus.dll ............. [Build 241231, API 241231]
000018.512: GRAVITY MODEL: GravityModels\mod_shgj120p.a01 LOADED, Terms 65/7380
000018.517: Module VenusAtm2006.dll ...... [Build 241231, API 241231]
000018.520: Loading module VenusAtm2006 (legacy interface)
000018.525: VSOP87(B) Venus: Precision 1.0e-05, Terms 79/1710
000018.548: Module Earth.dll ............. [Build 241231, API 241231]
000018.579: GRAVITY MODEL: GravityModels\egm96_to360.tab LOADED, Terms 65/65340
000018.584: Module EarthAtmJ71G.dll ...... [Build 241231, API 241231]
000018.589: Loading module EarthAtmJ71G (legacy interface)
000018.595: VSOP87(B) Earth: Precision 1.0e-08, Terms 2564/2564
Is it pulling D3D9 DLLs out of C:\Windows\SYSTEM32 (there for Orbiter 2016)? Is that problematic? I do have Orbiter 2016 on this machine (in a completely separate directory) and it is running smoothly.
I have read through the readme.txt file that lives in the root directory. I haven't read the entire User Manual, but I've looked through the first bits to see if I need to download any dependencies. Unsure what I'm missing or what I'm doing wrong or not doing correctly. Any/all help/advice/suggestions appreciated.
Thank you, and good evening,
Sam
Other machine specs:
Desktop PC running Windows 11
intel i7 - 12700K @ 3.6 GHz
32 GB RAM
Nvidia GeForce RTX 3060 Ti (8 GB)
display = Dell U2715H @ 2560 x 1440 (native)
Last edited:
