Jump to content

FalconAF

Members
  • Content Count

    929
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

211 Excellent

About FalconAF

  • Rank
    Member

Profile Information

  • Gender
    Male

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

Recent Profile Visitors

3,970 profile views
  1. OK. No, I'm not trolling. But Michael, your original post did contain two different questions. You said that yourself again only a few posts above: "Anyway this was about night performance in general and settings effecting that the most." You also said you were seeking solutions for a "Low end PC". Many different people have tested AutoFPS to achieve FS performance improvements using many different computer configurations. Some are using a regular monitor, some are using VR headsets, and all the different configurations of these things effect the results. I offered a possible solution for you, because although I first tested it on my more "state of the art" computer, out of curiosity I also tested it on my old 1080Ti GPU computer too. It works fine in achieving what you are trying to do. When configured properly it will stop trying to render graphics that you really don't need during night flying scenarios and will increase the graphics that would enhance your night flying experience. So I'll quit posting to this thread from now on. Have a good day and enjoy your simming.
  2. 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.
  3. 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.
  4. This is exactly the type of "documentation" I was referring about when I was discussing "Teach from the Known to the Unknown" in the AutoFPS thread. First, your narrative explanation defines what the acronyms on the GUI mean relative to the actual settings in the MSFS Graphics settings sliders, then there are actual example pictures from the sim that show how and when to use them (and the results) for different flying scenarios and the "wants" the user wants to achieve at the time. If you could make the post above into a PDF document someone could download, I'm sure it would be very beneficial for many, many new (and even current) users of the application. Maybe even get @Reset to link the PDF as an additional recommended download to enhance the Readme file download information. Great explanations! 👍
  5. Now THAT'S just BEYOND tyrannical. Somebody should spank you.
  6. 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.
  7. 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?
  8. 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.
  9. ROFL! Actually, a good beta tester WILL have a tyrannical approach to beta testing sometimes. It can be the things the developer never considered a user might try to do with the app that might be discovered then. So once in a while the beta tester may..."I'll bet ya the developer never thought anybody would try THIS! Let's see if it breaks the program!!!" 😆 Note: It's better to have a good relationship with the developer before you try that, though. 😀
  10. ESET is most likely blocking it and downloading a "protected" copy of it. There should be a way in ESET settings or notifications to tell ESET to ignore its concerns and download it "as is". If not, just turn off ESET then use EDGE to download it (like Bob said). Then Edge will offer you to "download anyway" after EDGE warns you about the file. After you download the good copy then you can turn ESET back on again (but you'll probably STILL have to tell ESET to ignore it when you try to run it...set an Exclusion in ESET for it).
  11. 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).
  12. If you're referring to the new MSFS2024 version, Asobo personnel already indicated there would "probably" be something similar in MSFS2024 to what the current AutoFPS does. One of them actually said something like, "It's already included in the XBOX version of 2020. I don't know why we didn't think of doing it in the PC version." Duh! 😏
  13. That's probably your problem with it. You don't need to use VSYNC with it. In fact, all the beta testers discovered that can actually interfere with the app. Try it disabling VSYNC in the MSFS Graphics section and see what happens. Just set your FPS in the APP'S FPS window for what frame rate you can normally get, then let the APP maintain that FPS by adjusting you TLOD, OLOD, and Cloud setting. Unless I'm misunderstanding you, the "old lod reset version" was made by the same developer of this new AutoFPS, and the developer himself actually says the old lod reset version should not be used anymore. If you can't get the new AutoFPS to do what the old lod reset app does (and a whole lot better) you are still doing something wrong with it. Initially the app can be confusing for a new user. You really, REALLY need to read the Readme file and if needed ask questions in the forum post I referenced. Once you get YOUR settings for YOUR computer dialed in, you won't be disappointed unless your expectations and associated setting choices are way too extreme for your hardware. Note: I edited my original (first) reply to you to better clarify a couple things. But STILL examine the Readme in its entirety.
  14. 0.4.2. Geez! Brain Dump. I need a vacation!!! 🤪 (I went back and changed my other posts to say v0.4.2. Thanks!)
  15. I thought it was Leo looking at you saying, "He set his TLOD to WHAT???" (No offense intended Cpt_Piett 😉 ) PS - The new full release version works like a charm. I'm sold on it and would buy you a cup of coffee if able. 👍
×
×
  • Create New...