VSYNC 50%refreshrate seems to be better and also the target FPS in AutoFPS. 

Not perfect but better. Also better at FL300.

Michael Moe

Edited March 16, 20242 yr by Michael Moe

2 hours ago, Michael Moe said:

Nope refering to latest beta

Michael Moe 

Ah, OK, I understand now.  Are you using a MSFS beta now?  The AutoFPS developer only updates the app for current non-beta MSFSs.  If you are using a beta that might cause issues too.  

EDIT:  I didn't see your above post about VSYNC 50% refresh rate until after I posted this. Looks like it may be working for you better now? 

Edit 2:  There's a series of questions the developer is answering about using VSync (or not) with the latest version.  It starts on the bottom of Page 3 of the thread I linked for you in my first post to this thread.  I don't know what your computer's specs are or what FPS you may be aiming for, but I was able to get a steady 30 FPS when I tested it on my old 1080TI GPU dinosaur machine. (I just used that computer as a test bed for the app...I run my MSFS2020 on a much more capable computer). 

Edited March 16, 20242 yr by FalconAF

Currently flying over southern Germany at FL350, I was up to 62fps now I'm down to 26fps with no apparent reason. AutoFPS app has been working very well up to this point and the issue is nothing to do with the app.

It fluctuates from 60 down to 20, will stay there for 5-10 minutes then back up to 50-60 again. I'm hoping the sim update will fix this.

7 hours ago, FalconAF said:

You won't need it anymore with the v0.4.2 AutoFPS.  The "Expert" mode option included with it will allow you to do basically the same things automatically, even on an "old low end PC" that would struggle to maintain 30 FPS in MSFS2020 (I tested it on one of my older PCs I still have from many years ago just for grins and giggles.  Can you say 1080Ti GPU?  🤪 With a motherboard that can't be upgraded to Windows 11?  🤣).  As long as you keep your expectations rational...ie - don't try Ultra Clouds at a payware JFK with 150 AI parked everywhere you'll be fine.  Just stay reasonable and you will be able to maintain 30 FPS with "High" clouds, fewer AI, etc.  Regardless of the computer capability, you still have to select settings that the computer can reasonably handle.  

Enter stage left my GTX 980Ti, which is currently doing a fantastic job of rendering MSFS in high detail @ 1080p resolution with hardly a stutter in sight. I do not have AI planes active at the moment, but the performance is borderline crazy on my PC of yesteryear. Oh, and I keep TLOD and OLOD @ 250/200 respectively at all times. No need for AutoFPS.

Edited March 16, 20242 yr by Christopher Low

Sorry, but 1080p is hardly "high detail" by today's standards.  I was using 4K resolution on my 65" Curved Samsung UHD TV and getting consistent 30FPS with TLOD and OLOD settings in the 400's on my "test" computer using AutoFPS with a 1080Ti.  All the people who report "It isn't working" have simply been found to be using it wrong.  They MUST read the readme and UNDERSTAND how it works so they don't ask it to do things it simply can't do.  If the frame rates are fluctuating between the 60's and the 20's, it is set up incorrectly.  WAY incorrectly. 

That said, if you are happy at 1080p, then you are right.  You don't need AutoFPS.

Edited March 16, 20242 yr by FalconAF

2 hours ago, El Diablito said:

Currently flying over southern Germany at FL350, I was up to 62fps now I'm down to 26fps with no apparent reason. AutoFPS app has been working very well up to this point and the issue is nothing to do with the app.

It fluctuates from 60 down to 20, will stay there for 5-10 minutes then back up to 50-60 again. I'm hoping the sim update will fix this.

I just saw you posted in the app's thread you completed the flight and the app worked fine.  Did your 60 to 20 to 60 FPS variations resolve themselves?  It shouldn't be doing that if you have the right values input to the app's GUI boxes. That large of "gap" between your FPS means something is wrong with your settings. Were you using the "Auto Target FPS" mode, or the "Use Expert Options" mode? 

31 minutes ago, FalconAF said:

I just saw you posted in the app's thread you completed the flight and the app worked fine.  Did your 60 to 20 to 60 FPS variations resolve themselves?  It shouldn't be doing that if you have the right values input to the app's GUI boxes. That large of "gap" between your FPS means something is wrong with your settings. Were you using the "Auto Target FPS" mode, or the "Use Expert Options" mode? 

I don't think it has anything to do with the app at all as my performance on the ground (in non-expert mode with a simple FPS target of 40) is buttery smooth at EGLL with FSLTL traffic. It only happens at altitude, and it only seems to happen over France, Belgium, Germany, Switzerland. which is why I think it's a server issue or something else as yet unidentified.

Once I had passed over the Alps and descended into Northern Italy the problem was gone, the app performed flawlessly for the rest of the flight. Its a strange one.

Something I thought of as I was writing this also - In every case this performance hit happens there is a sudden injection of FSLTL aircraft heading for the English channel. All of a sudden I will count up to 10 aircraft, all on the radar, all bunched up and easily observable from the cockpit. It looks great as it adds some realism but I'm wondering if there's a connection there. I haven't seen this replicated anywhere else. I'd be interested to know if anyone else experiences something similar. If FSLTL is causing a performance hit of that size at altitude I'll be very disappointed, but I'd doubt it.

56 minutes ago, El Diablito said:

I don't think it has anything to do with the app at all as my performance on the ground (in non-expert mode with a simple FPS target of 40) is buttery smooth at EGLL with FSLTL traffic. It only happens at altitude, and it only seems to happen over France, Belgium, Germany, Switzerland. which is why I think it's a server issue or something else as yet unidentified.

I recall seeing a post not long ago about other people having bandwidth problems recently in European areas and actually getting the "Bandwidth Too Low" message and getting disconnected from the MS servers.  If there are server fluctuations that bad AutoFPS WOULD be jumping through hoops trying to establish a baseline FPS value.  I had it happen to me once yesterday but I was flying in the U.S. area at the time.  But I still maintained a steady 30 FPS while AutoFPS just readjusted my TLOD and OLOD settings on the fly. So getting disconnected from the MSFS server may have something to do with your flight and FPS instability.  

The sudden FSLTL injections might do it also if they increased the processing and rendering requirements that quickly.  You would get an initial FPS drop that would (probably?) stay low until a lot of those FSLTL AI's got out of required processing range.

You could ask the developer in the other thread. He's still requesting and answering any questions/reports of "strange" stuff that may be happening with the new final version.

Edited March 16, 20242 yr by FalconAF

4 hours ago, El Diablito said:

I don't think it has anything to do with the app at all as my performance on the ground (in non-expert mode with a simple FPS target of 40) is buttery smooth at EGLL with FSLTL traffic. It only happens at altitude, and it only seems to happen over France, Belgium, Germany, Switzerland. which is why I think it's a server issue or something else as yet unidentified.

Once I had passed over the Alps and descended into Northern Italy the problem was gone, the app performed flawlessly for the rest of the flight. Its a strange one.

Something I thought of as I was writing this also - In every case this performance hit happens there is a sudden injection of FSLTL aircraft heading for the English channel. All of a sudden I will count up to 10 aircraft, all on the radar, all bunched up and easily observable from the cockpit. It looks great as it adds some realism but I'm wondering if there's a connection there. I haven't seen this replicated anywhere else. I'd be interested to know if anyone else experiences something similar. If FSLTL is causing a performance hit of that size at altitude I'll be very disappointed, but I'd doubt it.

I am in the same boat. Aircraft type not the case and with no traffic at all.

After 45minutes to 1 hour and in cruise its just a stutter and performance wreck

Michael Moe

AutoFPS app gives me stutters and reduces the textures which I can do manually. Sure there's some pro's with this app but no one wants to talk about the negatives like stutters which the base sim already suffers from.

2 hours ago, YVR_23 said:

AutoFPS app gives me stutters and reduces the textures which I can do manually. Sure there's some pro's with this app but no one wants to talk about the negatives like stutters which the base sim already suffers from.

IF that was true for EVERY user of MSFS2020 or the AutoFPS, then EVERYBODY would be reporting it.  But that simply isn't the case and NEVER has been.  Yes, there are isolated times when the MS servers may get overcrowded, etc, or there are "network problems", but EVEN THEN not EVERY user around the entire world experiences the things you are describing.  Time and time again, the real problem with MS Flight Simulators "running poorly" over the entire history of the products has been the USER using improper or unrealistic settings in the simulator or "utilities" for their own computer's capabilities (and failure to do routine maintenance of those computers to prevent bloated computers from causing the sim to run poorly).

What no one wants to "talk about" over and over again is complaints from users that it's the SIM or an APPS fault, only for other people to discover the users REAL problem was being created by themself in the way they use the sim or apps (or take care of their own computer).

The AutoFPS app WORKS.  Even Asobo recognizes that in the official MSFS2020 forum (not openly, but they have stated that the results that something LIKE AutoFPS produces ARE beneficial in using the simulator).  It's the same darn thing Asobo INCLUDED in the XBOX version of MSFS2020...the user just can't ACCESS it in XBOX to make manual adjustments with it, which was probably intentional so Asobo wouldn't get swamped with complaints about the XBOX MSFS2020 "running poorly" because the XBOX user screwed up the settings themself.

And for the same reason, IF Asobo ever included a similar AutoFPS capability in this or a future PC version of Flight Simulator, I wouldn't be surprised at all if it was a simple "One Button Click to turn On or Off" (as Asobo themself described how easy it would be to include it in the PC version), so the user COULDN'T change the individual settings of it.  Heck, too many users screw up their FS already by using the Graphics sliders in unrealistic and improper settings for their own computers. Asobo wouldn't want their forums filled with complaints about the sim "not running correctly" because the USER used wrong settings for any similar AutoFPS capability.  So "One Button...On or Off"...would be the SMART thing for them to include. Heck, even then they wouldn't take away the slider settings in the Graphics section of the sim, so users could STILL screw it up themselves any time they wanted.

Edited March 17, 20242 yr by FalconAF

The AutoFPS tool doesn't cause stutter on my system, it removes them.

Best thing since sliced bread.

Edited March 17, 20242 yr by JYW

14 hours ago, FalconAF said:

So getting disconnected from the MSFS server may have something to do with your flight and FPS instability. 

No that either because I never get disconnected or get any server disconnection messages. I tried this morning with a vanilla setup with no running apps in the background and I got the same issue. 

I get between 40 and 50 fps at a major hub at it drops down to 15-20 at altitude for periods of around 5 minutes, with fluctuations. High FPS return on approach.

41 minutes ago, El Diablito said:

No that either because I never get disconnected or get any server disconnection messages. I tried this morning with a vanilla setup with no running apps in the background and I got the same issue. 

I get between 40 and 50 fps at a major hub at it drops down to 15-20 at altitude for periods of around 5 minutes, with fluctuations. High FPS return on approach.

Ditto here

TLOD/OLOD 50 all the way at cruise and still stutters/fps issue.

Strange indeed. Will try a flight in USA

Michael Moe

Edited March 17, 20242 yr by Michael Moe

For those of you experiencing stuttering and large FPS changes during high(er) altitude cruise flight, I have to ask a question.  Are you switching back and forth between cockpit view and an external view a lot? That can cause swings in FPS due to the changing rendering requirements of the 2 different views that need to be displayed on your monitor (interior Cockpit View vs an Exterior Camera View).  Also, simply panning the scene can do the same thing, especially in a full exterior view.  With a very high TLOD setting trying to display an full outside view, just panning the outside view can cause your computer to have to load and display new data that wasn't already in your computer's memory (this is a common problem for older less robust computers running ANY graphics intensive software).  So if your chosen values are set too high (or just "incorrectly") in EITHER or BOTH MSFS and the AutoFPS GUI window, that can make AutoFPS have to keep adjusting TLOD, OLOD, and even the Clouds quality constantly.  If that happens AutoFPS won't be able to compensate for it and provide a "steady chosen FPS" result. Your chosen FPS rate may be unobtainable, with your TLOD, OLOD, and Clouds values making CONSTANT swings up and down by AutoFPS trying to maintain a steady FPS it can't achieve.  But that would NOT be because of any flaw in the app itself.

Folks, the bottom line in ANYTHING in this type of scenario is that if the MAJORITY of the people say something is working right, and a small MINORITY of the people are saying no it doesn't, the usual finding is that the minority is doing it wrong somehow.  

Edited March 17, 20242 yr by FalconAF