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?