When i set the target lossless scaling fps ex. 142 (beacause i want LS to upgrade my fps to 144) and i set fps sensitivity amount to 1, because i want lod reaction for even one fps lower, then after take off my LOD doesnt increase and stays at minimum (60). It changes when i set my sensitivity to 5 or lower my target fps. It was working before latest msfs update and lossless scaling update. (I tried reinstalling auto fps and reverting to previos version, but even with revert the problem exist. So i waked up today and it wasnt working

Not sure what the reason for the change is, but generally sensitivity of 1 is very low. I’ve never tried below 3, and recently increased to 5 (as I can have a TLOD range as high as 25 to 800).

@Reset XPDR

55 minutes ago, Cpt_Piett said:

Not sure what the reason for the change is, but generally sensitivity of 1 is very low. I’ve never tried below 3, and recently increased to 5 (as I can have a TLOD range as high as 25 to 800).

@Reset XPDR

Even 3 doesnt work with 142fps. I dont know what happened, it was running normally on 142 target and 1 sensitivity and it was normal. Today it started to not work. 

Although, when i dont use lossless scaling and lock my fps to 72 (set target fps to 69 and sensitivity 1) works normally, so the problem seems to be connected with lossless scaling. 

I wanted to contact the creator of auto FPS but i dont know how tbh

If you scroll down this forum you will find a thread titled MSFS 2020 Auto FPS App.

Reset XPDR is the developer for this product and follows this thread.

@FelipeThePilot Also make sure you have the latest version https://github.com/ResetXPDR/MSFS2020_AutoFPS/releases/tag/v0.4.3.1

13 hours ago, FelipeThePilot said:

When i set the target lossless scaling fps ex. 142 (beacause i want LS to upgrade my fps to 144) and i set fps sensitivity amount to 1, because i want lod reaction for even one fps lower, then after take off my LOD doesnt increase and stays at minimum (60). It changes when i set my sensitivity to 5 or lower my target fps. It was working before latest msfs update and lossless scaling update. (I tried reinstalling auto fps and reverting to previos version, but even with revert the problem exist. So i waked up today and it wasnt working

 

11 hours ago, FelipeThePilot said:

Even 3 doesnt work with 142fps. I dont know what happened, it was running normally on 142 target and 1 sensitivity and it was normal. Today it started to not work. 

Although, when i dont use lossless scaling and lock my fps to 72 (set target fps to 69 and sensitivity 1) works normally, so the problem seems to be connected with lossless scaling. 

I wanted to contact the creator of auto FPS but i dont know how tbh

I saw your message on github, which disappeared by the time I got to respond to it. I am away on vacation for the next week and my internet access is infrequent.

In any case, there is nothing particularly magical about how lossless scaling is supported by the app. It just scales up the FPS it is reading directly from MSFS by the lossless scaling multiplier it detects, which is why you now need to set your target FPS to what FPS you are expecting AFTER lossless scaling had done its thing, ie. 144 FPS in your case.

And using a sensitivity of 1 with a target FPS as high as 144 is pushing the app beyond the bounds of what a system is really capable of, especially when using frame generation of any form because 1 FPS is actually really 0.5 FPS without frame generation and it is not possible to achieve such a tight FPS tolerance on any system.

BTW, if you say that you now have the same issue with the previous version of AutoFPS when it worked fine before, then I can say quite confidently that AutoFPS is not the issue and it is something else you have done to your setup recently.

If you want further help on this, please ask on my github issue page here instead of Avsim as I don't wish to clog this forum up with support issues that have a more appropriate place to be dealt with. Please also supply screenshots and log files there as I am having trouble grasping what the actual issue is.

Oh and be patient. I am on vacation! Thanks.

 

Edited October 4, 20241 yr by Reset XPDR

4 minutes ago, Reset XPDR said:

 

I saw your message on github but I am away on vacation for the next week and my internet access is infrequent.

In any case, there is nothing particularly magical about how lossless scaling is supported by the app. It just scales up the FPS it is reading directly from MSFS by the lossless scaling multiplier it detects, which is why you now need to set your target FPS to what FPS you are expecting AFTER lossless scaling had done its thing, ie. 144 FPS in your case.

And using a sensitivity of 1 with a target FPS as high as 144 is pushing the app beyond the bounds of what a system is really capable of, especially when using frame generation of any form because 1 FPS is actually really 0.5 FPS without frame generation and it is not possible to achieve such a tight FPS tolerance on any system.

BTW, if you say that you now have the same issue with the previous version of AutoFPS when it worked fine before, then I can say quite confidently that AutoFPS is not the issue and it is something else you have done to your setup recently.

 

 

Ye, I think the problem may be something else, because the sensitivity 1 is working with frames locked to 72 and target fps 69 (without frame gen).

So the problem may be with frame gen, but I am trying to figure out why it suddenly stoped working. All I did was gpu software update and 24h2 windows update.

17 minutes ago, Reset XPDR said:

 

I saw your message on github, which disappeared by the time I got to respond to it. I am away on vacation for the next week and my internet access is infrequent.

In any case, there is nothing particularly magical about how lossless scaling is supported by the app. It just scales up the FPS it is reading directly from MSFS by the lossless scaling multiplier it detects, which is why you now need to set your target FPS to what FPS you are expecting AFTER lossless scaling had done its thing, ie. 144 FPS in your case.

And using a sensitivity of 1 with a target FPS as high as 144 is pushing the app beyond the bounds of what a system is really capable of, especially when using frame generation of any form because 1 FPS is actually really 0.5 FPS without frame generation and it is not possible to achieve such a tight FPS tolerance on any system.

BTW, if you say that you now have the same issue with the previous version of AutoFPS when it worked fine before, then I can say quite confidently that AutoFPS is not the issue and it is something else you have done to your setup recently.

If you want further help on this, please ask on my github issue page here instead of Avsim as I don't wish to clog this forum up with support issues that have a more appropriate place to be dealt with. Please also supply screenshots and log files there as I am having trouble grasping what the actual issue is.

Oh and be patient. I am on vacation! Thanks.

 

Okey, thx, so I will reach out