Reset,

Sir you are genius!!

Test 11 is working very very well.

 

Thank you

Mike

A new, hopefully final, test version 0.4.2.17-test12 is available to download here. Only minor changes in this release, most of which relate to Auto TLOD automation method when used with TLOD Min Extra and an FPS cap (so probably just affects me 😄), so more of a regression check to make sure I didn't break anything with the other modes. The ability to now use the Reset button with a hot key, which can be mapped to a voice command with Voice Attack that you need to set up separately, means VR users like me can reset Auto FPS by voice command from within MSFS without interrupting their flight, so I'm very happy about that one!

With this release, I hope to be on the home stretch for formal release, likely to be version 0.4.3 as there have been some significant changes under the hood. The only loose ends I have are regression testing of this release by you fine folk and trying to resolve some recent issues identified recently, although I am reasonably confident both of them are not actual bugs and are user expectation not aligning with how the functions work or should be used.

Changes since v0.4.2.17-test11:

• Added ALT-R hot key to Reset button function, which is particularly useful if you use VoiceAttack and want to assign a voice command to activate the AutoFPS Reset function.
• Added settings lockout logic, including advisory messages and config file changes, to enforce TLOD Base + not being able to be selected at the same time as TLOD Top + with the Auto TLOD automation method due to these settings being mutually exclusive ie. TLOD Base + increases both TLOD Min and Max and is auto adjusting whereas TLOD Top + only increases TLOD Max and is fixed, hence both can't be active at the same time.
• Minor tweaks to TLOD Min Extra and FPS seek functionality with Auto TLOD automation method to significantly reduce seek time when conditions are very favourable.

Example configuration with Voice Attack for voice activated Reset function:

 

 

@Reset XPDR

Tested during the last few days, a must have for me!

Pause when MSFS not in focus is working fine, though I only had to use it since installing the FSR3 mod for my 3090 and using FG.

Only thing I noticed is the initial settle time (or start of the settle time) during load-in is too short for my system. With a few addons running, GSX menu popping up and the PMDG777 initializing I always get a LOD of 50 after a very short settle time.

When I press reset, LOD increases to 100-180, depending on the airport of cause.

 

Cheers!

Edited September 13, 20241 yr by LibraryMan

56 minutes ago, LibraryMan said:

@Reset XPDR

Tested during the last few days, a must have for me!

Pause when MSFS not in focus is working fine, though I only had to use it since installing the FSR3 mod for my 3090 and using FG.

Only thing I noticed is the initial settle time (or start of the settle time) during load-in is too short for my system. With a few addons running, GSX menu popping up and the PMDG777 initializing I always get a LOD of 50 after a very short settle time.

When I press reset, LOD increases to 100-180, depending on the airport of cause.

 

Cheers!

Thanks for the feedback. I must admit that I too have experienced this, especially loading in to VR, so perhaps I should make the initial settle logic be time based, like it used to be, then condition based after that. It used to be 20 seconds, whereas now it is stable FPS any time after 5 seconds and that can sometimes only be 5 seconds if conditions are right. Would the original 20 seconds be long enough for you?

14 hours ago, Reset XPDR said:

Regarding exactly when you are going into the MSFS settings and changing it back to medium, are you still in your flight with AutoFPS running when you do so? If you are doing it then, the cloud setting will not permanently stick because AutoFPS is managing it at that time and will restore what it thinks is your default cloud quality setting based on when it started, not what you changed it to mid-flight. This could possibly be why you are experiencing this issue.

The upshot of this is that if you want to change your default settings with AutoFPS running you need to be in the main menu of MSFS and NOT in a flight. If you are in a flight, you need to exit the AutoFPS app completely, make the MSFS setting change then restart AutoFPS.

Also, I know this sounds obvious but it is easy to not do correctly, when changing your MSFS settings for VR make sure you are looking at VR settings (like your screenshot) and that you are not inadvertently making changes to PC mode  view that it defaults to if you change settings while in PC mode.

What might be happening is that I start the clouds at High and during the flight the AutoFPS changes this setting to medium due to performance, if I end the VR session with the GPU at high usage (at night near the gate), the MSFS will continue with the setting at Medium. That's why when I start another VR session the system doesn't return to High, does that make sense?

3 hours ago, Reset XPDR said:

Would the original 20 seconds be long enough for you?

That would be working fine for me! Thanks!

Did a 2 hr flight with test12 in Auto LOD mode. Performance was good throughout the flight. Normally I don't use Auto LOD, so I'm not that familiar with it. It seems that TLOD base extra and TLOD top extra are mutually exclusive. 

Landed with a TLOD of 50 even though I had a lot of headroom. After parking at the gate, TLOD gradually increased to 400. 

Log file: https://drive.google.com/file/d/12IZXmP3A5y6fQyACJUrfd21IHiB_W8lk/view?usp=sharing

Edited September 13, 20241 yr by Cpt_Piett

8 hours ago, TadeuPrimo said:

What might be happening is that I start the clouds at High and during the flight the AutoFPS changes this setting to medium due to performance, if I end the VR session with the GPU at high usage (at night near the gate), the MSFS will continue with the setting at Medium. That's why when I start another VR session the system doesn't return to High, does that make sense?

After not being able to reproduce this in the latest test version, I reinstalled 0.4.2.16 and was able to get it to do what you are experiencing. Looking at the code, you have uncovered a rare set of circumstances that didn't come up in my testing that can cause this, so well done on finding it and explaining how to reproduce it!

The good news is that the recent changes I made to the app reset code to accommodate the new Reset button is that on a graphics mode change like to/from VR there is a full reset of TLOD and clouds, regardless of their existing state, whereas with 04.2.16 if only reset clouds if the last state was clouds quality decrease was active, which could be bypassed using your unique sequence of events. As such, it turns out I fixed it by tightening up the reset process without even knowing about your issue!

To that end, can I ask you to install the latest .17 test build, which is very stable, from here and confirm that this is no longer an issue. You can easily return to 0.4.2.16 by running its installer and your existing settings will be reset. Please let me know how you go.

1 hour ago, Cpt_Piett said:

It seems that TLOD base extra and TLOD top extra are mutually exclusive.

Yes they are. The reason is that with the Auto TLOD automation method, TLOD Base Extra is used as an offset to the entire TLOD altitude schedule (so effectively TLOD Base and TLOD Top go up by the same amount) as opposed to FPS sensitivity/tolerance methods where it only gets added to TLOD Min. Because of this, TLOD Top Extra can't be used with it otherwise there would be two things trying to control TLOD Top and that doesn't work well.

1 hour ago, Cpt_Piett said:

Landed with a TLOD of 50 even though I had a lot of headroom. After parking at the gate, TLOD gradually increased to 400. 

It was bit hard to see what was happening in that second half of your flight because you changed settings quite a few times. It looks like this is when you turned on TLOD Base + and it didn't stick. You can see below it tried because your FPS dropped, suggesting it was moving TLOD up during a seek process, so you must have experienced unstable FPS for too long for it to give up, most likely because you run very high TLODs.

If at any time TLOD Base + doesn't seem to be doing it's thing, just hit the reset button and it should put you right. I don't have this mode constantly recalculating TLOD Extra like it does for FPS sensitivity/tolerance methods because Auto TLOD method is with TLOD Top + is intended for capped FPS being exactly the same as the target FPS and only go below that target FPS during the seeking process so that the FPS is maintained as much as possible.

As such, I would not use Auto TLOD for your use case because you do not use it the way it was intended (which is fine), but I realise you were helping me out with testing and this feedback is useful anyway as it confirms what I thought might happen, so thanks for that. For the remainder of this testing phase, can I ask that you go back to your usual FPS sensitivity method and confirm that it is still working as before.

Edit: Right after I posted this I realised that TLOD Base + can't have tried seeking when I said it was because there are no log file items showing the seeking process being active. I shall investigate further. Sorry for messing you around!

Edited September 14, 20241 yr by Reset XPDR

Duplicate

Edited September 14, 20241 yr by Reset XPDR
Duplicate

1 hour ago, Reset XPDR said:

It was bit hard to see what was happening in that second half of your flight because you changed settings quite a few times

Yeah, sorry about that. I should have just stuck to the same settings for the duration of the flight. I got curious, and things got a bit messy after that. 

1 hour ago, Reset XPDR said:

As such, I would not use Auto TLOD for your use case because you do not use it the way it was intended (which is fine), but I realise you were helping me out with testing and this feedback is useful anyway as it confirms what I thought might happen, so thanks for that.

That's right, it was for testing purposes. Hopefully, it was somewhat helpful. After this, I'll return to my usual FPS sensitivity 🙂

1 hour ago, Reset XPDR said:

so you must have experienced unstable FPS for too long for it to give up, most likely because you run very high TLODs.

Again, I'm not sure as I'm not very familiar at all with Auto TLOD. I was thinking though - could this be a good alternative for people who prefer DynamicLOD?

Edited September 14, 20241 yr by Cpt_Piett

6 minutes ago, Cpt_Piett said:

Yeah, sorry about that. I should have just stuck to the same settings for the duration of the flight. I got curious, and things got a bit messy after that. 

That's right, it was for testing purposes. Hopefully, it was somewhat helpful. After this, I'll return to my usual FPS sensitivity 🙂

Again, I'm not sure as I'm not very familiar at all with Auto TLOD. I was thinking though - could this be a good alternative for people who prefer DynamicLOD?

Well it turns out your test scenario not only revealed one logic issue with resetting TLOD Base + properly when switching between Mtns+ and TLOD Base + but I also found a copy and paste typo in that area that would have uncovered another obscure bug eventually, so it turns out your testing has been invaluable in helping me iron out some final bugs. As such, please completely ignore my last request to go back to FPS sensitivity mode only and you just keep testing whatever you want because it has all been useful. 👍

And you are right, Auto TLOD is intended to be an alternative to DynamicLOD because of the way it changes TLOD on an altitude schedule rather than FPS based. I have somewhat complicated its use with the introduction of TLOD Base + because then does work to an FPS as well but only if headroom is available otherwise it will disable itself quite quickly and be back to altitude schedule only. As such, Auto TLOD is now like an implementation of DynamicLOD with two altitude/TLOD pairs but, with the new TLOD Base +, it is smart enough to know when it can supplement these TLOD values when conditions support it. This is the mode I will be using for my VR flying and IMO gives a better experience than DynamicLOD configured that way.

I will release a new test build when I've fixed the two bugs you helped uncover, which will also include putting back in an the initial settle timer of 20 seconds and be condition based thereafter. In the meantime, please keep trying to break -test12! 😂

Guys, I need some help.

I am using this great app icw Lossless Scaling.

Client LS X2 ( 1 display )

Server LS X3 (2 displays )

AutoFPS has had several updates and LS has had an update ( to v2.9)

The following issue occurs on the server :

after 1,5+h the main screen on the server goes black. The extra outside view monitor keeps working, The sound keeps working.

To solve this I have to bring up the LS GUI and then Unscale / Scale and the main monitor works again.

As MSFS itself did not stop it is clearly that LS had an issue. 
However, when using LS alone without AutoGPS I do not have this issue.

Also several updates back icw LS 2.8 it also worked.

All suggestions are welcome 

( settings LS ? )

 

 

Edited September 14, 20241 yr by GSalden

1 hour ago, GSalden said:

However, when using LS alone without AutoGPS I do not have this issue.

What happens if you shut down AutoFPS when the display goes black?

I have relooked at the AutoFPS LS detection code and it is as simple as:

"Hey Windows, is LS running?"

• if (Process.GetProcessesByName("LosslessScaling").Length > 0)  LsModeEnabled = true;

"Hey Windows, open the LS config file for me to read"

• XDocument xmlDoc = XDocument.Load(xmlFilePath);

This is only done once at the start of a flight or if you hit the Reset button.

As such, I struggle to see how something as benign as AutoFPS detecting LS running and reading an unlocked XML LS config file via Windows functions at startup then never actually interacting directly with LS or MSFS about it's running state could cause a screen blanking issue in MSFS an hour and a half later.

 

Edited September 14, 20241 yr by Reset XPDR