Eric Bakker

Rob, thank you for updating the Legacy, it was my favourite FSX aircraft for a long time. So glad to have it back in P3Dv3, I really missed her.

Since Orbx, ASN and F1 GTN750 are updated now for HF#4, I guess there is no need to wait any longer with applying this hotfix. Or are there known issues with other add-ons?

Thanks for the information, Rob. Can you also tell if the next version will be v3, or that there will be (one or more) intermittent versions, like f.i. 2.6?

Steve, what are your NVIDIA driver version and your 2.5 hotfix version now?

Thanks Steve. I got confused about the NI setting of Multsampling Transparancy being 'disabled' by default, to me it suggested that this driver setting would not allow P3D to use MSAA from the program. Hence my question about enabling it. Apparantly it's two different things.

Steve, You seem to use slightly different wording than the program does. This is what I see and what I changed in NI (the two black lines): Only the 'Antialasing-Mode' can be enhanced, Transparency MS can only be disabled or enabled. Should I enable it?

Yes, SimLauncherX works perfectly with P3Dv2.5. If you have problems please consult the dedicated forum: http://forum.avsim.net/forum/722-simlauncherx/ Maarten (the developer) is extremely helpful.

Hi Mike, If I were you, I would ask it directly to the developer and Orbx support people, they are usually very prompt and helpful: http://www.orbxsystems.com/forum/forum/15-full-terrain-experience-ftx-payware-support-forum/

Steve, I confirm you are correct with this (in many posts ^_^ ), I have tried it and witnessed it myself on my system. Although setting the frame limiter (if lower than 30) may seem a bit less fluid the good thing is that it gives a more constant motion. I prefer to use that. One more question: I understand that I need to set the limiter in P3D for it to work best, but is there any benefit or use to set the limiter is NI as well (at the same value)?

Hi Chas, I have Version 5.2.2 - Final (Februrary 7, 2013). Are you referring to these or did I miss something?

I am running exactly the same settings on my i7-2600K@,4.3Ghz with GTX970 (27" single monitor) and for me it is the best compromise between looks and performance. I prefer this over using DSR. My main concern with DSR is that it looks 'darker' on my monitor/system, I don't like the small menus, I do not see much AA improvement, while performance is under pressure. But maybe I missed some sweet spot setting.

And anisotropic I assume?

Makes me wonder, it is possible that complex scenery theoretically can benefit from this setting too? Or are these meshes strictly related to the VC?

I assume I would need to turn Vsync on in P3D for that, or is it not necessary?

Steve, what do you advise (to try) regarding the use of TrackIR in the sim? I noticed that moving my head induces more stutter than banking the aircraft, and it also seems that using 'mouse look' to pan around is more fluid than TrackIR. Is there a logic and a sweet spot? Also, are their numbers that are with the limiter to avoid, or ones to favour? I mean using 23 or 27 makes no difference technically? Or do I need to divide something or multiply to get ideal fps numbers? And, if I use 20 it means that it will go under it a lot of the times it seems, loosing fluidity. I tried 25 with pretty good results. Last point: what is the use for using both P3D frame limiter and an outside one (like NI) at the same time?

Steve, thank you for this very helpful explanation. One of many, because I learn a lot from your posts. :Applause: There have discussions for years about the frame limiter in FSX (and now P3D) and if it is useful or even bugged. Many people said it is better to use an outside limiter, but this is not true than. I was wondering for some time already why the default setting of P3D is 'frame limiter 20'. I guess LM wants us to show this setting makes it smooth. However, I think 20 is a bit low for smoothness, On the other hand, 30 or 33 is a bit too high when I am flying in urban areas or detailed airports.

Now I am flabbergasted again The A2A is the most easy on the frame rates of all my planes (except the default Maule) in P3D! And the aircraft I fly the most, it has super smooth flying.

Try setting your 'Terrain level of radius' to a lower setting, like medium. Note that what was Max in FSX is comparable to Medium in P3D. Also try setting Tesselation on for better results.

I am surprised about this statement. On my P3Dv2.5 system the new P3D Turbine Duke is not at all framerate friendly!

Did you try to reset the nVidia P3D profile and the nVidia General Profile back to default, just to check if that helps?

OMG, are we on a weekly cycle now?

Sorry, you are right. :blush: I was clearly an impatient reader...

Flight1 is working on a (free) update for the GTN750 based on the new Garmin V5 trainer. So for the patient users the full world terrain database will be available in the near future (no release date known yet) without having to juggle yourself.

Rob, for your info, this is what I have on my system (running P3Dv2.5 since it's release): SimConnect v 10.0.61242.0 installed on 24/2/14 SimConnect v 10.0.61259.0 installed on 24/2/14 ESP SimConnect v 1.0.20.0 installed on 13/02/14 So all are there for a year now. I remember that last year I read in a forum the advise to install the Simconnect SP1 and SP2 packages (in \P3Dv2\redist\Interface) to avoid legacy problems, so that is what I did at that time...

Sorry to ask, but what is now your final best-working 'display setup' regarding Graphics/AA/DSR/NI? I know each has it own hardware, but still it might help me ^_^