hi

just tried to install latest version

but it says could not determine package path

my package path is not default but i cant see any settings to change this

have i got something wrong

thank for any help

I did some tests trying to solve my CTD problem with autoFPS and this is the summary of what I found:

- Of all the aircraft I have tested so far, the A330 (All Variants) and the Beluga XL are the only ones that are not affected by this problem, which is bizarre, since the A320neo and A321neo have this issue and both should share the same systems as the A330, since they are all made by iniBuilds.

- In some aircraft like the 737MAX and the 747-8, I have CTD as soon as I start pre-flight preparation, such as turn on the batteries and aligning the IRS. However, in most of them, I only have CTD after I import a flight plan into them, either from Simbrief or from Microsoft's flight planner. If I don't import any flight plan, they work normally with autoFPS.

- In event viewer, the following error message appears every time I have CTD with autoFPS:

Autopilot.dll wil error was reported.
HRESULT: 0x80070491
File: onecoreuap\admin\moderndeployment\autopilot\dll\dllmain.cpp, line 128
Message: NULL

- And just to recap, I had three successful flights using autoFPS before the v1.1.10.0 update. After the update, I got CTD with autoFPS

2 hours ago, Axis3600 said:

I don't understand, but it doesn't work for me, I just did a test flight with the application, it tells me in sim values that my TLOD is indeed at 4OO in green (sorry I forgot to take a photo).

But the terrain remains blurry, it is impossible that my TLOD is at this moment at 400
So, I go to the MSFS menu, the TLOD is still on 100 (This is not normal, it should be on 400? Like the application tells me?)

And there, I put it on 400 and yes OK the terrain is detailed the FPS have also gone down, but at this moment, I have TLOD 400.

Here is the photo with the application that tells me TLOD 400

And here I am who went into the settings and manually set it to 400

So I don't understand, because the application raises and lowers the TLOD according to my altitude, but it has no visual effect/impact and FPS on the game is stuck at 100 no matter what the application says.

Here, I took a picture of how AutoFPS is configured, did I make a mistake?
 

https://i.postimg.cc/52HVGCTV/APP.png

 

And otherwise after my flight, I took the problem the wrong way round!

I restarted MSFS with a TLOD 400 and I launched the application since I was on the GROUND AutoFPS should have lowered the TLOD to 100.

Same on the ground so it said 100 in green in the application, but in the game, I was still in LOD 400 (I know by the FPS it lags while at 100, it's smooth.

So, if anyone knows how to help me, because this application is a MUST!

Wow, this is an extensive testing 😅 One of the things that need to be fixed is that if you pause the game (go to the menu or even go into the photo mode) the app loads the default values that it reads upon starting the game. This is because probably due to changes between msfs 2020 and 2024 the app loses the connection with the session. You can see that if you go to the menu the fps and tlod count says n/a. That's why you see tlod 100 when you go to the menu. When you get back into the flight the app starts to gradually rise tlod as if you were climbing. I thought that this isn't a breaking problem and as I mentioned earlier I have limited time to work on this.So if you took the screen right after you closed the menu it might have look like that which doesn't mean that the app doesn't work. There is a way to test it and I did that and I clearly saw the difference. Fly low to the ground on autopilot in some small plane. In the autoFPS set the minimum tlod to 10 (without pausing the game), you should see almost none details on the ground. Then set the minimum told to let's say 200. You will see how different the ground looks. Of course there is still possibility that for me and some other people it works well and for you unfortunately not, the same with the CTDs that edu2703 has it issues with window visibility. Also, this might be due to unmaturity of the sim. This unfortunately is common in the programming world. Let me know what you find out and if possible please send me your log file that is in appdata/roaming/autoFPS2024/log. Good luck with testing 👍

Hmm.

 

Gave this a try but I am not sure it is actually changing the LOD. I set the LOD in sim to 10 to make it obvious.

The app was showing it had changed my LOD to 600 but still the sim was definitely running with 10 LOD.

 

You can see says 600 TLOD, but as you can also see it definitely isn't....

 

Edited December 4, 20241 yr by abennett

I understood that going to the menu stops the application, no problem.

But the photos are just to show the difference between the application that tells me LOD 400.
And me who stops Autofps and immediately takes a photo by changing the settings and manually putting LOD 400 to show the difference between the 2.

This is exactly what abennett has just shown in his photo where the application tells him LOD 600, we can clearly see that in his photo his LOD is still at 10.

When do you put TLOD 10 in the application what is your setting in MSFS?
And do you launch the application before launching MSFS?
Do you launch MSFS and AutoFPS in admin mode?

I would like to know if it works for you, follow step by step how you do it ...
Maybe I'm wrong somewhere ...

But what I am sure of is that the application responds well, it is well connected, the LOD increases with the altitude up to 400 and decreases little by little when I descend to return to LOD 100.

Everything works as it should, it's just that it doesn't change anything in MSFS, it is stuck at the LOD that you put in the parameters.

In any case, thank you for your involvement and your help

Edited December 4, 20241 yr by Axis3600
EDIT

I'm certainly doing something wrong as I felt confident launching this MSFS2024 compatible version (Thank you!) where it works flawlessly with the MSFS2020 and the MSFS2020 version. Unfortunately, MSF20204_AutoFPS by KayJay_1c6b (1.0.1.0) catch the session and some values (AGL is weird, FPM, FPS) but has no impact on TLOD (NAN) OLOAD (NaN) or clouds (n/a):

Does it work in VR?, the App doesn´t change to VR next to the FPS number box settings, when you enter in VR, like the FS20 AutoFps did.

From all of this of what I'm seeing it looks like they had to change something in the sim compared to 2020 that is dependant on specific PC because honestly for me it works great every time. I tested it this morning and again worked without any problem.

Here I have told 360 and you can see buildings all the way to the coast. With changing only max told to 20 during the flight I can see changes in real time.

The only thing that I did was changing max tlod from 400 to 20

I've noticed that some have the Auto Method set to something other than VR Optimized. 

Does this make a difference?

51 minutes ago, flyblueskies said:

I've noticed that some have the Auto Method set to something other than VR Optimized. 

Does this make a difference?

Probably yes as I changed only the vr optimized mode and didn't really look much at other modes and I haven't tested other modes much

Is it still recommended to set target FPS a few below desired FPS as it was in the 202 version?

In 2d yes, but in VR put your exact refresh rate (72, 90 etc)

3 hours ago, kayjay1c6b said:

The only thing that I did was changing max tlod from 400 to 20

I don't know what's going on, I'm going to test again this evening and put exactly that you in the application. 

Are you launching AutoFPS before MSFS or is MSFS already running?

And would launching MSFS and/or AutoFPS in admin mode change anything for me, I know that if I launch it without admin mode it does not connect to MSFS I get the error message in red.

47 minutes ago, Axis3600 said:

I don't know what's going on, I'm going to test again this evening and put exactly that you in the application. 

Are you launching AutoFPS before MSFS or is MSFS already running?

And would launching MSFS and/or AutoFPS in admin mode change anything for me, I know that if I launch it without admin mode it does not connect to MSFS I get the error message in red.

I don't believe that running in admin mode affects anything, if anything it would help. I sometimes launch the autoFPS before the sim and sometimes after if I forget. Make sure that you use VR optimized mode as flybluskies pointed out that you had selected other mode and I only looked at and changed this mode. I don't know exactly how other modes work. Maybe something is broken in them in msfs 2024. Strangely the app is protested exactly against what you experienceing and in case it doesn't read correct told old etc values it throws the boundary test error. So technically if it connects to the session it checked that it can read and write right values at correct memory addresses. Did you send me the log file? 

I sent you a private message, thank you again.
And yes now, I only use it in VR Optimized, but it doesn't work 😞