...for v5.3 HF1 (light fix).

Just got my notice and now have it running with the sim.  Be sure to set your FPS limit to 120, and not unlimited, or it defeats the program. 120 allows FFTP to control the fiber dynamically in real time. Unlimited sets to a defined non dynamic factor.

1 hour ago, Sesquashtoo said:

Be sure to set your FPS limit to 120, and not unlimited, or it defeats the program. 120 allows FFTP to control the fiber dynamically in real time. Unlimited sets to a defined non dynamic factor.

For the life of me I cannot see anywhere that this is the case. Maybe I'm missing it and the instructions make no mention of it (see below) also I get lower FPS with it if I limit the sim to 120 as opposed to (as per instructions) 'unlimited'.

 

Quote from manual included with FFTF :-
 

Quote

 

We present to you the Dynamic FFTF program. An application which covers every aspect of user configuration :

Unlimited frames + VSync enabled + TB enabled

Unlimited frames + VSync enabled + TB enabled + external limiter

Unlimited frames + VSync disabled + TB disabled Locked frames ( VSync + TB settings are ignored )

There are two options for dynamic FFTF calculation. Frames range and AGL height range.

Frames range option :

Suggested for unlimited frames + VSync disabled + TB disabled.

You set the minimum and the maximum frames + FFTF range + times you want FFTF to be updated per sec to Flight Simulator. An example can be: Min frames=24, Max Frames=28, FFTF minimum=0.05, FFTF maximum=0.33, times to update per second=1.

In this case at 24 frames FFTF will be 0.05, at 26 frames FFTF will be around 0.19 and at 28 frames, FFTF will be 0.33. Below minimum frames set, FFTF will always be 0.05 while above max frames set, FFTF will always be 0.33.

AGL height range option : Suggested for the rest options.

You set the minimum and maximum AGL altitude + FFTF range. (Times to update per second is not available for AGL height option). An example can be: AGL Min=0 feet, AGL Max=5000 feet, FFTF minimum=0.05, FFTF maximum=0.33. In this case at 0 feet FFTF will be 0.05, at 2500 feet FFTF will be 0.19 and at 5000 feet, FFTF will be 0.33. Above 5000 feet FFTF will always be 0.33. Every time that the application calculates the new FFTF, immediately updates the new FFTF value to Flight Simulator. This is the main reason that we do not need any timer option in this case.

 

 

11 minutes ago, Sparkrite said:

For the life of me I cannot see anywhere that this is the case.

Yep, FFTF doesn't require an in-sim FPS setting of 120 on my system as well.  I leave it at Unlimited, VSYNC off, TB off, VRR on (I have a GSYNC compatible monitor).  I use the AGL Height Scenario setting, and it all works fine.

I'd contact the dev, regarding the 120 in sim , instead of unlimited. He was answering a user quite a while back right here on Avsim, and because the user wasn't getting the performance he expected, the Dev suggested that the sim be locked outside, but keep the FPS lock at 120, and not unlimited. That's how I remember the post. If..I do not remember that post correctly, the Dev can easily come onto this thread and clarify.

Edited December 27, 20214 yr by Sesquashtoo

51 minutes ago, Sesquashtoo said:

I'd contact the dev, regarding the 120 in sim , instead of unlimited. He was answering a user quite a while back right here on Avsim, and because the user wasn't getting the performance he expected, the Dev suggested that the sim be locked outside, but keep the FPS lock at 120, and not unlimited. That's how I remember the post. If..I do not remember that post correctly, the Dev can easily come onto this thread and clarify.

If I remember correctly, this all started because at some point the internal P3D frame rate limiter became unreliable. The fix was to limit frame rates in NCP. However, setting frame rates to unlimited in P3D interfered with G-Sync's performance (again only G-Sync). So If you have VRR enabled with a G-Sync monitor, the solution was to set the internal frame limiter to 120 ( the highest frame rate before unlimited).

I haven't tested unlimited in v5.3, maybe unlimited works? Maybe the internal limiter is now reliable? There are also updated versions of G-Sync in newer monitors and Nvidia drivers can also impact this.

All I know is that 120 fps internally with an NCP max rate solved my problems and I've used it successfully ever since.

38 minutes ago, DonMuskopf said:

If I remember correctly, this all started because at some point the internal P3D frame rate limiter became unreliable. The fix was to limit frame rates in NCP. However, setting frame rates to unlimited in P3D interfered with G-Sync's performance (again only G-Sync). So If you have VRR enabled with a G-Sync monitor, the solution was to set the internal frame limiter to 120 ( the highest frame rate before unlimited).

I haven't tested unlimited in v5.3, maybe unlimited works? Maybe the internal limiter is now reliable? There are also updated versions of G-Sync in newer monitors and Nvidia drivers can also impact this.

All I know is that 120 fps internally with an NCP max rate solved my problems and I've used it successfully ever since.

I have as well...no loss of performance, and I do remember the Dev suggesting this be the case...120 internal, and 30 or 60 external.  I use 33 30(+3 for 10 percent latency allowance) with 1/2 Vsync, and then 120 internal.  I guess, the Dev who I KNOW 'ghosts' Avsim, could merely add to this thread...if this is still his suggested settings, or that you can use internal unlimited in these later P3D versions.  For now, I will stick with my 33 external locked and 120 internal.

Edited December 27, 20214 yr by Sesquashtoo

A short while ago I made my first flight in 5.3 HF1+LF.  I flew from the Sacramento area to Orbx's KRDD and shot the RNAV (GPS) Approach into RWY 34 flying the A2A 182 w/ ASP3D + ASCA, FFTF Dynamic, and the RXP GTN 750 addons.  Below are 4 quick grabs toward the end of the approach.  I wasn't enthused about flying in the Windowed Mode... only did it so I could easily get these shots with the FFTF Dynamic app open.  The airport at Redding is at 505' elev and the correlation between the decreasing altitude (in AGL Height Scenario mode) and the changing FFTF can easily be seen.  During the cruise phase (@ 4500' and about 4200' AGL throughout the cruise) I checked the FFTF and it was at .30.

at 1600'

 

at 1250'

 

at 1000'

 

at 800'

From 0.08 FFTF to 0.02 FFTF during the final few seconds of the approach.  Great addon... I didn't update to the latest P3D update till today when FFTF Dynamic was updated (no great loss of flying time this past weekend with the holiday and all 😁).