...what this thread is about is getting across the many various mind boggling options available to us and understanding that no one-recommendation will work best for all because of the plethora of kit, software and combinations. It's great to hear that guys are finding good results from this thread.

3 hours ago, SteveW said:

...what this thread is about is getting across the many various mind boggling options available to us and understanding that no one-recommendation will work best for all 

No, yours work best lol!

Thanks. 

On 31/01/2018 at 2:00 PM, supersym said:

Hi guys !

And how would you set P3D +- NVI with a GSYNC screen ?

Now I've a lot of tearing in full screen but very less in windowed mode. 

I tried a lot of set but nothing is better.

Help would be  very apreciate =)

How dummy am I !

Gsync on in Nvidia panel and Vsync on in P3d and no more tearing...

Well, I have finally took the dive..... and erased my FSX installation, after 12 years of nightmarish frustration.

It is almost liberating..... a weight off the proverbial shoulders...... a feel like a kid at Xmas !

But, I now have P3D v4.2 to look forward to. 

Hmmmmm....... may have a few stress free days before installing. Me thinks I have a long learning curve to look forward to....... not to mention the expense of buying "pure" P3D addons.

Wish me luck. I think I may need it....... Grrrrrr !

Postscript to above post (still cannot edit ? Come on AVSIM, it is 2018 !)

......

 

I now have to contend with xml files, dynamic lighting, reflections...... blah blah.

The grass is always greener, huh ? Lol.

On 12/12/2017 at 9:32 PM, Ursli80 said:

Hello everybody,

You are just super great here and many thanks for your support. This is unfortunately Google Translator. This has me translated it so that SteveW this multilingual writes.

I am concerned with the text of the SteveW on page one where he has himself quoted and he describes the procedure with Nvidia Inspector.

Also it would me with the AF entry wonder where exactly this must be placed and how I get to the number that I have to enter after the =

I would like to sincerely apologize for this. But as already mentioned, such things never had to start with the P4D V3 and always had over 20 FPS with my 3 projector setting and Warpalizer Warp Software.

 

Thank you for all your help.

 

Best regards from Switzerland

Urs

Well regardless of the Google translator, I am Googling the "Warpalizer Warp Software"..... sounds freekin awesome - whaterver it is  !!!

On ‎13‎/‎07‎/‎2017 at 2:11 AM, SteveW said:

Use the nvidiaProfileInspector fps limiter in P3D:

In the sim Display Settings set fps to Unlimited VSync=Off and set sliders far enough left so that we can observe (shift-Z) the sim running easily at more than the monitor refresh frequency.

Set VSync=On and observe the fps is now running at approximately the monitor refresh frequency say 60Hz for example.

Making a profile: Right-click - NVidia Control Panel - Manage 3D Settings, Global Settings, Default, Apply - Program Settings, select Prepar3D (add and point to v4 .exe), temporarily we are going to change vertical sync to off to create a new profile for nvidiaProfileInspector.exe (basically changing anything creates the new profile), Apply, Exit.

Start nvidiaProfileInspector.exe and select the Prepar3D profile, set vsync back to app controlled, set fps limit to 29.5 - Apply.

Start the sim and is limited to ~30, we can add some stability with VSync=On, we can also try  TP=On for more consistent fps.

What I'm saying here is how to reliably ensure the NVidia settings are factory defaulted with NVidia Control Panel (NCP) . After changing drivers it's important to be sure the factory defaults are installed. After that there will be no profile found in NVidia Profile Inspector (NPI).  I show how to make a change (any change will do) in NCP to create a new profile for NPI.

I explain about using NPI to limit frame rate - this might only be appropriate for certain systems - using projectors or multiple monitors could prove different settings are required.

Also when limiting fps it is best to choose the fps setting slightly below that intended or the GPU has to output extra frames for nothing. I've shown results for this effect on my website.

 

Urs asks about the Affinity Mask required - that's covered elsewhere in depth.

A new entry is inserted into the sim .cfg file, so long as it does not get inserted and split up another section we are OK, I just put it at the top if it's required.

If we don't specify a mask the sim uses AM=0 and because zero would mean no cores used this value is interpreted usually as meaning all cores selected.

[JOBSCHEDULER]
AffinityMask=0

So we don't need to put in a mask if we intend to let the sim do its job.

With the latest P3D versions it is hard to improve on that. However the problems arise from addons and other exe apps we must have running alongside the sim. For that we may then include an AM for the sim and we control where the other apps go by starting those with a mask. We can use apps or a batch file to do that if those apps do not have the AM setting themselves.

When we have sims that take care of the AM themselves we let them start as they would like and place no external control over them with other processes for best results.

 

So in answer to Urs I would say leave out the AM unless he feels some other process is taking too much advantage of the CPU. In which case we would look at that other process and see what can be done, then arrange the AM for the sim.

Edited March 1, 20188 yr by SteveW

2 hours ago, SteveW said:

When we have sims that take care of the AM themselves we let them start as they would like and place no external control over them with other processes...

What kind of "other processes"? Could you give a couple of examples of such "processes" you are referring to? Please clarify here.

Thanks!

Edited March 1, 20188 yr by Dirk98

Well, for example I have a Saitek setup which utilises two .exe programs that drive the panels. The installer sets up exe.xml for the panels to start up when the sim is started. Left like this, these processes would then start up in the affinity of the sim. Instead I start them from an external app or batch file so that they start with an affinity mask that keeps them off of the main cores that the sim is utilising. I start them each with two Logical Processors since giving them only one each can introduce more waiting for resources like the network.