3 hours ago, pmb said:

So you can keep 60 fps with unlimted/VSync+TB on over, say, FSDT KLAX with ORBX SCA in the background? In this case I would envy you. I can't even keep 30 fps unlimited /VSync with my 30 Hz monitor over such terrain, even in a simple Carenado C172.

Kind regards, Michael

Me too ...

FFTF alters the ratio of scenery loading to scene building - it does not affect fps.

The reason we see fps change is because we are building more/less of the scene depending on what's collected.

If we increase LOD and autogen = lower fps.

So if you mess with FFTF and see no change in fps that's because the scene building and loading has not topped out in the time available - per frame.

 

2 hours ago, GSalden said:

Imagine Vsync On / Unlimited with a 60 hrtz monitor 

The moment your pc drops too long below 60 Vsync cuts your syncd framerate in half : 30.

If you system can’t hold 30 it will drop to 20. If 20 is too much it will drop to 15 and even 12. So 60 /2/3/4/5 etc

Locked at the same framerate it smoother than that framerate at Unlimited...

This is similar to how my Oculus Rift works since it forces its own Vsync off a preferred 90 Hz so multiples of that ie 90 - 45 - 30 - 22 1/2 hence why Rift ASW uses 45 to double that is if you can hold 45. This is why I like FlyInside  which triggers off tripling 30 with their approach which is much easy to achieve in VR.

Sorry for the VR digression but the principle seems to apply and I am also intrigued by dynamic FFTF for VR as well since terrain loading also can be an issue there as well because running unlimited (FFTF =0.01) seems to be a must in VR. I will experiment a bit with FFTF values of 0.05 - 0.1 manually in unlimited mode until I make the Dynamic plunge.

Gerard, thanks for the clarity

Joe

6 minutes ago, SteveW said:

FFTF alters the ratio of scenery loading to scene building - it does not affect fps.

The reason we see fps change is because we are building more/less of the scene depending on what's collected.

 

So Steve

If one has the overhead to “build the scene” and is running too small a value of FFTF say 0.01 so that there is an insufficient amount of time to “load the scene” we could increase the FFTF value thereby applying a high fraction to loading assuming we have the overhead.

My question is what exactly does “insufficient loading time” cause on the screen? Is it blurries and delayed scenery popping in? 

I assume I have summarized what you said correctly?

Thanks in advance

Joe

3 hours ago, SteveW said:

FFTF alters the ratio of scenery loading to scene building - it does not affect fps.

The reason we see fps change is because we are building more/less of the scene depending on what's collected.

If we increase LOD and autogen = lower fps.

So if you mess with FFTF and see no change in fps that's because the scene building and loading has not topped out in the time available - per frame.

 

I also have Booster 2018 Live which changes the FFTF value in real-time by moving a slider . If I stand for 5 minutes on the rw from a detailed and move the FFTF slider form left ( high value ) to right ( low value ) the framerate increases by at least 25% .

If I move the slider full to the left I see the same buildings as with the slider full to the right. And if I slew to 2000 ft over Amsterdam and move the slider form left to right I can see the FPS going up , but I do not see any change in scenery detail.....

 

4 hours ago, SteveW said:

FFTF alters the ratio of scenery loading to scene building - it does not affect fps.

 

 

So a larger FFTF factor, say .40 would provide more time to which element, i.e. loading or building??

 

4 hours ago, SteveW said:

The reason we see fps change is because we are building more/less of the scene depending on what's collected.

If we increase LOD and autogen = lower fps.

So if you mess with FFTF and see no change in fps that's because the scene building and loading has not topped out in the time available - per frame.

 

With that, if no change in FPS = scenery building/loading not topped out/completed in time PER FRAME,,, then would it help to lock frames at a lower rate, thereby giving each frame more time?? (30fps allows twice as much time as 60fpd for the frame to be completed)

 

Thanks,

Mike

 

LM about FFTF :

”This setting, which defaults to a value of .33 (33%), defines the percentage of each frame that is devoted to loading scenery. Increasing this number can reduce "the blurries", but it can cause stutters, and can also reduce the overall frame rate. Try reducing the number to the lowest level where you still get smooth scenery paging. This will vary depending on disk speed as well as the type of flying, as well as the selected scenery settings.”

So choose the high value by testing which fits your system . As 0.33 is the default value a low value of 0.05 and high value of 0.3 will be safe.  I am using 0.45 as highest value myself. You have to test it on your system ...

So what you can try is setting your scene so that the terrain looks bald. Then try setting any FFTF you like and fps remains the wobbly old same - probably. All depend on the power of your machine.

So I set up The Grand Canyon and try 0.1, 0.5 and 0.9. Only thing I see is stutters after 0.5 and terrain focussing in bigger chunks.

 

 

I've got a more general question: If we speak about terrain loading (and the share of time for it w.r.t. FFTF), does this only refer to terrain loading as such or include autogen loading as well?

Thanks and kind regards, Michael

 

Autogen and special buildings and objects are assembled on top. So in that way if I make my terrain 'less bald' the fps drops due to the object count increasing.

Actually I had in mind, if you can improve autogen loading by choosing a proper FFTF value in the same way you can eliminate blurries. I read quite often people observing late (or no) autogen loading or autogen loading in patches. I observe the latter over large plains, too, 

Kind regards, Michael

2 minutes ago, pmb said:

Actually I had in mind, if you can improve autogen loading by choosing a proper FFTF value in the same way you can eliminate blurries. I read quite often people observing late (or no) autogen loading or autogen loading in patches. I observe the latter over large plains, too, 

Kind regards, Michael

Autogen and other buildings and objects are on top of terrain loading and assembled in the remaining time.

If we refer again to the manual and what Gerard has repeated we can see that the fps is not altered by the FFTF ratio, we are not swapping terrain loading for fps - rather by the amount of work it has to do on top of loading the stuff in - altered by the result of the ratio and the settings and sliders.

To answer the question - do we just slap in the new FFTF app on top of our current setup? We would almost certainly need to adjust the way we have it all set up and tune the app for our system prefferences - refer to Gerards first set of posts.

Insufficient loading time results in an overall drag on the sim

9 hours ago, joepoway said:

So Steve

If one has the overhead to “build the scene” and is running too small a value of FFTF say 0.01 so that there is an insufficient amount of time to “load the scene” we could increase the FFTF value thereby applying a high fraction to loading assuming we have the overhead.

My question is what exactly does “insufficient loading time” cause on the screen? Is it blurries and delayed scenery popping in? 

I assume I have summarized what you said correctly?

Thanks in advance

Joe

The fps runs with what its got and displays tiles even though only a few lines have been read in. textures are arranged to provide a low res view first rather than require complete loading before the sim can paint the tile. Since every pixel in the sim is projected with those few values from the texture the result looks blurred.

Thanks, Steve, sounds plausible.

Just pondering if I should spend the money on the tool.

Kind regards, Michael

Hey Michael, it's a tricky one. With few cores and a low fps it might help a little. If you are already fiddling with settings trying to get a good result and no satisfaction you need to look elsewhere, more power or reduce expectations.

15 hours ago, pmb said:

So you can keep 60 fps with unlimted/VSync+TB on over, say, FSDT KLAX with ORBX SCA in the background? In this case I would envy you. I can't even keep 30 fps unlimited /VSync with my 30 Hz monitor over such terrain, even in a simple Carenado C172.

Kind regards, Michael

Hi Michael,

Not 60 FPS but it is smooth for the most part.