Software d3d9 client not working on widnows 11

[cmm]

On my new windows 11 computer when i check the d3d9 client in the graphics section of modules it and the graphics tab disappear and then orbiter server crashes. and orbiter.exe wont launch. Any ideas would be helpful.
this is my computer https://www.lenovo.com/us/en/p/lapt...000qus?orgRef=https%3A%2F%2Fwww.google.com%2F

 

[n72.75]

This is not an uncommon problem, but I'm sure we can get you up and running.

Could you post your orbiter.log file?

Have you installed the directx9 runtimes from Microsoft?

 

[jarmonik]

Can you switch the display mode to "nVidia GPU only" and see if it works ? If it does, report back. I wonder how much it impacts in battery life, if that's important.
https://nvidia.custhelp.com/app/answers/detail/a_id/5097/~/nvidia-advanced-optimus-overview

Automatic switching doesn't seem to work anymore:

The display will not switch to discrete GPU in the following scenarios -

• The display will not switch to discrete GPU if the application in allow list is a DirectX9 application.

Crashing immediately after checking the box indicates a crash while trying to enumerate display modes. Which kinda indicates a DX9 device failure but why ?
If the nVidia GPU fails to kick in then shouldn't it just run with the integrated GPU. Why the crash ?
Submit the log requested above.

 

[cmm]

here is the orbiter log for orbiter_ng

 

[cmm]

this is the log whenever I try (and fail too) launch orbiter.exe. I think it might have to do with the graphics card not supporting T&L capability but not sure?

 

[cmm]

I thought I would also add this. its a screen recording of me clicking on the d3d9 module and then it disappears and orbiter just stops responding. so i can't even press the launch button. sorry about the cursor not aligning with the video idk why.

 

[cmm]

This is not an uncommon problem, but I'm sure we can get you up and running.

Could you post your orbiter.log file?

Have you installed the directx9 runtimes from Microsoft?

yes I have installed them.

 

[n72.75]

There is a similar thread, with similar issues (that we were unfortunately unable to resolve):

Software - Orbiter not working on laptop

So I recently tried downloading Orbiter 2016 on my laptop. It's not really meant from flight simulators though and I'm starting to think it's probably a hardware issue at this point. But just in case here are the issues: When I open orbiter_ng.exe I don't get an option to check D3D9, even...

www.orbiter-forum.com

Software - Orbiter w/ D3D9 not working on Laptop

I am having an issue where the D3D9 client doesnt work on my laptop for orbiter unless its through an external monitor. Orbiter doesnt appear to be recognizing the dedicated GPU (RTX 3050 ti) and instead is just recognizing the iGPU under the video tab of the normal client. If I try and select...

www.orbiter-forum.com

I don't think the root cause is the graphics card, I believe people have Orbiter working on Intel graphics (correct me if I'm wrong).
If you have any ability to force Orbiter to use the NVidia card, that's probably your best bet.

My memory and forum searching aren't at 100% right now. Others will probably have better ideas.

 

[jarmonik]

Could you try to delete Orbiter_NG.cfg and see if it helps ?

 

[cmm]

Could you try to delete Orbiter_NG.cfg and see if it helps ?

i successfully deleted that file and it didn't do anything different

 

[cmm]

I was able to force both apps to run on both cards individually. No luck. Question I just looked at the d3d9 logs-does "[Not Compiled with nVidia API]" mean anything (like orbiter isn't meant to run on Nvidia cards?)

 

[jarmonik]

I was able to force both apps to run on both cards individually. No luck. Question I just looked at the d3d9 logs-does "[Not Compiled with nVidia API]" mean anything (like orbiter isn't meant to run on Nvidia cards?)

At some point in time nVidia API was required to enable stereoscopic 3D but nothing else.

 

[jarmonik]

Could you copy paste the error information. If it points in a right place then I can prepare a debug build that should provide additional information about the crash.

Press "windows key" + R
Run application called "msinfo32"

Open "Software Environment" tree
Open "Windows Error Reporting"

Find the correct error based on it's time stamp and copy paste it. It's something like this:

26/11/2023 20.30    Application Error    Faulting application name: Orbiter.exe, version: 0.0.0.0, time stamp: 0x6563aa57
Faulting module name: Orbiter.exe, version: 0.0.0.0, time stamp: 0x6563aa57
Exception code: 0x80000003
Fault offset: 0x0025477c
Faulting process id: 0x0x39B0
Faulting application start time: 0x0x1DA20A7192E5FFA
Faulting application path: C:\Software\VCBake\Orbiter\Modules\Server\Orbiter.exe
Faulting module path: C:\Software\VCBake\Orbiter\Modules\Server\Orbiter.exe
Report Id: c69a9420-4423-4152-b746-65f44eac4a23
Faulting package full name: 
Faulting package-relative application ID:

Also, have you tried to use the latest Open Orbiter. Any fixes made will be applied to that one. No changes are made to Orbiter 2016 anymore.
https://github.com/orbitersim/orbiter/releases/tag/latest

 

[cmm]

heres one of them

12/25/2023 3:15 PM Application Error Faulting application name: orbiter.exe, version: 0.0.0.0, time stamp: 0x57c23433
Faulting module name: ucrtbase.dll, version: 10.0.22621.2506, time stamp: 0xac92626e
Exception code: 0xc0000005
Fault offset: 0x00066a3e
Faulting process id: 0x0x3738
Faulting application start time: 0x0x1DA37453BA0470A
Faulting application path: C:\Orbiter2016\orbiter.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll
Report Id: f459905f-9340-4602-810e-c442f99c9b72
Faulting package full name: 
Faulting package-relative application ID:

and heres the other

12/25/2023 3:17 PM Application Error Faulting application name: orbiter.exe, version: 0.0.0.0, time stamp: 0x57c23433
Faulting module name: ucrtbase.dll, version: 10.0.22621.2506, time stamp: 0xac92626e
Exception code: 0xc0000005
Fault offset: 0x00066a3e
Faulting process id: 0x0x669C
Faulting application start time: 0x0x1DA37455E25A6B7
Faulting application path: C:\Orbiter2016\orbiter.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll
Report Id: 253068dc-acb3-4aba-9011-b49954668720
Faulting package full name: 
Faulting package-relative application ID:

no I am using Orbiter2016 since when I extract it properly into the main root directory for OpenOrbiter it doesn't show up in modules

 

[jarmonik]

Thanks about the information. It's strange that fault occur in ucrtbase.dll

no I am using Orbiter2016 since when I extract it properly into the main root directory for OpenOrbiter it doesn't show up in modules

It ? If you mean D3D9Client. That's no longer located in modules in Open Orbiter, the renderer (client) is selected in a Video Tab.

I have attached a debug build of Open Orbiter and D3D9Client binaries. It's meant to be extracted on a top of Open Orbiter installation but might also work with Orbiter 2016. I have added more checks and tests there. If you test it then following information would be useful:
1. Orbiter.log
2. D3D9ClientLog.html
3. CrashDump C:/Users/<user name>/AppData/Local/CrashDumps/

 

[cmm]

thanks for the patch I have the following information for you
orbiter.log is from running orbiter _ng. once I selected the d3d9 (same thing happened when I selected d3d7 too) the launchpad would immediately crash.
orrbiter.exelog.log is from running orbiter.exe which would just crash after getting to the loading screen with the image of earth saying loading.
I have attached the CrashDump files too for two of them (not sure which)
I have switched completely to open orbiter (all of these were run on OpenOrbiter. if you want me to try them on orbiter2016 let me know and I can do the same thing?

 

[cmm]

also in order to launch the server launchpad i had to delete the orbiter_ng.cfg file first

 

[n72.75]

no I am using Orbiter2016 since when I extract it properly into the main root directory for OpenOrbiter it doesn't show up in modules

I might be misreading this, but are you extracting Orbiter 2016 over an OpenOrbiter install?
OpenOrbiter is a standalone application and comes with everything (except planet textures, because they're huge files)

Also, you have the correct version of D3D9 client for O2016: https://www.orbiter-forum.com/resources/d3d9-for-orbiter-2016.5493/ right?

OpenOrbiter comes with D3D9 client, so no need to install anything there.

 

[cmm]

I might be misreading this, but are you extracting Orbiter 2016 over an OpenOrbiter install?
OpenOrbiter is a standalone application and comes with everything (except planet textures, because they're huge files)

Also, you have the correct version of D3D9 client for O2016: https://www.orbiter-forum.com/resources/d3d9-for-orbiter-2016.5493/ right?

OpenOrbiter comes with D3D9 client, so no need to install anything there.

good point. I have reinstalled a fresh copy of OpenOrbiter and tried it again over the open orbiter install and attached the docs @jarmonik requested. I thought the debugging patch was for OpenOrbiter but now that I notice it @jarmonik was it meant for Orbiter 2016 or OpenOrbiter-can you clarify?

 

[jarmonik]

was it meant for Orbiter 2016 or OpenOrbiter-can you clarify?

It was meant to Open Orbiter. I found something pretty odd. It looks like you are trying to run the Orbiter through something called d3d9on12. It's a wrapper layer to translate DX9 to DX12 https://github.com/microsoft/D3D9On12 the crash occur on the very first directx9 call that's made on IDirect3D9* d3dObject = Direct3DCreate9(D3D_SDK_VERSION);
Did you install this somehow or was it installed by default ? Microsoft has quit supporting d3d9 on some graphics chips and d3d9 is provided through emulation layer. If I recall there exists a similar layer d3d9onVulkan. So, I guess the question would be how to disable d3d9on12 and run it natively with 3050 GPU ?

I suppose it might be possibility to officially compile the D3D9Client with Vulkan wrapper but I am worried about problems that a wrapper might cause.