13 hours ago, SkylanePilot said:

Following up on the conflict between TweakUI and MSFS2020_AutoFPS, I decided to test whether the new nVidia app's statistics overlay causes the same failure. I am pleased to report that it does not. If the nVidia app is loaded after MSFS2020_AutoFPS, it will show NA for FPS. If nVidia is loaded first and MSFS2020_AutoFPS second, both apps will report FPS. But, so far, neither app has caused the other to crash. 

As for Roman Designs question, I use MSFS2020_AutoFPS in VR. I am still experimenting with settings. I have motion reprojection in the sim set to DEPTH. Using Varjo Aero and RTX4090 on an i9-13900K system. I set  the desired fps to 90 in MSFS2020_AutoFPS and the Varjo base software to 45 fps. It seemed to struggle a bit. So, tonight I set the desired fps to 90 in MSFS2020_AutoFPS and the Varjo base to 30 fps. That gives me a solid 30-31 fps in VR with motion reprojection. However, the TLOD and OLOD drop to minimum and the clouds drop from ultra to high.  I will continue to play with it but so far, in MSFS2020_AutoFPS has not broken motion reprojection on this system.

 

I don't have Varjo, but AFAIK what you're doing is setting a target FPS to 90, but then hard-limiting it to 30. That way AutoFPS can't ever reach the target and should just bump everything to minimums and keep it there. Also, MSFS reprojection is not the same as VR HMD reprojection and to my knowledge doesn't do anything with the framerate on any HMD. So that setup doesn't sound logical. If you hard-limiting FPS to 30 in the Verjo, then the target sould be set to slighly below 30, as far as I understand the concept. Things may be different with Varjo, but should not be that different.

Initial, and hopefully final, 0.4.2 Test Version 06Mar240110Z test version is available here. Changes are:

• Added + option for cloud recovery TLOD, similar to + FPS for cloud recovery FPS with DynamicLOD_ResetEdition.
• Fixed issue where cloud quality decrease was not resetting on graphics mode change the first time when it otherwise should have.
• Fixed issue where cloud quality decrease was not resetting when cloud recovery TLOD had been achieved and FPS was at least the FPS target value.
• Changed AutoOlod to default to on for non-expert mode following no major negative feedback on default AutoOlod settings causing issues when AutoOlod is enabled. Non-expert AutoOlod settings are: OLOD @ Base your default MSFS OLOD, Alt OLOD Base 2000 ft, OLOD @ top the greater of 20% of your default MSFS OLOD or 10, and Alt OLOD Top 10000 ft.
• Added interface to GPU-Z to run as a companion app and provide accurate GPU load information to the app. This information will potentially be used in future to determine whether to activate/deactivate GPU or CPU related reduction settings as performance goes below or above target FPS respectively. Will require GPU-Z to be running in the background and if not detected these new features will just not be enabled.
• Changed app icon, in memory of my bestest buddy Leo.
• Added tootips for key settings.
• Added minimise button to app window.
• Changed window background colour from glaring white to light grey.
• Added SmoothFlight to list of apps to check if already running, as these apps would conflict.

As always, feedback on these changes is welcome.

Edited March 6, 20242 yr by Reset XPDR

58 minutes ago, Reset XPDR said:

As always, feedback on these changes is welcome.

Excellent work Reset! Lots of exciting new features here. I was actually able to update whilst running MSFS, started the app and it connected. 

I'll just put a screenshot here to show my settings, as well as tooltips in action. GPU-Z integration (not sure what I should call it) is interesting, although GPU load seems a bit odd (no, my 4090 is not on fire!).

I'll check the log after landing in Bergen, Norway and report back!

Oh - Leo looks great as an icon 😄

10 minutes ago, Cpt_Piett said:

Excellent work Reset! Lots of exciting new features here. I was actually able to update whilst running MSFS, started the app and it connected. 

I'll just put a screenshot here to show my settings, as well as tooltips in action. GPU-Z integration (not sure what I should call it) is interesting, although GPU load seems a bit odd (no, my 4090 is not on fire!).

I'll check the log after landing in Bergen, Norway and report back!

Oh - Leo looks great as an icon 😄

 

Interesting your GPU load looks like it is showing memory used, ie the item before it in the list. I think I know what it is. I was using the GPU-Z a fixed sensor value offset in the GPU-Zshare memory DLL that worked with mine but the sensor list must be dynamic, not static so I'll have to search for the right sensor name in the list first and then use its offset to get the load. This DLL is 14 years old and the documentation is sparse to say the least so I am fumbling a bit in the dark on this one. 🤪😄

Good pickup and thanks for getting back to me on it so quickly! I should be able to fix it similarly quickly and it is certainly not an app breaker in the interim.

Edited March 6, 20242 yr by Reset XPDR

22 minutes ago, Cpt_Piett said:

GPU-Z integration (not sure what I should call it) is interesting, although GPU load seems a bit odd (no, my 4090 is not on fire!)

I just upgrade my GPU-Z to the same, latest version as yours and I am getting the same thing with memory used being the value showing. I could fix it to be right for this version but then it will be broken for users with older version like mine, so I'd better fix it properly if I can.

New Test Version 06Mar240340Z here:

- Fixed GPU-Z not reading the correct sensor value for GPU Load (thanks for finding this @Cpt_Piett!). Rather than use a fixed index, which seems to change between GPU-Z versions, GPU Load is searched for in the sensor name list and its associated offset is used.
- Added logging of GPU-Z running detection and correct GPU Load index being found or not.

49 minutes ago, Reset XPDR said:

Fixed GPU-Z not reading the correct sensor value for GPU Load

That was quick, it's working!

2 minutes ago, Cpt_Piett said:

That was quick, it's working!

It has a very simple interface, albeit somewhat undocumented. I went for this after trying to put my own code in to detect GPU load, which worked sort of but gave nowhere near as accurate a GPU load number as GPU-Z and it was taking up 5% CPU time which is excessive for a little app like this. The GPU-Z shared memory access works perfectly, should work for pretty much any GPU out there and I can't even measure any performance impact when using it, so it's a definite yes from me to use.

This is another must have utility for MSFS! Thanks so much for making this! And so sorry to hear your loss! Leo looks great as an icon! My prayers and sympathy goes out to you and your best friend Leo.

8 hours ago, Reset XPDR said:

New Test Version 06Mar240340Z here:

- Fixed GPU-Z not reading the correct sensor value for GPU Load (thanks for finding this @Cpt_Piett!). Rather than use a fixed index, which seems to change between GPU-Z versions, GPU Load is searched for in the sensor name list and its associated offset is used.
- Added logging of GPU-Z running detection and correct GPU Load index being found or not.

What is the best way to upgrade to the latest version?

6 minutes ago, Bobsk8 said:

What is the best way to upgrade to the latest version?

Just run the new installer and install over the top. I usually choose do not configure autostart so that it doesn't try to change any autostart I already have in place. You can downgrade to an older version the same way.

1 hour ago, Reset XPDR said:

Just run the new installer and install over the top. I usually choose do not configure autostart so that it doesn't try to change any autostart I already have in place. You can downgrade to an older version the same way.

I just tried running update, and it stalls on "deleting old version" and then nothing happens. 

 

Up[date would not work, but then the program would not start either. Then I tried to delete the folder, and it wouldn't let me do that either. I had to restart PC,, then I could delete the original folder, and then installed latest version. 

Edited March 6, 20242 yr by Bobsk8

5 hours ago, Bobsk8 said:

I just tried running update, and it stalls on "deleting old version" and then nothing happens. 

 

Up[date would not work, but then the program would not start either. Then I tried to delete the folder, and it wouldn't let me do that either. I had to restart PC,, then I could delete the original folder, and then installed latest version. 

I haven't experienced that, and I update that way daily, sometimes hourly, with new test builds that I create. At least you got it working.

18 hours ago, Reset XPDR said:

Initial, and hopefully final, 0.4.2 Test Version 06Mar240110Z test version is available here. Changes are:

• Added + option for cloud recovery TLOD, similar to + FPS for cloud recovery FPS with DynamicLOD_ResetEdition.
• Fixed issue where cloud quality decrease was not resetting on graphics mode change the first time when it otherwise should have.
• Fixed issue where cloud quality decrease was not resetting when cloud recovery TLOD had been achieved and FPS was at least the FPS target value.
• Changed AutoOlod to default to on for non-expert mode following no major negative feedback on default AutoOlod settings causing issues when AutoOlod is enabled. Non-expert AutoOlod settings are: OLOD @ Base your default MSFS OLOD, Alt OLOD Base 2000 ft, OLOD @ top the greater of 20% of your default MSFS OLOD or 10, and Alt OLOD Top 10000 ft.
• Added interface to GPU-Z to run as a companion app and provide accurate GPU load information to the app. This information will potentially be used in future to determine whether to activate/deactivate GPU or CPU related reduction settings as performance goes below or above target FPS respectively. Will require GPU-Z to be running in the background and if not detected these new features will just not be enabled.
• Changed app icon, in memory of my bestest buddy Leo.
• Added tootips for key settings.
• Added minimise button to app window.
• Changed window background colour from glaring white to light grey.
• Added SmoothFlight to list of apps to check if already running, as these apps would conflict.

As always, feedback on these changes is welcome.

Thank you. I will update, although I don't think I will be using the new features. I rarely use GPU-Z and would rather not have another app running in the background.

Speaking of background apps, I have never been able to have the installation process add the auto launch entry into my exe.xml. I had to type it in manually, despite uninstalling fully before reinstalling.

8 minutes ago, mmcmah said:

Thank you. I will update, although I don't think I will be using the new features. I rarely use GPU-Z and would rather not have another app running in the background.

Speaking of background apps, I have never been able to have the installation process add the auto launch entry into my exe.xml. I had to type it in manually, despite uninstalling fully before reinstalling.

The GPU-Z integration functionality is entirely optional. Having said that, if I had implemented what I can get from GPU-Z internally in my app, it would have used far more system resources than the way I have it working now, so having one more icon in your system tray overflow is a minor price to pay IMO.

A few users have had issues with EXE.xml changes. The installer simply finds your EXE.exe, looks for an existing autostart for this app and if it doesn't find one it adds it. The usual issue is that EXE.xml doesn't exist as it is only created when a third party app needs it for autostarting. My app doesn't create one yet, but I may add that in future.

Edited March 6, 20242 yr by Reset XPDR