Just did another test with FG mod off in MSFS2024 and using just LSFG. Detection is working fine for that too , if I close LSFG and hit reset it will detect that I've gone back to regular FPS.

Once again a huge thanks for all your work on on this little gem.....its been a real game changer for me in 2020 and 2024. Now i just have to try a few more of the different app settings but for now I'm very happy with running it on Auto Target FPS.

oops a double post

Edited February 16, 20251 yr by Chris Boyce

I know how complicated this can be with many moving targets.  I have a quiet Sunday and will see how it goes for a few more flights.  I see the flight as I was trained in different flight segments:  Takeoff; Climb-out; Cruise; Descent; Landing; and Roll-Out. 

I think you can set a minimum FPS that should apply to all but the TLOD seems to require rules depending up prior values or to be set individually for each flight segment... which would then require you to determine what segment you are in...

I am not sure if the log was on any help, but it was to me to follow the fine changes.  I'll try another flight as it is quiet here and see how it evolves.  Seems there are also differences in MSFS 2024 starting fresh or restarting.... maybe my setting adjustments will be enough for government work. 

2 minutes ago, Jerryyyyy said:

I know how complicated this can be with many moving targets.  I have a quiet Sunday and will see how it goes for a few more flights.  I see the flight as I was trained in different flight segments:  Takeoff; Climb-out; Cruise; Descent; Landing; and Roll-Out. 

I think you can set a minimum FPS that should apply to all but the TLOD seems to require rules depending up prior values or to be set individually for each flight segment... which would then require you to determine what segment you are in...

I am not sure if the log was on any help, but it was to me to follow the fine changes.  I'll try another flight as it is quiet here and see how it evolves.  Seems there are also differences in MSFS 2024 starting fresh or restarting.... maybe my setting adjustments will be enough for government work. 

I had a quick scan of your log file and yes it will be helpful in getting to the nitty gritty of the issue. Re flight phases, for IFR it is relatively easy to work them out as aircraft generally follow those set flight segments you listed. It's VFR where it gets a bit tricky but that doesn't seem to be where this issue lays thankfully.

A quick update on this. After looking at the code I've already run into an issue with changing this behavior to be in flight only in that the seeking process, which is required to increase TLOD Base +, has always been set to automatically initiate on the ground at the start of a flight because it has to change TLOD significantly to find the right tuning point for your FPS cap. If this now triggers when you are in flight crossing Alt TLOD Base (actually I think Alt TLOD Top would be better) then you are going to likely experience significant stuttering for the next minute or so while it does its thing. As such, for this to work I will have to slow the process right down to be a trickle increase (like + 5 TLOD per second), otherwise I will just be moving the stuttering issue to a more noticeable phase of flight. It shouldn't be too big a deal, but it does complicate things somewhat.

33 minutes ago, Reset XPDR said:

I had a quick scan of your log file and yes it will be helpful in getting to the nitty gritty of the issue. Re flight phases, for IFR it is relatively easy to work them out as aircraft generally follow those set flight segments you listed. It's VFR where it gets a bit tricky but that doesn't seem to be where this issue lays thankfully.

A quick update on this. After looking at the code I've already run into an issue with changing this behavior to be in flight only in that the seeking process, which is required to increase TLOD Base +, has always been set to automatically initiate on the ground at the start of a flight because it has to change TLOD significantly to find the right tuning point for your FPS cap. If this now triggers when you are in flight crossing Alt TLOD Base (actually I think Alt TLOD Top would be better) then you are going to likely experience significant stuttering for the next minute or so while it does its thing. As such, for this to work I will have to slow the process right down to be a trickle increase (like + 5 TLOD per second), otherwise I will just be moving the stuttering issue to a more noticeable phase of flight. It shouldn't be too big a deal, but it does complicate things somewhat.

Well I am running another evolution and indeed the flight started at 300 not the 100 base TLOD and it went right up to 500 despite TLOD Top at 300,  I unchecked Hr+ and restarted MSFS_AutoFPS and it still went to 500.  Will see how the landing sequence goes.  Seems to me an issue of initializing variables, which maybe get reset somehow later in the evolution of the running of the program. 

10 minutes ago, Jerryyyyy said:

Well I am running another evolution and indeed the flight started at 300 not the 100 base TLOD and it went right up to 500 despite TLOD Top at 300,  I unchecked Hr+ and restarted MSFS_AutoFPS and it still went to 500.  Will see how the landing sequence goes.  Seems to me an issue of initializing variables, which maybe get reset somehow later in the evolution of the running of the program. 

I am assuming you are above Alt TLOD top when you are seeing TLOD 500 where TLOD can indeed go above TLOD Top because TLOD Base + gets added to the entire TLOD altitude schedule, not just TLOD Base. This is how it is supposed to work, per the readme as follows, and is the bit that @Jazzwants to keep. Is this not what you want too?

• TLOD Base + is applied across the entire altitude schedule, potentially allowing a higher TLOD Top than set if performance conditions are favorable, so be particularly conservative when setting TLOD Top.

Edited February 16, 20251 yr by Reset XPDR

I see that it is added, but seems to be added at times on take off and on landing, when it seems to me the Base parameters should trump the add ons.  I tried a decrement of 20 and that helped to get down from 500 to 100 faster but it does not necessarily make it on landing and I get stutters because the TLOD is higher that my card can handle in the complex airport environs.  TLOD 300 is fine at 1000' but not at 100'. 

Think the principle is good may just need to see why the on the ground settings do not trump the increments... maybe increments should only be operational above a certain AGL.... and once incremented need to be able to get down fast... IMHO. 

19 minutes ago, Jerryyyyy said:

I see that it is added, but seems to be added at times on take off and on landing, when it seems to me the Base parameters should trump the add ons.  I tried a decrement of 20 and that helped to get down from 500 to 100 faster but it does not necessarily make it on landing and I get stutters because the TLOD is higher that my card can handle in the complex airport environs.  TLOD 300 is fine at 1000' but not at 100'. 

Think the principle is good may just need to see why the on the ground settings do not trump the increments... maybe increments should only be operational above a certain AGL.... and once incremented need to be able to get down fast... IMHO. 

OK, I think you and @Jazzare saying the same thing - ground and low down ops is where the issue is.

What I am going to do is to formally release the current test version as it is, because the new auto update functionality seems to be pretty solid and I'd like to get it out there for everyone, then work on a new test version where I can have a rethink of the whole TLOLD Base + feature and try out what you guys are asking for plus a few other changes that may even end up negating what you are asking for if they do the job well enough. Stay tuned!

3 hours ago, Reset XPDR said:

OK, I think you and @Jazzare saying the same thing - ground and low down ops is where the issue is.

What I am going to do is to formally release the current test version as it is, because the new auto update functionality seems to be pretty solid and I'd like to get it out there for everyone, then work on a new test version where I can have a rethink of the whole TLOLD Base + feature and try out what you guys are asking for plus a few other changes that may even end up negating what you are asking for if they do the job well enough. Stay tuned!

Great.  One change at a time.  I'll volunteer to test the Beta this time and can run it through its paces.  You have done a real service with this software, hope they find a place for it. 

Last call for an nVidia 5000 series GPU owner to try out the new interim Multi Frame Generation (MFG) manual multiplier selection in the latest 0.4.4.6 test version available here and let me know what you think. Otherwise, I will be going live the formal release of 0.4.4.6 tomorrow as I want to get the new Auto Update functionality, which is working well, out to the user base before I embark on the next test version addressing TLOD Base + issues. 

I do understand that the likely reason I haven't received any feedback on this is that there are very few 5000 series GPU owners out there right now and possibly none that participate in test phases for this app. As such, in the event that a future 5000 series GPU owner finds this new MFG functionality to be unacceptable after this formal release, I will include include a mechanism whereby the user can disable it manually by manually editing a key in the common config file located in the app's root directory.

If anyone REALLY wants to help out with future 5000 series card testing with this app, please send a 5090 to P. Sherman, 42 Wallaby Way, Sydney. 😂 jk.

Edited February 17, 20251 yr by Reset XPDR

15 hours ago, Reset XPDR said:

Just to make it absolutely clear, you want an option to only apply TLOD Base + when above Alt TLOD Base and upon descent to be locked at TLOD Base by the time you cross back below it?

 

There is not a checkbox in FPS Cap mode to enable TLOD Base + but I assume that it's on by default which is why it exhibits this behaviour of trying to push beyone my TLOD Base setting? If that is actually what is happening then yes, that is exactly what I'm asking for.

When I load into the sim with FPS Cap mode I don't want it to try and push my TLOD above my TLOD Base setting until I have taken off and flown above my ALT TLOD Base setting. Once above that it's great to have it do its thing. Inversely, I want it to be back at my ALT TLOD Base setting as I pass back through ALT TLOD Base.

With the way I currently have this set up it would mean that I remain at a TLOD Base of 100 until my ALT TLOD Base altitude of 500ft when it can start pushing up my TLOD should the correct conditions be met. And the same in reverse when landing.

I'm perfectly fine with it doing it's seeking thing for a minute when I load up as long as it does what it needs to do and gets the info it needs and then sets and sticks to my TLOD Base until ALT TLOD Base altitude.

 

15 hours ago, Reset XPDR said:

I will also look at modifying Hr+ so that it imposes even greater headroom and caps the maximum amount that TLOD Base + can settle at to be a lower value than it currently calculates to be so that those who still wish to use TLOD Base + on the ground may still do so in challenging environments with a much lower chance of downward adjustment following the initial seeking and setting of TLOD Base +.

My personal concern with that is, won't that mean that it will limit more how far it will push the TLOD limit when in flight? As an example, if it would push up to 300 TLOD in flight now then it may limit it to 250 or something after such a tweak? Or would this only affect when on the ground?

Does Hr+ affect the entire range of flight from ground to cruise or is it aimed at something more specific? I just what to clarify. From my testing it seems to effect the entire range which is why I'm concerned with that. I suppose though, that if more restrictions were placed on that and it did limit more then one phase then I could increase the TLOD Top setting to compensate for reduced TLOD in cruise? Would that be a correct assumption?

HI,

Just did some testing switch back to Auto TLOD from FPS Cap and the bottom line is it worked better for my Reno/SFO B787 evolution.  I unchecked the + TLOD Base and set it to 100 and checked the Top and set it to 300. 

It went back and forth to TLOD 100 on both Reno and SFO runways and minimal stutter seemed to choose a good FPS at minimum of 50-60... will have to check log.  Over the mountain to SFO TLOD went up to 500 then back down. 

IMHO this was working better than FPS Cap in my hands. 

Will send log via email.... did two flights. 

@Jazzand @Jerryyyyy, let me just get 0.4.4.6 formal release dealt with then I will turn my attention to TLOD Base +.

Edited February 17, 20251 yr by Reset XPDR

MSFS_AutoFPS version 0.4.4.6 has just been formally released and is available here. If you were on the test version and had Auto Updates selected, the app should prompt you to update to this release version. My thanks go to everyone who participated in the test phase and provided valuable feedback.

Summary of changes:

• Added auto update installation and optional test version participation capability.
• Added manual MFG multiplier and target MFG FPS selection for 5000 series nVidia GPUs.
• General improvements, optimisations and minor bug fixes.

14 minutes ago, Reset XPDR said:

MSFS_AutoFPS version 0.4.4.6 has just been formally released and is available here. If you were on the test version and had Auto Updates selected, the app should prompt you to update to this release version. My thanks go to everyone who participated in the test phase and provided valuable feedback.

Summary of changes:

It did like a charm, however it reset all the changed settings which of course can't remember in the first place :)