So what is my FSX using? I looked up DXDIAG and found the version number and it says DX11... So what does that mean then?

 

Scott

The way I understand it is that DX versions are backwards compatible.

I think Win7 ships with DX 11, and it is backwards compatible.

 

This means that games made for DX9c (FSX) or DX10 (an option for FSX) can still be played on a platform that has DX11 installed.

 

The DX10 option for FSX is, again as I understand it, an unfinished product.

Which is why it is called DX10 preview.

This unfinished product causes all kinds of problems and artifacts but the DX10 fixer is supposed to fix those problems.

I dont use DX10 at the moment (FSX option unticked), but it sounds like it is doing a good job and I think that 35$ for all the work that went into it (to fix things microsoft did not finish) is not that bad.

DX10 Preview with or without SteveFSX fixes will use memory more efficiently than DX9, like with high res planes and airports, that's why a reduction in OOMs is apparent with DX10. However, any way of reducing memory load reduces OOMs, like reducing texture sizes, Autogen, water effects, or LOD radius. LOD radius does not have to come down much to save a lot of resources if the autogen, mesh, and detail is set high.

The way I understand it is that DX versions are backwards compatible.

I think Win7 ships with DX 11, and it is backwards compatible.

I'm afraid your understanding in wrong. DirectX 11 is only backwards as far 9.1 - so 9.0c (needed for FSX) is not included. DirectX is shipped with Windows 7 but also needs a graphic card that supports DirectX 11, it not it won't give the features of DirectX.

 

Prepar3D v.2.x uses DirectX 11 but it also still needs for DirectX 9 and includes it in in requisitions.

 

 

Quote from Zach Heylmun on December 13, 2013, 09:37

Hey Mr. Karl,

DirectX includes the software for handling the wide variety of input supported by P3D, and while we don't use Dx9 for any rendering, the library is still used for some input and sound functionality. Did you by chance install using the .msi? If so, you unintentionally skipped installing the per-requisites for the program. It is perfectly valid to install the 9.0c run time on a windows 8 computer, otherwise most PC games wouldn't be able to run on W8.

 

Zach Heylmun

Software Engineer - Prepar3D® Team

I'm afraid your understanding in wrong. DirectX 11 is only backwards as far 9.1 - so 9.0c (needed for FSX) is not included.

 

Oh ok, that is possible, I have to take your word for it.

I am no software specialist, but I was trying to explain things to SAEB99 who is even more confused about DX9, DX10 and DX11 than I am, lol.

 

So when you install FSX, it will install the required DX9.0C and that is why the game works even when Win7 is shipped with DX11?

And uninstalling DX11 from Win7, then re-installing DX10 is not required (nor possible I think) because DX11 (which he has on his system) is backwards compatible with DX10?!

 

For the purpose of trying to explain what FSX is using and why DX10 needed fixing and why this costs 35$ it does not change much though.

Right?

 

I mean FSX still does not use DX11 even if SAEB99 has that installed (like most of us) according his DXDIAG readout (see post #26)

FSX uses DX9.0c unless you click the option for DX10 preview.

 

And DX10 in FSX was not finished.

Steves DX10 fixer fixes (most of?) this.

You are not paying another 35$ to be able to fly the PMDG777, but you are paying 35$ to fix FSX DX10 preview. And that seems to have been a lot of work, so 35$ is fair I guess.

 

I fly the PMDG777 in DX9.

With GEX (worldwide) and UTX (where available) + REX clouds I usually still have 1.0GB free VAS with the PMDG777.

So if I add some departure and arrival addon that is relatively light VAS wise, or maybe just corrected AFCAD files so the runways and navigations aids are correct, then I should have no problem. (still testing my new setup).

 

Any HD airports on top of what I have (or on top of something like FTX Global) will require, it seems, FSX be run in DX10 preview mode and the DX10 fixer.

Shutting down FSX, and restart/reload is another proven option: It will clear the VAS "remains" from your departure and cater for increasing VAS demand during your approach
 

I was thinking someone should write a program just to do that without shutting down

FSX  if Possible.

VAS use shown depends on the software that measures VAS, some only show the peak used and so never drop until the app is restarted and measurement begins again. However, if the app measuring VAS used by FSX does actually show current VAS only ever increasing, it is more likely you are linking a process to FSX that does not give up memory used, and is said to be leaking memory. Shutting down and restarting is not a proper solution. A better solution would be to remove the process that leaks memory. Pare down the sim back to stock condition, then introduce the .dlls, addon airports, or planes one by one and monitor VAS.

So when you install FSX, it will install the required DX9.0C and that is why the game works even when Win7 is shipped with DX11?

Yes, that is correct.

 

And uninstalling DX11 from Win7, then re-installing DX10 is not required (nor possible I think) because DX11 (which he has on his system) is backwards compatible with DX10?!

It isn't practical because DirectX 11 is an integral part of Windows 7. Anyway, DirectX 11 includes 11.x through 9.1

 

And DX10 in FSX was not finished.

Yes, but there are two things are that are needed. First DirectX 10 must be installed as part of Windows, and second FSX must contain the code to use it - the tweak".

Why are people using DX10P if the PMDG manual clearly states NOT to use DX10P? It's not even DX10, but a preview and it sucks. So many sceneries and aircraft go nuts with this option. Don't use it if you don't want more problems than solutions.

PMDG may not recommend the DirectX 10 preview for its add-ons, but many people use it with no problems. See the DX-10 Discussions, Hints and Help on AVSIM.

Why are people using DX10P if the PMDG manual clearly states NOT to use DX10P? It's not even DX10, but a preview and it sucks. So many sceneries and aircraft go nuts with this option. Don't use it if you don't want more problems than solutions.

 

You need to to more research.  DX10 without the "Fixer" is a problem, with the "Fixer" it is much more FSX freindly than DX9; and if your system is relativley current, FSX will run much smoother with more eye candy albeit likely with less FPS.  FPS is not the problem with DX10 that it is in DX9.  You have to see it to beleive it.  Trust me:lol.

 

To answer an earlier question, FSX was written for DX9.  DX10 was but a distant thought and the DX10 Preview was not intended to be used for flights, only give us an idea of what FSX could look like at some future time.

 

There is plenty of documentation available if you want to upgrade your machine and FSX without having to spend tons of money on hardware by using Steve's DX10 Fixer.  Just search here and on google etc.

 

My two cents

Rick S.

VAS use shown depends on the software that measures VAS

 

I use ProcessExplorer from sysinternals to show VAS while running FSX. Recently I was hitting 3.8GB landing the 777 at aerosoft mega EFHK (all addon settings maxed) with a few other VATSIM planes present there. With DX10 it don't exceed 4GB vas anymore because the vas useage seems more stable so I can tweak / control things better. I increased my FSX texture setting to 7cm.

 

FPS is not the problem with DX10 that it is in DX9. You have to see it to believe it. Trust me.

 

I keep seeing people say this, and yet that is not what I see on my PC. I have used DX10 with Steve's Fixer utility, and the framerates appear to be no different to those in DX9 mode......and with inferior graphical quality. Yep, that's right. I said inferior, because that is what it is. The AA and AF in DX10 mode cannot match 8xS AA, 2xSGSS, and 16xAF in DX9 mode on my PC.

 

The only advantage with DX10 mode (again, on my PC) is that it reduces the risk of an OOM. A rather big advantage certainly, but that's the only improvement that I see between DX10 and DX9.

 

 

The only advantage with DX10 mode

 

And don't forget the Cockpit shadows, cannot fly without them now.

I was one of the folks who thought that FSX in DX9 was just as good as FSX + the DX10 Fixer

I was very wrong, once you have it set up correctly it blows DX9 away.

 

However I am now running P3Dv2.2 exclusivly as it runs and looks much better on my system, but if I ever went back to FSX it would be with DX10

I know how to set up FSX in DX10 mode. It simply does not look as good as DX9 mode on my PC.

I hope you get your IQ issues sorted out in DX10 Christopher, you will really enjoy it when you do.

I also had problems getting my AA looking as good but got there in the end with some messing about in NV inspector, the bioshock setting and enabling Aero seemed to do the trick

After that it was hard to go back to DX9 after flying for some time with the Cockpit shadows and it was those shadows that finally pushed me toward P3Dv2.2 which is graphically spectacular.