@Reset XPDR

mis it correct that AutoTarget FPS or Target FPS are now only visible in Non Expert mode ? Or do I have an issue on my end ?

I could not find them tillI disabled Expert Mode. And I always use Expert Mode.

 

 

3 hours ago, GSalden said:

@Reset XPDR

mis it correct that AutoTarget FPS or Target FPS are now only visible in Non Expert mode ? Or do I have an issue on my end ?

I could not find them tillI disabled Expert Mode. And I always use Expert Mode.

 

 

Target FPS and/or Auto target FPS will be present when they need to be and absent when not applicable and should behave the same as they always have for FPS Sensitivity, Tolerance and Auto TLOD modes since Oct 24.

The new FPS Cap mode is just Auto TLOD with TLOD Base + checked, so it will look and behave the same as Auto TLOD does when configured that way.

Post a screenshot if this is not the case with what you used to have set in expert mode.

Edited January 18, 20251 yr by Reset XPDR
simplified

9 hours ago, Reset XPDR said:

Target FPS and/or Auto target FPS will be present when they need to be and absent when not applicable and should behave the same as they always have for FPS Sensitivity, Tolerance and Auto TLOD modes since Oct 24.

The new FPS Cap mode is just Auto TLOD with TLOD Base + checked, so it will look and behave the same as Auto TLOD does when configured that way.

Post a screenshot if this is not the case with what you used to have set in expert mode.

Expert mode : no Target PC FPS or Auto Target FPS in the gui 

Non Expert mode : they are there 

 

Earlier version : they exist in Expert mode :

 

Edited January 18, 20251 yr by GSalden

17 minutes ago, GSalden said:

Expert mode : no Target PC FPS or Auto Target FPS in the gui 

Non Expert mode : they are there 

 

Earlier version : they exist in Expert mode :

 

Your first screenshot should not look like that as it should have Target FPS but no Auto Target FPS in FPS Cap mode mode like this, so something has gone wrong:

Try rerunning the 0.4.4.3 installer and select the clean install option and tell me if it fixes it.

 

3 minutes ago, Reset XPDR said:

Your first screenshot should not look like that as it should have Target FPS but no Auto Target FPS in FPS Cap mode mode like this, so something has gone wrong:

Try rerunning the 0.4.4.3 installer and select the clean install option and tell me if it fixes it.

 

Thank you.  I was encountering the same or similar discrepancy, was reading and re-reading previous guidance, and scratching my head.  Clean install cured it.

2 minutes ago, Reset XPDR said:

Your first screenshot should not look like that as it should have Target FPS but no Auto Target FPS in FPS Cap mode mode like this, so something has gone wrong:

Try rerunning the 0.4.4.3 installer and select the clean install option and tell me if it fixes it.

 

Will do that tomorrow morning and report back.

Normally I first uninstall the older version of the app and then install the new version.

This time I just choose Update.

18 minutes ago, GSalden said:

Will do that tomorrow morning and report back.

Normally I first uninstall the older version of the app and then install the new version.

This time I just choose Update.

I just looked into it some more and it seems it is possible to trigger this if the existing settings before updating are set a certain way.  It can be worked around by just picking another automation mode and going back to it, but that's a bit average to expect users to do so I'll come up with a fix for it.

Edited January 18, 20251 yr by Reset XPDR

1 hour ago, GSalden said:

Will do that tomorrow morning and report back.

Normally I first uninstall the older version of the app and then install the new version.

This time I just choose Update.

I believe I have fixed it. Since you have the issue right now, can I get you to NOT uninstall nor clean install 0.4.4.3 like I suggested and instead download and install 0.4.4.4-test2 available here and do NOT check the clean install option, then tell me if it is working correctly when you start the app. If you uninstall or clean install you will not be able to test this properly as clean installs worked fine with the current 0.4.4.3, so please make sure you don't do either of these for this specific test.

If you confirm this now works correctly, I will roll out 0.4.4.4 formally with this fix in it as I think it is important to get it out there as soon as possible.

BTW, you still will not see the Auto Target FPS checkbox in FPS Cap as it is not applicable in this mode because you have specifically chosen this mode meaning you are the one who needs to enter the target FPS, not the app doing it automatically. In FPS Sensitivity and Tolerance modes you will see both the Target FPS and Auto Target FPS checkboxes.

 

Edited January 18, 20251 yr by Reset XPDR

@Reset XPDR

The link is pointing me to GitHub where it says that I need an account, which I do not have.

All other updates I could DL without an account.

- - 

However, I was able to solve the issue by re-updating ( not renoving ) the app with the same Installer.

Now both view pc’s have the App working correctly.

Edited January 19, 20251 yr by GSalden

Last night I was flying over PNW with the Norden and I can only say: one the smoothest flight I ever enjoyed in this last FS gen. Look at these figures:
 

What kind of witchcraft is this?!!! OMG! TLOD 500 and 60 frames with a humble 3070.

Obviously, that moment happened in a pretty flat area (over Kelso, OR, IIRC). In the Mount Rainier area, the TLOD goes down to 100-150 while keeping 60fps, because the VRAM gets up to 97-98%. Anyway, it was a really smooth flight. What an enjoyable experience!

Quick update: I forgot to mention that all these values are based on 1440p resolution with the texture resolution on low (I don’t really notice much difference with medium). 1080p would give better data, but I recently switched to a 1440p monitor.

Edited January 19, 20251 yr by Maddormo

Even after studying the readme carefully, there is still one question open for me:

When using the Non-Expert-Mode: Which Auto-Method will the program use? Or do I have to first switch to Expert-Mode, select the corresponding Auto-Method e.g. FPS Cap and then swich back to Non-Expert-Mode?

For me it seems LSFG is not correct detected. If i use it, AutoFPS only shows LSFG without modifier (2x/3x).

Was the same in past versions. 

 

11 hours ago, GSalden said:

@Reset XPDR

The link is pointing me to GitHub where it says that I need an account, which I do not have.

All other updates I could DL without an account.

- - 

However, I was able to solve the issue by re-updating ( not renoving ) the app with the same Installer.

Now both view pc’s have the App working correctly.

I really wanted you to try the new test version to see if it fixed it for someone currently experiencing the problem but oh well. My bad though as I posted the link to the edit page for that release, not the the actual release itself. I'm glad you got it sorted.

5 hours ago, ohny said:

Even after studying the readme carefully, there is still one question open for me:

When using the Non-Expert-Mode: Which Auto-Method will the program use? Or do I have to first switch to Expert-Mode, select the corresponding Auto-Method e.g. FPS Cap and then swich back to Non-Expert-Mode?

The readme does say under the Expert Settings option section:

• If an FPS cap is automatically detected (ie. the FPS matches the target FPS over a 10 second period at the end of the initial 20 second settling period), non-expert mode will use the FPS Cap TLOD automation method with the following settings:

....

• Otherwise, FPS Senstivity will be used with the following settings:

ie. It will try and see if an FPS cap is present that matches the target FPS you have set and will then use FPS Cap mode, otherwise it will default to FPS Sensitivity mode like it always has. You do not need to go to Expert mode at all.

25 minutes ago, flieger28 said:

For me it seems LSFG is not correct detected. If i use it, AutoFPS only shows LSFG without modifier (2x/3x).

Was the same in past versions. 

 

As long as you are using the latest version of LSFG (with 3.0 support) and if you are using a profile it is named either MSFS2020 or MSFS2024 for each MSFS version respectively, it should work. If you have done both and are still experiencing an issue can you message me the contents of your LSFG settings.xml file, found in %localappdata%\Lossless Scaling and I'll check it out. Thanks.