No, but I heard you could just point the installer to the P3D v3 folder.

 

And they won't release P3D v3 installers anytime soon...

 

http://www.flytampa.org/forum/viewtopic.php?f=1&t=7737

Happy to oblige!

 

I did my first full flight last night from Fly Tampa CYYZ to FSDT CYVR in the PMDG 77W flying over the recently released UTX Canada v2.  In P3Dv2 this would have been a guaranteed OOM for me but there was no OOM, and my FPS were noticeably better (at CYYZ I was in the high 20's consistently rather than the mid to high teens).  I was running ASN for weather and REX4/soft clouds for textures.  I'm very happy with what LM has done with v3, bravo!

May I ask what your settings were at?  Are you able to have things close to maxed out?  Even flying between these two airports?  Or do you have to turn things down?  I've been watching v3 from afar so far.  Waiting to see real scenarios prove that VAS issues are (mostly) gone before buying.

May I ask what your settings were at?  Are you able to have things close to maxed out?  Even flying between these two airports?  Or do you have to turn things down?  I've been watching v3 from afar so far.  Waiting to see real scenarios prove that VAS issues are (mostly) gone before buying.

 

From  tests done by FSDT the savings is around 600mb more or less . Thats a room to fill with LOD ,HD and some other sliders or GSX etc etc

 

Michael moe

May I ask what your settings were at?  Are you able to have things close to maxed out?  Even flying between these two airports?  Or do you have to turn things down?  I've been watching v3 from afar so far.  Waiting to see real scenarios prove that VAS issues are (mostly) gone before buying.

Sure:

 

Lod ultra, tessellation factor high, mesh 10m, texture res 1m, water detail medium, all scenery objects dense, special fx detail high, sfx distance medium, aircraft ai traffic 34% (using mt6 this provides a normal amount of traffic).

All I can say after all the years of watching the back and forth. I believe LM nailed it! 

 

Ye i think V3 is great, loving it,  loads of little extras and options in there.  Enjoying getting my Ad On's installed. Slowly but worth the wait.    

 

 

Also a big thanks to our Beta tester Rob,  fantastic job there Rob   :smile:

Greetings All,

 

Quick question, Rob mentioned disabling a few BGL's in FlyTampa's scenery to enhance performance... I tried searching but didn't come up with anything, and hate to be redundant if this is a known tweak, but could someone link or pass along what he recommends disabling?

 

Thanks!  Loving v3!!!  So far everything I've tried has worked great.

Greetings All,

 

Quick question, Rob mentioned disabling a few BGL's in FlyTampa's scenery to enhance performance... I tried searching but didn't come up with anything, and hate to be redundant if this is a known tweak, but could someone link or pass along what he recommends disabling?

 

Thanks!  Loving v3!!!  So far everything I've tried has worked great.

 

I search for "Flytampa EKCH" and Robs post came along . Think it might be this one  :wink:

 

http://www.avsim.com/topic/468824-oom-workaround-for-flytampas-copenhagen/page-5?hl=%2Bflytampa+%2Bekch#entry3241494

 

 

allthough i have no issues at EKCH my self

 

Michael moe

LM has done a great job with V3 no doubt, but I can't help but keep wondering about a lot of the VAS claims when one of the biggest offenders--ORBX global products--haven't been released for V3 yet. Are we all celebrating too early? Vector chews up not only VAS but I think some CPU cycles as well...

LM has done a great job with V3 no doubt, but I can't help but keep wondering about a lot of the VAS claims when one of the biggest offenders--ORBX global products--haven't been released for V3 yet. Are we all celebrating too early? Vector chews up not only VAS but I think some CPU cycles as well...

 

No because ORBX is not the reason for memory leak or been building up during flight and not released . The work of P3Dv3 is why my Flytampa Dubai OMDB shows 600mb less VAS in P3Dv3 vs P3Dv2. (can be compared as ORBX Global might not add to much VAS to the area in V2)

 

Adding ORBX,Vector etc is just like adding a new plane or something else to the equation but i now have 6-700mb more to spend  and even better ,   The memory seems to NOT build up during flight. Thats the BIG different.

 

Michael Moe

I think Global doesn't add VAS at all: the textures look better but have the same size etc. as default... Vector however does indeed eat VAS. The question is: how much. It seems that most people have around 500 to 700 extra VAS headroom with v3: the question is how much VAS Vector eats. But in the end the MAIN difference is indeed that VAS doesn't build up anymore: THAT was the main problem. 

 

The next question is: when will developers start to fill up the extra headroom we have now... History has proven that if there is a gap left somewhere, someone will fill it up somehow. I do believe that in the end LM still has to go for 64 bit: cleaning up memory management first was a very, very wise decision, and we all reap the benefit of that now already, but in the future we still need 64 bit.

 

And then the next question will be: if we get 64 bit and a lot more memory to load things into, how much will that hurt performance! Some think 64 is the solution for all problems but it seems to me it solves a few problems but brings new ones too. But er... this probably is beyond the scope of this topic... so let me end with a BRAVO indeed!  :wink: