45 minutes ago, vgbaron said:

MSFS ctding leaving changed values that then get read vas defaults.

Got it. Actually I'm working on this right now and it is looking very promising, now that I've worked out how to remove XML nodes. 😁

I have the improved default settings save/restoration fully functioning now.

When the app loads, it looks in its config file for default settings being saved there. If they are there, it means they didn't restore properly from either MSFS CTDing or an issue with the app, so the app will use the defaults saved in the config file, otherwise it will read the defaults from MSFS settings. When you finish a flight or exit the app, the default settings used for the session will be restored and the config file entries will be removed, signifying that it was a clean restoration for the next session. It is simple, but it works!

 

22 minutes ago, Reset XPDR said:

I have the improved default settings save/restoration fully functioning now.

When the app loads, it looks in its config file for default settings being saved there. If they are there, it means they didn't restore properly from either MSFS CTDing or an issue with the app, so the app will use the defaults saved in the config file, otherwise it will read the defaults from MSFS settings. When you finish a flight or exit the app, the default settings used for the session will be restored and the config file entries will be removed, signifying that it was a clean restoration for the next session. It is simple, but it works!

 

Thanks for fixing this so quickly! Looking forward to the improved ATFPS mode too - but don't stress, take your time 🙂

When you say "it will read the defaults from MSFS settings" - are you referring to what we set in the menu, or in usercfg.opt? Or perhaps these will always be the same. 

As we speak I'm in an experimental aircraft somewhere North of the Polar Circle, experimenting with some experimental settings in non-expert non-ATFPS mode. I have to say that generally, I like what I see. Which of course is a huge understatement 😄 

I found that a TLOD of 1800 (!) was perhaps unessecarily (I can never spell that word right) high, so I've settled with a more modest 955 @ target 60 FG-FPS for now. 

18 minutes ago, Cpt_Piett said:

When you say "it will read the defaults from MSFS settings" - are you referring to what we set in the menu, or in usercfg.opt? Or perhaps these will always be the same. 

MSFS sets its own settings based on what it reads in your usercfg.opt when it starts up but if you change them in game it doesn't write them back to usercfg.opt until the game exits. The read the default settings from MSFS settings memory, because you may change them in the main menu and it needs to use those for subsequent flights.

18 minutes ago, Cpt_Piett said:

Thanks for fixing this so quickly! Looking forward to the improved ATFPS mode too - but don't stress, take your time

One minute I'm putting out too many test versions, and the next it is hurry up with the next one! 🤣 A new test version should be out today with this and more. From now I on, unless something is so badly broken in a test release that it needs fixing immediately, I will put out no more than one test version per day so as not to overload testers with too many test versions too quickly.

18 minutes ago, Cpt_Piett said:

I found that a TLOD of 1800 (!) was perhaps unessecarily (I can never spell that word right) high, so I've settled with a more modest 955 @ target 60 FG-FPS for now. 

That's still ridiculous, but possibly good for edge case testing anyway, so go for it!

Edited March 11, 20242 yr by Reset XPDR

3 hours ago, Reset XPDR said:

Already acknowledged and thanks for putting it so enthusiastically. 😄

I guarantee I will not put this feature out behaving like that. It will either be fixed or removed.

LMAO!  I can get "enthusiastic" when I'm tired with only one eye open and posting.  My Quality Control can suffer at that time.  🤪

Just to be sure, I wasn't complaining about the quality of the app.  Just reporting what I was experiencing with the new auto-FPS ability in obviously what would be only one of many possible flight environment scenarios.  It just surprised me that it was doing what I saw it doing at the time.

I was like you.  I made my post then went to sleep.  When I woke up and logged back on my first thought was, "Darn!  I may have implied something I never intended to imply!"

Your app still improves my flight simming experience greatly.  I was just surprised at what the auto-FPS did when I used it.  In the scenario I was in at the time, it didn't improve it for the reasons I stated.  I didn't mean to imply the entire app was "useless" or "not needed".  

I'm gonna go make some coffee and eat a few chocolate muffins with it to get my caffeine and sugar levels back to their normal states.  You keep up the great work with the app.  It's an overall great improvement for the flight sim experience. 😄 

11 minutes ago, FalconAF said:

LMAO!  I can get "enthusiastic" when I'm tired with only one eye open and posting.  My Quality Control can suffer at that time.  🤪

Just to be sure, I wasn't complaining about the quality of the app.  Just reporting what I was experiencing with the new auto-FPS ability in obviously what would be only one of many possible flight environment scenarios.  It just surprised me that it was doing what I saw it doing at the time.

I was like you.  I made my post then went to sleep.  When I woke up and logged back on my first thought was, "Darn!  I may have implied something I never intended to imply!"

Your app still improves my flight simming experience greatly.  I was just surprised at what the auto-FPS did when I used it.  In the scenario I was in at the time, it didn't improve it for the reasons I stated.  I didn't mean to imply the entire app was "useless" or "not needed".  

I'm gonna go make some coffee and eat a few chocolate muffins with it to get my caffeine and sugar levels back to their normal states.  You keep up the great work with the app.  It's an overall great improvement for the flight sim experience. 😄 

I gathered you weren't complaining but it is one of the strongest constructive feedback statements I have seen for a while and it actually made me smile because of your "enthusiasm" 😄

And you'll be pleased to know that I have already disabled auto target FPS increases while in the air in my test bed version until I can work out a better mechanism to use this without compromising descent graphics quality by having to go through TLOD min and cloud quality reduction to reduce if necessary on descent.

Duplicate

Edited March 11, 20242 yr by Reset XPDR
Duplicate post for some strange reason.

I keep getting astounded by the capabilities of your app, Reset. Been flying in non-expert non-ATFPS mode for a while now, and I do realise that I might possibly be exploiting the capabilities of your app, slightly. Sorry for that! I promise not to tell Microsobo. 

But I have to say this: I think when flying GA, I'd rather settle for a lower FPS and much, much higher TLOD. It just looks too gobschmackingly good!

Just departed from ENTC Tromsø, this is what I got on the ground: 

EDIT: @Reset XPDR, I just noticed in the above image, the status line shows TLOD+ 600 priority. Not exactly sure what this means, but my guess is that it relates to this:

Quote

Changed TLOD Min Extra behaviour in non-expert mode to only be enabled on descent if transitioning from FPS to TLOD Min priority and TLOD Min Extra TLOD is currently being achieved.

Am I correct?

Up at FL180 en route to North Cape and beyond the Arctic Circle:

The scenery just looks too delicious that I can't see any good reason not to be doing this. 

Of course, when flying the Fenix into Toronto Pearson with heavy clouds and AI traffic, I'd probably go for expert mode and more sensible settings. But to have this kind of flexibility - awesome 😄 

If you don't hear from me again, I've probably disappeared into a new dimension that I might call MSFS-Nirvana  🤪

52 minutes ago, Reset XPDR said:

LMAO!  I can get "enthusiastic" when I'm tired with only one eye open and posting.  My Quality Control can suffer at that time.

Believe me, I've been there! In fact I'm typing with only one eye open as we speak!

Edited March 11, 20242 yr by Cpt_Piett

I'm away from this thread for a couple of days and there's at least one new feature and tons of messages!

I downloaded and installed v0.4.2-test_10Mar240100Z in order to try out the new Auto FPS feature. I put it in a very taxing environment and felt that it created too many stutters by trying to change settings to hit the FPS mark. Between changing the clouds (which I find creates the biggest stutters) and the TLOD a lot, I felt like a lot of stutters were created when I kept oscillating around the FPS mark.

I turned off Auto FPS and went back to non-Expert mode, which I had previously felt worked really well. I don't know if something changed in the underlying logic of that mode, but I also felt like that mode wasn't as smooth as it had previously been. I also felt that it varied the TLOD a fair bit but that it hit a hard limit when trying to adjust things downwards. As such, I have settled on Expert mode again and enable a 50 TLOD at 50 feet and that seems to be working well in demanding environments. I will try the insane settings up above a bit in more remote locations to see how much of a difference I see.

1 hour ago, Cpt_Piett said:

Of course, when flying the Fenix into Toronto Pearson with heavy clouds and AI traffic, I'd probably go for expert mode and more sensible settings. But to have this kind of flexibility - awesome 😄 

How did you set the settings that high in non-Expert mode? Did you alter the UserOpt.cfg file manually before launching the sim?

24 minutes ago, mmcmah said:

How did you set the settings that high in non-Expert mode? Did you alter the UserOpt.cfg file manually before launching the sim?

That’s right. I tweaked usercfg.opt to TLOD 6.00000. Then after loading the flight I started AutoFPS in non-expert, non-auto target fps mode. 

The app will then essentially set TLOD min at 600/2 and TLOD max at 600x3, if I understand this correctly. It’s still a bit muddy to me how this logic works though.

12 minutes ago, Cpt_Piett said:

The app will then essentially set TLOD min at 600/2 and TLOD max at 600x3, if I understand this correctly. It’s still a bit muddy to me how this logic works though.

Interesting. I saw the TLOD min / 2, but not the x3 effect when running in non expert non auto FPS mode. I only saw it increase to three bae TLOD set in the sim, not higher, deeper having a 20-24 FPS cushion vs me desired FPS setting.

7 hours ago, Reset XPDR said:

Are you using non-expert mode or TLOD Min on ground/landing and/or Auto Target FPS? What sim values if any, are showing as changing while these stutters happen?

No. Expert mode on, no Tlod min, no Auto target.

I did try though, ticking the various options on or off which did not make a difference.

what do you mean by “sim values”?

thanks!!

// Mike

10 minutes ago, ha5mvo said:

No. Expert mode on, no Tlod min, no Auto target.

I did try though, ticking the various options on or off which did not make a difference.

what do you mean by “sim values”?

thanks!!

// Mike

These:

17 minutes ago, ha5mvo said:

No. Expert mode on, no Tlod min, no Auto target.

 

I just realised, when you say no Tlod Min I assume you mean TLOD Min on ground/landing is unchecked. This will cause the app to continuously adjust for the best TLOD for your target FPS on the ground and is probably what you are seeing. I suggest you reenable this option and if you want TLOD to change lower than the default 1000 ft, just set a lower Alt TLOD like 100 ft, which is what I do when flying GA.