FPS Not Displayed Correctly With RTSS Running

[steve5031]

I've noticed when I have RTSS enabled AutoFPS only displays 11 FPS when in fact the true FPS is 36 FPS. When I stop RTSS AutoFPS displays the correct FPS. I have attached 2 screenshots demonstrating the issue.

Steve

[steve5031]

I am running v7.3.7 of RTSS

[ResetXPDR]

I haven't seen that before, and I use RTSS v7.3.7 in VR sometimes too. Can you send me a log file, located in %appdata%/MSFS_AutoFPS/log, associated with when this occurs and I will take a look.

[ResetXPDR]

I haven't seen that before, and I use RTSS v7.3.7 in VR sometimes too. Can you send me a log file, located in %appdata%/MSFS_AutoFPS/log, associated with when this occurs and I will take a look.

BTW, which VR headset and associated connection software do you use?

[steve5031]

Here's the log file. The log session starting at 8/2/2026 @10:54:03:339 has RTSS as the FPS source. The next session without RTSS (MSFS is FPS source) starts at 11:19:45:370. My headset is a Pimax Super QLED 57PPD running Pimax Play v2.0.2. OpenXR Runtime is Pimax OpenXR. The OpenXR API Layer is the OpenXR toolkit API layer. Cheers, Steve.

…

On Sun, Aug 2, 2026 at 5:37 PM ResetXPDR ***@***.***> wrote: *ResetXPDR* left a comment (ResetXPDR/MSFS_AutoFPS#267) <#267 (comment)> I haven't seen that before, and I use RTSS v7.3.7 in VR sometimes too. Can you send me a log file, located in %appdata%/MSFS_AutoFPS/log, associated with when this occurs and I will take a look. BTW, which VR headset and associated connection software do you use? — Reply to this email directly, view it on GitHub <#267?email_source=notifications&email_token=AX7DVX5O6FVTL3OVNHJ45435H6YBFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMJWGA2DKNBXG4Y2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-5160454771>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AX7DVXY37HOAF4EHRZWPT6D5H6YBFAVCNFSNUABFKJSXA33TNF2G64TZHM4TAMZWGY3DOMRTHNEXG43VMU5TKMBUGMZTMMRRHEY2C5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AX7DVX4BHMCFJ77FHHKLYJ35H6YBFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMJWGA2DKNBXG4Y2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/AX7DVX4L5J5BGJ4I3NLTUTD5H6YBFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMJWGA2DKNBXG4Y2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>

[ResetXPDR]

The log doesn't attach if you do it by email. You need to attach it on github.

[steve5031]

Ok, I will do that.

…

On Sun, Aug 2, 2026, 9:40 p.m. ResetXPDR ***@***.***> wrote: *ResetXPDR* left a comment (ResetXPDR/MSFS_AutoFPS#267) <#267 (comment)> The log doesn't attach if you do it by email. You need to attach it on github. — Reply to this email directly, view it on GitHub <#267?email_source=notifications&email_token=AX7DVX4W4MIKXV7LJGOTSIT5H7UQ5A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMJWGE2DIMJRGY3KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-5161441166>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AX7DVX52QOKVGVV3HCZS5DL5H7UQ5AVCNFSNUABFKJSXA33TNF2G64TZHM4TAMZWGY3DOMRTHNEXG43VMU5TKMBUGMZTMMRRHEY2C5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AX7DVX4GUSYW7TSJNLYYUJD5H7UQ5A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMJWGE2DIMJRGY3KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/AX7DVX6QBKCF2JUGYZCJZRT5H7UQ5A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMJWGE2DIMJRGY3KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>

[steve5031]

MSFS_AutoFPS20260802.log

[ResetXPDR]

Got it that time thanks.

Firstly, has RTSS ever worked properly in VR with this app or is the the first time you have experienced this issue? If it is new, what previous app version did it work?

Next, these log lines are saying the RTSS data is frozen:

2026-08-02 11:01:48.991 [WRN] [ ServiceController:GetRTSSFrameTi ] RTSSFrozen bufPos=729 
2026-08-02 11:02:22.522 [DBG] [ LODController:DetectFixedFPS     ] RawFPS: 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8 
2026-08-02 11:02:42.844 [DBG] [ LODController:DetectFixedFPS     ] RawFPS: 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8 
2026-08-02 11:03:03.195 [DBG] [ LODController:DetectFixedFPS     ] RawFPS: 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8 
2026-08-02 11:03:23.559 [DBG] [ LODController:DetectFixedFPS     ] RawFPS: 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8 
2026-08-02 11:03:43.865 [DBG] [ LODController:DetectFixedFPS     ] RawFPS: 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8 

You are the second user to reveal that RTSS data is frozen, but only when in VR. Theirs is with a Quest 3 I have not yet been able to determine whether it is an app or RTSS issue. The easiest way to tell is, without AutFPS running, to look at the RTSS overlay on your 2D screen when in VR and, while moving the headset around a bit, see whether the FPS and frame time data is changing eg you can see frame time spikes on the graph in this, indicating the data is changing.

If the FPS and frame time data is not updating, and AutoFPS is not running either, then the issue is with how RTSS is hooking in to the Window's graphic system and has nothing to do with AutoFPS. If they are updating, then there is an issue with the AutoFPS RTSS shared memory interface that I would need to look into.

As such, can I get you to run this check (ie. in VR, RTSS overlay and no AutoFPS) and tell me what you observe.

FWIW, it works fine on my system, hence why I have not be able to hunt it down yet:

2026-08-03 12:46:03.987 [INF] [ LODController:UpdateVariables    ] Mode:VR FPS:39 Pri:TLOD TLOD:50 TLODRng:50 OLOD:100 AGL:2 FPM:-0 GPU:91% VRAM:70% CPU:37% Dom:60%(#2) Top2Avg:63% MSFS:14% 
2026-08-03 12:46:06.006 [DBG] [ ServiceController:GetRTSSFrameTi ] BufPos:943 FrameTimesCSV:25018,24959,24951,25100,24818,25127,24916,24985,25042,27697,24999,24995,25045,24950,24987,24937,24971,25101,25002,24580,25215,25234,24813,25195,24982,24995,24781,25113,24637,25389,25008,25092,24858,25168,24855,25125,24746,25255,24033,29689,25134,24802,25184,25000,24935,25008,25047,24979,25010,24834,25139,24768,25211,24979,25025,24946,24652,25477,24941,25089,24922,24998,24967,25083,24905,25107,24976,24971,25012,26979,24998,24949,24996,24844,25044,25144,24968,24986,24942,25037,24974,25059,24986,25021,25006,24846,25104,24940,25045,24955,25119,24964,24733,25282,24954,25075,24827,25111,24942,27433,25046,25031,25121,24721,25206,24944,25081,24921,25157,24868,25101,24977,24997,24930,25030,25041,24998,24937,25090,24906,25133,24670,25230,24903,25092,24741,25181,25027,24848,28421,25135,24923,24982,24944,25148,24917,25074,24910,24862,25190,25013,24952,25000,24900,25093,24982,25088,24915,25070,25012,24948,25049,24890,24695,25263,25160,24995,24968,24963,28531,25165,24886,25012,24989,25050,24888,24959,25085,24885,25188,25048,24954,25064,24938,25062,24911,25032,24920,25129,24939,25031,24929,24937,25133,24945,24806,24625,24735,25940,26636,24787,25174,25061,24948,24891,25175,24804,25178,24370,25601,24944,24963,22138,13464,69222,24935,24971,25085,25036,24859,25113,25064,25011,25004,24908,25009,25037,24902,24780,30043,25048,24826,25216,25046,25020,24909,24957,24925,25095,25031,24082,25976,24669,25263,25016,24911,25133,24908,25105,25013,24960,25000,25077,24952,24975,25006,25026,24942,25000,28820,25066,24929,25047,24995,24994,24944,24863,24903,25316,24940,24997,25001,24779,24487,25818,25077,24967,24873,24946,25193,25013,25002,24946,25009,24382,25548,25040,24951,24939,40529,23043,27131,21292,27485,18215,31581,28530,19791,28000,26064,25895,25257,21353,15014,44146,25113,25000,25132,24986,24066,25918,24675,25391,25072,24909,25035,25146,24923,24819,27371,24832,25154,24758,31269,34555,24866,24866,24482,25304,25550,24703,25268,15636,33991,106271,68108,54566,32759,46978,1451517,414654 
2026-08-03 12:46:07.015 [DBG] [ ServiceController:GetRTSSFrameTi ] BufPos:983 
2026-08-03 12:46:08.023 [DBG] [ ServiceController:GetRTSSFrameTi ] BufPos:1023 

In the meantime, I will research why RTSS data would freeze in VR. Until resolved, the simple fix is to switch back to MSFS as the FPS data source.

[steve5031]

It has worked properly with RTSS in the past. I don't know which version it stopped working but probably within the last month or so. I'll have a chance tomorrow evening (Eastern Standard Time) to do some RTSS tests. Steve

…

On Sun, Aug 2, 2026, 11:02 p.m. ResetXPDR ***@***.***> wrote: *ResetXPDR* left a comment (ResetXPDR/MSFS_AutoFPS#267) <#267 (comment)> Got it that time thanks. Firstly, has RTSS ever worked properly in VR with this app or is the the first time you have experienced this issue? If it is new, what previous app version did it work? Next, these log lines are saying the RTSS data is frozen: 2026-08-02 11:01:48.991 [WRN] [ ServiceController:GetRTSSFrameTi ] RTSSFrozen bufPos=729 2026-08-02 11:02:22.522 [DBG] [ LODController:DetectFixedFPS ] RawFPS: 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8 2026-08-02 11:02:42.844 [DBG] [ LODController:DetectFixedFPS ] RawFPS: 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8 2026-08-02 11:03:03.195 [DBG] [ LODController:DetectFixedFPS ] RawFPS: 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8 2026-08-02 11:03:23.559 [DBG] [ LODController:DetectFixedFPS ] RawFPS: 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8 2026-08-02 11:03:43.865 [DBG] [ LODController:DetectFixedFPS ] RawFPS: 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8, 10.8 You are the second user to reveal that RTSS data is frozen, but only when in VR. Theirs is with a Quest 3 I have not yet been able to determine whether it is an app or RTSS issue. The easiest way to tell is, without AutFPS running, to look at the RTSS overlay on your 2D screen when in VR and, while moving the headset around a bit, see whether the FPS and frame time data is changing eg you can see frame time spikes on the graph in this, indicating the data is changing. image.png (view on web) <https://github.com/user-attachments/assets/fd02b0b3-0cde-4a2a-a7e9-43dfb771dc29> If the FPS and frame time data is not updating, and AutoFPS is not running either, then the issue is with how RTSS is hooking in to the Window's graphic system and has nothing to do with AutoFPS. If they are updating, then there is an issue with the AutoFPS RTSS shared memory interface that I would need to look into. As such, can I get you to run this check (ie. in VR, RTSS overlay and no AutoFPS) and tell me what you observe. FWIW, it works fine on my system, hence why I have not be able to hunt it down yet: 2026-08-03 12:46:03.987 [INF] [ LODController:UpdateVariables ] Mode:VR FPS:39 Pri:TLOD TLOD:50 TLODRng:50 OLOD:100 AGL:2 FPM:-0 GPU:91% VRAM:70% CPU:37% Dom:60%(#2) Top2Avg:63% MSFS:14% 2026-08-03 12:46:06.006 [DBG] [ ServiceController:GetRTSSFrameTi ] BufPos:943 FrameTimesCSV:25018,24959,24951,25100,24818,25127,24916,24985,25042,27697,24999,24995,25045,24950,24987,24937,24971,25101,25002,24580,25215,25234,24813,25195,24982,24995,24781,25113,24637,25389,25008,25092,24858,25168,24855,25125,24746,25255,24033,29689,25134,24802,25184,25000,24935,25008,25047,24979,25010,24834,25139,24768,25211,24979,25025,24946,24652,25477,24941,25089,24922,24998,24967,25083,24905,25107,24976,24971,25012,26979,24998,24949,24996,24844,25044,25144,24968,24986,24942,25037,24974,25059,24986,25021,25006,24846,25104,24940,25045,24955,25119,24964,24733,25282,24954,25075,24827,25111,24942,27433,25046,25031,25121,24721,25206,24944,25081,24921,25157,24868,25101,24977,24997,24930,25030,25041,24998,24937,25090,24906,25133,24670,25230,24903,25092,24741,25181,25027,24848,28421,25135,24923,24982,24944,25148,24917,25074,24910,24862,25190,25013,24952,25000,24900,25093,24982,25088,24915,25070,25012,24948,25049,24890,24695,25263,25160,24995,24968,24963,28531,25165,24886,25012,24989,25050,24888,24959,25085,24885,25188,25048,24954,25064,24938,25062,24911,25032,24920,25129,24939,25031,24929,24937,25133,24945,24806,24625,24735,25940,26636,24787,25174,25061,24948,24891,25175,24804,25178,24370,25601,24944,24963,22138,13464,69222,24935,24971,25085,25036,24859,25113,25064,25011,25004,24908,25009,25037,24902,24780,30043,25048,24826,25216,25046,25020,24909,24957,24925,25095,25031,24082,25976,24669,25263,25016,24911,25133,24908,25105,25013,24960,25000,25077,24952,24975,25006,25026,24942,25000,28820,25066,24929,25047,24995,24994,24944,24863,24903,25316,24940,24997,25001,24779,24487,25818,25077,24967,24873,24946,25193,25013,25002,24946,25009,24382,25548,25040,24951,24939,40529,23043,27131,21292,27485,18215,31581,28530,19791,28000,26064,25895,25257,21353,15014,44146,25113,25000,25132,24986,24066,25918,24675,25391,25072,24909,25035,25146,24923,24819,27371,24832,25154,24758,31269,34555,24866,24866,24482,25304,25550,24703,25268,15636,33991,106271,68108,54566,32759,46978,1451517,414654 2026-08-03 12:46:07.015 [DBG] [ ServiceController:GetRTSSFrameTi ] BufPos:983 2026-08-03 12:46:08.023 [DBG] [ ServiceController:GetRTSSFrameTi ] BufPos:1023 In the meantime, I will research why RTSS data would freeze in VR. — Reply to this email directly, view it on GitHub <#267?email_source=notifications&email_token=AX7DVX2HP3S7O3R3VHZGWNL5H76DNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMJWGE4DKMBZGAZ2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-5161850903>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AX7DVX4E4QITW5MDLIGJRSL5H76DNAVCNFSNUABFKJSXA33TNF2G64TZHM4TAMZWGY3DOMRTHNEXG43VMU5TKMBUGMZTMMRRHEY2C5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AX7DVX6YQUSI2I2CYRPE5KT5H76DNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMJWGE4DKMBZGAZ2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/AX7DVX65FQ4VDP5XQ5CHBM35H76DNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMJWGE4DKMBZGAZ2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>

[ResetXPDR]

That would be good thanks. It was probably version 0.5.1.0 if it was a month ago if you have been keeping your app up to date. you can get the installer for it here if you don't have it any more.

I have also just put out 0.5.3.0-test3 that logs the first 5 RTSS data dumps after a reset, which will let me know if data is stale or not, that you could also try. You will need to enable Log+ for it to record. eg:

2026-08-03 15:37:06.029 [WRN] [ ServiceController:GetRTSSFPS     ] Flags=Record StatStart=3/08/2026 9:14:09 AM StatEnd=3/08/2026 7:08:42 AM StatFrames=150544 StatCount=150544 StatMinFPS=89 StatAvgFPS=199 StatMaxFPS=208 InstStart=3/08/2026 7:08:43 AM InstEnd=3/08/2026 7:08:42 AM InstFrames=21 InstFrameTimeUs=49681 InstFPS=20.1 BufFPS=20.0 
2026-08-03 15:37:07.066 [WRN] [ ServiceController:GetRTSSFPS     ] Flags=Record StatStart=3/08/2026 9:14:10 AM StatEnd=3/08/2026 7:08:42 AM StatFrames=150565 StatCount=150565 StatMinFPS=89 StatAvgFPS=199 StatMaxFPS=208 InstStart=3/08/2026 7:08:43 AM InstEnd=3/08/2026 7:08:42 AM InstFrames=21 InstFrameTimeUs=50347 InstFPS=20.1 BufFPS=19.9 

To summarise what I would like you to do:

• Observe RTSS OSD data WITHOUT AutoFPS running and advise whether FPS and frame time info is frozen or not when in VR.
• Try installing 0.5.1.0 and tell me if it works again.
• Try installing 0.5.3.0-test4, or the latest version from here if superseded and no longer available, and send me the log.

Thanks.

[steve5031]

No problem. How do you enable log+?

…

On Mon, Aug 3, 2026, 1:40 a.m. ResetXPDR ***@***.***> wrote: *ResetXPDR* left a comment (ResetXPDR/MSFS_AutoFPS#267) <#267 (comment)> That would be good thanks. It was probably version 0.5.1.0 if it was a month ago if you have been keeping your app up to date. you can get the installer for it here <https://github.com/ResetXPDR/MSFS_AutoFPS/releases/download/v0.5.1.0/MSFS_AutoFPS-installer-v0.5.1.0.exe>if you don't have it any more. I will also put out a new test version that logs the first 5 RTSS data dumps after a reset that you could also try. You will need to enable Log+ for it to record. To summarise what I would like you to do: - Observe RTSS OSD data WITHOUT AutoFPS running and advise whether FPS and frame time info is frozen or not when in VR. - Try installing 0.5.1.0 and tell me if it works again. - Try installing 0.5.3.0-test3 <https://github.com/ResetXPDR/MSFS_AutoFPS/releases/download/v0.5.3.0-test/MSFS_AutoFPS-installer-v0.5.3.0-test3.exe>, or the latest version from here <https://github.com/ResetXPDR/MSFS_AutoFPS/releases/tag/v0.5.3.0-test> if superseded and no longer available, and send me the log. Thanks. — Reply to this email directly, view it on GitHub <#267?email_source=notifications&email_token=AX7DVXYLNZAABQOA7QG3PY35IAQTRA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMJWGI3TEMBVGE42M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-5162720519>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AX7DVXZE2BBB23UFNBKWVHL5IAQTRAVCNFSNUABFKJSXA33TNF2G64TZHM4TAMZWGY3DOMRTHNEXG43VMU5TKMBUGMZTMMRRHEY2C5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AX7DVX4G7J26XOF3JVWWFST5IAQTRA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMJWGI3TEMBVGE42M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/AX7DVX55WUATV5DS3VSVJPT5IAQTRA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMJWGI3TEMBVGE42M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>

[ResetXPDR]

No problem. How do you enable log+?
…

[steve5031]

Well I started with just have the RTSS displaying the FPS which worked fine with the FPS matching the in game FPS display. When I went into VR the RTSS display would disappear. Going back to 2D it re-appeared. I then brought up AutoFPS and it downloaded a new version which I accepted. AutoFPS is now working as expected in both 2D and 3D. Weird. I've attached the logfile for that session. Everything seems normal now. Very strange????

MSFS_AutoFPS20260803.log

[ResetXPDR]

I can see what you mean! I've looked over the release notes between test2, which you were using when you experienced the issue, and test4, which magically seems to have fixed it, and I see nothing changed with the RTSS interface, other than logging of RTSSs stat with Log+ enabled which you didn't have enabled anyway.

I suggest you turn on Log+ and keep an eye out for the issue occurring again and send me the log if it does, because something tells me we are not done with this through sheer luck alone! 😆

[steve5031]

Sounds good. Thanks for your excellent support. Cheers, Steve

…

On Tue, Aug 4, 2026, 4:25 a.m. ResetXPDR ***@***.***> wrote: *ResetXPDR* left a comment (ResetXPDR/MSFS_AutoFPS#267) <#267 (comment)> I can see what you mean! I've looked over the release notes between test2, which you were using when you experienced the issue, and test4, which magically seems to have fixed it, and I see nothing changed with the RTSS interface, other than logging of RTSSs stat with Log+ enabled which you didn't have enabled anyway. I suggest you turn on Log+ and keep an eye out for the issue occurring again and send me the log if it does, because something tells me we are not done with this through sheer luck alone! 😆 — Reply to this email directly, view it on GitHub <#267?email_source=notifications&email_token=AX7DVXZIMNHPLWNDQLDBBPL5IGMYNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMJXGY2DKNRWHA3KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-5176456686>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AX7DVXY44X5PLIMULBJ5FRL5IGMYNAVCNFSNUABFKJSXA33TNF2G64TZHM4TAMZWGY3DOMRTHNEXG43VMU5TKMBUGMZTMMRRHEY2C5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AX7DVX5VSEXIDYXOLHUSG3L5IGMYNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMJXGY2DKNRWHA3KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/AX7DVX5K2U5DBMPYOFITMI35IGMYNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMJXGY2DKNRWHA3KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>