Eric Bakker

I hope that the next MSF update (today?) will not break the flight model, I believe Asobo has been refining it?

Browsing the internet I found this copy of an original Flight Manual of the FW P149D registration D-EDBW:

https://www.avsimrus.com/f/documents-16/flight-manual-piaggiofocke-wulf-p149d--33209.html

I am always a sucker for these things, love it.

I Purchased this ATS for MSF yesterday, and it flies indeed beautifully, thanks Alex!

Looking forward to the update also.

Found it here in mentioned video, thanks:

I have exactly the same problem, any help is appreciated.

4 hours ago, Milviz said:

Yes.  The B-55 will be updated for v4 shortly.  No promises or dates as to when though....

Thanks, I appreciate this a lot.

On 17-8-2015 at 4:46 PM, n4gix said:

Where did you buy the C310R? That's the exact problem that prompted me to fix and recompile all of the installers to begin with.

Bill, sorry for going off-topic, but can you say already if the B55 will also get an update?

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.

Excellent, Orbx are pretty good about getting the patches quickly and in some cases before an official update/hotfix is released.

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?

Beau Hollis has already commented publicly on items that will be addressed in v3.0 so that should be a pretty good indication there will be a v3.0.

When will v3.0 be available ... I'm not permitted to say obviously, but I will say it's not going to be years or a year.  What will it include ... just have to wait and see.

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?

Good to hear it works, Mike. I hope you will enjoy SLX.

I've had some problems recently with driver/P3D version that displayed a lot of shimmer with no SGSSAA too, but those problems seem to be gone with the current setup.

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

I have no Flights file in my P3D v2 directory and I have no Prepar3D.FLT in my saved flights file in the documents\Prepar3D v2 files.

Hi Mike, is your problem solved now or still the same?

I really appreciate your help. When I pointed the program to that directory I get a new error message. Default Flight D:\ Prepar3D v2\Flights\other\Prepar3D.FLT not found, cannot continue. I have no Flights file in my P3D v2 directory and I have no Prepar3D.FLT in my saved flights file in the documents\Prepar3D v2 files.

Mike, I hope Maarten comes to the rescue with this.  :smile:

What I can do is showing my own (working) SLX setup:

The default LM flight situation is stored here:

C:\Users\username\AppData\Local\Lockheed Martin\Prepar3D v2\Prepar3D_Default

When you save a new 'default' flight it will be stored in 

C:\Users\username\Documents\Prepar3D v2 Files

you only need change the "Antialiasing - Transparency Supersampling" setting to the same multiple as you have MSAA set in P3D, leaving others at default.

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.

With P3D DX11 (and FSX DX10), only the Transparency settings make any difference and can be enhanced, but not overridden. DX10 and DX11 make up the scene from more complex images than DX9 and the AA can only be enhanced with the Transparency AA.

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?

When I launch the application,I get an error box. It says: Error in preferences, Prepar3D flight folder D:\Lockheed Martin\ Prepar3D v2\ Flights does not exist. Where should the program be pointing so I don't get this error?

HI Mike,

the flights are normally stored in:

C:\Users\your username\Documents\Prepar3D v2 Files

(I could have answered this in the other forum, sorry, but I thought it was important to make you aware of this SLX dedicated forum in case the cause is different :smile: )

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.

 Apologies, I am new to posting and I may have this in the wrong spot.  Thank you.

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/

Since the pre-rendering is doing work ahead of time, it can be seen from monitoring the sim, that the sting is taken out of dips during more complex scenes, and peaks are taken care of by limiting.

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)?

[...], and TrackIR, with its new drivers, my smooooth head tracking...my grin almost broke my face.

Hi Chas,

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

Im running 4x SGSS in NVI, FXAA OFF in P3D and 4x AA in P3D.

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.

Clouds, volumetric fog, the particle system, and AA will load up the GPU .

And anisotropic I assume?

AA is always GPU bound ... well, I shouldn't say always, because you can force AA to be "software rendered" but that would only happen if the GPU didn't support hardware accelerated AA and it's been at least 2 decades since AA wasn't handled by the GPU. FPS drop is due to the raw GPU performance needed to accomplish SGSS AA.

 

I don't use NI (except when I'm doing screenshots for someone else).  I find MSAA and/or FXAA are enough for nice visuals on my setup (3840 x 2160) ... sometimes FXAA will work better for 3rd party airports that contain objects with narrow geometry that doesn't work with MSAA.

Thanks for the explanation, Rob. I tried it, and I am very happy now with the following results : P3D 4x MSAA, FXAA off, and SGSS 4x in NI.

The GTX970 can handle this very well.

If you use nVidia Inspector and run high levels of SGSS AA you might want to OC the GPU, but otherwise I've found no benefit to it.

That is interesting. I always thought that the (SGSS) AA settings brings down the fps due to the CPU having to work harder. I have a 2600K running OC @4.3.

This weekend I traded my GTX660 for a GTX970 EXOC BE, but I did not do the whole NI exercise again because I assumed it was fruitless.

Which GPU/NI settings can I change to benefit from my new GTX970 you think?

With recent GPUs there are emerging several optimisation techniques, including Instancing I mentioned earlier, which can improve performance but only if the objects in the scene lend themselves to those techniques.

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?