The EULA doesn't allow you to use it in P3D so you can't discuss how to get it working on the AVSIM forums as its against the TOS.

 

 

Im here waiting for the heavies to show up but theres not alot on the table regarding quality.

 

If what you really mean here is PMDG isn't on board yet ... then yes.  Otherwise there are plenty of heavy P3D options including FSX migrated heavies and mediums -- check out the compatibility list thread.

 

 

Quality Wings 146
RealAir Duke/Turbine Duke
Aerosoft Dublin X

Flight1 Ultimate Traffic 2

 

Top 3 yes, last one no idea.

 

Please, if anyone is discussing the EULA in an attempt to shut this thread down, please don't.

 

 

Why don't they just make it clear with settings that you are at DNE if you want to get the performance they are going for, but leave the settings in for young bold simmers to thrill themselves with.

 

Because there are a lot of people out there that max out everything and say "my system should be able to get 100 fps because I can do that in Call of Duty".  Give them an inch and they feel entitled to the entire planet

 

 

 

I'm pretty sure the 3D lighting on the C172 is calculated in real-time and illuminates all objects

 

Agree, I take that back.

 

Cheers, Rob.

RealAir Duke

Is that the Duke 2.0? If yes, I'm pretty sure it has plenty of issues in Prepar3D 2.x.

 

 

Does P3D come with an SDK?

 

Yes.  

 

Cheers, Rob.

Thanks for all the updates (and vids) Rob!

 

Would you be able to comment if the terrain shadow performance has also been improved (I just noticed in your suggested 2.3 settings that you still run with that off...) 

The EULA doesn't allow you to use it in P3D so you can't discuss how to get it working on the AVSIM forums as its against the TOS.

 

There is a thread on here about installing UT2 into P3D.

 

 

Would you be able to comment if the terrain shadow performance has also been improved (I just noticed in your suggested 2.3 settings that you still run with that off...)

 

I never really liked terrain shadows hence why I don't have them on ... but I'll certainly turn them on and test with them and let you know how they impact performance.

 

Cheers, Rob.

My motherboard and GPU failed together a week ago, so I am currently waiting for a new PC to be built. That being the case, I am seriously considering taking this opportunity to move over to P3D. Is there an expected release date for version 2.3? I think it would be sensible to wait for the release of this version before purchasing, so that I don't have to update very soon after that. Can anyone tell me if the following addons work fine in version 2.2?

 

Quality Wings 146

RealAir Duke/Turbine Duke

Aerosoft Dublin X

Flight1 Ultimate Traffic 2

 

I see that there is a thread regarding the latter on one of the forums here, but I just wanted to make sure that it can be installed and used in P3D (including PowerPack updated schedules and repaints) without any kind of link to FSX. If I decide to purchase P3D, then it will be a 100% commitment (ie. FSX will not be installed).

 

Does P3D come with an SDK? I want to be able to use Airport Design Editor, since I am a "fiddler" when it comes to AFD files :smile:

 

QWSim 146 works perfectly - point the installer to the P3D directory during the install. There is also a P3Dv2 compatible version of their dispatch tool for setting pax/fuel loads and installing new liveries.

 

RealAir Duke v2 works perfectly using the latest 'development build' of the Flightsim Estonia migrator tool, if you install it without the migrator tool it will still work but some of the custom sound (flaps. cockpit switches etc) wont work.

 

Aerosoft Dublin has a native P3Dv2 installer and works perfectly.

 

I currently use Ultimate Traffic 2 as my traffic addon for P3Dv2. I'm running UT2 version 2.09 with the latest schedules installed - I have GA traffic disabled and airliner traffic set at 60%. Sat on the ramp at Flytampa Vienna during the afternoon in the Majestic Q400 switching UT2 on and off I see a drop of roughly 4-5 fps with my settings.

You have to mess around with it a bit to install it but it works just fine if you follow this guide:

http://forum.avsim.net/topic/444156-ultimate-traffic-2-in-p3d-step-by-step-guide-without-migration-tool/

 

I have (and use) all the addons above in P3Dv2 so you can trust me on those ones. And I don't have FSX installed anymore

Here is a quick video showing A2A's C172R and Cherokee in P3D V2.3 Beta 2 ... it also shows the improved global night lighting (at least I think so) ... aircraft are no longer so dark at night.

 

 

Thanks so much for testing this and for posting these videos,Rob!

 

It looks like the Cherokee landing light is not working in the beta either. In v.2.2, the landing light (and beam) is visible in the exterior views . . . but it totally disappears when in the VC.

 

As requested by someone (Arwen?) ... Windsocks appear to be work in P3D v2.3 Beta 2 ... ObjectFlow isn't working for P3D V2.3 beta so can't test out the Windsock for Orbx payware airports but for the other airports the Windsocks are working well:

 

 

Yes, that was me, and thanks for checking them!  I guess I wasn't clear, the only windsocks that don't seem to work fine in v.2.2 are the ones in the Orbx regions and airports (Orbx blames this LM, stating that F9 windsocks are not compatible).  The windsocks in the non-Orbx airports seem to work fine in v.2.2 (at least the ones that I have checked).

 

I'm wondering if you have tested the Anisotropic 16x setting in the beta. Does it now work correctly?

Orbx regions and airports (Orbx blames this LM, stating that F9 windsocks are not compatible).  The windsocks in the non-Orbx airports seem to work fine in v.2.2 (at least the ones that I have checked).

 

Ok, I didn't understand correctly ... I can't test any Orbx airports that use ObjectFlow in v2.3 beta 2 as Orbx appear to do some type of version check (or it could be anti-theft process) so v2.2 ObjectFlow will not work in v2.3 beta 2.  Orbx would have to provide me with an ObjectFlow that works in 2.3 Beta 2 (I'm sure they have one or they're working on one).

 

But logically, if Windsocks are working on non-Orbx airports but don't work in Orbx airports, then I'd suggest this is perhaps something Orbx need to adjust and it's not a LM issue since windsocks are working?

 

Not tested AF yet.  FYI, you can make AF "stick" via nVidia Inspector as a work around.

 

Cheers, Rob.

Not tested AF yet.  FYI, you can make AF "stick" via nVidia Inspector as a work around.

Is there any difference between the filtering in Prepar3D and NVIDIA Inspector? The one in FSX was more optimised and worked better with water compared to driver anisotropic filtering.

 

 

it also shows the improved global night lighting (at least I think so) ...

 

Apologies if this question is answered somewhere in the thread and I just missed it... but assuming I did... are the streetlights FTX Global or P3D default?  I'm assuming they're FTX Global - if they're default, that's a more radical improvement than I was anticipating.

 

Thanks in advance... and thanks for all your testing and reporting - most appreciated. 

 

 

streetlights FTX Global or P3D default?

 

They are FTX Global ... my reference to night lighting was Global lighting not street/building lights.  The aircraft are no longer very dark and the atmospheric lighting is lighter ... in v2.2 the global night lighting felt more like someone had just entered a dark room but not allowed time for one's eyes to adjust to the darkness.  In v2.3 it's presenting a more realistic eye adjustment to darkness.

 

Cheers, Rob.

 

 

Is there any difference between the filtering in Prepar3D and NVIDIA Inspector?

 

They should be the same since it's a hardware function and hence driver ... I highly doubt it's software AF (possible, but that would be very slow and would be the only way to have a difference in visuals) ... as far as I know AF can not be "out of order" when it comes to rendering, but don't quote me.  But I will get around to testing to see if AF bug is fixed.

 

Cheers, Rob.

 

 

They are FTX Global ... my reference to night lighting was Global lighting not street/building lights.  

 

Got it now, thanks!  The atmospheric light is definitely better - in 2.2 I've had to turn off HDR to get any decent kind of "night vision," and it's still not ideal.

 

I'm impressed by the performance you're getting with FTX lights (including vector lights) enabled, and by how good the lights look.  Again, better than my current results using your settings in 2.2.  Am definitely looking forward to 2.3 whenever it gets here.

 

 

Am definitely looking forward to 2.3 whenever it gets here.

 

I think it's getting close, but I have no idea when it'll be released.  LM have a much larger crew of software engineers working on this than I had originally thought --  which is a good indication of LM's commitment to this platform and it's success.

 

Cheers, Rob.