I am using LS with its Version 1.1 because the shimmering in Night conditions is very ugly. With 1.1 there are no problems at Night 

19 hours ago, Reset XPDR said:

A break from testing and enjoying a flight over Nevada, pushing TLOD right up to 1000 😁

Just tried it on old system with a 1060 card, running close to these settings clouds on high, albeit 15 FPS target. Was one long pause after T/O. Otherwise it ran smooth as ever.

This is a help request, please direct it to the right thread in not for here....

I have install the app sometime ago and now after the last MSFS UG I have lost the gui window so I cannot see or change anithing,,,..any help or direciton , thankyou 

 

Jorge

2 minutes ago, aeronauta said:

This is a help request, please direct it to the right thread in not for here....

I have install the app sometime ago and now after the last MSFS UG I have lost the gui window so I cannot see or change anithing,,,..any help or direciton , thankyou 

 

Jorge

Use the downloaded EXE to remove the app. Then reinstall. 

40 minutes ago, aeronauta said:

This is a help request, please direct it to the right thread in not for here....

I have install the app sometime ago and now after the last MSFS UG I have lost the gui window so I cannot see or change anithing,,,..any help or direciton , thankyou 

 

Jorge

  On 9/5/2024 at 3:32 PM, Recognition said:

When I click on exe it says AutoFPS already running, even after I end it in Task Manager.

If I reboot it runs first time when exe. But after that I cant get the window to show on desktop say AutoFPS already running.

Hope this Advice below from Reset XPDR helps.

You should never need to end AutoFPS in task manager. Per the readme, to exit the app, right click on the app icon in the system tray and select exit. Again per the readme, if you are not seeing the app window and the app is already running, just double click on the app icon in your system tray and the app window will open again.

@gsalden  tank you for the quick and effective reply, all is good now...to @recognition the exe to click is the one you downloaded nott the one you use to start the app, thet will give you the msg that is already running, the downloaded one will ask if you want to remove it...

 

Jorge

I've been testing .17-test9 today. Fenix A320 LOWK Klagenfurt to LIPZ Venice with a missed approach at LIPB Bolzano in the Italian Alps (yes I know I should not try to land the A320 there...). 

Overall, this build works really well!

Log file analysis:

Takeoff and climb to FL130:

• TLOD Min Extra 400 on the ground
• Gradual increase to TLOD 800 once above the terrain threshold
• FPS stayed above target

Bolzano VOR approach:

• Descent from 10,000ft to 5000ft
• TLOD Max Extra active as above the terrain threshold
• Gradual TLOD reduction from 800 to 460
• FPS stayed above target

Bolzano visual approach with prescribed tracks rwy 19:

• Descent from AGL 5000ft to AGL 500ft
• Gradual TLOD reduction from 700 to 200
• FPS stayed above target

Venice RNAV approach rwy 22R:

• Descent from AGL 5000ft to AGL 9ft
• TLOD 400 down to AGL 1200ft
• Gradual TLOD reduction from 400 at AGL 1200ft to 370 on the ground
• FPS stayed above target with FPS 64 on the ground

I guess Mtns+Res: 1 means that TLOD Max Extra is active?

In summary, I couldn't see any strange issues in the log file. Test9 seems to work as intended. 

I also did several CapFrameX tests (each about 5min duration):

• Cruising at FL130 over the Alps: avg FPS 67, 1% low average 49.1
• Bolzano VOR approach: avg FPS 71, 1% low average 38
• Venice RNAV approach: avg FPS 78, 1% low average 44

In all of the above captures, frame time variance was very good (<2ms at least above 76%), indicating that the sim ran smoothly. 

Settings:

Sorry if all of this might seem a bit confusing for people that don't have experience with AutoFPS. I just wanted to provide as much detail as possible to @Reset XPDR. This thread is now 100 pages long, and is a mixture of info on new releases, feedback from testing and questions. 

In terms of lossless scaling implementation in future builds, I'm happy to test this. Even though I'm not using LS at the moment, I have it. 

Edited September 7, 20241 yr by Cpt_Piett

I did another Fenix A320 shared cockpit flight (YourControls) with a friend (henceforth referred to as first officer). We both agree that this is the best AutoFPS version so far. It seems solid despite very different hardware and several addons that consume CPU cycles. 

• EDDM Münich to LIMJ Genoa
• VoxATC with AIG traffic at 50%
• My FO was streaming VoxATC through Discord hence running all the traffic and Vox

I had a few minor stutters on the ground and takeoff roll at Münich with a TLOD Min Extra at 400. Same with my FO. After that: smooth, including the approach to Genoa.

Unrelated: we got a visual approach to rwy 10 initially but had to go missed due to the terrain. Then got a really interesting and challenging VOR/DME rwy 28 approach with a transition to a left visual approach to rwy 10. 

My FO's specs: AMD Ryzen 5 5600G 6-Core 12 Thread 4.1 Ghz 64 GB DDR4 3200 Ram Nvidia RTX 3060 12 GB

My FO's log file in case it's of any interest (I haven't had a chance to look through it yet): https://drive.google.com/file/d/1LOy837V4putqw1G8hR9QshBagI20iPxp/view?usp=sharing

Edited September 7, 20241 yr by Cpt_Piett

4 hours ago, Cpt_Piett said:

I guess Mtns+Res: 1 means that TLOD Max Extra is active?

Yes, if greater than 0 it shows TLOD Max Extra is active and by how much, including any taper off reduction.

4 hours ago, Cpt_Piett said:

Sorry if all of this might seem a bit confusing for people that don't have experience with AutoFPS. I just wanted to provide as much detail as possible to @Reset XPDR.

This detailed feedback is great and very helpful. Thanks!

32 minutes ago, Cpt_Piett said:

I did another Fenix A320 shared cockpit flight (YourControls) with a friend (henceforth referred to as first officer). We both agree that this is the best AutoFPS version so far. It seems solid despite very different hardware and several addons that consume CPU cycles. 

That is pleasing to hear and good to know.

4 hours ago, Cpt_Piett said:

In terms of lossless scaling implementation in future builds, I'm happy to test this. Even though I'm not using LS at the moment, I have it. 

I have been trying LS on my main gaming rig and gaming laptop, just to get a feel for it. Interestingly, it works best on my main gaming system, where it isn't really needed, and is a bit hit and miss on my gaming laptop.

Of note to AutoFPS however is that, as far as I can tell, LS does not actually change the detectable FPS of a game like MSFS, rather it does it's trickery between frames and leaves the FPS reading alone. As such, and correct me if I am wrong, there is nothing for AutoFPS to detect or actually do with LS as you just set your AutoFPS target FPS based on your pre-FG in-game FPS target and be done with it. Am I missing something?

eg. Here's my current flight with LS set to 2X, showing 30 FPS in game, same as if I don't run LS, but actually getting 60 FPS visually. AutoFPS doesn't care whether LS is running or not and works the same either way.

4 hours ago, Cpt_Piett said:

I've been testing .17-test9 today. Fenix A320 LOWK Klagenfurt to LIPZ Venice with a missed approach at LIPB Bolzano in the Italian Alps (yes I know I should not try to land the A320 there...). 

Are you still running your fps unlocked in RTSS and selecting 60 as your target only in AutoFPS?

14 minutes ago, RJC68 said:

Are you still running your fps unlocked in RTSS and selecting 60 as your target only in AutoFPS?

Yes. Unlocked for now so the frame time graph is not completely flat. 

2 minutes ago, Cpt_Piett said:

Yes. Unlocked for now so the frame time graph is not completely flat. 

Thank you,

The only thing about running unlocked is do you not find your GPU pegged close to 100% ?

 

56 minutes ago, Reset XPDR said:

Of note to AutoFPS however is that, as far as I can tell, LS does not actually change the detectable FPS of a game like MSFS, rather it does it's trickery between frames and leaves the FPS reading alone. As such, and correct me if I am wrong, there is nothing for AutoFPS to detect or actually do with LS as you just set your AutoFPS target FPS based on your pre-FG in-game FPS target and be done with it. Am I missing something?

I apologize in advance for summoning @V1ROTA7E, but they seem to have a firm grasp of the intricacies of LS. I'm not sure if they use AutoFPS though.  

Edited September 8, 20241 yr by Cpt_Piett
singular they to conform with current pronoun conventions. Apologies @jordanbpeterson

13 minutes ago, RJC68 said:

Thank you,

The only thing about running unlocked is do you not find your GPU pegged close to 100% ?

 

Not at all. I'm using 4K DLSS+DLAA with no render scaling. Tested over the Alps at FL130, VOR approach to Bolzano and RNAV to Venice,  and avg GPU use is below 79%. 

Edited September 7, 20241 yr by Cpt_Piett

1 minute ago, Cpt_Piett said:

Not at all. I'm using 4K DLSS+DLAA with no render scaling. Tested over the Alps at FL130 and avg GPU use is 70%. 

I know you used to run MSFS with FPS locked using RTSS to 63 and removed that lock so that TLOD Min Extra can do it's thing, but FYI you can still run an FPS cap with that still working as long as your FPS cap still gives you good headroom. eg. If you set an FPS cap of 80 FPS with a target FPS of 60 (ie. 33% headroom) it will still work, but may just take another seeking step to finalise as the first ones may not jump as high as it used to, but it will get there.

The reason I'm telling to this is, as @RJC68says and I have experienced myself, running uncapped FPS can have your GPU running at 100% before AutoFPS does its TLOD increasing thing and you don't have to let that happen by using an FPS cap. It's not a big deal as the time when your GPU may be at 100% is less than a minute, but it will help avoid having your GPU fans ramp up to max for no good reason.