Jump to content

Reset XPDR

Members
  • Content Count

    2,969
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

1,156 Excellent

1 Follower

About Reset XPDR

  • Rank
    Member - 2,000+

Profile Information

  • Gender
    Male

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    VATSIM
  • Virtual Airlines
    Yes

About Me

  • About Me

Recent Profile Visitors

5,514 profile views
  1. I linked it a few pages ago when I announced the new test version but here it is. BTW, you can see all the releases out there, even older ones by going to this link which you can get to by clicking on releases in on the main AutoFPS page.
  2. Something must have changed on your system in the last day. Are you SURE you haven't been tinkering with something? 🤪😄
  3. Yes, quite often. I too copy my long posts to the clipboard so I have a backup.
  4. Further to @Cpt_Piett's response, yes the bigger the gap the more change can occur. Previously if you had set 1 or 2 FPS below target, you wouldn't have even crossed the FPS tolerance threshold and no upwards adjustments would occur but with this latest version it will work but much slower than if you gave it a couple more FPS to work up a greater difference from target FPS. In your case, 5 FPS would have done it, but 10 obviously works too.
  5. Your first screenshot is fine, because FPS is above target so you expect TLOD Max. The second screenshot does not though, unless you took it the very second you gave MSFS back the focus and it was still showing the non-FG FPS, which is I reckon what happened. You have to wait a few seconds for FPS to stabilise when giving MSFS back the focus. I just checked the code and it does not force a settle timer when MSFS gets the focus back with FG so it is possible to see such a thing as your second screenshot immediately after doing this. I will change the code so that a settle timer gets engage all times MSFS regains focus. Re the internal halving I was talking about, you can see you have 113 FG FPS with an FG active target of 100. When you switch to the app having the focus, your FG FPS will normally halve to 56.5, which it looks like it did on your second screenshot which I have already discussed above. The internal halving I am talking about is the app now halves your FG active FPS target to 50 because it is really now your FG INactive FPS target, and since 56 current FPS is greater than the modified 50 target FPS, you are still above target FPS so your TLOD remains pegged at TLOD Max. I had to do this back in the DynamicLOD_ResetEdition otherwise your TLOD would try to dive because your 56 FPS was way under your 100 target, but that 100 target is no longer valid because FG is not active if that makes sense.
  6. Nothing has changed with the app, unless you were using 0.4.3.1-test which from your screen shot you are not. The app gets FPS from simconnect, and simconnect can have many apps using it at one. So, I have no idea why this is suddenly happening for you.
  7. If anything switching between VFR and IFR should set both to TLOD Min and work up from there, not just with IFR mode, but I did that with app startup on ground intended and maybe I need to alter it so that it doesn't have to do that in flight. I'll look into it.
  8. Just to clarify, AutoFPS does actually take into account the massive drop in FPS when using FG and MSFS loses focus, in that it internally halves your target FG active FPS and uses that. This works fine most of the time, as @jarmstrois experiencing, however FG inactive is not always exactly half FG active and when you give MSFS back the focus there are a few seconds of FPS weirdness until FG settles down, so either of these can confuse the automation algorithm.
  9. Sorry, no more MSFS settings than the ones currently being manipulated are planned to be added.
  10. Already answered but can I ask why you want this with the non-expert option? If a compelling reason, like when using FG in this mode causes TLOD hunting when switching focus between MSFS and the app, then I could hard code it in for that particular configuration, but only if it makes sense for everyone's use in that configuration.
  11. You should be aiming for 30+ non-FG FPS because FG works better that way and will give you less artifacts. All of the other questions have answers in the readme.
  12. I am keeping the non-expert section as clean as possible from a UI perspective, so I am not going to do this sorry. Just use expert settings, leave the defaults as they are and use the pause feature there.
  13. The how to remove this app if required is already in the readme, which says: To uninstall, ensure you have completely exited the app (ie. it is not hiding still running in your Systray), run the installer and select remove on the first window. This will remove all traces of the app, including the desktop icon, MSFS or FSUIPC autostart entries if you used them, and the entire app folder, including your configuration file. To be frank, the only users that have had an issue with uninstalling is because they did not follow these instructions and got themselves into trouble trying to manually delete it. I am not going to provide more instructions on how to remove it manually if they can't even be bothered to read and perform the instructions already there that actually work!
  14. FYI, I will be releasing progressive update builds for the next AutoFPS version, which is only planned to be a minor maintenance release so they are more a preview than full on test builds, the latest version of which you can always get here. I will also keep all previous test build installers there from now on so you can go backwards or forwards anytime you want, mainly the former if you experience issues with the latest test release. Note that I have changed the test build naming convention to be numerical for the last digit e.g 0.4.3.1-test, 0.4.3.2-test etc. This is so users always know what test build they are on when after it is installed as it will be shown in the running app, which should clear up confusion with the DTG convention used previously that only applied to the installer. eg. you'll see something like this: Edit: Oh, and I may as well mention what is in this new test build. Initial Test Version 0.4.3.1-test: Added last window position saving/restoration on next startup. This may only work for single monitor as I haven't worked out how to place the app on a specific monitor yet, but it seems to be working fine on my dual monitor setup. If something goes wrong and it doesn't appear anywhere, you can just go into the config file and delete the two lines windowLeft and windowTop and it should reset it back to default. Improved MSFS settings saving and restoration to immediately reset cloud quality if a previously abnormal shutdown of either MSFS or this app was detected and to provide more log file detail on MSFS settings saving and restoration activities. Enhanced logging of cloud quality settings to use the actual textual description from the MSFS settings menu rather than the numeric it is stored as in MSFS memory.
×
×
  • Create New...