8 minutes ago, Divij said:

Fantastic. Look forward to trying this out!

It seems to be working. If FPS drops below FPS Adaption trigger value, it will not activate FPS Adaption until it sees another value below this trigger value again. ie. you will see red FPS and black LOD values on the first go (screenie 1), then red FPS and red LOD values on the second go (screenie 2) with the first step down towards the reduction LOD level. Is that what you are after?

Edited January 29, 20242 yr by Reset XPDR

Yes in theory this should cut scenarios where adaption kicks in for those 1 second fps drops. Looks good to me! Would like to give it a go and see if it works as we think it should .. 

1 hour ago, Divij said:

Yes in theory this should cut scenarios where adaption kicks in for those 1 second fps drops. Looks good to me! Would like to give it a go and see if it works as we think it should .. 

Link to 0.3.6 test version here. It is a stable test version but does have some more polish required.

Note the following changes since 0.3.5 when deciding whether or not to install:

• Added a separate TLOD/OLOD minimum for FPS adaption because, if you are like me you are setting lower OLOD as you get higher in altitude and the way it was coded the FPS Adaption was actually increasing, not decreasing, my OLOD at times. Now they are individually settable.
• Removed Reduce on pairs/indices setting for FPS adaption because it seems to work opposite to what some of us think it should do. ie. it sets a minimum pair/index when it would be more useful being a maximum pair/index. Even then I still wouldn't use it as FPS Adaption is more likely to trigger on the ground in a busy scenario anyway, so it seems superfluous and takes up UI space. If you are using this feature with a setting of anything other than 0, do NOT install this update as you will lose it.
• Added a Decrease cloud quality by 1 level lower option for FPS Adaption with a user definable recovery FPS buffer.
  • eg. if your FPS Adaption triggers at 30 FPS and you have decrease cloud quality checked and a cloud recovery FPS of +10 as shown below, your system will need to achieve 40+ FPS for the full reduce for period (5 seconds in the example below). This is to stop FPS adaption constantly triggering if your system gains good FPS by reducing cloud quality by 1, then promptly loses it again when it switches back. Mine can gain/lose up to 8 FPS changing cloud quality, so I set it to 10 and it keeps the FPS adaption going until I am getting better than that. 
  • Those numbers next to TLOD and OLOD sim values are the current PC and VR cloud settings respectively, where 0 is low through 3 which is ultra, and will only be shown in the test version. You will see them decrease by 1 (if not already at 0) when Decrease Cloud Quality is enabled and FPS Adapation is activated.
  • I'm still working on automating restoration of original cloud (and TLOD/OLOD) values when exiting the app. Just make sure FPS Adaption isn't currently triggered and active when you exit the app otherwise your cloud settings will remain 1 level lower than what you had originally set. Uncheck FPS Adaption if you have to. This will be fixed in an upcoming version but in the meantime it is pretty easy to avoid. Worse comes to worse if your clouds are not restored correctly, just go into your MSFS settings and put the cloud quality back where you want it.
  • If you don't like it or can't get it working to your satisfaction, uncheck Decrease Cloud Quality.
• Added a Delay start to FPS Adaptation to stop it false triggering with a transient FPS drop from an external app or from panning around too quickly. The default is 1 second, meaning that an FPS drop must still be there after 1 second before FPS Adaption will trigger. Higher values mean a longer period the FPS drop must be present. If you want instant like the original 0.3.2 version, which I don't recommend because it is too easy to false trigger FPS Adaption, set it to a value of 0. 1 or 2 seems to be pretty good.
• Refined LOD change logging to only record the initial full LOD change being enacted, whereas previously if using LOD Step Max each progressive LOD step was being recorded. This should significantly reduce logging activity to more essential entries.

 

Edited January 29, 20242 yr by Reset XPDR

I'm so impressed with the quality of your work  Reset XPDR, your updates to this App is bringing me a whole new love for this sim.

I'm most impressed by the logic you are adding.

Thanks for making my old PC feel new again 🙂

 

Edited January 29, 20242 yr by Stona

Hello,

I wanted to know how we leave the OLOD at 200 instead of it being 100 at AGL 0?

I would like it to stay permanently at 200 because on my config the OLOD does not impact the FPS.

40 minutes ago, Axis3600 said:

Hello,

I wanted to know how we leave the OLOD at 200 instead of it being 100 at AGL 0?

I would like it to stay permanently at 200 because on my config the OLOD does not impact the FPS.

Just delete all other steps in the OLOD table and set it to 200 for AGL 0.

That's what I did but I can't delete the last one (AGL 0 100 OLOD) and when I put AGL 0 OLD 200 it doesn't work

1 minute ago, Axis3600 said:

That's what I did but I can't delete the last one (AGL 0 100 OLOD) and when I put AGL 0 OLD 200 it doesn't work

Remember after you change it from 100 to 200 you need to Save it(click the S) ...

Just FYI the download shows:

Google Drive can't scan this file for viruses.

This file is executable and may harm your computer.

DynamicLOD-Installer-v0.3.6-test.exe (1.7M)

Assume this is due to it not being signed...

 

Edited January 29, 20242 yr by Flyfaster_MTN002

30 minutes ago, Flyfaster_MTN002 said:

Just FYI the download shows:

Google Drive can't scan this file for viruses.

This file is executable and may harm your computer.

DynamicLOD-Installer-v0.3.6-test.exe (1.7M)

Assume this is due to it not being signed...

 

You can still download it and manually run a virus/malware scan using whatever is on your system if you want before installing it. I've used this distribution method for a couple of weeks and no one has reported to me of any nasties contained within, but feel free to check yourself.

Edited January 29, 20242 yr by Reset XPDR

its all good my end 👌

On 1/28/2024 at 9:08 PM, Reset XPDR said:

eg. if your FPS Adaption triggers at 30 FPS and you have decrease cloud quality checked and a cloud recovery FPS of +10 as shown below, your system will need to achieve 40+ FPS for the full reduce for period (5 seconds in the example below). This is to stop FPS adaption constantly triggering if your system gains good FPS by reducing cloud quality by 1, then promptly loses it again when it switches back. Mine can gain/lose up to 8 FPS changing cloud quality, so I set it to 10 and it keeps the FPS adaption going until I am getting better than that. 

Quick question,

For those that are using FG and the FPS Adaption feature do you set the limit of the FG FPS or the actual FPS in MSFS? I use FG with my Sony X90K @ 100Hz so my target FPS is set to 97 but in MSFS the FPS is showing 48

5 hours ago, RJC68 said:

Quick question,

For those that are using FG and the FPS Adaption feature do you set the limit of the FG FPS or the actual FPS in MSFS? I use FG with my Sony X90K @ 100Hz so my target FPS is set to 97 but in MSFS the FPS is showing 48

I don't use FG, as it messes with VR, however I can say that FPS Adaption works off whatever FPS is showing in the DynamicLOD app Sim Values area, so go off that one. 

Link to latest 0.3.6 test version is here .

Changes since the initial 0.3.6 test release described here are:

• Auto saving and restoring of TLOD, OLOD and Cloud Quality settings, individually for both PC and VR modes, has now been fully implemented. You can still change your default settings of these, but only when in the main menu. Once you are in a flight the app will likely override them, as is its intended purpose, even if you do change them in the settings menu while in flight. Once you exit the flight, quit the app or quit MSFS, your original settings will be restored. This has allowed for the removal of the "Reset TLOD/OLOD after Session to" label and associated text boxes because it is no longer needed. 
• Continued simplifying and minimising app log entries. Waiting for Connection and Waiting for Session events are now only a single log entry, as there could be many of these if you did not start your flight immediately. Added log entries for the auto save and restore of the aforementioned applicable sim settings. Edit: You can see the revised log layout in my post below this one.

Intended functionality is now mostly complete, pending any major issues found by other users that I need to fix, so I should be able to release 0.3.6 in the next day or so.

 

Edited January 31, 20242 yr by Reset XPDR

Just another point, separate to my new 0.3.6 test release post as it is not directly related, that I'd like to seek others input.

One thing I have encountered quite often in my app log file, which I have confirmed also occurs in the original 0.3.2 I started working on, is a bunch of error messages when exiting MSFS from the main menu and the app subsequently auto closes. I am investigating but I am not very familiar with MobiSimConnect functionality, which is otherwise working fine so I have not had to change anything with it. It is only a minor issue, as it does not affect MSFS or the app actually exiting, but it triggers my OCD seeing an error that shouldn't be there.

They look like this, highlighted in blue:

Is anyone else experiencing these?