3 hours ago, Cpt_Piett said:

What do you mean? Because I tried to help with an issue? Because I mentioned CIV? To be frank, Frank… It’s not the first time you voice your opinion on what should be said in this thread and not. Perhaps you’re a bit out of place doing that?

Not making an attack, but the discussion, which certainly has value, seemed to be better served in its own topic.  No malice intended. Just wishing to see staying topics on course.  Have been guilty myself over the past 23 years diverting topics and believe learned from those.  And the comment was not directed at you personally by any means. So please do not take it as such.

 

Edited February 19, 20251 yr by fppilot

Quote

From the readme: "A + next to TLOD indicates that TLOD Min + has been activated and that a higher TLOD Min should be expected. Similarly, a + next to ATLOD indicates that TLOD Base + has been activated and that a higher TLOD offset across the entire altitude schedule should be expected."

Trying to understand the readme...

Using Auto TLOD method with FPS capped in MSFS at 60, Target PC FPS=60.

Does the above quote mean that TLOD (base, top, and/or current) will increase as able to keep the FPS at 60? In other words, TLOD will increase to whatever the maximum is that will still respect the FPS target?

 

34 minutes ago, prolixindec said:

Trying to understand the readme...

Using Auto TLOD method with FPS capped in MSFS at 60, Target PC FPS=60.

Does the above quote mean that TLOD (base, top, and/or current) will increase as able to keep the FPS at 60? In other words, TLOD will increase to whatever the maximum is that will still respect the FPS target?

Yes, that's correct. In other words, the TLOD increase will remain in place at all altitudes until such time as the target FPS is no longer able to be maintained, in which case it will automatically decrement the additional TLOD, down to zero if required. 

At this time, it will not attempt to increase TLOD again after the initial seek process or if conditions improve later, as the only way the app can currently do this by the abrupt seeking process it does at the start of a flight, which you do not want to be happening while you are in the air. You can of course hit the reset button at any time and it will re-seek, but at least then you are the one that initiated it so you shouldn't be surprised when it happens.

I will shortly be working on revised TLOD extra functionality whereby this TLOD increase should be able to occur in flight, with a much slower re-seeking process so as to only minimally, possibly negligibly, impact a user's ongoing flight. You are more than welcome to participate in the test phase and a discussion group has been established here for that purpose.

Edited February 19, 20251 yr by Reset XPDR

Thanks, I signed in to GitHub and I'll be following (with the same username). 

Just want to say for now that things seem to be working very well for me. I've noticed that ATLOD+ has ranged from 150-900, to 400-1150, with TLOD Base=50 (+ checked) and I'm seeing just what I want to see, which is 60 fps no matter what else is going on. Happy to help troubleshoot or provide input, but right now AutoFPS seems to be doing just what I'd want it to do.

 

16 minutes ago, prolixindec said:

Thanks, I signed in to GitHub and I'll be following (with the same username). 

Just want to say for now that things seem to be working very well for me. I've noticed that ATLOD+ has ranged from 150-900, to 400-1150, with TLOD Base=50 (+ checked) and I'm seeing just what I want to see, which is 60 fps no matter what else is going on. Happy to help troubleshoot or provide input, but right now AutoFPS seems to be doing just what I'd want it to do.

 

Thanks for joining. The more the merrier!

Out of interest and of possible relevance, is this with MSFS 2020 or 2024?

Edited February 19, 20251 yr by Reset XPDR

MSFS 2024.

7 minutes ago, prolixindec said:

MSFS 2024.

Interesting. Others are reporting stuttering issues with the TLOD set that high with 2024 in complex scenarios. Are you flying in complex scenarios (ie. complex aircraft, scenery, photogrammetry, and/or addons) or is this for VFR flying in remote areas?

My use case is fairly unique (maybe there are a few hundred of us). I use MSFS as the scenery generator for another flight simulator, Aerowinx PSX. The latter provides all the aircraft systems, flight physics, and cockpit visuals. MSFS is used only to show what’s outside. That said, my performance in MSFS 2024 is comparable to others in this thread (e.g. Piett), so I’m seeing AutoFPS as an essential component just like people who use MSFS normally.

I have everything in MSFS set to the maximum possible; photogrammetry on, etc.

Still getting used to 2024, I’ve only had it for two weeks. My latest flights have been at medium-level airports with between 0 and 70 live aircraft injected with PSXTraffic. I haven’t done any real testing yet at heavy airports, because of demoralizing experiences in 2020. I’m still working up the courage to do that. 

Edited February 19, 20251 yr by prolixindec

6 hours ago, fppilot said:

And the comment was not directed at you personally by any means. So please do not take it as such.

Thanks for the reply. Sorry that I overreacted. 

On 2/18/2025 at 12:04 AM, Cpt_Piett said:

don't know until I do some more in-depth testing. Since CIV7 released sometime last week, I haven't used the sim 😉 But I got back into the sim tonight, and I'll keep an eye on things and report back if I discover anything useful. 

I didnt even get a chance to get a tank, game ended. No more one more turn! 

For anyone that wants to participate in the 0.4.4.7-test TLOD Base + improvements test phase, test1 has just been released and is available here. Discussion of this and all future 0.4.4.7 test versions will be conducted here, hence there will be no further updates on this here at avsim until it is formally released.

4 minutes ago, Reset XPDR said:

For anyone that wants to participate in the 0.4.4.7-test TLOD Base + improvements test phase, test1 has just been released and is available here. Discussion of this and all future 0.4.4.7 test versions will be conducted here, hence there will be no further updates on this here at avsim until it is formally released.

Whats new in this one reset? my previous was 4.5 i think

2 minutes ago, sonny147 said:

Whats new in this one reset? my previous was 4.5 i think

Click the link and you will see. You should be on 0.4.4.6 already anyway, which was released 2 days ago and to which I recommend you upgrade.

BTW, with 0.4.4.6 you can check + Tests next to the updates choice on app startup and you will be notified when any new test version has been released, including a link to show you what is in it and the installer to download if you wish.

In reference to the VRAM, I wonder if there is a possibility of modifying the offscreen terrain pre-cache option. Right now, we are only allowed to make basic changes (Low, Medium, High, Ultra), and their effects are very abrupt: in medium mode, there is a considerable reduction in VRAM usage, but at the same time, when you pan the camera, the mesh pop-up is horrible, and the only way to avoid it is by selecting high mode, which consequently increases the VRAM. I wonder if there would be any way, using your magic, to make finer adjustments to this parameter (in percentage, for example), as it is a powerful tool for controlling VRAM without having to reduce the TLOD so much.

18 minutes ago, Maddormo said:

In reference to the VRAM, I wonder if there is a possibility of modifying the offscreen terrain pre-cache option. Right now, we are only allowed to make basic changes (Low, Medium, High, Ultra), and their effects are very abrupt: in medium mode, there is a considerable reduction in VRAM usage, but at the same time, when you pan the camera, the mesh pop-up is horrible, and the only way to avoid it is by selecting high mode, which consequently increases the VRAM. I wonder if there would be any way, using your magic, to make finer adjustments to this parameter (in percentage, for example), as it is a powerful tool for controlling VRAM without having to reduce the TLOD so much.

I just took a look at the MSFS memory map and unfortunately the terrain pre-cache option is an integer with only 4 possible values, namely 0 - low, 1 - medium, 2 - high and 3 - ultra. As is the nature of integer variables, it is not possible to have finer adjustments between each value so your desired solution is not feasible sorry.