4 minutes ago, GSalden said:

Any idea when this new (beta)version will be released ?

Here is AutoFPS v0.4.2.17-test for you and anyone to try. As usual feedback on these changes will be appreciated.

Changes since v0.4.2.16:

• Updated MobiFlight Wasm flight install version from 0.7.1 to 1.0.1.
• Updated Dot NET install version from 7.0.14 to 7.0.20.
• Reinstated ability to have free range TLOD automation between TLOD Min and Max at any altitude, including on the ground, following Asobo finally fixing the DX12 ground texture corruption issue in SU15.
  • Enabled by being in either FPS Sensitivity or Tolerance automation methods and entering 0 ft for Alt TLOD Base.
  • On the ground and stopped, the TLOD rate of change is your nominal FPS Sensitivity or Tolerance amount setting.
  • While taxiing or on takeoff/landing roll, the TLOD rate of change is limited to one TLOD per second, to minimise the potential for introducing stutters during these phases.
  • In the air, the TLOD rate of change scales increasingly proportional from the ground up to the altitude that is calculated as usual based on your average rate of descent setting, again to minimise change during critical flight phases.
  • Above this calculated altitude, normal FPS Priority automation logic applies.
  • The app status line has been updated so that when TLOD is enabled on the ground, the status "FPS Priority (Air & Gnd)" is shown, otherwise "FPS Priority (Air only)" is shown.

 

 

 

@Reset XPDR

Many thanks for the update. Will try it tomorrow morning and report back.

7 hours ago, 109Sqn said:

Alternatively, if using Addons Lineker, you can set any exe to run with MSFS, even adding a delayed start if desired.

I did NOT know that, time to get manual reading!

Thanks :D

1 hour ago, sloppysmusic said:

I did NOT know that, time to get manual reading!

Thanks 😄

Very handy feature. I'm not at the PC right now but go to Options in AOL, then second tab IIRC. There you can browse for any programs you want to start with MSFS. You can set an order for them to start and, as I said, set a delay. For example, I have a delay of 2 minutes or so for FSLTL as there's no point in it loading up before I've had time to select an aircraft and set a flight plan.

31 minutes ago, 109Sqn said:

Very handy feature. I'm not at the PC right now but go to Options in AOL, then second tab IIRC. There you can browse for any programs you want to start with MSFS. You can set an order for them to start and, as I said, set a delay. For example, I have a delay of 2 minutes or so for FSLTL as there's no point in it loading up before I've had time to select an aircraft and set a flight plan.

Brilliant! I've wanted to do that for FSTL too. I guess it won't auto press 'N' in the command box too will it? :D

3 hours ago, sloppysmusic said:

I guess it won't auto press 'N' in the command box too will it? 😄

It's good, but it ain't that good. 😄

The again, AOL does keep improving... 😉

16 hours ago, Reset XPDR said:

Also, can someone tell me whether the app works with the lossless scaling app, which I don't have, by showing the correct FPS when it is active or do users just have to factor in a doubling of FPS like they initially had to do before I worked out how to display FG FPS correctly?

It’s showing fps with or without frame gen, before scaling is applied. And AutoFPS seems to work fine with lossless.

4 hours ago, sloppysmusic said:

too. I guess it won't auto press 'N' in the command box too will it?

You can set it to auto in the config.

12 hours ago, Reset XPDR said:

• In the air, the TLOD rate of change scales increasingly proportional from the ground up to the altitude that is calculated as usual based on your average rate of descent setting, again to minimise change during critical flight phases.
• Above this calculated altitude, normal FPS Priority automation logic applies.

Could you tell us a bit more about how the altitude (bold) is calculated. A few other thoughts:

• what could be the benefit of having TLOD change at ground level?
• it’s only possible to specify descent rate, not climb rate
• the descent rate would most likely change e.g. 2000fpm initially then reduce during the approach - how would that affect the TLOD calculations?

I’ve yet to test the latest version.

Edited August 6, 20241 yr by Cpt_Piett

1 hour ago, Cpt_Piett said:

5 hours ago, sloppysmusic said:

too. I guess it won't auto press 'N' in the command box too will it?

You can set it to auto in the config.

Wow, I didn't know this could be done as it has always annoyed me too. I found the config file in my roaming folder and set silent mode to Yes and it works. Thanks!

1 hour ago, Cpt_Piett said:

Could you tell us a bit more about how the altitude (bold) is calculated. A few other thoughts:

• what could be the benefit of having TLOD change at ground level?
• it’s only possible to specify descent rate, not climb rate
• the descent rate would most likely change e.g. 2000fpm initially then reduce during the approach - how would that affect the TLOD calculations?

The benefit of having TLOD change at ground level is that is what the original intent of this app was for VFR flying, where you want to get the best TLOD possible for a given target FPS no matter what phase of flight you are in, including being on the ground. I had to remove this functionality in v0.4.2 because the DX12 ground texture corruption issue was being exacerbated by changing TLOD on the ground, but that is no longer the case so I am reintroducing the feature for those that wanted it in the first place (including me!). It is entirely optional to use it and it can be disabled simply by having an Alt TLOD Base greater than 0 ft.

The altitude is calculated per the readme for FPS priority modes and is to ensure there is enough altitude to descend through for the TLOD to reduce from TLOD max to TLOD min on descent. It is only applicable on descent as that is when FPS priority is normally working towards TLOD Min for landing.

In any case, all that is moot with free range TLOD and I was just using the existing altitude band for testing of this new function. I will be updating the app to change the terminology for this avg descent rate setting when in free range TLOD mode to better reflect what it actually is ie. an altitude below which TLOD changes are gradually tapered off down to the ground to minimise changes on departure and final approach.

 

2 hours ago, Cpt_Piett said:

You can set it to auto in the config

Mind blown. Thanks Cpn! 

19 hours ago, Cpt_Piett said:

You can set it to auto in the config.

What setting is this that can be set?

40 minutes ago, mmcmah said:

What setting is this that can be set?

Go to C:\Users\YOURNAME\AppData\Roaming\fsltl-trafic-injector,

open "fsltl-trafficinjector-config.json"

Edit to say Yes - "silent": "Yes",

Yeah my system is too old I think. I leave it on auto but the TLOD changes are too much and it causes stuttering for me (not trying latest build yet).

I ended up using TLOD setting of FPS Tolerance 1%. I would rather the TLOD go slowly up and down for me.

 

8 hours ago, cj-ibbotson said:

Go to C:\Users\YOURNAME\AppData\Roaming\fsltl-trafic-injector,

open "fsltl-trafficinjector-config.json"

Edit to say Yes - "silent": "Yes",

Thank you - no wonder I didn't know what was being referenced! I don't use FSLTL...

New test version v0.4.2.17-test2 is available to download here.

While I have continued to refine the TLOD changes on the ground functionality in this release, the most important change is what I have done to reduce MSFS memory interaction, particularly when app values are not changing, by as much as 30 times less. In my testing, this has significantly reduced micro stutters that were often occurring every second while this memory interaction was taking place.

Even if you don't care about TLOD changes on the ground (I have received no feedback on this to date, so it is probably not of any interest for most users ), please try out this new test version as you usually run it and let me know if it has improved smoothness on your system too.

Changes since the previous test version are:

• Refined TLOD on ground logic as follows:
  • On initial flight loading, TLOD will increase at 4 times its normal amount every 3 seconds until within range of the target FPS.
  • Once within target FPS range and stationary, TLOD will increase at the normal amount but at double the FPS tolerance to minimise the frequency of TLOD changes in this state.
  • TLOD will not change when moving on the ground except during high acceleration or deceleration when taking off and landing respectively, during which TLOD will reduce 25% once to account to reduced system performance during these taxing flight phases.
  • In the air up to 1000 ft, TLOD will increase at the normal amount but at double the FPS tolerance to minimise the frequency of TLOD changes in this state.
  • Above 1000 ft, TLOD changes will function normally.
• Significantly reduced MSFS memory space interaction when nothing is being changed by the app. The app will no longer poll all monitored settings each second and, excepting VR mode detection, instead will read the initial values then change what is displayed as their value only when the app changes them. This had been done to significantly reduce MSFS memory space interaction by up to 30 times when nothing is being changed by the app which may reduce stutters that frequent interaction may be causing.
• Reduced FPS settle time from 20 to 10 seconds as it was unnecessarily long.

I use 4.2.16, which is for me more stable than .17 test1

.17 gave some strong stuters and freeze at different level of the flight, more during descent, run ms without it gave me better result so return to .16 and i am happy with