v0.5.3.0-test Minor Maintenance Update

[ResetXPDR]

MSFS Compatibility: 1.39.12.0, 1.7.35.0, 1.8.9.0.

Release notes for 0.5.3.0-test

Test1:

• Re‑introduced the spike‑protection stack panel when spike protection and Log+ are enabled, showing the multiplier checkbox, RTSS frame‑time record button, and spike status line.
• Changed DynFG to always use MSFS FPS, as RTSS cannot supply the base FPS required for dynamic FG.
• Updated the status line to show DynFG instead of Man FG when DynFG is the active Target FPS type.

---

This discussion was created from the release v0.5.3.0-test Minor Maintenance Update.

[jerryyyyy]

This is from today but a bit of a mess since my VR connection went down after a Meta update and had to restart a bit. Believe MSI was off.

Mixed Alaska MSFS_AutoFPS20260731.log

I will run some more with it On or OFF.

Here is a run with VR and msi ON...

VR MI MSFS_AutoFPS20260731.log

msi OFF here

VR msi OFF MSFS_AutoFPS20260731.log

VR wired settings reset. Luckily I had written a how to which I upload here as a reference just in case.

How to Attach Quest.docx

All your programs output look good in the plane and what I could see here.

[ResetXPDR]

FYI, the just-released Test2 will only show that RTSS not running and data stale messages once.

[jerryyyyy]

Here are some runs without and with rtss. Test 4.

A bit rough as landing practices with Kodiak.

VR NUQ RTss MSFS_AutoFPS20260805.log
VR NUQ No RTss MSFS_AutoFPS20260805.log

[ResetXPDR]

Thanks for those.

I see that RTSS data is still freezing when switching to VR. I had a breakthrough on this with another user where they found that if you are using any form of FG before switching to VR, then RTSS data will freeze and will remain frozen even if you switch back to 2D. If you are using NFR, it never freezes.

If you don't mind doing a bit of a test for me with your next VR flight, can you do the following:

• Make sure MSI and RTSS are already running.
• Start MSFS, go into setting and set frame generation to none.
• Quit MSFS and restart it, as it is important for it to have started with no FG being enabled.
• Start AutoFPS and commence your flight in 2D, then switch to VR and finish your flight.

Once you have done this, send me your log then you are free to re-enable FG in MSFS settings. What I expect to see in your log is that RTSS data remain alive for the entire flight, regardless of whether in 2D or VR.

Thanks.

[jerryyyyy]

AM starting a flight but was not clear how to turn off FG. DLSS just gives me 2 3 4x. I can turn off frame limiting, which is set to 36. Is that what you want?

[ResetXPDR]

Right here:

[jerryyyyy]

sorry, got it. It is at the end of this log that includes a long flight in VR at the start but if you work from the back it is a flight in the pattern where the transition to VR is at about 1000' AGL.

MSFS_AutoFPS20260806.log

[ResetXPDR]

Thanks. That shows what I thought ie. RTSS data no longer freezes when you switch to VR if switching from NFR. I am currently coding up a new test version that provides a warning for this.

[jerryyyyy]

Longer Test 4 flight today.

cOSTA rICA MSFS_AutoFPS20260807.log

[jerryyyyy]

Test5. Not sure what was up but bad performance. CJ4 then 787. In Discord group flight.

VR MSFS_AutoFPS20260808.log

[ResetXPDR]

Performance didn't seem too bad:

I found a bug with RTSS frame time buffer freeze in your log, so I am fixing that now.

Edit: Should be fixed now in test7 just released.

[jerryyyyy]

Here is your latest but I forgot to restart MsI as I rebooted the machine. I am testing the new VD Beta that runs off USB3. Seems as fast if not a touch faster than my ethernet hack. Requires a good cable and I bought the AMVD one that has a power input.

Was seriously considering the Pixmax now that I have young eyes again and can appreciate it, but the Q3 is running well.

If I have time will do a few more landings with the MSI on.

VR NUQ UsB Connection VD Beta MSFS_AutoFPS20260809.log

VR NUQ MsI ON MSFS_AutoFPS20260809.log

[jerryyyyy]

Yes, more readable.

[jerryyyyy]

Your latest from today.

MSFS_AutoFPS20260815.log

[ResetXPDR]

As I don't have a 5000 series card, can I get you to do a quick test for me.

Load up somewhere on the ground with AutoFPS running then go into the MSFS menu and, with nVidia frame generation type (which you normally use) selected, select Dynamic FG as the frame rate multiplier in here:

Then go back to your flight, take a screenshot of the app and let it sit for 30 seconds or so, then send me the screenshot and the log file. When finished, switch back to whatever FG multiplier you were using - 2X I believe.

I just want to confirm that the app auto detects and displays dynamic FG. Do not switch to Man FG / DynFG to do this as that overrides auto detection.

Also, if you get asked to enter a target dynamic FG FPS when you select Dynamic FG in the MSFS menu, can you take a screenshot of that menu and provide that too. It should ask for a target FPS somewhere, as dynamic FG needs that to function correctly.

Thanks.

[jerryyyyy]

It tagged the log on the end of an earlier longer one but I send it all.

MSFS_AutoFPS20260816.log

Looks like the Dyn FG 1X is there?

[ResetXPDR]

That's what I was hoping it would display and log as. Thanks