Guys, I would post in each of the dev's forums as well. They can't address what they don't know.

 

Edited April 19, 20206 yr by B777ER

I will do, I've been trying to gather as many facts as possible.

I've actually already reached out to both FlyTampa and FSim Studios and will post further as I get time.

In working with Gabriel from Fsim to troubleshoot we found that this issue only crops up as you increase the resolution.
These were my test results from FSSim CYLW:

3840x2160: Day 44

Night
3840x2160: 23
2560x1440: 31
1920x1440: 38
1920x1200: 43
1680x1050: 51
1280x800: 60
1152x864: 60

So as the resolution increases so the fps drops.

I did some more tests at native resolution.

Turning AA off completely FPS only went from 23 to 26. So little to no difference

Turning shadows off completely got me to 31, which I had not seen much if any improvement before. Still a long way off the day FPS value.

I've found FPS drops at almost every airport I have installed including MKS LEPA, WFSS ZPPP and LatinVFR KMSY.
The airports that I found zero or less than 10% drop were FlyTampa KLAS, KBOS and Orbx LEAS

To replicate:
1: Have to be running in a high monitor resolution. More noticeable running at 4K
2: Have to position the aircraft directly under the lights, preferably at the main gate area.
3: Have to be running unlimited FPS to compare the true day FPS to true night FPS. With a limited FPS at say 30 some drops may not be noticeable.

You can use the time preview setting to see instantly the FPS drop from day to night under the DL.

Step 2 is important because I have found once you move far enough away from the lights themselves the performance hit goes away, even though the lighting is visible. For example at the runway threshold performance can appear totally normal, its only once you get closer to the actual lights does the performance start to crater.

I'll post this all at LM because I'm not sure what causes this and its not restricted to any single dev, so there must be something in the base sim that is causing it.

Edited April 19, 20206 yr by atco

I believe I have found the cause of this issue.

Working with several developers we have found that the issue is caused by copying over old fx files from V4 scenery into V5.

This is not going to work for V5 scenery.

All the airports that showed no FPS loss at night in the lights were developed with new fx files written in accordance with the V5 SDK.

Airports where there was a large drop in performance had used fx files copied over from V4.

So for airport developers, please create new fx files for V5 sceneries that have been created in line with the V5 SDK and do not simply re-use old fx files from V4 and earlier as they no longer work properly.

I am working with a couple of developers at the moment to see if we can identify where the changes are and what parameters are affected. Hopefully the changes will be small and easy for developers.

Thank you to everybody who has helped so far, it seems that we are now much closer to resolving this.

I just downloaded the inibuilds LVFR KSNA Orange County DL and same behavior at 4k.  my locked 30, turns to 15 when under a dynamic light

On 4/18/2020 at 12:25 AM, atco said:

Flightbeam SEQM:
First Test: Frame Rate Umlimited
Day 57
Night 17
Truly awful jittery, stuttering performance

Was vsync on for this?   What is your refresh rate?

On 4/18/2020 at 12:25 AM, atco said:

Second Test: Frame Rate Locked at 30
Day 30
Night 30

Locked using the internal limiter?

 

4 hours ago, Mace said:

Was vsync on for this?   What is your refresh rate?

Locked using the internal limiter?

 

1) Yes, 60Hz

2) Yes