I've been struggling with OOMs even though I have a new computer.

I could make an OOM error consistently by just flying over Aerosoft's US Cities Los Angeles, especially with the Coolsky's/McPhat DC-9. I couldn't even get near LAX.

Then I read these forum on using DX-10. I made the changes, downloaded and installed the suggested files and....VAVOOM!!

Now I can fly circles around Aerosoft's Los Angeles and FSDT's LAX with the DC-9 as smooth as butter.

I can't believe the difference.

FSX seems like a brand new sim again!

I'm almost afraid to celebrate. The dream may end :mellow:

Certainly interesting. Seems like overall its hit and miss for people and its split down the middle as to its benefits vs reverting back to dx9.

 

Doesnt seem to be too many addons code for dx10 in the first place or at least dont market it that way.

 

That is great for you though! Might have to consider it with all these fancy sceneries and high depth high quality aircraft coming out.

Same here...directx 10 is just amazing altough it's a preview in fsx.

Huge improvement overall and now my Js4100 works as it should even with icing effects turned on!

On the downside I have a lot of scenery not compatible with directx 10.

You can give Addon Converter X a try and see if it fixes any scenery / aircraft incompatibilities (think they have a free trial).

For me, there is no way back to DX9. DX10 performance and smoothness in my system is just great.

 

<snip>

FSX-SP2 DX10

 

The features we do have are:

1) VC shadows

2) HDR Bloom

3) Water enhancements

4) Efficiency improvements via more Autogen batching, more efficient shaders, and a more efficient method of generating bloom.

<snip>

And the lack of FSX-SP1 level backwards compatibility is the key reason why what we decided to label the FSX-DX10 work “preview”.

 

Here are two screenshots to show the efficiency of the water and bloom improvements, taken on a 2.4 Ghz Intel Core Duo, with 1GB of RAM, and a GeForce 8800 GTX.

<removed dead links>

That is 20% better FPS under load.

 

Phil Taylor's Blog

 

 

Cheers.

Here is a test for you and your DX10. download the new FSDT CYVR with the NGX , and see what your VAS is. More importantly if your session survives.

You can definitely run out of memory with DX10. Anytime I fly the ConcordeX between London and New York with FDSD New York and EGLL scenery I get the OOM usually just after landing....at least I make it to landing in the first place. Having said that with DX10 and Addon Converter X, there is no way I would ever go back to DX9.

 

Interesting comments on CYVR airport, I did not want to buy because of OOM's and looks like that is proving to be the case.

Dont you run into aircraft and scenery incompatibilities and issues for products not marketed and coded for dx10?

 

What about just default stuff?

Don’t need FSDT CYVR + the NGX to kill the system; I can easily do that using Eaglesoft’s Citation X with default KSEA,ORBX PNW and REX+OD installed.

 

VAS limitations are not DX10 fault. FSX is the culprit (legacy x86 code with backward compatibility plus memory leaks and who knows what else.). I wrote a small app (for other FSX purposes) that on a side line seems to help with OOM’s, not fully tested, but at least I can now land and park without killing the system. No gain you FPSs thought.

 

 

Cheers.

Dont you run into aircraft and scenery incompatibilities and issues for products not marketed and coded for dx10?

What about just default stuff?

 

Nothing will be coded or marketed for DX10. No FSX commercial developer in their right mind would sell their product as DX10 compatible. DX10 Preview is a tiny, tiny glimpse into the capabilities of this higher level technology (which is now very old as DX11 and DX12 has arrived since). Since FSX is not under further development, there will be no more coding for DX10, and never for DX11 or DX12. If the Microsoft developers would have stayed in business, FSX probably would have been upgraded for compatibility with DX12 by now or a whole new product would have been released. Steve's Shader10 fix provides fixes to issues found with the original DX10 Preview. DX10 Preview works with every FSX product but, if you don't install the fix provided by Steve, you'll see issues that the Microsoft Aces Team was unable to fix before release of SP2 and Acceleration way back in 2007. For me, DX10 Preview and Steve's fix works for every product I own but, under certain circumstances for some products, I will see anomalies. Like flying at night into FSDT KORD. I know the taxi/runway lights are not lit and instead there are dark squares but it works great during the day. I hate flying at night as it requires more system resources and it is sometimes difficult with FSX products. So I can handle the issues (anomalies) with night lighting. If FSDT said the product was DX10 compatible, everyone would be jumping on them for the tiniest anomalies found and they might not be able to fix it because of the old FSX engine. The lights can be fixed one day and, based on the comments of the developer of FSDT products in another thread about the release of CYVR, I expect there will be an SP issued someday to fix this issue because the developer knows his products works better in the DX10 environment. But he doesn't have to make it DX10 compatible as the product was made for FSX/FS9.

 

All of the default FSX products should be fully compatible for DX10 BUT, they don't have to be as Microsoft did not develop FSX to be DX10 compatible, only DX9 compatible. Fortunately, we have bright persons like Steve who are trying to enhance FSX just a little bit more for all of us and maybe fix some of the anomalies found in the original product.

 

Best regards,

Jim

For me, DX10 Preview and Steve's fix works for every product I own but, under certain circumstances for some products, I will see anomalies. Like flying at night into FSDT KORD. I know the taxi/runway lights are not lit and instead there are dark squares but it works great during the day.

 

Thank you so much for this explanation. I was wondering what all the flurry of DX10 threads were about. Several kind members of AVSIM pointed me to Steve's site and I installed his DX10 fixes. The performance increase was outstanding, especially when using Word Not Allowed's tweaks and getting the NVIDIA inspector settings good.

 

I have many FSDT airports and I love flying at night, so the fact that night textures did not work at these airports was the deal breaker for me and I went back to DX9. However with the significant performance increase I got, I am considering uninstalling these airports and going back to the original FSX ones. If the developers could release a service pack to update the night textures, I would switch back in a minute.

Ya, night lighting missing from addon airports is a bummer, but in the testing I have done I'm seeing in most cases 10 more fps betwedn Dx10 vs Dx9. That makes all the difference when weather gets heavy.

I just made a trip from FSDreamTeam's CYVR to their KLAX along with Aerosoft's US Cities Los Angeles, using about 40% AI in the Captain Sim Boeing 707 in DX10. The skies were filled with REX clouds from the Opus weather engine.

No problemo (:

Very smooth flight. I even went over top of Aerosoft's US Cities San Francisco without a problem (I could see the Golden Gate Bridge from FL320).

I started out with 60% AI, but getting close to LA I started getting a message that SimConnect requests that I lower my AI because it is getting over 1000 simultaneous requests (whatever that means), so I lowered it to 40%.

That flight was over 1000 miles.

After landing, I went back and took off again, going back to the IAF for another approach and landing at Rwy 25L. Still no OOM.

One would have a hard time convincing me that DX10 didn't make a difference. I would NEVER have been able to do a flight like this before with DX9 settings.

I'll have to check out the night problems.

Next flight will be with the NGX, although I was getting quicker OOMS with Coolsky's DC9

Whoops! After sitting at the gate typing this post, I just got an OOM error. That is still not bad though. A big improvement over what I had.

Dont you run into aircraft and scenery incompatibilities and issues for products not marketed and coded for dx10?

 

What about just default stuff?

 

Older aircraft releases probably have a problem, but I think most newer payware aircraft are good with DX10.

I never use default aircraft, so they wouldn't matter.

Funny this should come up,

I tried this last night myself.

Does anyone else get the FSX splashscreen momentarily on the aircraft textures?