Is this because your running DX10? Your getting super smooth all around and others are getting killed when they look at the terminal. Whats the difference? Hardware specs are somewhat similar and shouldnt be that much of a gap.

 

I'd be pretty sure this is the reason, Dave. I worked VancouverPlus for hundreds and hundreds of circuits, all the time taking consecutive screenshots (with the "V" key mapped to a button) - same circuit, just altering TBM size, BufferPools Pool and RT sizes, and slowly pushing up the settings as they become "solid". This went on until 29.9 and 30 stayed there, without dips - any further increase in most any setting - particularly road traffic - was met with artifacting.

In addition I also start TrackIR via AlacrityPC, have FSX on its own drive, a "custom" pagefile on a separate drive, and the desktop heap mod done in the registry. I have also checked each texture file for the existence of mips and Alphas.

 

Here's a link to the current setting used last night: I'll do some pics with fps showing fps sometime later today. Getting the sim to run like this can be done, and can be done with DX9, too, but it takes a few weeks of dedicated testing.

I'd be pretty sure this is the reason, Dave. I worked VancouverPlus for hundreds and hundreds of circuits, all the time taking consecutive screenshots (with the "V" key mapped to a button) - same circuit, just altering TBM size, BufferPools Pool and RT sizes, and slowly pushing up the settings as they become "solid". This went on until 29.9 and 30 stayed there, without dips - any further increase in most any setting - particularly road traffic - was met with artifacting.

In addition I also start TrackIR via AlacrityPC, have FSX on its own drive, a "custom" pagefile on a separate drive, and the desktop heap mod done in the registry. I have also checked each texture file for the existence of mips and Alphas.

 

Here's a link to the current setting used last night: I'll do some pics with fps showing fps sometime later today. Getting the sim to run like this can be done, and can be done with DX9, too, but it takes a few weeks of dedicated testing.

 

Looking at your screenshots you dont seem to have much AA at all, whats the difference if you get rid of the jaggies?

This airport is amazing!!! I have to wait till servers are updated, so I can't activate. Don't you just love these activation requirements?

 

With the demo it was a steady 30fps without ORBX enabled. With ORBX enabled, dense AG, and the NGX I was in the 20s and smooth. Was not able to check for CTDs. The demo ended before I flew a circuit around the airport.

 

1st impression is that this is probably the best airport I have ever purchased and I got the discount too. :rolleyes:

Looking at your screenshots you dont seem to have much AA at all, whats the difference if you get rid of the jaggies?

Which screenshots are you talking about, Simon?

I have to wait till servers are updated, so I can't activate. Don't you just love these activation requirements?

^_^

Which screenshots are you talking about, Simon?

 

The one in your Dropbox link, just the one with the default 182 in the menu.

Yes - that's the spinning aircraft, and no attempt has been made to fix that. When FSX gets to the flying stage that changes.

 

Here's a link to the old FS9 FlightZone's KPDX (that I'm still dicking around with). These were taken a while ago, but all DX10. AA is still an issue for some folks, but it's improving all the time, and for me, it's quite as good as my old DX9 was.

UPDATE: Umberto from FSDT told me that the OOM I experienced combining FSDT, PMDG, and ORBX can be fixed with DX10 preview, and that did the trick. Since all three products are compatible with DX10 preview, things look and work great now.

:lol: He was lucky!! DX10 is not the fix-all for many folks, and, whereas it will better your chances of not getting an OOM - the real answer is to ensure clean, separate, custom VAS and do that desktop heap fix, close off anything else that's running and taking up precious memory, and wind back the known memory hogs, like cloud distance, LOD and traffic.

DX10 just gives you some more (system memory) headroom and in some respects, a better-looking sim.

Yes - that's the spinning aircraft, and no attempt has been made to fix that. When FSX gets to the flying stage that changes.

 

Ah ok! Thanks, I always used DX9 in FSX, but will be changing to DX10 when i build a new rig.

Paul would you mind posting the exact lines to be pasted into reg value for desktop heap for windows7, thanks a lot. Tried Microsoft fix and checked it and it did not work not sure why. Thinking I should not do this thats why microsoft did not do the update.

 

Just read this: Note: 64-bit versions of Windows have a much larger default desktop heap limit, and you should not hit this issue.T

Thank's for info. BTW, what two files from KORS must be removed?

You don't have to remove any KORS files for YVR to work as it should.

I'd be pretty sure this is the reason, Dave. I worked VancouverPlus for hundreds and hundreds of circuits, all the time taking consecutive screenshots (with the "V" key mapped to a button) - same circuit, just altering TBM size, BufferPools Pool and RT sizes, and slowly pushing up the settings as they become "solid". This went on until 29.9 and 30 stayed there, without dips - any further increase in most any setting - particularly road traffic - was met with artifacting.

In addition I also start TrackIR via AlacrityPC, have FSX on its own drive, a "custom" pagefile on a separate drive, and the desktop heap mod done in the registry. I have also checked each texture file for the existence of mips and Alphas.

 

Here's a link to the current setting used last night: I'll do some pics with fps showing fps sometime later today. Getting the sim to run like this can be done, and can be done with DX9, too, but it takes a few weeks of dedicated testing.

 

Thanks for the info. Perhaps DX10 is the only answer, but seems like there is still too many incompatibilities. Is it just scenery issues? what happens with Complicated systems aircraft like PMDG? I dont think they support DX10.

 

Paul would you mind posting the exact lines to be pasted into reg value for desktop heap for windows7, thanks a lot. Tried Microsoft fix and checked it and it did not work not sure why. Thinking I should not do this thats why microsoft did not do the update.

 

Just read this: Note: 64-bit versions of Windows have a much larger default desktop heap limit, and you should not hit this issue.T

 

I tried the MS fix but didnt help one bit. OOM Crash within minutes. :(

 

Maybe another fresh install will do it. Must be a memory leak somewhere.

UPDATE: Umberto from FSDT told me that the OOM I experienced combining FSDT, PMDG, and ORBX can be fixed with DX10 preview, and that did the trick. Since all three products are compatible with DX10 preview, things look and work great now.

:lol: He was lucky!! DX10 is not the fix-all for many folks, and, whereas it will better your chances of not getting an OOM - the real answer is to ensure clean, separate, custom VAS and do that desktop heap fix, close off anything else that's running and taking up precious memory, and wind back the known memory hogs, like cloud distance, LOD and traffic. DX10 just gives you some more (system memory) headroom and in some respects, a better-looking sim.

 

Hmm, interesting. Can anyone shed more light on this. I was always under the impression that DX10 Preview was a framrate killer. Any comments.

You'll have to go to the Avsim DX10 forum, Mike. Grab the "How-To" doc, and read it a couple of times. It's far too deep for me to attempt to give a precis` of what has taken us five months to learn! No - it's most definitley the other way - it gives back lots of frames.

 

Incidentally - the NGX works fine, too.

 

All the Best,