DX9 +ENB series+shade+REX

What is this gentleman, Steve going to fix still? I have yet to try dx10 sure to the night issues.

 

Sent from Samsung Galaxy Note 2

Several incompatibilities.  You'll have to check out the DX10 Forum for details.  PaulJ is keeping on top of the upcoming fixes.  It's not a for sure thing though as nothing is guaranteed to work for everyone.  Personally, I'm completely satisfied with all the fixes he has done to date.

 

Best regards,

Jim

Just shows we're all not running Playstation 3's here. Everybody's experience will be different.

Some necromancy brought this thread up from the grave, but I missed it first time around...

 

I've gotten hooked on DX10 with its enhanced visuals and performance.  I've had a few times where its shortcomings irritated me enough to switch back, but that lasts only for a few days.  The switch between the two is at most a five minute operation (at least for me).  If I do night flying I usually switch back to DX9.

I guess some of you guys use extremely high LOD values because blurry textures are more noticeable with larger, higher resolution, widescreen monitors? I use LOD=4.5, and I do not have a problem with blurry textures in the distance, but I am still running FSX at 1280x1024 resolution on a standard 19" TFT monitor.....

DX10..Since doing so I havent had an OOM,CTD or "FSX has stopped working". I can fly the PMDG NGX with ORBX scenery to my fat hearts content.

I've been using the DX10 since ever..

It's better for the whole FSX stability and it boost the performance quite a bit!

But lately, I found out that alot of people are having much better graphics in FSX with ENB shader..

I also tried SweetFx but I didn't like it, switched to DX9 and couldn't be happier.

My understanding is that RadeonPro fixes this, at least i'm pretty sure that user "cvearl" said that.  

 

I tried DX10, really like it; but found that EGCC xtreme with AES just looked awful at night, solid grey textures. In the end too many compromises, so i moved back to DX9

True. Radeonpro is like nvidia inspector for ATI. It does lock vsync no prob. And it has Dynamic Framerate Control where you can set a max frame rate. So I lock at 30 and set FSX to unlimited. This works smoother and with higher frame rates than with no lock and 30 set in FSX. With nvidia it was the other way around for me. Smoother with 30 set in fsx and no external limiter.

 

DX10 needs add on dev support at this point. Its no longer bugged. But many add ons have not been optimized or tested wiwith it it seems.

This turned out to be a lot closer than I expected. If I did the tally correctly:

 

DX9:   38

DX10: 31

 

FWIW, I am very reluctant to buy any add-ons that are not DX10 compatible now.

I am bored of switching for different usage. DX9 for night lights of some airports and DX10 for no CTDs.

Recently moved to DX10 and won't go back.  The only issues I have right now are the OrbX "night lighting" flashing.  I can live with disabling that and just having the lighted ground textures similar to how default does it.  I believe eventually those will be fixed anyway as FTX redoes their night lighting as I believe they said would happen as part of making their older products come in line with FTX Global's new night lighting.  (pretty sure I read in one of the big FTX Global threads over there that John said that was going to happen)  I don't own any of the big addon airports that have the gray textures issues, and never really planned to, so the only thing I lost was some misc. freeware planes I downloaded years ago before I could really even run FSX and never used them.  Most were silly things anyway like UFO's and such.

I revert to DX9 when I'm using add-ons that are not DX10 compatible.  I don't mind switching back and forth.  With my specs, DX10 seems smoother and faster.