4 hours ago, rutrA said:

The only thing I noticed after the new update is that AutoFPS does not detect the enabled FG, only after restarting the SIM it returns to normal.

I've just noticed this as well. 0.4.4.6-test4 version. I tried the reset button, but noticed that its not "detecting" the FG. Other than that everything seems normal though.

https://ibb.co/5gmPNQ5R

5 hours ago, KERNEL32 said:

I've just noticed this as well. 0.4.4.6-test4 version. I tried the reset button, but noticed that its not "detecting" the FG. Other than that everything seems normal though.

https://ibb.co/5gmPNQ5R

I can reproduce this and will look into it.

6 hours ago, KERNEL32 said:

I've just noticed this as well. 0.4.4.6-test4 version. I tried the reset button, but noticed that its not "detecting" the FG. Other than that everything seems normal though.

https://ibb.co/5gmPNQ5R

I think I've found and fixed it. Please update to test 7 and let me know how it goes. And my apologies to @rutrA as it looks like this really was an issue!

Edited February 15, 20251 yr by Reset XPDR

1 hour ago, Reset XPDR said:

I think I've found and fixed it. Please update to test 7 and let me know how it goes

Updated to test 7, "FG Active" all good now! Thank you!! 😁

Link ? my app says I have latest 0.4.4.5 - thanks much 

45 minutes ago, Richard Sennett said:

Link ? my app says I have latest 0.4.4.5 - thanks much 

This is still a test version, hence no notification of an update for you. If you want to participate in the test phase of the new auto update feature, go here. I am about to drop another test version (8) in the next 30 minutes, so if you want to install test7 first you can get to see how the auto update process works when I do.

Is the FG issue also seen in 4.4.5 as I set the Target to 40 and it runs at 80+ Nice that it runs at 80+ but would like to increase the detail...  Yup if I change the target to 20 it runs at 40-50... this is actually a nice surprise....

Edited February 16, 20251 yr by Jerryyyyy

12 minutes ago, Jerryyyyy said:

Is the FG issue also seen in 4.4.5 as I set the Target to 40 and it runs at 80+ Nice that it runs at 80+ but would like to increase the detail...  Yup if I change the target to 20 it runs at 40-50... this is actually a nice surprise....

No, the FG issue was inadvertently introduced in 0.4.4.6-test but has since been rectified. 0.4.4.5 should be behaving correctly with FG detection, which still requires the Reset button to be clicked if you enable FG after starting a flight session with the app already running.

Thanks much I like updates 🙂 

On 2/14/2025 at 9:54 PM, Reset XPDR said:

I just tried installing with the fsuipc autostart option and the app started up fine just after fsuipc loaded for both MSFS 2020 and 2024. Are you running at least the latest release version 0.4.4.5 and did you see the successfully added message when you ran the installer like this?

yes i have the succesfully message at the end of installation but the proigram doesn't strat automatically when fsuipc is started

2 minutes ago, motishow said:

yes i have the succesfully message at the end of installation but the proigram doesn't strat automatically when fsuipc is started

Please message me the contents of your fsuipc.ini file, located in the fsuipc install directory, and I'll take a look. In the interim, after you've sent me the fsuipc.ini file contents, try the start with MSFS install option, which basically does the same thing.

On 2/14/2025 at 8:31 PM, Reset XPDR said:

There is already this option, per my initial reply to you:

The thing is, buddy, this is not the answer because it solves one issue and creates another. If I use Auto TLOD with the + additional unchecked then it will indeed force the TLOD Base below ALT TLOD Base and that is great but then it creates a new problem when flying and that is that I have to have my TLOD Top set so low that everything looks ugly all the time because I may fly over an area such as London or New york. That means that most of my flight looks poorer than it needs to in order to have the headroom to fly over London without it turning into a slide show. 

FPS Cap mode gets rid of this problem because it's changing things on the fly according to what it sees my FPS doing. That means I can set it up so that it looks great when it can and drops it when it has to such as high demand areas and this works very well for me generally speaking when flying. It really impresses me. The trouble is that it doesn't seem to work well on the ground at the start of the flight and as I have said. It consistantly tries to push this far too far and after a min of it working it out I'm left with a figure far too high and this goes on and on until it eventually realises that it's wrong and drops it to the TLOD Base level anyway. This can take forever and normally is still going on during the preflight, start up and taxi and the entire time I have erratic FPS which is an immersion killer.

The Auto TLOD mode has the checkbox '+ additional TLOD with good performance conditions'. What I'm suggesting is that we have a similar checkbox in FPS Cap mode that allows us to force it to always use TLOD Base below ALT TLOD Base. I'm fine with it being erratic for a minute while it does what it does but it needs to settle at my TLOD Base and not try to push this until  I get above the threshold of Alt TLOD Base when it can go about it's adjustments to maximise the visuals without dropping the frame rate. If we had that option in that mode it would be the perfect mode as far as I can see. Is there any technical reason that this cannot be achieved?

I believe that @rjack1282 is seeing the same problem as me and has suggested this or something very similar as a way to remove the problem.

Anyway, it's your baby and I hope you are taking what I'm saying in the way I am intending it and not as a criticism. I think it's a great piece of work and I'm just trying to help you make it better and make my flying experience better.

 

 

Hi,

I too have moved from AutoTLOD to FPS Cap and the settings seem very sensitive.  This Sunday AM I flew three flights from Reno NV to SFO to fine tune settings.  This is my home turf so I know what the visuals should look like. 

I have a 3070Ti and a Ryzen 7950. 

I started with FPS set at 40 and got stutters on the Runway in Reno and for some reason TLOD went to 300.  Normally is 100 on runway.  At cruise the FPS was fine and the TLOD went up to 500.  Problem was descent and landing the 500TLOD did not dissipate and was near 300 on landing with stutters. 

Took me two iterations but I increased the FPS set to 50 thinking this might not allow me to go to the excessive 500 TLOD at cruise.  I also increased the LOD step to 10 then 15 without problems so get a faster drop on landing. 

I also decreased the Alt TLOS Base to 100 as I had not seen stutters at low altitudes and this game me a longer time to get to a tolerable 100 TLOD on landing to avoid stutters. 

Anyway, these machinations seemed to work with an N of 1 flight. 

I am sending our Fearless Leader the log. 

Best wishes and I enjoy fine tuning this.  I should do the Betas....

Late to the party but updated to test ver 8 and FG Active is working fine now , that's with the FG mod for my RTX3080 in MSFS2024 store version.

Also ran combined with LSFG and it detected that I was in LSFG......if I closed LSFG and hit reset it went back to detecting the the FG mod version.

All seems good now.

Edited February 16, 20251 yr by Chris Boyce

6 hours ago, Jazz said:

The thing is, buddy, this is not the answer because it solves one issue and creates another. If I use Auto TLOD with the + additional unchecked then it will indeed force the TLOD Base below ALT TLOD Base and that is great but then it creates a new problem when flying and that is that I have to have my TLOD Top set so low that everything looks ugly all the time because I may fly over an area such as London or New york. That means that most of my flight looks poorer than it needs to in order to have the headroom to fly over London without it turning into a slide show. 

FPS Cap mode gets rid of this problem because it's changing things on the fly according to what it sees my FPS doing. That means I can set it up so that it looks great when it can and drops it when it has to such as high demand areas and this works very well for me generally speaking when flying. It really impresses me. The trouble is that it doesn't seem to work well on the ground at the start of the flight and as I have said. It consistantly tries to push this far too far and after a min of it working it out I'm left with a figure far too high and this goes on and on until it eventually realises that it's wrong and drops it to the TLOD Base level anyway. This can take forever and normally is still going on during the preflight, start up and taxi and the entire time I have erratic FPS which is an immersion killer.

The Auto TLOD mode has the checkbox '+ additional TLOD with good performance conditions'. What I'm suggesting is that we have a similar checkbox in FPS Cap mode that allows us to force it to always use TLOD Base below ALT TLOD Base. I'm fine with it being erratic for a minute while it does what it does but it needs to settle at my TLOD Base and not try to push this until  I get above the threshold of Alt TLOD Base when it can go about it's adjustments to maximise the visuals without dropping the frame rate. If we had that option in that mode it would be the perfect mode as far as I can see. Is there any technical reason that this cannot be achieved?

I believe that @rjack1282 is seeing the same problem as me and has suggested this or something very similar as a way to remove the problem.

Anyway, it's your baby and I hope you are taking what I'm saying in the way I am intending it and not as a criticism. I think it's a great piece of work and I'm just trying to help you make it better and make my flying experience better.

 

 

Thanks for you and @Jerryyyyymaking the issue clearer. While I personally do not experience such ongoing adjustments on the ground, I can see how it would be annoying if you do. I normally do not add anything to the already busy UI, but since FPS Cap mode actually removes two check boxes compared to Auto TLOD (TLOD Base + and TLOD Top +), the required real estate to put in an 'in the air only' option for FPS cap is available so I will have a go at implementing what you two and @rjack1282 and @Cpt_Piettare requesting.

Just to make it absolutely clear, you want an option to only apply TLOD Base + when above Alt TLOD Base and upon descent to be locked at TLOD Base by the time you cross back below it?

I will also look at modifying Hr+ so that it imposes even greater headroom and caps the maximum amount that TLOD Base + can settle at to be a lower value than it currently calculates to be so that those who still wish to use TLOD Base + on the ground may still do so in challenging environments with a much lower chance of downward adjustment following the initial seeking and setting of TLOD Base +.

 

Edited February 16, 20251 yr by Reset XPDR