7 hours ago, JaseMelbo said:

I'm really confused now.  @GSalden is showing 2.9 on his latest LS, I downloaded mine again yesterday and it shows 2.11???  Anyway, I'll take it that my version is current.  

Jase

Nothing to be confused of. I have downloaded v2.9 and that is the one I use.

Online in Steam there is v2.11.

 

3 hours ago, GSalden said:

Nothing to be confused of. I have downloaded v2.9 and that is the one I use.

Online in Steam there is v2.11.

 

No probs, got it.  So are you on an older version?  Is that right?

Jase

Hello

With rc1, i need to manually change target fg active fps, autofps calculate 60 fps on ground, but when i am at cruise tlod stay at 50, rarement above 110

I did a second flight after set target fg..to 50, tlod stay at 300, my fps stay 58-62 

 

Edited September 17, 20241 yr by grandfred29

7 hours ago, grandfred29 said:

Hello

With rc1, i need to manually change target fg active fps, autofps calculate 60 fps on ground, but when i am at cruise tlod stay at 50, rarement above 110

I did a second flight after set target fg..to 50, tlod stay at 300, my fps stay 58-62 

 

Are you saying that Auto Target FPS picked too high an FPS for the first flight? Nothing has changed with Auto Target FPS functionality since the last formal release 0.4.2.16, so it should be behaving the same in RC1.

In any case, per the readme, if Auto Target FPS sets an inappropriate target FPS, especially because your flight conditions change to make it no longer valid, just uncheck then recheck the option and it will recalculate you a new target FPS.

12 hours ago, Reset XPDR said:

Are you saying that Auto Target FPS picked too high an FPS for the first flight? Nothing has changed with Auto Target FPS functionality since the last formal release 0.4.2.16, so it should be behaving the same in RC1.

In any case, per the readme, if Auto Target FPS sets an inappropriate target FPS, especially because your flight conditions change to make it no longer valid, just uncheck then recheck the option and it will recalculate you a new target FPS.

No it is like with test.13, on ground fps set to 60, tlod is set to 50. But after To tlod stay at 50 during cruise to, because and i don't know with during this flight my fps stay between 58-62, gpu 48/50% and quality cloud reduce to high. 

By changing calculate fps from 60 to 50( manually) tlod during cruise set to 300 instead 50 and cloud to ultra.

3 minutes ago, grandfred29 said:

No it is like with test.13, on ground fps set to 60, tlod is set to 50. But after To tlod stay at 50 during cruise to, because and i don't know with during this flight my fps stay between 58-62, gpu 48/50% and quality cloud reduce to high. 

By changing calculate fps from 60 to 50( manually) tlod during cruise set to 300 instead 50 and cloud to ultra.

It sounds like a target FPS of 60 is simply too much for your system to attain with a TLOD any higher than 50, even causing your cloud quality reduce as a result. When you reduce the FPS target to 50, your system now has the performance headroom to be able to increase TLOD and keep your clouds at ultra. This is how it is supposed to work, and pretty much always has. Have I understood you correctly this time because, if so, I am not seeing an issue with what you are experiencing? 

10 minutes ago, Reset XPDR said:

It sounds like a target FPS of 60 is simply too much for your system to attain with a TLOD any higher than 50, even causing your cloud quality reduce as a result. When you reduce the FPS target to 50, your system now has the performance headroom to be able to increase TLOD and keep your clouds at ultra. This is how it is supposed to work, and pretty much always has. Have I understood you correctly this time because, if so, I am not seeing an issue with what you are experiencing? 

I don't think my system is the problem or is not enough powerfull, as i told you with old test version my fps was 80/90, but last monday i updated activesky with latest beta, updated gaist to v6 more boats traffic, yesterday during cruise sky was very cloudy 

Tomorrow i will fly and check if one of my settings had changed

3 minutes ago, grandfred29 said:

I don't think my system is the problem or is not enough powerfull, as i told you with old test version my fps was 80/90, but last monday i updated activesky with latest beta, updated gaist to v6 more boats traffic, yesterday during cruise sky was very cloudy 

Tomorrow i will fly and check if one of my settings had changed

The best way to check whether AutoFPS is the culprit or not is do one test run with it configuring your TLOD, Clouds and OLOD, then do the same test run scenario without AutoFPS but with the exact settings it was making in MSFS. If you get around the same FPS, then AutoFPS is not the issue and it is something else that has changed recently, perhaps some of your supporting apps as you have mentioned.

Also, if you can post up your AutoFPS log file for your test flight, I can look through that to see if anything looks out of place.

A new release candidate test build v0.4.3.0-RC2 is available here, containing one minor tweak and logic fix.

Changes since v0.4.3.0-RC1:

• Revised Reset button function to include recalibrating Auto Target FPS.
• Fixed setting lock out logic issue whereby TLOD Min + couldn't be selected on one profile if Auto Target FPS was selected on the other profile.

As mentioned with the v0.4.3.0-RC1 release, I have updated the readme in anticipation of formal release but am yet to receive any feedback on the changes. The most significant wording change is that relating to the revised TLOD Min + functionality, which is as follows:

TLOD Min + - additional TLOD Min with favourable performance conditions.

• Requires at least 15% FPS headroom above target FPS to work at all. If you use an FPS cap, set your target FPS to at least 15% below it, preferably more.
• When enabled, the TLOD Min + seek process will automatically start when commencing a flight, regardless of your aircraft's position, and at the conclusion of a flight when on the ground and stopped.
• This seeking process can be manually restarted by pressing the Reset button, should flight conditions change such that the original TLOD Min + is no longer valid.
• When seeking on the ground, TLOD Min + will progressively increase, in larger steps at first, until a higher TLOD Min with less than 15% FPS headroom is available.
• On climb out, TLOD Min + will remain set until your aircraft passes the calculated altitude threshold for the app priority mode to transition from TLOD to FPS priority.
• While in FPS priority mode, TLOD Min + will calculate to be 50% of the lower of either whatever TLOD you are currently getting or TLOD Max without TLOD Mtn Amt, but no lower than TLOD Min.
• On descent through the calculated TLOD priority mode transition altitude, TLOD Min + will lock until landed to give the app time to reduce TLOD to Min at a moderate rate.
• If at any time conditions deteriorate after TLOD Min + is set, there is an automatic 20% reduction of TLOD Min + in order to maintain target FPS.
• Avoid rapidly changing views or panning your external view too quickly, especially initially as un-cached scenery loads in, as you will induce temporary FPS drops that may trigger an unnecessary TLOD Min + reduction.
• Cannot be enabled at the same time as Auto Target FPS due to automation control ambiguity. Selecting both will result in the most recent selection being enabled and the other disabled, with a dialog box to advise this.

Any comments on my proposed rewording here will be appreciated (perhaps @Cpt_Piettas you seem to have tested this new functionality the most 🙏).

Edited September 18, 20241 yr by Reset XPDR

28 minutes ago, Reset XPDR said:

Any comments on my proposed rewording here will be appreciated (perhaps @Cpt_Piettas you seem to have tested this new functionality the most 🙏).

The only thing that seems a bit unclear to me is this:

31 minutes ago, Reset XPDR said:

At any time, there is an automatic 20% reduction of TLOD Min + should conditions deteriorate after TLOD Min + is set such that TLOD Min is causing FPS to drop too far below target.

I think I understand the meaning, but I’d suggest changing it, e.g.:

At any time, there is an automatic 20% reduction of TLOD Min + should conditions deteriorate after TLOD Min + is set, in order to prevent FPS to drop too far below target.

What do you think?

Also, I’m a bit curious about the calculated altitude threshold on climb/descent. It’s probably not necessary to include in the readme, but could you elaborate a bit on how this altitude is calculated?

By the way, I’ve had to put my testing on pause for a little while as something has rendered my simming hardware… temporarily incapacitated. Hopefully I’ll be up and running again in a couple of days 🙂

35 minutes ago, Cpt_Piett said:

I think I understand the meaning, but I’d suggest changing it, e.g.:

At any time, there is an automatic 20% reduction of TLOD Min + should conditions deteriorate after TLOD Min + is set, in order to prevent FPS to drop too far below target.

What do you think?

Yes, that sound better. I'll edit the original post and the readme to say that.

Edit: actually I've rejigged it again because my original sentence structure sounds awkward. It is now:

• If at any time conditions deteriorate after TLOD Min + is set, there is an automatic 20% reduction of TLOD Min + in order to maintain target FPS.

 

35 minutes ago, Cpt_Piett said:

Also, I’m a bit curious about the calculated altitude threshold on climb/descent. It’s probably not necessary to include in the readme, but could you elaborate a bit on how this altitude is calculated?

It's the same calculated altitude threshold described for IFR and VFR flights transitioning between FPS and TLOD priority. I've changed it to say:

• On descent through the calculated TLOD priority mode transition altitude, TLOD Min + will lock until landed to give the app time to reduce TLOD to Min at a moderate rate.

 

35 minutes ago, Cpt_Piett said:

By the way, I’ve had to put my testing on pause for a little while as something has rendered my simming hardware… temporarily incapacitated. Hopefully I’ll be up and running again in a couple of days 🙂

Oh no! Hopefully it wasn't those rascally rebels firing proton torpedoes into the reactor core. 🤣

Edited September 18, 20241 yr by Reset XPDR

5 hours ago, Reset XPDR said:

A new release candidate test build v0.4.3.0-RC2 is available here, containing one minor tweak and logic fix.

Changes since v0.4.3.0-RC1:

• Revised Reset button function to include recalibrating Auto Target FPS.
• Fixed setting lock out logic issue whereby TLOD Min + couldn't be selected on one profile if Auto Target FPS was selected on the other profile.

As mentioned with the v0.4.3.0-RC1 release, I have updated the readme in anticipation of formal release but am yet to receive any feedback on the changes. The most significant wording change is that relating to the revised TLOD Min + functionality, which is as follows:

TLOD Min + - additional TLOD Min with favourable performance conditions.

• Requires at least 15% FPS headroom above target FPS to work at all. If you use an FPS cap, set your target FPS to at least 15% below it, preferably more.
• When enabled, the TLOD Min + seek process will automatically start when commencing a flight, regardless of your aircraft's position, and at the conclusion of a flight when on the ground and stopped.
• This seeking process can be manually restarted by pressing the Reset button, should flight conditions change such that the original TLOD Min + is no longer valid.
• When seeking on the ground, TLOD Min + will progressively increase, in larger steps at first, until a higher TLOD Min with less than 15% FPS headroom is available.
• On climb out, TLOD Min + will remain set until your aircraft passes the calculated altitude threshold for the app priority mode to transition from TLOD to FPS priority.
• While in FPS priority mode, TLOD Min + will calculate to be 50% of the lower of either whatever TLOD you are currently getting or TLOD Max without TLOD Mtn Amt, but no lower than TLOD Min.
• On descent through the calculated TLOD priority mode transition altitude, TLOD Min + will lock until landed to give the app time to reduce TLOD to Min at a moderate rate.
• If at any time conditions deteriorate after TLOD Min + is set, there is an automatic 20% reduction of TLOD Min + in order to maintain target FPS.
• Avoid rapidly changing views or panning your external view too quickly, especially initially as un-cached scenery loads in, as you will induce temporary FPS drops that may trigger an unnecessary TLOD Min + reduction.
• Cannot be enabled at the same time as Auto Target FPS due to automation control ambiguity. Selecting both will result in the most recent selection being enabled and the other disabled, with a dialog box to advise this.

Any comments on my proposed rewording here will be appreciated (perhaps @Cpt_Piettas you seem to have tested this new functionality the most 🙏).

Is this different link or file location? Just goes to a dashboard and no file to download?

7 minutes ago, Flyfaster_MTN002 said:

Is this different link or file location? Just goes to a dashboard and no file to download?

Oops, I still had it in edit mode when I created that link. The correct link is here.

Re-posted, because I can no longer edit my post, with corrected download link:

A new release candidate test build v0.4.3.0-RC2 is available here, containing one minor tweak and logic fix.

Changes since v0.4.3.0-RC1:

• Revised Reset button function to include recalibrating Auto Target FPS.
• Fixed setting lock out logic issue whereby TLOD Min + couldn't be selected on one profile if Auto Target FPS was selected on the other profile.

 

Edited September 19, 20241 yr by Reset XPDR

Is it a bug or a feature, that Alt OLOD Base cannot be set lower than 1000 ft?