Not related to test 14 (it happens since quite a few versions) but when I select Auto-Start with MSFS I always get an error message saying:

FSUIPC installation not found. FSUIPC autostart not configured

Happens when Auto-Start with FSUIPC is not ticked but only Auto-Start with MSFS is ticked.
When I press OK on the error message, installation continues and shows Finished successfully.

Anyone knows if when you are climbing and passing the MinTLOD value ( eg 1000 ) , the app inmediately goes up to your Max TLOD when the FPS are good, or that there is a transition part ( eg 1000-3000 ft ) where TLOD slowly goes up ?

Edited December 28, 20241 yr by GSalden

10 hours ago, Reset XPDR said:

All I can suggest at this time is having a lower TLOD Max for that view if you are using HD textures.

What I am looking for is a that up to a certain altitude the App behaves like Dynamic LOD and above that altitude like AutoFPS.

Eg :

Min TLOD = 50 below 1000 ft

1000 ft - 2500 ft = 75

2500 ft - 5000 ft = 100

5000 ft -7500 ft =- 125

7500 ft  and above : automation like now with TLOD Max = 250

And with the automation Option that TLOD can be lowered automatically if the choosen/Fixed value of FPS cannot be reached.

AutoFPS is working fine till AG object batches suddenly appear ( Side views ) And that is when flying at a lower altitude.

5 hours ago, GSalden said:

Anyone knows if when you are climbing and passing the MinTLOD value ( eg 1000 ) , the app inmediately goes up to your Max TLOD when the FPS are good, or that there is a transition part ( eg 1000-3000 ft ) where TLOD slowly goes up ?

I think there's a transition part, an altitude range. 

All of a sudden I ran into a "compatibility test failed". App has been working fine since I first tried test14. Log file: https://drive.google.com/file/d/1tU13OQupHiBihAH5pL7lOCAxm125aNVg/view?usp=sharing

Note: I started the app in the middle of a flight. 

Edited December 28, 20241 yr by Cpt_Piett

Mine transitions up to the MAX TLOD and if the FPS dips below my set value the TLOD will transition down then back up as the FPS increases.

 

3 hours ago, Cpt_Piett said:

All of a sudden I ran into a "compatibility test failed". App has been working fine since I first tried test14. Log file: https://drive.google.com/file/d/1tU13OQupHiBihAH5pL7lOCAxm125aNVg/view?usp=sharing

Note: I started the app in the middle of a flight. 

These lines are why the compatibility test is failing all the time, ie. because your TLODs in your config file do not match the TLODs currently set in MSFS when the app started, before it made any changes itself:

2024-12-28 17:17:14.600 [DBG] [ MemoryManager:MemoryBoundaryTest ] TLOD PC: 100 
2024-12-28 17:17:14.600 [DBG] [ MemoryManager:MemoryBoundaryTest ] Config TLOD: 600 
2024-12-28 17:17:14.600 [DBG] [ MemoryManager:MemoryBoundaryTest ] TLOD VR: 100 
2024-12-28 17:17:14.600 [DBG] [ MemoryManager:MemoryBoundaryTest ] Config TLOD VR: 600 

Does this apply?

• Important Note - The new compatibility test uses a snapshot of your MSFS settings when MSFS starts to compare when it searches through memory. If you start MSFS and then make changes to MSFS settings and then start this app, it may fail this compatibility test. If you do accidentally perform this sequence and get a compatibility test failure, just restart MSFS and start this app BEFORE you make any changes to MSFS settings.

 

Edited December 28, 20241 yr by Reset XPDR

14 minutes ago, Reset XPDR said:

If you start MSFS and then make changes to MSFS settings and then start this app, it may fail this compatibility test

Makes sense 👍🏻 I guess I could have set TLOD to 600 in the sim menu before starting AutoFPS mid-flight, so that both values match.

EDIT: TLOD in the menu only goes to 400, so in that case I would have had to use usercfg.opt.

Edited December 28, 20241 yr by Cpt_Piett

9 hours ago, GSalden said:

Anyone knows if when you are climbing and passing the MinTLOD value ( eg 1000 ) , the app inmediately goes up to your Max TLOD when the FPS are good, or that there is a transition part ( eg 1000-3000 ft ) where TLOD slowly goes up ?

As @Cpt_Piettsays, there is a transition part, as follows:

Avg Descent Rate- Used in combination with FPS sensitivity to determine the altitude band in which TLOD will be interpolated between TLOD Min at the Alt TLOD base starting point and the lower of TLOD Max and the maximum TLOD your system can achieve while achieving at least your desired FPS target at a calculated top altitude. (200fpm - 10000fpm allowable)

• This band ensures that, if you descend at your set Avg Descent Rate or less, that the app can decrement TLOD from TLOD Max to TLOD Min by the Alt TLOD Base without exceeding the LOD Step rate associated with the FPS sensitivity level you have set.

If you want to be real nerdy, here's the formula the app uses to calculate it:

Quote

TLODMinAltBand = Math.Max(Model.AvgDescentRate[Model.activeProfile] / 60 * ((Model.activeMaxTLOD - Model.activeMinTLOD) / TLODStep), 1);

ie. if you want a large transition band then set the avg descent rate to a higher value.

If that doesn't make sense, message me your log and config files and I will interpret for you.

In my opinion, this app has been revolutionary to the sim community.  I frankly don't remember the last time I experienced a smooth landing/takeoff in a major city while also watching in delight the good scenery.  My kudos to the creator of this app.

9 hours ago, GSalden said:

What I am looking for is a that up to a certain altitude the App behaves like Dynamic LOD and above that altitude like AutoFPS.

Eg :

Min TLOD = 50 below 1000 ft

1000 ft - 2500 ft = 75

2500 ft - 5000 ft = 100

5000 ft -7500 ft =- 125

7500 ft  and above : automation like now with TLOD Max = 250

And with the automation Option that TLOD can be lowered automatically if the choosen/Fixed value of FPS cannot be reached.

AutoFPS is working fine till AG object batches suddenly appear ( Side views ) And that is when flying at a lower altitude.

The app pretty much does this if configured correctly, with the exception that there is no sudden jump to allowing TLOD Max of 250 up from 125.

Using the formula I recently posted for you, and assuming the value of the one variable you haven't given me, which is a TLOD Step of 5 being the default value, the answer works out to be for you to set an Avg Descent Rate of 9750.

This will give:

below 1000 ft = no higher than Min TLOD 50

1000 - 7500 ft = sliding scale of a maximum TLOD between 50 at 1000 ft and 250 at 7500 ft.

above 7500 ft  = up to Max TLOD of 250

If, at any time, a TLOD above 50 can't be achieved due to FPS being below target, then TLOD will automatically fall to as low as Min TLOD of 50 if required.

 

 

 

 

 

12 hours ago, Lange_666 said:

Not related to test 14 (it happens since quite a few versions) but when I select Auto-Start with MSFS I always get an error message saying:

FSUIPC installation not found. FSUIPC autostart not configured

Happens when Auto-Start with FSUIPC is not ticked but only Auto-Start with MSFS is ticked.
When I press OK on the error message, installation continues and shows Finished successfully.

The installer code does indeed put up this error message if it can't find FSUIPC installed, but it should only be doing it if you are trying to add the FSUIPC autostart option and it can't find an FSUIPC installation, not if it is checking it is being removed and you don't actually have FSUIPC installed in the first place. This is a great catch and already has been fixed for the next test or formal release version.

Edited December 28, 20241 yr by Reset XPDR

1 hour ago, Reset XPDR said:

As @Cpt_Piettsays, there is a transition part, as follows:

Avg Descent Rate- Used in combination with FPS sensitivity to determine the altitude band in which TLOD will be interpolated between TLOD Min at the Alt TLOD base starting point and the lower of TLOD Max and the maximum TLOD your system can achieve while achieving at least your desired FPS target at a calculated top altitude. (200fpm - 10000fpm allowable)

• This band ensures that, if you descend at your set Avg Descent Rate or less, that the app can decrement TLOD from TLOD Max to TLOD Min by the Alt TLOD Base without exceeding the LOD Step rate associated with the FPS sensitivity level you have set.

If you want to be real nerdy, here's the formula the app uses to calculate it:

ie. if you want a large transition band then set the avg descent rate to a higher value.

If that doesn't make sense, message me your log and config files and I will interpret for you.

Many thanks for your great help : I will experiment with a larger transition band.

That might do the trick 👍

 

Edited December 28, 20241 yr by GSalden

@Reset XPDR Is there any way to have AutoFPS work in the walk around mode in FS2024?  I noticed that it doesn’t work while in that mode and my fps and stuttering in VR is really bad at big airports until I get into the aircraft and then it starts working and stabilizing at my set 30fps.  

2 hours ago, thetford569 said:

@Reset XPDR Is there any way to have AutoFPS work in the walk around mode in FS2024?  I noticed that it doesn’t work while in that mode and my fps and stuttering in VR is really bad at big airports until I get into the aircraft and then it starts working and stabilizing at my set 30fps.  

It is supposed to work in walk around mode, but doesn't when you start flight outside your aircraft when I checked it just now. It looks like the camera states may have changed in the last 2024 update, so I'll take a look to see what's happening and see if I can get it working again.

Edit: Yep, they did change the camera states. Re-coding that area to fix it now!

Edited December 29, 20241 yr by Reset XPDR