Question DirectX runtimes

[KrazyKyle]

I was never able to get D3D9 running on my 2007, Win XP machine. I passed it off as being obsolete. Orbiter 2010 ran great. I finally upgraded to a shiny new Win 10 machine with Orbiter 2016. And I still can't get D3D9 to work. I get a DOS window saying no client found. Yes, the module is activated in Orbiter_ng.

Researching in the forum, I come across references to DirectX runtimes. Could it be that I've jumped right over DirectX 9? Would installing those V9 runtimes mess up my DirectX 12?

 

[kuddel]

No, installing DX9 does nothing to your DX12 (or DX11) installation.

You'll get the "June 2010" Version here https://www.microsoft.com/en-us/download/details.aspx?id=8109

 

[KrazyKyle]

Thanks! I'll give it a shot. I just tried Orbiter 2010 with an older D3D9 release, and the same thing happens. After enabling the D3D9 module, There is no "Video" tab, so I can't do any advanced setup. Orbiter cannot open the client when I try to launch.

---------- Post added 09-01-17 at 11:29 PM ---------- Previous post was 08-31-17 at 11:43 PM ----------

That worked! Thanks for the link! I think I'll try it with an Orbiter 2910 installation so I can run my favorite ships that aren't updated to 2016 yet.

 

[kuddel]

Nice, but keep in mind that there are (at least) two specific versions of D3D9Client:
The ones for Orbiter 2016, the ones for Orbiter 2010(-P1)
...and some that should be used for Orbiter BETAs (or one of it's latest commits).

Hopefully I did not add any further confusion :hmm: