1 hour ago, RJC68 said:

Hey Guys,

Has anyone seen any stuttering with the latest version and using the OLOD feature?

I was getting some stuttering around Toronto this morning and I put it down too a combination of the terrible photogrammetry and FLYTamper CYYZ which is pretty resource intensive. I was using the latest version 4.1 with a base OLOD of 200 at 1000ft and then 20 at 6000 feet. I decided to back to Liverpool to rule out what I thought may have been scenery related, and start from runway 27 in the PMDG 737 and run a CapFrameX capture for 15 minutes. Here is the results first with 4.1 and using the auto OLOD

 

Then I closed the sim and removed AutoFPS 4.1 and installed the latest version of 4.0 and did the exact same 15 minute test again. It would appear something odd is happening even though my OLOD settings were not crazy and I left plenty of altitude between the two values

 

It is interesting that you are experiencing these frame time spikes. When I first developed AutoFPS it had OLOD changes in it and I found that it was a bit stuttery down low when only OLOD was changing, which is why I removed it in the first place.

Could I get you to run that same test flight with 0.4.1 but with OLOD base and top both set to 200 (ie. auto OLOD will be effectively disabled) and see if you still get these frame time spikes. Also, can you make sure you have Sim Value Logging unchecked because it is possible the stutters are being caused by these logging events. Basically, I want to determine whether it really is OLOD changes doing it or something else I changed since 0.4.0. Thanks.

58 minutes ago, mmcmah said:

Would it be possible to have a minimum TLOD setting on the ground that's different from the one on landing?

There's another thread that has to do with the ability to pick out runways at a distance and the optimal TLOD value that I came up with after testing was 250-300. This was flying into LEPA, so clearly something like KJFK or KLAX would not require that level of detail due to the lights and area taken up by the runways, buildings, etc.

I'm trying to think of a way to have a high TLOD until you're basically lined up (1,500ft?) and then bring it down gradually, or allow the mod to go below the configured minimum if the system still can't handle it?

No, because the whole point of the landing part of TLOD Min on Ground/Landing is that your system has gradually worked its way down to a stable TLOD min for the final minute of landing. Having a high TLOD at 1500 then rapidly changing down to TLOD Min shortly thereafter is a recipe for maximum scenery change and likely stuttering as a result which is exactly what you don't want.

25 minutes ago, Reset XPDR said:

It is interesting that you are experiencing these frame time spikes. When I first developed AutoFPS it had OLOD changes in it and I found that it was a bit stuttery down low when only OLOD was changing, which is why I removed it in the first place.

Could I get you to run that same test flight with 0.4.1 but with OLOD base and top both set to 200 (ie. auto OLOD will be effectively disabled) and see if you still get these frame time spikes. Also, can you make sure you have Sim Value Logging unchecked because it is possible the stutters are being caused by these logging events. Basically, I want to determine whether it really is OLOD changes doing it or something else I changed since 0.4.0. Thanks.

No Problems,

I will try and do this in the next 30 mins or so, Sim value logging was unchecked.

2 hours ago, RJC68 said:

I was using the latest version 4.1 with a base OLOD of 200 at 1000ft and then 20 at 6000 feet.

Yeah there’s definitely more stuttering with 4.1 as seen in the CFX tests you posted. The objective difference is rather small though. Do you perceive this subjectively as well?

What I did was to go for an even wider OLOD range. What if you set top alt to 10,000ft?

Edited February 27, 20242 yr by Cpt_Piett

8 minutes ago, Cpt_Piett said:

Yeah there’s definitely more stuttering with 4.1 as seen in the CFX tests you posted. The difference is rather small though. Do you perceive this subjectively as well?

There was some significant stuttering this morning when I was flying from CYYZ, On the first test from Liverpool I did that showed the deviations It didn't seem too bad visually but when I went back to V4.0 it seemed smoother.

Just doing the test with both OLOD's at 200 as asked for by the Dev.

Results to follow

Edited February 27, 20242 yr by RJC68

13 minutes ago, RJC68 said:

It didn't seem too bad visually

That was what I was wondering. During my initial testing (with crazy high TLOD/OLOD settings), the CapFrameX session showed more stuttering that I usually get - but not something that bothered me much when flying.

Just finished a flight from Lima to Cusco in the A300 using 4.1 and it was smooth throughout the entire flight. I’m still using insane settings (TLOD 600 OLOD 1000).I didn’t bother with any CFX capture this time, but I glanced at AutoFPS every now and then, and things seemed fine.

1 hour ago, Reset XPDR said:

Could I get you to run that same test flight with 0.4.1 but with OLOD base and top both set to 200 (ie. auto OLOD will be effectively disabled)

Here are the results, Not quite as good as the capture with 4.0 but visually it was hard to see any issues. I will try a couple of flights when time permits to test further

Doing some testing with this in high density, high traffic, high level airports, namely FlyTampa YSSY and inibuilds KLAX. Just doing circuits in the stock Cessna 172.

Usual CPU temps in high 60° to mid 70°, but with this app, using @Cpt_Piett's numbers as a base, FPS holds steady at 60, it did dip to the low 50's when I parked next to some big iron at the LAX cargo ramp, but went straight back up in seconds. CPU temps holding at high 50° maximum, the odd second or 2 into the 60's. Just to be on approach and suffer no stutters, no scenery popping, with PSXT & real traffic is just mind-blowing. 

Ultimate test this afternoon after work, I'll go to what has been my "hottest" airport, ini's OMAA for a flight in the Horizon 787-9 to VABB. Abu Dhabi never EVER runs under 70+°, I'm hoping for some better results with this app. I have to admit I was of the opinion that I didn't need this program as I believed the sim was looking good and above all running good. But after doing the above testing, even what you think is GOOD can always be BETTER.

Will report my findings later today. All thanks to @Reset XPDR, legend. 

I'm not sure if this development is going in the right direction.

Let' recall what @Fragtalityrecommended for the usage of his original tool (which still is the foundation of the AutoFPS tool):

• Less is more:
  • Fewer Increments/Decrements are better. Of reasonable Step-Size (roughly in the Range of 25-75).
  • Some Time in between Changes is better.
  • Don't overdo it with extreme low or high xLOD Values. A xLOD of 100 is reasonable fine on Ground, 200-ish is reasonable fine in Air.
  • Forcing the Sim to (un)load Objects in rapid Succession defeats the Goal to reduce Stutters. It is not about FPS.

 

 

2 minutes ago, RJC68 said:

Here are the results, Not quite as good as the capture with 4.0 but visually it was hard to see any issues. I will try a couple of flights when time permits to test further

That’s a significant difference vs 4.0 though, looking at the CFX capture. Looks like dynamic OLOD changes puts a strain on something - perhaps higher main thread frame times? I’m not able to test right now unfortunately…

4 minutes ago, RJC68 said:

Here are the results, Not quite as good as the capture with 4.0 but visually it was hard to see any issues. I will try a couple of flights when time permits to test further

Do you recall what was happening in MSFS and with the app at the time those spikes occurred?

1 minute ago, RALF9636 said:

I'm not sure if this development is going in the right direction.

Let' recall what @Fragtalityrecommended for the usage of his original tool (which still is the foundation of the AutoFPS tool):

• Less is more:
  • Fewer Increments/Decrements are better. Of reasonable Step-Size (roughly in the Range of 25-75).
  • Some Time in between Changes is better.
  • Don't overdo it with extreme low or high xLOD Values. A xLOD of 100 is reasonable fine on Ground, 200-ish is reasonable fine in Air.
  • Forcing the Sim to (un)load Objects in rapid Succession defeats the Goal to reduce Stutters. It is not about FPS.

 

 

That was before Max LOD stepping was implemented, which changed everything related to this.

1 minute ago, RALF9636 said:

I'm not sure if this development is going in the right direction.

Let' recall what @Fragtalityrecommended for the usage of his original tool (which still is the foundation of the AutoFPS tool):

I think the last point could be relevant to the current discussion. However I do believe in having a wide range of TLOD/OLOD values to choose from, so that users with various hardware can choose what gives the best results.

4 minutes ago, Reset XPDR said:

Do you recall what was happening in MSFS and with the app at the time those spikes occurred?

I’d suggest bringing up the dev mode OSD to check CPU and GPU frame times.

30 minutes ago, Cpt_Piett said:

Just finished a flight from Lima to Cusco in the A300 using 4.1 and it was smooth throughout the entire flight. I’m still using insane settings (TLOD 600 OLOD 1000).I didn’t bother with any CFX capture this time, but I glanced at AutoFPS every now and then, and things seemed fine.

I used AI traffic but both airports were very quiet. However there are many objects (buildings), especially departing from Lima, and I had OLOD base set at 1000. ‘Unloading’ objects during the climb didn’t seem to have any detrimental effects.

Edited February 27, 20242 yr by Cpt_Piett