10 hours ago, Maddormo said:

Hi:
Long user of your app. As others have mentioned before: it's a real game changer. Thank you so much for your dedication.

I have a 'little' request that I think could be useful: I ask you to consider including text boxes, as well as controls, in the excluded elements of the double click tool to hide certain parts of the interface.

When I want to enter a new value in a text box, I usually double-click the previous value and type in the new one. I've done this so often that every time I try to modify a parameter, I end up hiding the expert options, which means I have to double-click twice more to bring them back.

I hope this change won't be very difficult to implement.

Best regards

I think I've got it licked. Try this and let me know how it goes.

Great job thanks much 🤩

On 1/6/2025 at 8:04 AM, Reset XPDR said:

I'm pretty sure that's what it will be. I put in the settling period upon returning to FG active because the FPS is not stable for a while after the transition due to the new values being double what the previous FG inactive values were, so it takes a good few seconds for it to settle again.

Anyway, if that's not how it is working, I'm sure you'll let me know, with screenshots to boot! 😂

This doesn't happen very often, but I just encountered a situation where there's a mismatch between FPS detected by AutoFPS and actual FPS. As can be seen by the screenshot (wonky colors due to HDR), the mismatch is there even though AutoFPS is not in "FPS settle" mode. 

There's a few things going on here though - a VRAM LTD situation amongst other things. I was probably alt-swapping between windows just before it happened - so I don't think it's a huge issue at all. 

And yeah - as always I'm testing the limits of my hardware by using a very high TLOD 🙂

EDIT: Here's another example (AutoFPS window looks different as I did some highly advanced editing in Paint): 

Edited January 7, 20251 yr by Cpt_Piett

18 hours ago, Reset XPDR said:

I think I've got it licked. Try this and let me know how it goes.

WOW! super fast! Thank you so much!

4 hours ago, Cpt_Piett said:

This doesn't happen very often, but I just encountered a situation where there's a mismatch between FPS detected by AutoFPS and actual FPS. As can be seen by the screenshot (wonky colors due to HDR), the mismatch is there even though AutoFPS is not in "FPS settle" mode. 

There's a few things going on here though - a VRAM LTD situation amongst other things. I was probably alt-swapping between windows just before it happened - so I don't think it's a huge issue at all. 

And yeah - as always I'm testing the limits of my hardware by using a very high TLOD 🙂

EDIT: Here's another example (AutoFPS window looks different as I did some highly advanced editing in Paint): 

Interesting. The app gets its FPS readings from SimConnect via MobiSimConnect and averages them over 5 seconds, the same method used all the way back to Dynamic LOD days.  I must admit though that I've experienced it a few times myself while testing the app with FG but it never stays around long enough for me to find out why.

If you can come up with a sure fire way of triggering it, I should be able to find out what is going on. I'll take a look myself as well.

Also, I notice your VRAM+ is always cut off in the screenshots you take, most likely because you use Mtns+ and that status item is pushing it over the edge. I'll have a think about how to declutter so that you see what you need. Losing GPU load comes to mind as you are not using the GPU cloud quality activation method.

4 minutes ago, Reset XPDR said:

If you can come up with a sure fire way of triggering it, I should be able to find out what is going on. I'll take a look myself as well.

At the moment I have no idea why it happens - I'll let you know if it starts to make more sense. 

2 hours ago, Cpt_Piett said:

At the moment I have no idea why it happens - I'll let you know if it starts to make more sense. 

I just tried multiple times myself to trip it up with similar settings to yours but it is behaving itself nicely ie. upon making MSFS the active window again, FPS settle shows until the FPS has stabilised to what RTSS is reading then the automation is allowed to resume. I'll keep an eye on it though.

Edited January 7, 20251 yr by Reset XPDR

3 hours ago, Reset XPDR said:

Interesting. The app gets its FPS readings from SimConnect via MobiSimConnect and averages them over 5 seconds, the same method used all the way back to Dynamic LOD days.  I must admit though that I've experienced it a few times myself while testing the app with FG but it never stays around long enough for me to find out why.

 

I used the game’s FPS counter and compared it to the FPS in the AutoFPS app, and I got almost identical numbers. It is very accurate in my experience. 

Here the same. The MSFS gramerate shows about the same as AutoFPS and the NV framerate counter.

I'm prototyping the idea of presenting users with a "new" TLOD Automation Method called "FPS Cap" to satisfy the desire of some, particularly VR users utilising motion reprojection, to see an FPS cap friendly mode. The reason I wrote "new" is that it is not actually new, rather it is a specific configuration of Auto TLOD that works well with an FPS cap but now with an obvious name.

No, I haven't copied kayjay's idea from his MSFS2024_AutoFPS variant, rather I was bit confused when he felt the need to modify the code and create a VR optimised automation method when my existing code, when configured correctly, effectively does the same thing already.

I've also read comments on Facebook and in forums saying that my app isn't VR friendly because it doesn't support FPS caps. Well it actually does and has done since Oct last year (I use it in VR with an FPS cap for motion reprojection all the time!), so the issue is really that I didn't package it clearly enough for users to realise that it already exists. All I have done is forced that particular configuration when FPS Cap is chosen. No lines of automation have been changed.

Here's how it would look, being the forth item on the Auto Method drop down list. When selected, it will enable TLOD Base + and disable TLOD Top + and disable the user being able to change either of those settings while in this specific mode. The word Cap will be added to the Target FPS label.

 

 

Still amazed by this little tool, but what drives me nuts on a regular basis is the "feature" that the window can be expanded/shrinked by a simple mouse-click somewhere in the window. This happens all the time and is utterly annoying, cant this be made optional?

1 hour ago, AnkH said:

Still amazed by this little tool, but what drives me nuts on a regular basis is the "feature" that the window can be expanded/shrinked by a simple mouse-click somewhere in the window. This happens all the time and is utterly annoying, cant this be made optional?

It is caused by a double, not single, mouse click. The latest test version excludes all controls so unless you are double clicking on the window area where there are no controls you will be safe. Give it a try here and see if that is now acceptable.

Edited January 8, 20251 yr by Reset XPDR

That's exactly what happened before you exluded the controls - I double clicked to select the value in the input field which would then collapse the dialog. Should be fine now, but did not test (yet).

 

Smal information.

v0.4.4.3-test1 gives me allways medium clouds and set my clouds allways to medium.

Huh. When I use the MSFS (2020) FPS counter it always says its like capped at 20-24 fps which is impossible. The AutoFPS app says what it really should be around 50ish. Not sure if that includes Frame Generation. But my recent CPU and GPU upgrade should NOT mean its getting 20ish FPS. My previous build had better fps than that number.