8 minutes ago, GSalden said:

The target fps has gone up.

Got it. I'm working on a dual implementation of Auto Target FPS and TLOD Min Extra where checking one either unchecks or disables the other due to the aforementioned mutual exclusivity so you can't get yourself into setting conflict trouble.

Edited September 11, 20241 yr by Reset XPDR

14 minutes ago, Reset XPDR said:

Got it. I'm working on a dual implementation of Auto Target FPS and TLOD Min Extra where checking one either unchecks or disables the other due to the aforementioned mutual exclusivity so you can't get yourself into setting conflict trouble.

That would be very welcome.

Thanks to your great work I can taxi , take off and land at Aerosoft Frankfurt where many people (not using your app) see FPS below 10.

🥳

I've managed to get allowing only one of either Auto Target FPS and TLOD Min Extra to be checked, essentially having them operating as radio buttons but are located separately where they usually are. The tooltips, and eventually the readme, are updated to show what will be disabled by the checking action.

Here's how it works. Say you have Auto Target FPS set in your settings. Upon loading the new app version, it sees if you have Auto Target FPS set and, if so, will automatically deselect both VFR and IFR Flight Mode TLOD Min Extra settings (because you can't have both at the same time). The UI would load up looking like this and if you hover your mouse over the TLOD Min Extra checkbox, the tool tip will warn you that checking this will uncheck Auto Target FPS.

 

If you proceed anyway and check TLOD Min Extra, then you'll find that Auto Target FPS is now unchecked.

And vice versa if you now hover over the Auto Target FPS checkbox.

Finally, full circle if you go ahead and check Auto Target FPS.

And where it differs from a normal radio button arrangement is you have neither option selected.

How does that sound?

 

9 minutes ago, Reset XPDR said:

I've managed to get allowing only one of either Auto Target FPS and TLOD Min Extra to be checked, essentially having them operating as radio buttons but are located separately where they usually are. The tooltips, and eventually the readme, are updated to show what will be disabled by the checking action.

Here's how it works. Say you have Auto Target FPS set in your settings. Upon loading the new app version, it sees if you have Auto Target FPS set and, if so, will automatically deselect both VFR and IFR Flight Mode TLOD Min Extra settings (because you can't have both at the same time). The UI would load up looking like this and if you hover your mouse over the TLOD Min Extra checkbox, the tool tip will warn you that checking this will uncheck Auto Target FPS.

 

If you proceed anyway and check TLOD Min Extra, then you'll find that Auto Target FPS is now unchecked.

And vice versa if you now hover over the Auto Target FPS checkbox.

Finally, full circle if you go ahead and check Auto Target FPS.

And where it differs from a normal radio button arrangement is you have neither option selected.

How does that sound?

 

Incredible how you have managed this in a few minutes. 

This will work for both AutoFPS users as Fixed Framerate users.

Well done and a big thankyou 

 

14 hours ago, Reset XPDR said:

While yours is pretty much the only feedback I've had on this latest test version, that's actually a good sign because users are usually very quick to tell me if I've broken something and are often silent if it is all working good. Either that or everyone else has given up in disgust 😆

I would appreciate your testing efforts with the next test build I will be putting out in the next day or so, not so much to test TLOD Min Extra in Auto TLOD automation mode (although that is appreciated), but to regression test TLOD Min Extra in FPS Sensitivity and Tolerance modes just to make sure I didn't break anything there while coding for Auto TLOD.

Another thing I'd appreciate your, and anyone else's, opinion on is whether to scrap Auto Target FPS completely from the app in the next release mainly because it conflicts with the new TLOD Min Extra functionality. Auto Target FPS requires a fixed TLOD Min so that it can calculate a suitable target FPS, whereas TLOD Min Extra requires a fixed target FPS, so it can calculate a suitable TLOD Min Extra ie. the logic needs one item to be fixed to vary the other, hence making them mutually exclusive.

While I could do some UI trickery to grey out the other option when one of these conflicting functions is checked, I get the impression that not a lot of users are using auto target FPS anyway, so the simplest solution is to just completely remove auto target FPS and be done with it.

Your, and others, thoughts on this before I wield the big coding axe are appreciated.

I have been trying test 10 lately but my hardware is too limited. My TLOD is 20 in larger airports and its still a stutter fest. Though somewhat improved performance on descent 

5 hours ago, Sonosusto said:

I have been trying test 10 lately but my hardware is too limited. My TLOD is 20 in larger airports and its still a stutter fest. Though somewhat improved performance on descent 

Am I reading your msg signature correctly?  Are you sending to (2) monitors, one @ 1080p and one @ 4K?  Is that 11G memory?

7 hours ago, Sonosusto said:

I have been trying test 10 lately but my hardware is too limited. My TLOD is 20 in larger airports and its still a stutter fest. Though somewhat improved performance on descent 

The new TLOD Min Extra functionality introduced in these test builds only activates if your system has enough FPS headroom, so you should be seeing similar performance to the last formal release version 0.4.2.16. If it is activating and that's what's causing your stuttering then I suggest you uncheck it and don't use it.

10 hours ago, GSalden said:

Incredible how you have managed this in a few minutes. 

This will work for both AutoFPS users as Fixed Framerate users.

Well done and a big thankyou 

 

There was still a bit more to do to get the interlocks working properly, including on startup, but I think I'm there now. I've also added a message box warning for those who don't read tooltips so they have to acknowledge the consequence of their setting choice if they try to tick both options. I hope to have a test build out today.

Edited September 11, 20241 yr by Reset XPDR

6 hours ago, fppilot said:

Am I reading your msg signature correctly?  Are you sending to (2) monitors, one @ 1080p and one @ 4K?  Is that 11G memory?

Yeah, it wasn't always an issue. Until this test build but I found culprits.  And yes, two monitors (one for apps, 4k for sim). The sim runs TAA at 70%, FG mod in use. 11gb memory for the 2080ti card. 32gb ram total.

I figured it out partly. For some reason, I still have airport workers walking around but I never had them.....they're always off. The other is Auto OLOD. Anything more than 50 and it kind of starts stealing FPS.

Regardless. I have a 7800x3d chip in front of me, and the ddr5 6400ram, 4090 and other goodies will be here in about 6 days.

CANNOT WAIT to finally get solid (er?) 60fps in big hubs as long as I keep my settings not to high on the ground. Gotta have my traffic, ATC and GSX.....

Edited September 12, 20241 yr by Sonosusto

11 minutes ago, Sonosusto said:

Regardless. I have a 7800x3d chip in front of me, and the ddr5 6400ram, 4090 and other goodies will be here in about 6 days.

Happy for you.  I just had the system detailed below built. For GPU I stopped with a 4080 Super in deference to the pending emersion of MSFS 2024 and anticipated nVidia GPU rollouts.  I expect you have been highly taxing the 2080ti.  I migrated from one to a 3080 about two years ago, prior to building this new system.

A new test version 0.4.17-test11 is available here.

Changes since v0.4.2.17-test10:

• Added settings lockout logic, including advisory messages and config file changes, to enforce Auto Target FPS not being able to be selected at the same time as TLOD Min Extra due to these settings being mutually exclusive ie. Auto Target FPS requires a fixed TLOD Min whereas TLOD Min Extra requires a fixed target FPS, hence both can't be active at the same time.
• Added reseeking of TLOD Min Extra after a flight above Alt TLOD Base and back on the ground stopped.
• Minor tweaks to TLOD Min Extra and FPS settling functionality.
• Updated UI so that if Decrease Cloud Quality is not selected, all associated sub-settings are either hidden or collapsed.

Revised summary of where we are right now since v0.4.2.16:

• Added Lossless Scaling (LS) app and associated FG scaling detection to allow the app to show the actual LSFG FPS being produced in MSFS and allow the user to set an LSFG target frame rate.
• Added Reset button to the General section of the UI that will reset your TLOD, Cloud, LSFG, and FG settings to initial app flight start values and will recalculate TLOD Min Extra if required.
• Completely reworked TLOD Min Extra functionality to allow far higher TLOD Mins than previous versions when performance conditions permit, to also work in Auto TLOD automation mode and to reseek after a flight.
• Added settings lockout logic to enforce Auto Target FPS not being able to be selected at the same time as TLOD Min Extra due to these settings being mutually exclusive.
• Completely reworked FPS settle and TLOD Min Extra seek timing be condition based rather than a set time period, resulting in much shorter settle/seek times.
• Added TLOD Max Extra functionality, which is disabled by default, to trigger additional TLOD at higher ground elevations, namely mountain regions, to allow much greater object drawing distance in scenic areas with minimal performance penalty.
• Significantly reduced MSFS memory space interaction by up to 30 times when nothing is being changed by the app, leading to a smoother flight experience.
• Revised status line to show the current allowable TLOD range and simplified app priority and mountains status messages accordingly.
• Updated supporting apps ( MobiFlight Wasm Flight and Dot NET) to their latest versions.
• Added DecCloudQNonExpert config file option setting, which defaults to true, to be able to disable cloud quality reduction in non-expert mode by setting it to false.
• Updated app logging to record events and settings relating to the new TLOD Min Extra and TLOD Max Extra functionality.

 

28 minutes ago, fppilot said:

Happy for you.  I just had the system detailed below built. For GPU I stopped with a 4080 Super in deference to the pending emersion of MSFS 2024 and anticipated nVidia GPU rollouts.  I expect you have been highly taxing the 2080ti.  I migrated from one to a 3080 about two years ago, prior to building this new system.

Yeah, I got all this stuff around 2018-19 and have used it since. 2080ti I had since 2020 because my 1070 failed on me. The 8086k has enough single core juice but its just lacking with everything else. The 4090 I got because I am crazy and way late into the game but at this rate, I wont get anything for probably another 5-6 years again.

I have like 4-7 hobbies.... its bad.

This app made all of it doable, however, with my now older system. The newer system should be a little smoother. 🙂

I've found another mutual exclusive setting combination in Auto TLOD mode only, which is very rare and relatively benign if encountered and that I have addressed in the next build already, but otherwise -test11 now contains everything I wanted in the next formal release.

From my extensive testing, and feedback from others trying out the test builds to date, the new and updated features are working quite well and reliably, so I am getting close to putting out a release candidate.

I will wait a few days to see if any major issues come up with -test11, so please do your best to try and break it and let me know if you are successful! 😂

Sorry all,

Regarding assisting with CPU frame times requested by @Flyfaster_MTN002 and @Reset XPDR, my understanding is that because this application directly accesses and modifies program memory, it has been deemed to be against the EULA and thus cannot be supported by anyone on the MSFS team, nor discussed on the official forums, as far as I am aware.

Don't shoot the messenger, but that my most recent understanding from reading the official forums.

-Matt

Edited September 12, 20241 yr by MattNischan

51 minutes ago, MattNischan said:

Sorry all,

Regarding assisting with CPU frame times requested by @Flyfaster_MTN002 and @Reset XPDR, my understanding is that because this application directly accesses and modifies program memory, it has been deemed to be against the EULA and thus cannot be supported by anyone on the MSFS team, nor discussed on the official forums, as far as I am aware.

Don't shoot the messenger, but that my most recent understanding from reading the official forums.

-Matt

Yes it cannot be discussed on the official MSFS forum, but we have been freely discussing it here for the last 6 months with no red card from MS. In any case, I'm just after a way to get the CPU load of MSFS externally, via Windows performance monitors, like you can supposedly do for any app without breaking any EULAs. My attempts have resulted in reading really low CPU loads for MSFS, like 1-2%, when in a flight and that is clearly not correct. If you can offer any help in this regard it will be much appreciated.