I forgot about that. About 90% of my add-ons aren't DX 10 compatible. Well, that's out of the window.

Hi all,

 

Ok so today I flew OMDB Dubai to VHHX Kai Tak both FlyTampa, using the 777 and real world weather from REX and I have to report, no OOM at Kai Tak, which I got last time I tried to fly there with the 777 in DX9 mode. I even included a hold at CH vor, nearest one to Hong Kong.

 

Ok so I'm not getting huge frames per second only 19 in the cruise, fixed at 32! but it's silky smooth and doesn't look like only 19fps. weird. 

 

More flights are obviously needed to test this more, but so far I'm really impressed with DX10. Someone above asked what you have to do to run DX10. Well simply flick the DX10 preview mode switch in the settings menu, and restart fsx and your in DX10 mode. You will need to buy Steve's scenery fixer to correct any scenery problems, it's about £20 and just runs in the background. However you can try DX10 without the fixer just to get an idea most things work fine.............You can switch back whenever you want too, flick the switch and restart fsx, that's it. 

 

I think the reason DX10 doesn't cause OOM's is the fact it causes the CPU to run some of the GPU processes, I believe!

I forgot about that. About 90% of my add-ons aren't DX 10 compatible. Well, that's out of the window.

You know, the whole OOM thing is not too much of a problem for me as I tend to do relatively short flights (3hrs max). I want to go to places I have never been before. As in land there, try different approaches there, go arounds, visual cirquits in areas with difficult terrain around, etc.

 

So an Amsterdam to Dubai flight would keep me bussy for days if not weeks.

I would land in a couple of mountain airports in Eastern Turkey, maybe visit Teheran and a few other mountain airport in Iran. Each flight would leave where I landed durin the last session. Those flights would be short (and I guess unrealistic) but I would have fun and I would never OOM.

 

But even if you want to do a realistic long haul flight, that is possible too.

I think if we all just become a bit more "VAS aware" then we could adapt our actions and prevent OOMs.

 

You need "process explorer" so you can have a look at how much VAS you are using.

By looking at it during the course of a flight you can develop a feeling/experience on how much your VAS usually goes up during the flight.

(in my case about 100Mb per hour it seems)

 

Examples:

Just take a look where you are with your VAS level when you start a flight.

If it is low (2.5Gb or less) chances are good you can do that 12hr flight no problem.

(unless your destination is something like Manhattan X or unless your VAS goes up way faster than mine)

 

If you start your flight with very high VAS (if I start from Manhattan X I am sitting at 3.6Gb from the get go!) then I would just save my flight, and restart FSX after reaching top of climb. This clears the departure scenery, etc out of VAS and I can continue the flight from here with probable something like 2.0Gb VAS and thus ample room to grow.

I performed a 10+ hr flight ( don't remember exactly now ), sometimes using "cruise time compression", witout an OOM.  As a matter of fact, on the many flights I performed in FSX Gold with these 777, I never experienced a OOM.

 

I am on Win 7 Home Premium, 16 GB DDR3 RAM, i5 2500 @ 3,3GHz, and a Geeforce GTX 650 Ti 1GB GDDR5 graphic card.

 

Was only using default FSX scenery, and edited  DLL.xml before each flight to make sure only the required DLLs would come into play.

 

Also, never experienced any dramatic, down to stuttering, low on my FPSs.

 

I should say I used FSX as my PMDG 777 platform. It was there to give me the plausible scenery for the World it includes, nothing more & nothing less. Ah! not absolutely tru - I used a weather injector I was beta-testing and sometimes FSGRW too.

 

Never OOMd, never stuttered :-)

FSX is a game of trade-offs; you've got a 5-lb. sack and you can't put more than 5 lbs. in it. So, there are choices to be made depending on your style of flying. I have too many add-ons that are not DX10 compatible, so I run DX9. I can do so reliably by reducing autogen to the minimum (I'm focused on the runway when landing, not counting the number of buildings with orange roofs) and reducing LOD to 4.0 (there's no visible difference to me compared to the default value of 4.5 and again I'm focused on the runway, not 20 miles past on the horizon). Using these settings with AS2012, GEX, UTX, and My Traffic 4.5c set to 25-30 percent AI, I've flown the 777 on flights of 8-12 hrs into the most demanding airports FSDT, FlyTampa, Flightbeam can offer with absolutely no OOMs ever, although I did come close once flying into FSDT JFK with Drzewiecki's NYC photo scenery. FSX was beeping with VAS at 4.001 GB (yes, there is a little slack in the system), but I made it to the gate, shutdown, and deboarded without crashing.

I forgot about that. About 90% of my add-ons aren't DX 10 compatible. Well, that's out of the window.

Not exactly out the window. DX10 fixer makes most airports DX10 compatible. I have over 450 entries in my scenery cfg, and every airport works in DX10. The only airports some may have trouble with would be fs9 port overs. ( and how many people are using those).

So, 100% of my addon airports work in Dx10.

 

 

PMDG777 is not DX10 either.

It is Rob.With the freeware fixer and the payware one. The reason PMDG state it is not in the intro manual, is they won't offer support for it. That does not mean it does not work. Aerosoft say the same.

I'm planning a flight from EGLL to KSFO for Saturday. This is about 10 to 11 hours. I'll be monitoring VAS hourly. I never really OOM, but I'm just curious.

Not exactly out the window. DX10 fixer makes most airports DX10 compatible. I have over 450 entries in my scenery cfg, and every airport works in DX10. The only airports some may have trouble with would be fs9 port overs. ( and how many people are using those).

So, 100% of my addon airports work in Dx10.

It is Rob.With the freeware fixer and the payware one. The reason PMDG state it is not in the intro manual, is they won't offer support for it. That does not mean it does not work. Aerosoft say the same.

Ok thx. I am going to stay with DX9 for now. But if I ever decide to change, that is good to know.

On the topic of disabling "in-between" sceneries, lookup a tool in the file library called "Scenery Config Editor". It allows you to enable/disable whatever you want in your scenery library without having to start-edit-restart FSX to do changes. 

Never OOMd, never stuttered :-)

I would be more interested what VAS you had at the beginning of the flight and what at the end!

 

If you (just like me) have VAS going from 2.5Gb to 3.5Gb during that 1hr flight...then ok, thx for the info but nothing I can learn from your setup. Same here.

 

If on the other end you start with 2.5Gb VAS and after 10hrs still only have 2.6Gb used.....then I would want to know what settings you are using, DX10 or DX9, FSX.cfg, what scenery addon, etc etc, and learn from your info.

Ok thx. I am going to stay with DX9 for now. But if I ever decide to change, that is good to know.

Keep it in mind Rob. For the price of one addon airport, the payware fixer is the way to go. The freeware one is good too, for those that run just default airports ( some do ). Paris Orly looks stunning in DX10 btw.

Having only two - even if these are two rather large sceneries - activated, may work and not get You close to the "4GB limit".

If for instance though You also have other sceneries activated "in between" and "en-route", then an OOM will become way more likely.

.......

In other words:

 

It may be hard to turn them off as they really shine when being looked at from "high above" - but it is also a fact that photorealistice textures always demand far more VAS then repeating LandClass textures for instance.

So then it may be up to testing individually.

 

........

This is just one example, but i just want to point out again, that OOM's have no real predefined pattern and depend on various factors!

It is proofen though however, that the chance of experiencing an OOM rises noticeably when a large amount of individual sceneries are activated, real world weather delivers heavy clouds, high res textures are being used and lots of AI traffic circles around in the sim.

On that 15 hour flight I mentioned, I passed in the vicinity of good quality airports at the following: Phoenix, Denver, Chicago, Philadelphia, NY, London, Amsterdam, Dubai (Aerosoft, Flightbeam,FlyTampa, FSDT, Imaginesim, Sunskyjet, UK2000).  And I never said anything about I like looking at my scenery from 35000ft - just that I refuse to deactivate scenery.

On that 15 hour flight I mentioned, I passed in the vicinity of good quality airports at the following: Phoenix, Denver, Chicago, Philadelphia, NY, London, Amsterdam, Dubai (Aerosoft, Flightbeam,FlyTampa, FSDT, Imaginesim, Sunskyjet, UK2000).  And I never said anything about I like looking at my scenery from 35000ft - just that I refuse to deactivate scenery.

Lets talk again if you ever get an OOM hey ;-)

How exactly do we do this DX 10? Is it just on the FSX Settings page or are there any external programs I need to download?

 

It's been a few years since I last OOM'ed. It used to happen a lot on my old computer. I am just expressing concerns over my imminent purchase of the PMDG 777... and it would be pretty bad to spend 90$ when on every long-haul you do; you OOM. 

Hi Luke!

For DX10 - have a look here:

 

http://forum.avsim.net/forum/569-dx-10-discussions-hints-and-help/

 

and here

 

http://forum.avsim.net/forum/644-the-official-dx10-scenery-fixer-support-forum/

 

There is a - also in my opinion - great tool, named DX10 Scenery Fixer Tool available nowadays via the FlightSimStore - and it definitely fixes a lot of issues FSX suffered from under DX10 - not all issues, but a lot!

But again - for more info:

Please feel free to have a look at the links posted here right above.

Cheers, Christoph

 

I would be more interested what VAS you had at the beginning of the flight and what at the end!

 

...

 

Hi Rob!

I will look forward to upload some screenshots from my VAS measurements if time allows it - maybe this weekend, but no promises!

Sure - also on my PC VAS does rise under DX10, but by far not as much as it did under DX9 and most important of all - it remains far more stable!

But again saying:

I will look forward to upload some screenies here, as they may tell more than a thousand words.

Cheers, Christoph

 

On that 15 hour flight I mentioned, I passed in the vicinity of good quality airports at the following: Phoenix, Denver, Chicago, Philadelphia, NY, London, Amsterdam, Dubai (Aerosoft, Flightbeam,FlyTampa, FSDT, Imaginesim, Sunskyjet, UK2000).  And I never said anything about I like looking at my scenery from 35000ft - just that I refuse to deactivate scenery.

... well:

Trust me: If FSX would allow me to do so, i'd leave it all turned on and maxxed out (and i am sure we'd all make it so) - i mean that's what good sceneries and add-ons are about - to be used! :wink:

All i said though was that the compromise(!) of turning off some scenery on long haul flights at high altitudes may be a compromise(!) (yes, that's what i wrote) worth to be considered, because many details are not visible at higher altitude anyways, while on the other hand running into an OOM may be avoided by turning them off - that's all - okay - therefore please, no worries:

Because even if You'd like to watch out the window whil in flight and see and enjoy it all, it'd fully okay! :wink:

So if You refuse to turn off any scenery - good, go on, seriously:

As long as it works, there is no need to worry!

If however (and only then) You may once encounter an OOM ... - then, turning off some sceneries might be a help- and useful compromise on longer flights at higher altitudes.

That's all. :smile:

Cheers, Christoph

I would like to add that if you own a 7000 series AMD card or maybe also HD6XXX series i would stay away from DX10 as you will get artifacts and corruption with every driver out there and AMD does not support further DX10 in FSX.

 

I have testet this over the last 3-4 weeks now with a couple of other guys and the solution is Nvidia (GTX780) instead of my brand new HD7970GHZ Edition.

 

look here :

 

http://forum.avsim.net/topic/422802-serious-issue-with-ati-and-steves-dx10-fix-tears-and-spikes-everywhere/

 

 

Just to clearify this goes with and woiuthout Steves DX10 Fixer