d3d9on12 was installed by default. the only graphics thing I have installed is https://www.microsoft.com/en-us/download/details.aspx?id=8109 which I don't think includes that but did include d3d9. I'm not sure how to disable d3d9on12-if you have any ideas I would love to try them.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 ?
that didn't seem to change anythingYou could try copying d3d9.dll from Windows/SysWOW64 to Orbiter/Modules/Server/
Not working with DX9 apps.Have any of the steps on this page been tried: https://techwiser.com/ways-to-set-default-graphics-card-on-windows-11/
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.
yes. I tried both of those before coming to the forum I've known about that for a while and had to use it since some apps (Namely Autodesk Fusion 360) would switch back and forth frequently and grind to a halt but I was able to resolve it that way.Have any of the steps on this page been tried: https://techwiser.com/ways-to-set-default-graphics-card-on-windows-11/
Orbiter launchpad crashed with iGPU disabled.
Not sure where to look for the surface textures (they don't seem to be in "Textures or Textures2"if you could let me know which folder to search I can look for them?
; === Subdirectory locations
PlanetTexDir = C:\Software\Orbiter2016-SVN-Clean\Textures\
there are two things that are a bit strange to me first is that I cannot seem to be able to have the option to select the nvidia card
the textures aren't there. Can I just copy them from the orbiter 2016 installation or is there a different way?Planetary textures are located in /Textures/<PlanetName> and they are in a *.tree format.
Yes, you can copy them from Orbiter 2016 or specify the path like in a post above.the textures aren't there. Can I just copy them from the orbiter 2016 installation or is there a different way?
It's fine that it can't be used on the nvidia graphics. I just want to use orbiter and the intel card is doing a perfectly fine card so I am happy using orbiter on that card. Although doesn't the wrapper enable it through DX12 so that the computer thinks its using DX12 or does something different happen?New laptop computer don't have that ability any more with DirectX9 applications, based on my understanding, DX9 is stuck using the same GPU as the desktop uses. There is one report somewhere saying that disabling iGPU would have solved the problem.
I have never had a laptop with dual graphics. My old laptop only uses Intel HD Graphics 4000
As far as I can tell, d3d9on12 is a DirectX9 driver that reroutes the calls to DirectX12 driver. So, OS would still see it as DX9 application.It's fine that it can't be used on the nvidia graphics. I just want to use orbiter and the intel card is doing a perfectly fine card so I am happy using orbiter on that card. Although doesn't the wrapper enable it through DX12 so that the computer thinks its using DX12 or does something different happen?
thanks for the help now everything is working including textures. whats the usual framerate though since im seeing about 300?I think I managed to enable the DX9 through DX12, so I have a new patch for testing. There is a new configuration option "EnableDX12Wrapper = 0" added to D3D9Client.cfg
With the DX12 wrapper enable I have noticed a rendering problem in DG ID label on the wing (black square) and the frame rate is about 50% lower, so, it's not really a victory. Could you test it with and without the wrapper.
ok thanks for the tip. I'll let you know if any other related issues come upOk, thanks for your help with the issue. I'll include this DX12 wrapper mode officially into the Open Orbiter.
Edit: I would recommend disabling anti-aliasing to improve frame-rates, it hits hard on intel HD graphics 4000 at-least.