9 hours ago, xsever said:

Winner winner, chicken dinner! This did it. Thank you so much. I will start with 30 and then experiment with 35 and 40 maybe later on and then using adaptive mode in lossless scaling to go to 60.

I noticed in your screenshot that you're not running the latest version of profile inspector so I thought I'd flag that out to you.

Thank you again!

Any idea why the in-sim v-sync and frame limit options don't work for us?

I've had issues with using v-sync to lock fps on other games whether inside the game or using v-sync in NPI.I don't know the reason why those options don't work for myself, but locking it using the Frame Rate Limiter in NPI works really good.

I've tried a newer version of NPI about a month ago and will download the latest version and test that. Thanks for the tip!

4 hours ago, Reset XPDR said:

I hope this alleviates @FakeWayne's rightful concern that Fixed is too aggressive on the down swings and decides to give it another go in 0.4.6.8-Test16 which has now been released. I would also appreciate if others could give Fixed Target FPS a go and provide feedback, either good or bad, as it all helps make it better.

Just tried the new test version and yes, it's certainly better (less aggressive) in my opinion.  I will do a bit more testing in the morning and provide some more feedback.  Thanks for this!

I have a question. I start RTSS prior to starting autoFPS, and I have a framerate limit set in RTSS. But every time autoFPS starts, it indicates that it is getting its FPS from the sim and not from RTSS. I thought if you had RTSS open autoFPS would get it from there.

What am I missing here in my understanding?

Thanks.

Edited April 22Apr 22 by Rob G
Additional info

16 minutes ago, Rob G said:

I have a question. I start RTSS prior to starting autoFPS, and I have a framerate limit set in RTSS. But every time autoFPS starts, it indicates that it is getting its FPS from the sim and not from RTSS. I thought if you had RTSS open autoFPS would get it from there.

What am I missing here in my understanding?

Thanks.

Just click on the FS icon to the immediate right of the FPS value and it should change to RTSS. It will stay that way for future startups, unless you don't have RTSS running beforehand, in which case it auto switches to MSFS as the source and stays that way until you click it again. If you have RTSS auto load when windows starts, this setting will always stick.

33 minutes ago, Reset XPDR said:

Just click on the FS icon to the immediate right of the FPS value and it should change to RTSS. It will stay that way for future startups, unless you don't have RTSS running beforehand, in which case it auto switches to MSFS as the source and stays that way until you click it again. If you have RTSS auto load when windows starts, this setting will always stick.

Thanks much!

I am not up to date with this thread over the past week or two and generally test updates work without issues, or changing things, but my flight tonight using 0.4.6.8-test 17 showed problems.

I was previously using the IFR 'Flight Type' and had frame rate set to 120 since my sim rate is 30 and using a 4x MFG on the 5090. Had Auto Method set to FPS Cap TLOD Base min is 50@1000 ft and extra x1.5 was selected. TLOD Top Max is 400@5000ft and extra 2x.  Worked fine before and TLOD went to 400 or greater above 5000 ft.  New test gave me some popup about FPS Sensitivity new prefered mode, app auto changed to this. I see Extra 2x not available under Sensitivity method. I did a flight there from EGAA to EGPH, short flight cruise at 19000 feet YET max TLOD went to was 75 (50x1.5), it refused to see I was above 5000 feet so the 400 never kicked in.  Ground textures were blurry.

I do struggle to understand the various modes and how certain things are enabled or disabled or their impact with each other.  Also the FPS to be set, should it be less than the 120 my sim generally generates and is locked at?   Will being lower allow TLOD to utilise the extra and go higher like old way with the Cap method?  I guess I will need to re-read the huge readme.  Sorry I just cant get my head round all the variables.

 

37 minutes ago, cj-ibbotson said:

I am not up to date with this thread over the past week or two and generally test updates work without issues, or changing things, but my flight tonight using 0.4.6.8-test 17 showed problems.

I was previously using the IFR 'Flight Type' and had frame rate set to 120 since my sim rate is 30 and using a 4x MFG on the 5090. Had Auto Method set to FPS Cap TLOD Base min is 50@1000 ft and extra x1.5 was selected. TLOD Top Max is 400@5000ft and extra 2x.  Worked fine before and TLOD went to 400 or greater above 5000 ft.  New test gave me some popup about FPS Sensitivity new prefered mode, app auto changed to this. I see Extra 2x not available under Sensitivity method. I did a flight there from EGAA to EGPH, short flight cruise at 19000 feet YET max TLOD went to was 75 (50x1.5), it refused to see I was above 5000 feet so the 400 never kicked in.  Ground textures were blurry.

I do struggle to understand the various modes and how certain things are enabled or disabled or their impact with each other.  Also the FPS to be set, should it be less than the 120 my sim generally generates and is locked at?   Will being lower allow TLOD to utilise the extra and go higher like old way with the Cap method?  I guess I will need to re-read the huge readme.  Sorry I just cant get my head round all the variables.

 

Re new modes being potentially confusing for now, yes this will be the case when converting over but once FPS Cap mode is eventually removed these changes will provide more consistent terminology between the modes. eg. with TLOD Top, all modes with have TLOD Top Max, as FPS Cap with its TLOD Top Min and locked multiplier will be gone. The auto conversion should have set TLOD Top Max to TLOD Top Min X the Top multiplier for equivalency.

I have to go out for a few hours, so will not be able to look into this or answer your other questions until I am back. In preparation, can you PM me the contents of your log file, located %appdata%\MSFS_AutoFPS\log, associated with this happening and I will take a look, particularly as to why your TLOD refused to scale up on the flight you mention. Thanks.

Edited April 22Apr 22 by Reset XPDR

7 hours ago, cj-ibbotson said:

I am not up to date with this thread over the past week or two and generally test updates work without issues, or changing things, but my flight tonight using 0.4.6.8-test 17 showed problems.

I was previously using the IFR 'Flight Type' and had frame rate set to 120 since my sim rate is 30 and using a 4x MFG on the 5090. Had Auto Method set to FPS Cap TLOD Base min is 50@1000 ft and extra x1.5 was selected. TLOD Top Max is 400@5000ft and extra 2x.  Worked fine before and TLOD went to 400 or greater above 5000 ft.  New test gave me some popup about FPS Sensitivity new prefered mode, app auto changed to this. I see Extra 2x not available under Sensitivity method. I did a flight there from EGAA to EGPH, short flight cruise at 19000 feet YET max TLOD went to was 75 (50x1.5), it refused to see I was above 5000 feet so the 400 never kicked in.  Ground textures were blurry.

I do struggle to understand the various modes and how certain things are enabled or disabled or their impact with each other.  Also the FPS to be set, should it be less than the 120 my sim generally generates and is locked at?   Will being lower allow TLOD to utilise the extra and go higher like old way with the Cap method?  I guess I will need to re-read the huge readme.  Sorry I just cant get my head round all the variables.

 

Never mind sending the log file, as I am able to reproduce with your stated post-migration settings on my dev system, so I will work on a fix. Thanks for letting me know about the issue!

12 hours ago, cj-ibbotson said:

I am not up to date with this thread over the past week or two and generally test updates work without issues, or changing things, but my flight tonight using 0.4.6.8-test 17 showed problems.

I was previously using the IFR 'Flight Type' and had frame rate set to 120 since my sim rate is 30 and using a 4x MFG on the 5090. Had Auto Method set to FPS Cap TLOD Base min is 50@1000 ft and extra x1.5 was selected. TLOD Top Max is 400@5000ft and extra 2x.  Worked fine before and TLOD went to 400 or greater above 5000 ft.  New test gave me some popup about FPS Sensitivity new prefered mode, app auto changed to this. I see Extra 2x not available under Sensitivity method. I did a flight there from EGAA to EGPH, short flight cruise at 19000 feet YET max TLOD went to was 75 (50x1.5), it refused to see I was above 5000 feet so the 400 never kicked in.  Ground textures were blurry.

I do struggle to understand the various modes and how certain things are enabled or disabled or their impact with each other.  Also the FPS to be set, should it be less than the 120 my sim generally generates and is locked at?   Will being lower allow TLOD to utilise the extra and go higher like old way with the Cap method?  I guess I will need to re-read the huge readme.  Sorry I just cant get my head round all the variables.

 

I have now found and fixed the issue you were experiencing in Test18. eg. with your settings and MFG complements of the DLSS Enabler mod:

I had made a late breaking change to Test17 to fix FreeTLOD just before I released it and even though I had tested the other modes, I had only done so on the ground, so the issue that you found was not caught by my test net. Lesson learnt, so I have tested Test18 in all TLOD Extra modes at all altitude thresholds and with each Target FPS type and it seems to be behaving itself well now.

I should also note to you, and any other (M)FG users out there, that there is also a change in FPS Sensitivity and Tolerance modes where when MSFS is no longer the active window and (M)FG becomes inactive, the app will no longer allow TLOD and Cloud Quality increases and you will see the FPS and TLOD values be shown in orange. This is consistent with FPS Cap mode and is done so because the performance conditions when FG is inactive are too favourable compared to how they will be when FG comes back on, so it is prudent to not allow the app to react to such unrealistic favourable performance. As such, please don't be surprised when TLOD in particular stops increasing if you move away from MSFS and be assured it will resume when MSFS gets the focus again.

Re what FPS setting to use in FPS Sensitivity mode if you were using FPS Cap mode with an FPS cap set before like you have been, the auto settings the app has chosen for you will be correct, which is to use Fixed Target FPS and to set it to the 120 FPS you previous had it set to in FPS Cap mode.  Previous app versions would not have worked set this way, and you would have needed to set a Target FPS lower than the FPS cap, but the new Fixed mode is specifically designed to have them match and does does away with the TLOD/Altitude schedule and Max Extra overheads that FPS Cap required because of the way it was built on AutoTLOD mode. In short, stay with Fixed and 120 FPS as your target.

Once I get the kinks ironed out, as I hope we are close to doing in this test phase, and release 0.4.6.8, this paves the way to retire FPS Cap mode and to make FPS Tolerance mode legacy only (ie. you can only use it if you already had it enabled, otherwise it will not be available to set), thus simplifying the app to two distinct modes - FPS Sensitivity (the core AutoFPS experience) and AutoTLOD (the DynamicLOD-like experience).

You can get Test18 in the usual place here. Please continue to report any issues.

Edited April 23Apr 23 by Reset XPDR

@Reset XPDR

After a few months of cockpit building I am now adjusting the settings in MSFS 24 to get a good quality view and still have a smooth sim.

As I now use a Triple screen setup, even with a 5950x3d running @5.5 GHz , the Render Thread is the bottleneck.

So I started AutoFPS and till my surprise the load on the Render Thread increased from around 26 to 35-38. So the total framerate dropped. I waited till the FPS were settled.

Closing AutoFPs and the load dropped till 26-27 again and the framerate went up.

I have tried with DLDS and FSR3

Any idea what is going on here ?

 

 

 

 

 

Edited April 23Apr 23 by GSalden

15 minutes ago, GSalden said:

@Reset XPDR

After a few months of cockpit building I am now adjusting the settings in MSFS 24 to get a good quality view and still have a smooth sim.

As I now use a Triple screen setup, even with a 5950x3d running @5.5 GHz , the Render Thread is the bottleneck.

So I started AutoFPS and till my surprise the load on the Render Thread increased from around 26 to 35-38. So the total framerate dropped. I waited till the FPS were settled.

Closing AutoFPs and the load dropped till 26-27 again and the framerate went up.

I have tried with DLDS and FSR3

Any idea what is going on here ?

 

 

 

 

 

My first instinct was that your AutoFPS set TLOD is greater than your MSFS default, but it is doing it at TLOD 25 which I seriously doubt is higher than your MSFS default, especially with your high system specs!

I will try and recreate tomorrow when I am back at my dev PC, but in the interim try unchecking the MSFS performance optimiser option and see if that recovers it. 

Edit: That seems pretty low performance for such hefty hardware, even if AutoFPS is contributing (although excluding the perf option, at a TLOD 25 floor AutoFPS would not be interacting with MSFS much at all, possibly not at all). What FPS do you get without AutoFPS and at what default TLOD?

Edited April 23Apr 23 by Reset XPDR

11 minutes ago, Reset XPDR said:

My first instinct was that your AutoFPS set TLOD is greater than your MSFS default, but it is doing it at TLOD 25 which I seriously doubt is higher than your MSFS default, especially with your high system specs!

I will try and recreate tomorrow when I am back at my dev PC, but in the interim try unchecking the MSFS performance optimiser option and see if that recovers it. 

Edit: That seems pretty low performance for such hefty hardware, even if AutoFPS is contributing (although excluding the perf option, at a TLOD 25 floor AutoFPS would not be interacting with MSFS much at all, possibly not at all). What FPS do you get without AutoFPS and at what default TLOD?

The Lower Lower framerate is caused by 40+ parked and moving AC in Realtime using PSXT.

One screen 70+ 

Two screens 38 / 35 AutoFPS

Three screens 29 / 27 AutoFPS

Default test tLOD = 150

So with 150 I am heffing higher FPS and lower Render Thread load than with AutoFPS with tLOD at 25.

 

2 hours ago, Reset XPDR said:

I have now found and fixed the issue you were experiencing in Test18. eg. with your settings and MFG complements of the DLSS Enabler mod:

I had made a late breaking change to Test17 to fix FreeTLOD just before I released it and even though I had tested the other modes, I had only done so on the ground, so the issue that you found was not caught by my test net. Lesson learnt, so I have tested Test18 in all TLOD Extra modes at all altitude thresholds and with each Target FPS type and it seems to be behaving itself well now.

I should also note to you, and any other (M)FG users out there, that there is also a change in FPS Sensitivity and Tolerance modes where when MSFS is no longer the active window and (M)FG becomes inactive, the app will no longer allow TLOD and Cloud Quality increases and you will see the FPS and TLOD values be shown in orange. This is consistent with FPS Cap mode and is done so because the performance conditions when FG is inactive are too favourable compared to how they will be when FG comes back on, so it is prudent to not allow the app to react to such unrealistic favourable performance. As such, please don't be surprised when TLOD in particular stops increasing if you move away from MSFS and be assured it will resume when MSFS gets the focus again.

Re what FPS setting to use in FPS Sensitivity mode if you were using FPS Cap mode with an FPS cap set before like you have been, the auto settings the app has chosen for you will be correct, which is to use Fixed Target FPS and to set it to the 120 FPS you previous had it set to in FPS Cap mode.  Previous app versions would not have worked set this way, and you would have needed to set a Target FPS lower than the FPS cap, but the new Fixed mode is specifically designed to have them match and does does away with the TLOD/Altitude schedule and Max Extra overheads that FPS Cap required because of the way it was built on AutoTLOD mode. In short, stay with Fixed and 120 FPS as your target.

Once I get the kinks ironed out, as I hope we are close to doing in this test phase, and release 0.4.6.8, this paves the way to retire FPS Cap mode and to make FPS Tolerance mode legacy only (ie. you can only use it if you already had it enabled, otherwise it will not be available to set), thus simplifying the app to two distinct modes - FPS Sensitivity (the core AutoFPS experience) and AutoTLOD (the DynamicLOD-like experience).

You can get Test18 in the usual place here. Please continue to report any issues.

Thanks for your in depth look into this.  I do appreciate it.  Please note I am not one for analysing performance data or stats etc in Development Mode.  If the sim looks and performs well I am happy.

I do struggle when there are too many variables as I loose focus on what is causing a positive or negative effect on fps or tlod etc.  Since reporting my experience I decided to reset all the settings back to default using the installer. I only used FPS Sensitivity Auto Method since you are phasing out the FPS Cap mode.

I had my Fenix A320 and simply slewed up and down to different altitudes and monitored Autofps which keeping MSFS 2024 window active (I have 2 screens).  What I did find was I couldnt find patterns, which is key to understanding anything in life. Under General if I selected fixed and fps set to 120 TLOD would peak at 100 not 200 as set under "tlod top max". In order for TLOD to go up to 200 I need to change to manual and select 115 fps, selecting 120 fps and tlod doesnt change. I will try test 18, thanks.  BTW in your screens above you seem to have Dynamic Settings enable "DTLOD", I do not use that in the sim.

Edited April 23Apr 23 by cj-ibbotson

43 minutes ago, cj-ibbotson said:

Thanks for your in depth look into this.  I do appreciate it.  Please note I am not one for analysing performance data or stats etc in Development Mode.  If the sim looks and performs well I am happy.

I do struggle when there are too many variables as I loose focus on what is causing a positive or negative effect on fps or tlod etc.  Since reporting my experience I decided to reset all the settings back to default using the installer. I only used FPS Sensitivity Auto Method since you are phasing out the FPS Cap mode.

I had my Fenix A320 and simply slewed up and down to different altitudes and monitored Autofps which keeping MSFS 2024 window active (I have 2 screens).  What I did find was I couldnt find patterns, which is key to understanding anything in life. Under General if I selected fixed and fps set to 120 TLOD would peak at 100 not 200 as set under "tlod top max". In order for TLOD to go up to 200 I need to change to manual and select 115 fps, selecting 120 fps and tlod doesnt change. I will try test 18, thanks.  BTW in your screens above you seem to have Dynamic Settings enable "DTLOD", I do not use that in the sim.

When I get a few more ripples sorted out, the app will soon auto correct for you if you have a Fixed FPS cap like you do and have set the target FPS lower, because leaving it set like that will skew the automation to be too generous with TLOD increases, potentially resulting in your Fixed FPS being compromised, which is contradictory to the term Fixed. As suggested, with Test18 if you set Fixed Target FG FPS to 120 it will automate correctly.

Re DTLOD, that is because I have MSFS dynamic settings enabled and set to my native target frame rate of 40 FPS, the same as I have set for MSFS max frame ratet . Even prior to 0.4.6.8, the app works very well when all three of these are set the same.

Edited April 23Apr 23 by Reset XPDR

1 hour ago, GSalden said:

The Lower Lower framerate is caused by 40+ parked and moving AC in Realtime using PSXT.

One screen 70+ 

Two screens 38 / 35 AutoFPS

Three screens 29 / 27 AutoFPS

Default test tLOD = 150

So with 150 I am heffing higher FPS and lower Render Thread load than with AutoFPS with tLOD at 25.

 

I see in your video what you are saying. I note that you still have MSFS performance optimiser enabled, so as mentioned previously it could be the cause. Try running AutoFPS without that enabled.

FYI, I just tried the same thing on my gaming laptop, and with AutoFPS running I get a render time of around 13ms at TLOD 25, 14ms at TLOD 50 and 15 ms at TLOD 100. Without AutoFPS, I get around 14ms at default TLOD 50. ie. The results are the same at the same TLOD and scale slightly up and down correspondingly, indicating there is no impact of running AutoFPS.

I will try the same test on my dev PC when I am at it tomorrow morning.