Yes Ben I actually overclocked my 680 a bit which I do not believe in but it actually helped, shouldn't have to OC 4 gig card oh well all in good fun.

 

You probably are getting a decent bump in performance over me... I am stuck here with a GTX660Ti

I tried the demo of YVR and performs worst then KLAX. Wish it would be as good the FPS as KPHX of Flightbeam. It performs good and steady. I ll try later to overclock a bit my GTX470 see if it helps if not I ll get this scenery when I upgrade to the 680

I tried the demo of YVR and performs worst then KLAX. Wish it would be as good the FPS as KPHX of Flightbeam. It performs good and steady. I ll try later to overclock a bit my GTX470 see if it helps if not I ll get this scenery when I upgrade to the 680

 

I believe Its your CPU, not your graphics card which is the issue. I get 30FPS (locked) with my Intel i5 2500K OC to 4.7 ghz.

I got an i5 3570k @4.4 I might try go higher

just tried the demo with 737ngx800 on the ground got between 22 to 25 fps in vc view so iam happy with that being on the ground with orbox and rexe as well

This airport is actually very optimized. I really shouldn't be complaining that it actually USES my GPU. GPU usage was around 80-100% on approach.... These new FSDT airports are actually requiring powerful GPUs to keep the FPS up.

 

Yes, that's the main idea behind it.

 

The real problem with FSX is that it's too CPU intensive, when using scenery made with legacy FS8/9 code.

 

By getting rid entirely of any single line of FS8/9 code in it, and relying more on shaders, we are putting more workload where it's supposed to go: on the GPU.

 

Which of course makes sense, since it's definitely easier to upgrade a video card, than the entire system to support a newer CPU, which is not giving the same benefit anyway, since CPU are keep increasing cores and multi-threading efficiency, but FSX can't get so much benefit from it, unless you over-clock like mad, but with this kind of scenery, over-clocking alone is not enough (it might, with sceneries with a lot of legacy code), there must be a fast GPU too, otherwise a screaming fast i7 over-clocked to 4+ ghz, would just wait for the "slow" GPU to finish its thing, before being able to supply more data.

 

A system should be well balanced, unbalancing in favor of the CPU, as it was usual wisdom with FS9/FSX until now, is not so effective with a GPU-intensive scenery like this.

Gonna be a great addition to Vancouver+ 3 by FSAddon!

Does anyone know how it compares with UK2000's Heathrow Xtreme in terms of frame rate?

Yes I look forward to hearing more about this airport from people with the whole kit - Orbx, Vancouver v3, GEX NA, UTX, REX, Opus, UT2.

 

I am out of town so have another week or two to decide on this. But I have been looking forward to it for a long time.

Orbx doesn't seem to address the duplicate files you end up having if you buy some of their payware addons or other addons and use them with their scenery. I have no idea why. But my guess is besides the CYVR files you need to remove from the ORBX scenery folders there might be a seaplane base file or 2 as well. Also if you have Orbx scenery, say KORS, you need to go into the main PNW scenery folder and remove the 2 KORS entries as well. That also will cause OOM errors in the region. Just FYI.

 

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

I tried the demo of YVR and performs worst then KLAX. Wish it would be as good the FPS as KPHX of Flightbeam. It performs good and steady. I ll try later to overclock a bit my GTX470 see if it helps if not I ll get this scenery when I upgrade to the 680

I don't see that on my system which is not that up to date.

I'm getting very good performance just like I do with klax.

Is no one getting OOMs? I have I5 2500k OC with a 660 cad and I'm in low 20s but I have an OOMs within a minute or two. Having been able to enjoy the scenery. Just took down all sliders a notch or two. No difference. LOD is 4.5 now too.

 

What is our VAS on startup?

Is no one getting OOMs? I have I5 2500k OC with a 660 cad and I'm in low 20s but I have an OOMs within a minute or two. Having been able to enjoy the scenery. Just took down all sliders a notch or two. No difference. LOD is 4.5 now too.

 

What is our VAS on startup?

 

I've been getting these too, once I unclick "Force HD Textures" in the add-on manager I'm fine with everything else to the right. I'm running with PNW and Vancouver V3 with the NGX and this seems to be the only way to make this combo work unless I really dial back something else. It's still pretty solid without the HD textures but I'll continue tweaking to try and make it work.

Tested the trial version.

 

Works perfectly with DX10, constant 30 FPS and smoothness even with maximum autogen density !

What is the best traffic program to use with FS Dream Team's CYVR?