Hi all,

 

I have been a P3D v2.x dabbler for a year or so now but 2.4 is the first version where I feel that I am comfortable using it more for everyday use than my trusty FSX installation.

 

A few questions:

 

1) Although it seems better in 2.4, there is still a slight lag in the scenery rendering giving a little bit of jerky appearance now and again. This was fixed with the 1/2 refresh rate fix in FSX. I know it doesn't work in P3D because its not true full-screen. Do we have any word on either LM or Nvidia doing something to get 1/2 refresh rate working in P3D?

 

2) FPS killers - A list? Is there any idea in terms of a list of features and its known effect on FPS? For instance with a GTX 770 and a 2600k at 4.6 ghz, is high tessellation an FPS killer? What about a comfortable setting for shadows etc. I think its difficult to know which features are 'free' or a small penalty vs which features are a high perf hit.

 

3) SGSS AA - I am still having to add 2x SGSS in inspector to get decent cockpit gauges clarity and redcuced shimmering. Is this everyone's experience or is the new fangled DSR a better option?

 

 

Thanks

 

Glenn

2) FPS killers - A list? Is there any idea in terms of a list of features and its known effect on FPS? For instance with a GTX 770 and a 2600k at 4.6 ghz, is high tessellation an FPS killer? What about a comfortable setting for shadows etc. I think its difficult to know which features are 'free' or a small penalty vs which features are a high perf hit.

 

From my experience there is no single most important frame killer. It is really about finding a balanced setup depending on your hardware. E.g. a lot of people have claimed that volumetric fog is a fps killer. That might be the case if you have an old graphics card. On my GTX780 volumetric fog has almost zero impact. I can manage to get an almost perfectly smooth experience with consistent 30+ fps in the Aerosoft Airbus A320 on complex add-on airports with 3 screens in 1080p + 1 additional monitor for pop-up gauges if I use intermediate settings. If I crank up just one of the sliders to max from those intermediate settings than the system really goes down on its knees. If I reduce other settings in turn, this is not a problem. So you really have to try to find the sweet spot for your system. I'm using SIMStarter to setup different profiles for IFR and VFR flying, because you can choose much higher settings in a GA aircraft than in a tubeliner. So just try to find what works best on your system. Once you have found the sweet spot, you can only smile when reading discussions on FSX SE. Prepar3d v2 at its sweet spot is just much better in every regard than FSX...

Prepar3d v2 at its sweet spot is just much better in every regard than FSX...

Amen to that!

 

Vic

Hi all,

 

I have been a P3D v2.x dabbler for a year or so now but 2.4 is the first version where I feel that I am comfortable using it more for everyday use than my trusty FSX installation.

 

A few questions:

 

1) Although it seems better in 2.4, there is still a slight lag in the scenery rendering giving a little bit of jerky appearance now and again. This was fixed with the 1/2 refresh rate fix in FSX. I know it doesn't work in P3D because its not true full-screen. Do we have any word on either LM or Nvidia doing something to get 1/2 refresh rate working in P3D?

 

2) FPS killers - A list? Is there any idea in terms of a list of features and its known effect on FPS? For instance with a GTX 770 and a 2600k at 4.6 ghz, is high tessellation an FPS killer? What about a comfortable setting for shadows etc. I think its difficult to know which features are 'free' or a small penalty vs which features are a high perf hit.

 

3) SGSS AA - I am still having to add 2x SGSS in inspector to get decent cockpit gauges clarity and redcuced shimmering. Is this everyone's experience or is the new fangled DSR a better option?

 

 

Thanks

 

Glenn

 

Hi Glenn,

 

i would say it is a combination of add ons you are using that produces  fps hits. In my experience the major hubs that has been made for FSX and came with triple installers like Flightbeam KPHX are a real killer even if you use a standard plane.

I try to keep away from known FPS killers.

 

The solution might be a add ons that are native  P3D2 would solve a lot of FPS killers. That means the dev would need to do 2 products for ex like MilViz.

 

to answer your 3. question, i do use the 2x SGSS AA to get good gauge quality. I dont use the DSR feature.

 

But one of the biggest hits in P3D2 are the shadows. If you use cloud and veggie shadows cast+receive and fly through PNW or NOR @ sunset or sunrise you will encounter a good hit in FPS. AFAIK the building autogen in P3D2 is an FPS killer too.

Hi Glenn, here's a few suggestions:

 

1) Although it seems better in 2.4, there is still a slight lag in the scenery rendering giving a little bit of jerky appearance now and again. This was fixed with the 1/2 refresh rate fix in FSX. I know it doesn't work in P3D because its not true full-screen. Do we have any word on either LM or Nvidia doing something to get 1/2 refresh rate working in P3D? You could try setting 1/2 refresh rate in the Nvidia Control Panel (and enabling Aero) and see if it makes any difference. Also you could try changing the Fiber Frame Time Fraction setting to 0.10 (with frames set to unlimited) or 0.01  (with frames locked) and see if it helps.

2) FPS killers - A list? Is there any idea in terms of a list of features and its known effect on FPS? For instance with a GTX 770 and a 2600k at 4.6 ghz, is high tessellation an FPS killer? What about a comfortable setting for shadows etc. I think its difficult to know which features are 'free' or a small penalty vs which features are a high perf hit. On my rig, building autogen seems to be one of the big culprits, as can vegatation shadows at certain times of day; another is SGSS in dense cloud cover. Surprisingly, HDR, volumetric fog, and cloud shadow draw distance have almost no effect on performance (personal experience only).

3) SGSS AA - I am still having to add 2x SGSS in inspector to get decent cockpit gauges clarity and redcuced shimmering. Is this everyone's experience or is the new fangled DSR a better option? 2X DSR for me, as I don't have the huge fps hit in overcast conditions.