A new test version 15 fixing issues identified by @Lange_666and @thetford569is available here: https://github.com/ResetXPDR/MSFS_AutoFPS/releases/tag/v0.4.4.2-test

• Revised camera states that make the session active following changes made by Asobo in MSFS 2024 1.2.8.0 which will now allow the session to commence when the flight starts up in walk around mode as it used to.
  • A side effect of this change is that the session may briefly activate when loading in a flight, due to new MSFS 2024 camera state inconsistencies, however this does not impact correct session commencement when your flight starts.
• Fixed installer giving error message when configuring MSFS autostart and FSUIPC is not installed.

25 minutes ago, Reset XPDR said:

A new test version 15 fixing issues

It seems to be working 🙂

1 hour ago, Cpt_Piett said:

It seems to be working 🙂

I am glad it is working again for you and hopefully everyone else.

FYI, Asobo decided to change walk around view from camera state 26 to camera state 30 when you first load in your flight just because and, what the heck, let's make it 31 if you reload a flight. Oh and while you are loading in a flight where you are destined for the cockpit, let's throw in a camera state 30 while loading in because everyone likes to walk around before the flight has finished loading then we'll take it away when you are presented with the Fly now button. 😕

Sometimes I wonder if these guys have a randomise button to generate some of the code that goes in to these MSFS updates! 😂

Edited December 29, 20241 yr by Reset XPDR

14 minutes ago, Reset XPDR said:

Sometimes I wonder if these guys have a randomise button to generate some of the code that goes in to these MSFS updates! 😂

Haha - they probably do!!

13 minutes ago, Reset XPDR said:

I am glad it is working again for everyone.

FYI, Asobo decided to change walk around view from camera state 26 to camera state 30 when you first load in your flight just because and, what the heck, let's make it 31 if you reload a flight. Oh and while you are loading in a flight where you are destined for the cockpit, let's throw in a camera state 30 while loading in because everyone likes to walk around before the flight has finished loading then we'll take it away when you are presented with the Fly now button. 😕

Sometimes I wonder if these guys have a randomise button to generate some of the code that goes in to these MSFS updates! 😂

Thanks @Reset XPDR!  Some of their decisions are truly mind boggling!  I almost wonder between things like this and the cryptic message removed from the C208 medevac version in the previous patch if they don’t have some saboteurs working in their midst or at least some people that think it’s funny.

Hallo. Das ist kein Problem, aber ich finde keinen Button, wo ich dir eine Nachricht senden kann. Echt tolles Programm. Kleine Frage. Kannst du vielleicht eine Transparenz mit einem Art Schieberegler erstellen? Viele Grüße, Oliver

54 minutes ago, fliegeroli said:

Hi. That's not a problem, but I don't find a button where I can send you a message. Really great program. Small question. Can you perhaps create a transparency with a kind of slider? Many greetings, Oliver

Per my reply on my github issues page, there will be no transparency feature added as there is already a collapsible UI feature that offers similar decluttering of the app window as described in the readme here:

• The user can progressively hide parts of the UI when the app window is double clicked anywhere that is not a control. The first double click will hide the expert settings section (if applicable), the second will hide the general settings section and a third double click will restore all hidden settings sections. The last state in use will be restored when next starting the app.

Also gonna test. Near KJFK, KLAS and.....anyone want to pick another location?

EGLC!!! Full AI traffic running in the sim (default, no AIG stuff).

 

Default EGLC to EGNM in the AvroRJ was flawless. Very little stutter. Pretty much everything at Ultra settings.

Expert Settings with 50fps as my target (my monitor is only 60hz gsync, capped to 57fps in NVCP) and Vsync enable (I think lol).

FPS Senstivity is 2, TLOD min is 45 with the check box for additional. And max is 250 plus mountains. Approach to EGNM was pretty chill. Little stutters.

AutoLOD 200max, 20 lowest

Scenery/building popping in the background so i bumped it to 300 tlod but they were still popping into existence.

only complaint was that I could not...for the life of me...start the engines. Odd.

 

How to stop the stuff popping in ???

Edited December 30, 20241 yr by Sonosusto

I've got one more robustness improvement idea to potentially put in to the 0.4.4.2 update before I formally release it and that is to limit TLOD increases when GPU memory is near full (eg. 95%+) and possibly to reduce them if GPU memory use gets past a certain threshold (eg. 98%+). The reason I want to do this is because MSFS 2024 is DX12 only and it has been known to overflow VRAM at times, causing a significant performance drop, and this might be a way of avoiding it if users get too keen with their app settings or, even if their settings are reasonable but MSFS 2024 just decides to break the memory levy anyway.

I've managed to be able to detect which GPU is in use by MSFS via the UserCfg.opt file, to ask Windows to tell me how much VRAM that particular adapter is packing and, finally, to get GPU-Z (required to get this working) to tell me what is the current VRAM use. From there I can calculate current VRAM load and use it to manage TLOD Max if things get close to overflowing.

There would be no UI changes as the UI is cluttered enough as it is, so the thresholds would be hard coded, or maybe a config file setting at most, and all the user would have to do to have VRAM overflow protection is to be running the GPU-Z companion app at windows startup or at the very least when this app is running, which is easy enough to do. If GPU-Z isn't running, VRAM overflow protection is inactive ie. the app works as it currently does.

It's experimental at this time, and may not make the 0.4.4.2 release cut if it doesn't come to fruition within a few days, so I thought I'd throw it out there and see what others think of the idea before I go too much further on it.

Example log file lines from what I have already coded:

2024-12-30 16:10:33.593 [INF] [ MemoryManager:GetUserOptCfgSetti ] configGPUModel NVIDIA GeForce RTX 4090
2024-12-30 16:10:33.596 [INF] [ MemoryManager:GetUserOptCfgSetti ] Successfully read required settings from UserOpt.cfg

2024-12-30 16:10:49.160 [INF] [ LODController:gpuzRunning        ] GPU-Z companion app running
2024-12-30 16:10:49.161 [INF] [ LODController:gpuzRunning        ] GPU-Z GPU Load sensor found
2024-12-30 16:10:49.161 [INF] [ LODController:gpuzRunning        ] GPU-Z GPU Memory Used sensor found
2024-12-30 16:10:49.161 [INF] [ LODController:gpuzRunning        ] GPU-Z Initial Memory Used: 17766 MB
2024-12-30 16:10:49.184 [INF] [ LODController:gpuzRunning        ] System Reported Total GPU Memory: 24142 MB
2024-12-30 16:10:49.184 [INF] [ LODController:gpuzRunning        ] GPU Initial Memory Usage: 73%

Example VRAM usage display, only in test version for now:

Let me know what you think.

Edited December 30, 20241 yr by Reset XPDR

I'm in. At first I though that launching GPU-Z was one-more-stuff-to-launch but the benefit could be higher. If GPU-Z is not launch, there's no drawback and the user doesn't benefit from the feature, right?

Edited December 30, 20241 yr by vbazillio

30 minutes ago, vbazillio said:

I'm in. At first I though that launching GPU-Z was one-more-stuff-to-launch but the benefit could be higher. If GPU-Z is not launch, there's no drawback and the user doesn't benefit from the feature, right?

That's right. Same as if you want to use GPU Load for cloud reduction you have to have GPU-Z running but if you don't it just doesn't get presented as an option. I'm basically offering optional VRAM overflow protection, which IMO is useful if running MSFS 2024 and using reasonably high settings that sometimes overflow their available VRAM, which will just be inactive if you aren't running GPU-Z.

The prototype is working pretty well, in fact too well which makes me think I've missed something 😄

Edited December 30, 20241 yr by Reset XPDR

I am all in for this, let's give a test.

8 hours ago, Sonosusto said:

Scenery/building popping in the background so i bumped it to 300 tlod but they were still popping into existence.

I also see this and have no clue if there's anything that can be done about it...

3 hours ago, Reset XPDR said:

I've got one more robustness improvement idea to potentially put in to the 0.4.4.2 update before I formally release it and that is to limit TLOD increases when GPU memory is near full (eg. 95%+) and possibly to reduce them if GPU memory use gets past a certain threshold (eg. 98%+).

Great idea. If a test version it out I'll be able to test it this evening CET. 

5 hours ago, Reset XPDR said:

I've got one more robustness improvement idea to potentially put in to the 0.4.4.2 update before I formally release it and that is to limit TLOD increases when GPU memory is near full (eg. 95%+) and possibly to reduce them if GPU memory use gets past a certain threshold (eg. 98%+). The reason I want to do this is because MSFS 2024 is DX12 only and it has been known to overflow VRAM at times, causing a significant performance drop, and this might be a way of avoiding it if users get too keen with their app settings or, even if their settings are reasonable but MSFS 2024 just decides to break the memory levy anyway.

Let me know what you think.

Okay.

Remember what the doctor said ?

Those crazy ideas ! You have to stop ! The time has come to say enough is enough ! I have to put you into a retirement home !

😁🤣

 

 

 

Edited December 30, 20241 yr by deepstar