55 minutes ago, mikeklimek said:

I would also willingly donate, this app is phenomenal! Between this app, the smoothness of the beta, and frame generation, I'm in flight sim nirvana.

No need to donate. I do it for the challenge and a bit of self interest.

From time to time I'll be dropping test versions, announced here, before formally releasing a new version to get other people to trial it, as I can't possibly cover all combinations of use, software and hardware configurations with my own testing. If you do want to help me out, participate in the trial and give me feedback on what's new and what, if anything, is no longer working. If you have any major issues, it is easy enough to go back to the last formal release by running its installer and updating over the top of it.

As a heads up, I'll be releasing a test version shortly. Nothing major, rather a few minor bug fixes, refinements and a bit of fine tuning of the TLOD Min on Ground/Landing logic, the latter of which I want to make sure people are happy with it before I formally release it.

As recently hinted at, a test version for the next release of MSFS2020_AutoFPS is now available for download here for volunteers to trial some new refinements and minor bug fixes. Please only participate if you are already familiar with the app, are confident with what existing settings do, generally understand what the changed functionality will be and are willing to provide feedback on any issues you find.

New test version 25Feb240230Z:

• Modified TLOD Min on Ground/Landing logic to lock out TLOD increases once final descent to landing occurs, which was previously able to occur if leveling off or slightly climbing during that descent phase. It now uses a predictive approach to determine the trigger altitude at which this occurs and is based on nominal TLOD stepping (derived from FPS tolerance), current descent rate and how much of a TLOD change is required to get down to TLOD minimum. The predictive trigger altitude has a base of 1000 ft and works upwards from there. In this test version you can see what this continuously calculated altitude is, as well as the state of the internal logic flags for TLOD increase lock out, on the app status line. These are Prime, which should change to true at 1000 ft above the instantaneous predictive trigger altitude, and Active which should change to true as long as Prime is already true and you have descended below the instantaneous predictive trigger altitude. When Active is true and your aircraft remains below the instantaneous predictive trigger altitude, TLOD should never increase. Once you descend below 500 ft, both of these flags should reset to false.
• Changed cloud quality recovery to additionally occur if TLOD Min on Ground/Landing is enabled and FPS is at least 15% over the FPS target.
• Fixed cloud quality reduction logic issue where when active it was not getting reset on re-selection of TLOD Min on Ground/Landing.
• Changed startup to load PC FPS target by default in lieu of original FPS target that is no longer used.
• Added app version recorded at start of log file
• Added test version option to log key sim values every 10 seconds, and app settings on startup and whenever they change, with a checkbox to enable that is only visible in test mode. This will be disabled in release versions, so enjoy while helping out with test trials!

 

3 hours ago, Reset XPDR said:

As recently hinted at, a test version for the next release of MSFS2020_AutoFPS is now available for download

I haven't had a chance to do any comprehensive testing yet, but I've been running the new version in the background whilst parked on the ground (been testing some other stuff in the sim). I've restarted the sim numerous times, and the app have started correctly with MSFS every time, indicating in green on all parameters. 

I'll report back when I've tried it up in the air!

Edited February 25, 20242 yr by Cpt_Piett

And now as a windows store app with auto update function - that would be the icing on the cake 

Reason: As a simmer you have soooo many tools to take care of (Navigraph, ATC, StreamDeck, MiniFCU, etcpp) that it would make life a lot easier for us 🙂

It´s such a great tool. Thank you for that!

Great utility. Works like a charm. Easy install. No fiddling around with settings. No moving files here and there. 

Hopefully, at some point the developer can make some money off of this tool. 

Asobo should include this tool in MSFS 2020 by default. 

Stupid question that was mostflikely already answered somewhere: if I use FG, what value do I put for FPS? My guess: the FPS before FG, correct? So if I want a minumum of e.g. 70FPS with FG, I put 35 in the tool? Or 70?

1 hour ago, AnkH said:

My guess: the FPS before FG, correct?

That’s the way I do it. It gets a bit confusing as you’d never see FG-FPS reported in the app, as it’s disabled as soon as MSFS is in the background. 

Edited February 25, 20242 yr by Cpt_Piett

2 hours ago, AnkH said:

Stupid question that was mostflikely already answered somewhere: if I use FG, what value do I put for FPS? My guess: the FPS before FG, correct? So if I want a minumum of e.g. 70FPS with FG, I put 35 in the tool? Or 70?

 

45 minutes ago, Cpt_Piett said:

That’s the way I do it. It gets a bit confusing as you’d never see FG-FPS reported in the app, as it’s disabled as soon as MSFS is in the background. 

Yes, you input your desired Target FG FPS, hence the label Target FG FPS. It is also covered in the readme. If anyone can think of a clearer way to show this, please let me know because this question is coming up quite often.

Edited February 25, 20242 yr by Reset XPDR

I suggest to investigate, is there way to disable ground services, when airborne. Msfs injects lots of airport simobjects, when flying near. 

2 hours ago, Reset XPDR said:

Yes, you input your desired Target FG FPS, hence the label Target FG FPS.

I think I was unclear in my answer to @AnkH, as I just said "that's the way I do it", without actually explaining how I do it 🤦‍♂️ What I meant to say was what you wrote above  🙂

I've used this app since the early stages of the development phase, but it took a while to wrap my head around the fact that the app simply cannot list the FPS with FG on, as FG turns off as soon as MSFS is no longer in focus. In other words, it can only display the native FPS - which is the value in the dev mode FPS overlay. 

I do think, however, that the way it is now is as clear as it's going to get. 

9 hours ago, Reset XPDR said:

Modified TLOD Min on Ground/Landing logic to lock out TLOD increases once final descent to landing occurs, which was previously able to occur if leveling off or slightly climbing during that descent phase. It now uses a predictive approach to determine the trigger altitude at which this occurs and is based on nominal TLOD stepping (derived from FPS tolerance), current descent rate and how much of a TLOD change is required to get down to TLOD minimum. The predictive trigger altitude has a base of 1000 ft and works upwards from there. In this test version you can see what this continuously calculated altitude is, as well as the state of the internal logic flags for TLOD increase lock out, on the app status line. These are Prime, which should change to true at 1000 ft above the instantaneous predictive trigger altitude, and Active which should change to true as long as Prime is already true and you have descended below the instantaneous predictive trigger altitude. When Active is true and your aircraft remains below the instantaneous predictive trigger altitude, TLOD should never increase. Once you descend below 500 ft, both of these flags should reset to false.

I've had some time to test 0.4.1, doing several approaches and touch 'n go's in the TBM850. I think I'm starting to understand how the new logic works. I noticed on approach that the app lists a Trigger Alt value. In my case it was around 1700. As I reached that altitude, the TLOD started gradually decreasing to TLOD min, which it elegantly reached at 1000ft. So I guess the app calculates this Trigger Alt in order to be able to gradually reach TLOD Min at 1000 AGL. 

This IMO is an excellent approach as it stays locked from 1000 AGL and will not change drastically when descending on final approach. My TLOD max is 400, Min 100. So I guessed that based on those values the app calculates the Trigger Alt. 

Am I understanding this correctly? Sorry but had some trouble deciphering your explanation. 

And I guess Primed: True could mean that the app gets "ready" to start decreasing TLOD on descent. And Active: True means, well that it starts doing so. I'm just wildly guessing here, trying to understand the new logic. 

I'm wondering though that the terms Trigger Alt, Primed and Active will confuse people, and perhaps should be moved to the expert section. But perhaps you only intend to include those in the test version, so that we might understand better what's happening under the hood. 

 

Edited February 25, 20242 yr by Cpt_Piett

I just tried it and wow, it is super easy and works even better than the original Dynamic LOD app. Super impressive 👍. 

Small question, I apologize in advance if was already answered as I looked in the readme but couldn't find an answer. For FG target FPS, I assume we set here the FG FPS (the one we see from Nvidia overlay) not the in-game one, correct? 

Ah is answered here 

 so basically FPS before FG aka the one is reported in MSFS not Nvidia overlay 

For those slightly confused around the 'Target FPS' setting, here's how I think about it (maybe this will help):

The 'Target FPS' setting is one that can hold, remember, and use three different values depending on how you are using your sim:

• Target PC FPS  - for users who have FG and VR turned off (default).
• Target FG FPS - for users who have FG turned on.
• Target VR FPS - for users who have VR turned on.

The app will automatically "sense" how you are using your sim and automatically switch to that "mode" or value that you can use (and change to your preference) when in that mode.  Examples:

1. Let's say I open the app but have MSFS closed.  The app will default to 'Target PC FPS' because it doesn't "sense" any use of FG or VR (which makes sense because MSFS is closed).  I could set this to value to 30 fps which is what it will use when FG and VR isn't turned on.
2. Now let's say I open MSFS and load into an airport, sitting in the cockpit ready to go--since I'm not using FG or VR, same thing: 'Target PC FPS' is used (and can be changed to my preference).
3. Now let's say I'm a user that decides I want to turn on and use FG.  I load into an airport and am sitting in the cockpit ready to go---the app now senses I'm using FG, so it'll switch to 'Target FG FPS'. Since I'm now using FG, I would go into that field and enter 60 fps because that's double my 'real' framerate, and what I want the app to maintain when I'm using FG.
4. Same principle when turning on VR.

The app will remember what values you entered for all 3 scenarios and auto-switch to those modes/values when it sees what you're using (FG, VR, or neither).

Edited February 25, 20242 yr by mikeklimek

On about my 7th flight now since installing this app. I have to say, it seems like MSFS is running great now, very smooth.