3 hours ago, Reset XPDR said:

Someone has already put up on the MSFS forum what I think is a great half-way compromise for this sort of mod to exist legitimately in future here, namely to give us devs a simconnect interface to make MSFS settings changes externally. This way Asobo doesn't have to code these features in MSFS themselves, although they could have a very basic implementation, and devs like me can come out of hiding and make apps like these even better.

I recommend everyone using this app and who are on the MSFS forum vote for this wishlist item, like I did.

 

today's official MSFS twitch session mention:

Sebastian Wloch re. Dynamic LOD:

"it's not very complex, it's exactly how it works on the Xbox. it's already working very well, we never thought about doing it on the pc. it's not very complex, only adding the option, adding a button, I think it's a very good idea, we never had it on our plans. I agree with the community it works very well. so I think we will put it on our backlog."

8 minutes ago, Flyfaster_MTN002 said:

today's official MSFS twitch session mention:

Sebastian Wloch re. Dynamic LOD:

"it's not very complex, it's exactly how it works on the Xbox. it's already working very well, we never thought about doing it on the pc. it's not very complex, only adding the option, adding a button, I think it's a very good idea, we never had it on our plans. I agree with the community it works very well. so I think we will put it on our backlog."

Oh dear. I really hope it isn't just 1 option for dynamic/auto LOD or whatever they want to call it. It needs to be more than that. Look how many user options there are here on Reset's version. Everyone has a different idea of the performance v graphics ratio and how far they want to see at what altitude etc.

15 hours ago, Ray Proudfoot said:

16 hours ago, craigeaglefire said:

Let’s be clear here,

this is a memory ‘hack’,

Are you aware this is how FSUIPC was created many years ago? It takes a very clever person to disassemble a executable and analyse the contents. The original UIPC was created by Adam Zofran and then Pete Dowson developed his version from the work Adam had done.

He asked Microsoft for help but none was forthcoming. He battled on because with every new version variables were broken so work had to start again. Eventually after many years the Aces team decided to cooperate and Pete's life became a lot easier.

Without that effort flight sim 25+ years ago wouldn't have become what it is today. The development work passed to Pete's son John. These are very clever people whom we should all be very grateful to whatever sim you fly.

This is a greatly appreciated post, Ray!

Wonderful history & personally I’m very much hoping for the same outcome for @Reset XPDR’s project & efforts so far,

It is an effective game changer for MSFS performance & utility,

Far too important to be officially ‘ignored’ by Microsobo…

It is a great pleasure to financially support all the clever developers who greatly enhance this hobby of ours… 🙂

@Cpt_Piett

 

Sorry i should have asked, and do you set TLOD to 600 and OLOD to 1000 in the Usercfg for your settings to work?

I just had a few giggles for myself sitting alone in the Fenix flightdeck (my FO abandoned me a long time ago) whilst reading about Seb's comments in another thread. For the sake of not violating any FAA regulations, I'll keep most of my thoughts to myself. I will say this though: Why oh why haven't they already thought of implementing a dynamic LOD feature before, when "it's not very complex, only adding the option, adding a button"

...

🤔

...

🤐🤷‍♂️

Edited March 14, 20242 yr by Cpt_Piett

18 minutes ago, abennett said:

Sorry i should have asked, and do you set TLOD to 600 and OLOD to 1000 in the Usercfg for your settings to work?

No worries. I set TLOD in usercfg.opt like this: Terrain LoDFactor 6.000000. Then OLOD as usual in menu (200). This way, in expert mode, AutoLOD will adjust TLODs accordingly to maintain FPS. 

When using non-expert mode, I set TLOD 200 in menu. AutoLOD will then use 200/2 as TLOD Min and 200*300 as TLOD Max. 

Not sure if you know, but usercfg.opt can be found here: %localAppData%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache

EDIT: sorry, just saw that you referred to usercfg.opt in your post, lol 😅

@Reset XPDR please feel to correct me if I'm wrong about this as I don't want to spread misinformation. 

 

Edited March 14, 20242 yr by Cpt_Piett

13 minutes ago, Cpt_Piett said:

No worries. I set TLOD in usercfg.opt like this: Terrain LoDFactor 6.000000. Then OLOD as usual in menu (200). This way, in expert mode, AutoLOD will adjust TLODs accordingly to maintain FPS. 

When using non-expert mode, I set TLOD 200 in menu. AutoLOD will then use 200/2 as TLOD Min and 200*300 as TLOD Max. 

Not sure if you know, but usercfg.opt can be found here: %localAppData%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache

EDIT: sorry, just saw that you referred to usercfg.opt in your post, lol 😅

@Reset XPDR please feel to correct me if I'm wrong about this as I don't want to spread misinformation. 

 

Thanks, Interesting in expert mode, I found that setting TLOD Max to 600 allowed me to reach that figure without any usercfg modifications, so using expert mode, what is the purpose of setting 6.000000 in the usercfg? Also, if you are setting TLOD in the usercfg, why do you not set OLOD to 1000 in there when using expert mode, i.e. why do one and not the other?

 

31 minutes ago, Cpt_Piett said:

No worries. I set TLOD in usercfg.opt like this: Terrain LoDFactor 6.000000. Then OLOD as usual in menu (200). This way, in expert mode, AutoLOD will adjust TLODs accordingly to maintain FPS.

If you are using expert mode, there is no need to set anything in MSFS settings or usercfg.opt other than your default cloud setting. In expert mode, TLOD Min and TLOD Max completely override any default settings you may have previously set in MSFS settings or usercfg.opt and the defaults get restored when you exit your flight. Only non-expert mode cares about your default MSFS TLOD and OLOD settings.

Edited March 14, 20242 yr by Reset XPDR

Just wondering why here, I am getting 100 TLOD when I am not reaching the target FPS, so the extra TLOD given by the TLOD + should not be added surely? I should just be getting TLOD Min?

3 hours ago, Reset XPDR said:

FG Active is because even though you think you cleaned out that FG mod totally, you did not. From the 0.4.1 readme:

If I cleaned up all the other steps in the FG hack and FG is not appearing at all in MSFS General Options, why is the app still indicating it?  And here is a twist.  If I change the setting to RTSS  0 in that file, my framerates reported in both the app and in MSFS appear locked at 30.  I have vsync off in both MSFS and the NV control panel. I do not then have FPS locked anywhere I am aware of.  If I change it back to 2 the app reports FG, and my OFPS in the app settles to about 60.  MSFS still reports 30 FPS.  So I went back to the readme files to look up OFPS so I understand what it is.  Can find no mention of OFPS, or for that matter 0FPS.  What is OFPS or 0FPS? 

What is then 60 0FPS/OFPS?

Edited March 14, 20242 yr by fppilot

1 hour ago, Reset XPDR said:

If you are using expert mode, there is no need to set anything in MSFS settings or usercfg.opt other than your default cloud setting. In expert mode, TLOD Min and TLOD Max completely override any default settings you may have previously set in MSFS settings or usercfg.opt and the defaults get restored when you exit your flight. Only non-expert mode cares about your default MSFS TLOD and OLOD settings.

Thanks Reset, that really cleared things up for me! Still got a fair bit to learn I'm afraid. 

1 hour ago, abennett said:

Thanks, Interesting in expert mode, I found that setting TLOD Max to 600 allowed me to reach that figure without any usercfg modifications, so using expert mode, what is the purpose of setting 6.000000 in the usercfg? Also, if you are setting TLOD in the usercfg, why do you not set OLOD to 1000 in there when using expert mode, i.e. why do one and not the other?

Sorry for giving inaccurate instructions. Lesson learned!

Edited March 14, 20242 yr by Cpt_Piett

1 hour ago, abennett said:

Just wondering why here, I am getting 100 TLOD when I am not reaching the target FPS, so the extra TLOD given by the TLOD + should not be added surely? I should just be getting TLOD Min?

It means that at some point you were getting enough FPS on the ground to engage TLOD Min + and once it is set it does not clear until you are off the ground. This is intentional to stop TLOD Min changing more than once on the ground, otherwise the app would be inviting ground texture tearing/corruption issues by doing this more often.

Edit: False triggering of TLOD Min + can occur when using FG because FG FPS tends to spike high when MSFS gets focus after having lost it. I'll see if I can come up with a fix in the next test build.

Edited March 14, 20242 yr by Reset XPDR

49 minutes ago, fppilot said:

If I cleaned up all the other steps in the FG hack and FG is not appearing at all in MSFS General Options, why is the app still indicating it?  And here is a twist.  If I change the setting to RTSS  0 in that file, my framerates reported in both the app and in MSFS appear locked at 30.  I have vsync off in both MSFS and the NV control panel. I do not then have FPS locked anywhere I am aware of.  If I change it back to 2 the app reports FG, and my OFPS in the app settles to about 60.  MSFS still reports 30 FPS.  So I went back to the readme files to look up OFPS so I understand what it is.  Can find no mention of OFPS, or for that matter 0FPS.  What is OFPS or 0FPS? 

What is then 60 0FPS/OFPS?

Re FG not appearing at all anymore in the MSFS menu but MSFS still internally indicating that it is on is just the way MSFS works. You need to do exactly what I stated to fix it.

BTW, tt is not RTSS, it is DLSSG you are supposed to change to 0 in usercfg.opt per the readme. It is either 0 or 1 so if you saw a 2 whatever you changed wasn't it. Are you sure you are even in the right file as mine has no RTSS line and I actually use RTSS externally?

Re 0FPS or OFPS, it is actually ØFPS in the app, which is the way it was when I forked off the original DynamicLOD. Googling Ø shows it to mean an empty set in maths, which is not really relevant to displaying FPS so I will remove that symbol in the next test version and you will just see FPS. Thanks for asking this question otherwise I would never have known what the symbol actually means.

Edit: Some more googling and the actual symbol for average is x̄, so I might use that and confuse even more users. Nah, maybe not 😄

Semantics aside, the FPS reading is explained in the readme, under the Sim Values section, and says:

• FPS shows the FPS for the current graphics mode averaged over 5 seconds which will smooth out any transient FPS spikes experienced when panning or loading new scenery or objects so that automated MSFS setting changes are minimised.

Edited March 14, 20242 yr by Reset XPDR

New AutoFPS Test Version 14Mar240550Z available here. Please give the new VFR and IFR features a go and let me know what you think.

This release primarily provides the new VFR/IFR flight profile nomenclature, being the old FPS priority and TLOD Min on ground/landing respectively. Also VFR mode is now allowed to be used in non-expert mode. Tool tips added to describe these new options in TLOD and FPS priority language. These modes are summarised as follows:

• VFR mode - your TLOD will be locked any time you are below 100 ft or are on the ground, except if TLOD Min + gets activated if enabled and performance conditions are good enough to boost your starting TLOD. Once in the air above 100 ft, your TLOD will dynamically change to achieve your target FPS, with the first 1000 ft having a increasing sliding scale of TLOD changeability as you ascend to minimise TLOD changes the closer you are to the ground. Once below 100 ft, your TLOD will lock to whatever it last was and will stay that way until you take off and climb above 100 ft.
• IFR mode - is exactly like the old TLOD Min on ground/landing option whereby your TLOD will be locked to either a pre-determined (non-expert) or user-selectable (expert) TLOD Min. Again, TLOD Min + may increase this should performance conditions be good enough to boost your starting TLOD. Once in the air and above either a pre-determined (non-expert) or user-selectable (expert) TLOD base altitude, TLOD will be allowed to change to the lower of either the schedule based on your TLODs, FPS sensitivity and average descent rate settings or what your current performance dictates. On descent your TLOD will progressively work its way down to TLOD Min by the TLOD base altitude. As with VFR mode, TLOD will not change on the ground unless TLOD Min + is activated and performance conditions are met.

Changes since the last test release are:

• Implemented new VFR/IFR flight profile nomenclature as radio button option.
• Fixed TLOD min + enabled setting not showing on startup, despite the app being shut down with it checked.
• Fixed FPS priority mode not resetting to default TLOD or cloud quality reset when switching graphics modes.
• Revised Auto Target FPS base reduction to be 96%, up from 95%, to help prevent TLOD Min + triggering too easily after auto target FPS has been set.
• Removed ∅ from FPS sim value display area as it means empty set not average and was causing confusion.
• Removed Open app Window on startup option as users report it is seldom used and it was taking up valuable UI space in the non-expert section. Users will still be able to change the window opening behaviour in the config file.
• Relocated Pause when MSFS loses focus under expert settings to where TLOD Min on ground/landing used to be.
• Added settling timer to TLOD Min + for MSFS focus transitions when using FG.

 

Edited March 14, 20242 yr by Reset XPDR

My apologies if anyone downloaded AutoFPS test version 14Mar240430Z in the last hour as I forgot to reset the FPS settle timer to 10 seconds after testing (I set it to 2 seconds so I don't have to wait so much while testing and triggering it numerous times). If so, please update to 14Mar240550Z available here. It is the same link as the one above.

Edited March 14, 20242 yr by Reset XPDR