@Reset XPDR would you like more help with testing latest version? I only did a couple of flights, but everything seemed to work really well. 

28 minutes ago, Cpt_Piett said:

@Reset XPDR would you like more help with testing latest version? I only did a couple of flights, but everything seemed to work really well. 

While yours is pretty much the only feedback I've had on this latest test version, that's actually a good sign because users are usually very quick to tell me if I've broken something and are often silent if it is all working good. Either that or everyone else has given up in disgust 😆

I would appreciate your testing efforts with the next test build I will be putting out in the next day or so, not so much to test TLOD Min Extra in Auto TLOD automation mode (although that is appreciated), but to regression test TLOD Min Extra in FPS Sensitivity and Tolerance modes just to make sure I didn't break anything there while coding for Auto TLOD.

Another thing I'd appreciate your, and anyone else's, opinion on is whether to scrap Auto Target FPS completely from the app in the next release mainly because it conflicts with the new TLOD Min Extra functionality. Auto Target FPS requires a fixed TLOD Min so that it can calculate a suitable target FPS, whereas TLOD Min Extra requires a fixed target FPS, so it can calculate a suitable TLOD Min Extra ie. the logic needs one item to be fixed to vary the other, hence making them mutually exclusive.

While I could do some UI trickery to grey out the other option when one of these conflicting functions is checked, I get the impression that not a lot of users are using auto target FPS anyway, so the simplest solution is to just completely remove auto target FPS and be done with it.

Your, and others, thoughts on this before I wield the big coding axe are appreciated.

33 minutes ago, Reset XPDR said:

Another thing I'd appreciate your, and anyone else's, opinion on is whether to scrap Auto Target FPS completely from the app in the next release mainly because it conflicts with the new TLOD Min Extra functionality. Auto Target FPS requires a fixed TLOD Min so that it can calculate a suitable target FPS, whereas TLOD Min Extra requires a fixed target FPS, so it can calculate a suitable TLOD Min Extra ie

So we'd only be working with a fixed target FPS?  I see no conflict there for me.  Will gladly test.

1 minute ago, fppilot said:

So we'd only be working with a fixed target FPS?  I see no conflict there for me.  Will gladly test.

Fixed as in you, the user, sets the target FPS for TLOD Min Extra, and all other TLOD automation for that matter, to work with, just like you have always done if not using Auto Target FPS.

In the interest of keeping things moving along, I will just disable Auto Target FPS and hide it for now in the next build and see if that flushes out any diehard Auto Target FPS users wanting it back that can't be convinced otherwise. It will then be simple enough to bring it back if required, otherwise I will remove it completely for the formal release.

Reset, I asked you in the Dynamic LOD thread if you thought you might continue to support that feature for MSFS24, but I don't think you read that thread anymore. 

I am assuming you will support the Auto FPS App for the new version; I'd like to ask this question. How would one go about setting up the Auto FPS app to mimic the simplistic settings in Dynamic LOD should it not work with MSFS24?

All I need and want to use is a minimum TLOD setting (I use 100) on the ground before takeoff and on approaches, and then I maximize TLOD (400) above 3500'. Simple as that... it works perfectly. I use the step up and step down feature for smoothness both on climb out and then on approaches.

Is the Auto FPS app so different that the simplistic approach of Dynamic LOD isn't possible with it?

Just wondering...

55 minutes ago, BaronKen said:

Reset, I asked you in the Dynamic LOD thread if you thought you might continue to support that feature for MSFS24, but I don't think you read that thread anymore. 

I am assuming you will support the Auto FPS App for the new version; I'd like to ask this question. How would one go about setting up the Auto FPS app to mimic the simplistic settings in Dynamic LOD should it not work with MSFS24?

All I need and want to use is a minimum TLOD setting (I use 100) on the ground before takeoff and on approaches, and then I maximize TLOD (400) above 3500'. Simple as that... it works perfectly. I use the step up and step down feature for smoothness both on climb out and then on approaches.

Is the Auto FPS app so different that the simplistic approach of Dynamic LOD isn't possible with it?

Just wondering...

Sorry I didn't see your post in the Dynamic LOD thread as I don't normally look there because that thread was started by the original Dynamic LOD developer, not me.

In any case, ideally with MSFS2024 these apps will no longer be needed because Auto LODs have been incorporated into MSFS itself. However, I am a realist and this may not happen so plan B is to see if I, or someone else more skilled than me, can find where the settings these apps need to interact with are located in MSFS2024 running memory space, and rejig my apps accordingly. If MS completely rejigs the memory space or makes these settings inaccessible externally then we are dead in the water, but I certainly will try. And if I can get one app working, I can get them all working relatively easily, so I'd either update both AutoFPS and DynamicLOD_ResetEdition or neither.

Re whether you could set up AutoFPS to do what Dynamic LOD does? Pretty much yes with the exact settings shown below under Expert Options, which give a gradual TLOD transition of 100 and 400 between 100ft and 3500ft in TLOD steps of 5 without a care what FPS you are getting, and you don't have to use any other features if you don't want to. I suggest you give it a try and if it doesn't do what you want, just uninstall and go back to using Dynamic LOD. I suggest you use the last formal release version which you can get here.

 

Proposed new look UI with Auto Target FPS removed, Reset button relocated to where it was and Decrease Cloud Quality options hidden/collapsed when unchecked:

 

4 hours ago, Reset XPDR said:

I would appreciate your testing efforts with the next test build I will be putting out in the next day or so, not so much to test TLOD Min Extra in Auto TLOD automation mode (although that is appreciated), but to regression test TLOD Min Extra in FPS Sensitivity and Tolerance modes just to make sure I didn't break anything there while coding for Auto TLOD.

Happy to test, I am 😊

4 hours ago, Reset XPDR said:

Another thing I'd appreciate your, and anyone else's, opinion on is whether to scrap Auto Target FPS completely from the app in the next release mainly because it conflicts with the new TLOD Min Extra functionality. Auto Target FPS requires a fixed TLOD Min so that it can calculate a suitable target FPS, whereas TLOD Min Extra requires a fixed target FPS, so it can calculate a suitable TLOD Min Extra ie. the logic needs one item to be fixed to vary the other, hence making them mutually exclusive.

I haven’t used it in ages. IMO it can be removed. I see that you already decided to do so in the next build.

2 hours ago, Reset XPDR said:

If MS completely rejigs the memory space or makes these settings inaccessible externally then we are dead in the water, but I certainly will try.

I’m really hoping that will not be the case. Even though some sort of dynamic LOD feature will be implemented, I very much doubt that it’ll be as versatile as anything you’d be able to create.

1 hour ago, Reset XPDR said:

Decrease Cloud Quality options hidden/collapsed when unchecked

That’s a good idea, looks a bit tidier.

Reset,

Thanks for your thoughtful reply to my questions, and the settings to try with the Auto LOD app that mimic Dynamic LOD. I'll give that a try and see what happens just for fun, because I'm happy with Dynamic LOD.

I am a little skeptical about dynamic LOD being implemented in 24 by MS/Asobo only because of the XBox issues being reported with their graphics problems and issues. Certainly don't want to see that or have those kinds of problems with 24 on my PC.

Thanks again.

3 hours ago, Reset XPDR said:

Proposed new look UI with Auto Target FPS removed, Reset button relocated to where it was and Decrease Cloud Quality options hidden/collapsed when unchecked:

 

Here my system ( 2 displays ) is smooth when using AutoFPS. A fixed value never showed the same smoothness.

Eg : at Aerosoft EDDF U see AutiFPS at 24 , but using Lossless Scaling with Vsync enabled I get 57-59 fps.

That scenery is very heavy on the system. Wheh taxiing away from the terminals the framerate in AutoFPS goes up and all is still smooth.

What do I need to do now AutoFPS has been removed ? Changing a fixed value inflight ?

I never had everything smooth trying a fixed value.

Your app I use with your default settings , I only check TLOD top

Thanks 

 

Edited September 11, 20241 yr by GSalden

1 hour ago, GSalden said:

Here my system ( 2 displays ) is smooth when using AutoFPS. A fixed value never showed the same smoothness.

Eg : at Aerosoft EDDF U see AutiFPS at 24 , but using Lossless Scaling with Vsync enabled I get 57-59 fps.

That scenery is very heavy on the system. Wheh taxiing away from the terminals the framerate in AutoFPS goes up and all is still smooth.

What do I need to do now AutoFPS has been removed ? Changing a fixed value inflight ?

I never had everything smooth trying a fixed value.

Your app I use with your default settings , I only check TLOD top

Thanks 

 

When using Auto Target FPS. sure the app is picking the target FPS not you, but once it has picked it the app functions exactly the same whether you picked it or not. The only real difference is that there are two instances when Auto Target FPS will pick another target FPS. The first is that if conditions deteriorate such that your TLOD drops to minimum and your system still drops a reasonable margin below your target FPS, then it recalculates a lower target FPS. The second is when you land and stop, where the target FPS gets picked by the app once again.

From what you are describing above, neither of these two differences seem to apply so it shouldn't make any difference whether you set the target FPS to 24 yourself or if Auto Target FPS does it for you because the FPS is increasing as you depart, which wouldn't trigger an Auto FPS recalculation, nor have you mentioned a follow on flight where the second Auto Target FPS recalculation condition would be met.

In both instances your target of 24 FPS would remain fixed for the entire flight, whether you or the app set it. As such, I recommend you try disabling Auto Target FPS and just set your own target FPS of 24 and see how the flight goes. Send me your flight log if you have any issues and I'll see what I can uncover.

BTW, I am willing to reinstate Auto Target FPS if you can give me a compelling reason to do so, but from the scenario you provided it doesn't look like you actually need it. If you have any other scenarios in mind where it would make a difference. please let me know.

 

 

@Reset XPDR

Thanks for the explanation. I will make the Frankfurt - Rome flight twice and report back.

One time with AutoFPS on in v9 and the other with v10 without it.

Each airport is different and in AutoFPS mode the starting framerate can be different too.The  target fps can be higher at smaller airport. With v10+ I would need to change it depending on the complexity of the airport ( if I am correct).

The idea is that on the ground tLOD is 50 and at cruising altitude 200 or more.

Settings Cloud Quality and OLOD done automatically.

- - - 

v9 ( only 1 of the 2 outside view displays in the screenshot - Lossless Scaling enabled 3x plus Vsync 60 hertz )

Working great !

In the air 

 

 

 

 

 

 

 

 

 

 

Edited September 11, 20241 yr by GSalden

1 hour ago, GSalden said:

I will make the Frankfurt - Rome flight twice and report back. One time with AutoFPS on in v9 and the other with v10 without it.

I haven't released a test version that doesn't have Auto Target FPS just yet, so you can test on the same version just checking and unchecking Auto Target FPS between the tests.

1 hour ago, GSalden said:

Each airport is different and in AutoFPS mode the starting framerate can be different too.The  target fps can be higher at smaller airport. With v10+ I would need to change it depending on the complexity of the airport ( if I am correct).

Now this is a good reason as to why you'd want to keep Auto Target FPS. If I am interpreting how you use AutoFPS correctly, you want your TLOD Min and Max to stay fixed but your target FPS can vary whereas other users want their FPS to stay fixed and their TLOD Min and Max to vary.

I certainly don't want to deprive you of how you have been able to use the app, so let me put my thinking cap on and see what I can come up with. It may just be that if you choose Auto Target FPS then you will not be able to use TLOD Min Extra and I see that's the way you have it configured right now. If you do want to use TLOD Min Extra as well as Auto Target FPS, well then we have a problem because, as I explained a couple of posts ago, their functionality is mutually exclusive.

1 hour ago, GSalden said:

In the air 

 

As postulated in my last post, your Auto Target FPS is the same value it was when your flight started so if you had have not used Auto Target FPS and set your Target FPS to 16, you should get exactly the same experience. As you say though, without Auto Target FPS you'd have to manually set your FPS each flight in a different scenery complexity area, but really it's not that hard to do as you would just set Target FPS 5% (for IFR flight type) below what FPS you are initially reading as that is all Auto Target FPS does anyway.

@Reset XPDR

This is how it looks after landing at Rome 

 

The target fps has gone up.

Edited September 11, 20241 yr by GSalden