New Test Version 07Mar240410Z here. These changes primarily relate improving the non-expert mode experience, which I fully intend to use myself. In short, I didn't like how it forced such a low TLOD Min on me if conditions were such (eg. GA, remote area, light weather) that I'd rather use the default MSFS settings I had without the app. To that end, if conditions are favourable, your TLOD Min in non-expert mode will increase automatically and stay that way on approach/landing as long as the conditions remain favourable. If I can get this working well, and I think I'm pretty close, many users could end up being happy with auto settings. Anyway, let me know what y'all think! 

Changes are:

• Added auto raising of TLOD Min in non-expert mode and on the ground to the default TLOD instead of 50% of it if conditions are such that decrease cloud quality is not active and FPS is still 15% higher than the target FPS. Also, this setting will remain during approach and lock at final approach provided that at no point does the FPS reduce lower than the target FPS minus the FPS tolerance. Intended to be only enabled for DX11 as DX12 can cause ground texture tearing on the ground at airports when TLOD changes. Test version will work with both DX11 and DX12. Please report any worsening of ground texture tearing issues at airports with DX12.
• Extended FPS setting timer to 20 seconds on initial flight loading to allow MP and AI traffic to load in fully, 20 seconds after auto raising TLOD Min in non-expert mode and to 10 seconds for all other graphics mode transitions.
• Changed non-expert default settings to have FPS tolerance at 2% to allow smoother TLOD transitions and to increase TLOD Max from 200% to 300% of default TLOD to allow extra TLOD range when auto raising of TLOD min is active.
• Fixed non-expert FPS tolerance being incorrectly set to the expert setting for FPS tolerance when it should be a fixed value instead.

Edited March 7, 20242 yr by Reset XPDR
Change to test version and release notes

25 minutes ago, Reset XPDR said:

New Test Version 07Mar240350Z here.

I'll test the non-expert mode this time (already got it up and running at FL360 en route to LAX) - the new changes looks very interesting! Hopefully, by being an early adopter and report of any issues, I'll be able to redeem myself for having succumbed to the RTFM monster 😄

25 minutes ago, Reset XPDR said:

Currently only enabled for DX11 as DX12 can cause ground texture tearing on the ground at airports when TLOD changes.

I'm using DX12 (FG) so unfortunately I won't be able to test this feature.   

EDIT:

25 minutes ago, Reset XPDR said:

Intended to be only enabled for DX11 as DX12 can cause ground texture tearing on the ground at airports when TLOD changes. Test version will work with both DX11 and DX12

Got it. On 07Mar240410Z now. A few minutes ago I was on 07Mar240350Z 🙂

Edited March 7, 20242 yr by Cpt_Piett

3 minutes ago, Cpt_Piett said:

I'll test the non-expert mode this time (already got it up and running at FL360 en route to LAX) - the new changes looks very interesting! Hopefully, by being an early adopter and report of any issues, I'll be able to redeem myself for having succumbed to the RTFM monster 😄 

OK, should be there now.

I'm doing a Concorde flight right now from LGAV to LFMN and the new auto TLOD Min increase has not activated, exactly as it should be doing because I was barely getting my target FPS on the ground and cloud quality reduction was active. Halfway there and so far so good.

After getting the newest version I did an approach to KLAX in the A300 with yet another touch 'n go. TLOD and OLOD adjusted very gradually on descent, reaching TLOD 200 (got max 600) at 6000 AGL and OLOD 200 at 2000 AGL. Target fps of 76 was maintained most of the time, although it dipped down to 51 around touchdown. That's to be expected I guess considering the density of the scenery + AI traffic. Clouds was also reduced from ultra to high. Climbing to higher altitudes, TLOD did go up to my max of 600 occasionally.

So my initial impression is that it seems to be working great! I'll do a performance test when I'm on approach to KSFO. 

Edited March 7, 20242 yr by Cpt_Piett

Completed my Concorde flight in VR, which is a pretty tough test because of the high aircraft speed. I'm not very good with charts, but here is ALT and FPS plotted across time. A bit of FPS variance at times, but the flight was smooth from start to finish. I might try putting FPS tolerance back to 5% as at times the app is not reacting quick enough. Target FPS was 45 and this was in non-expert mode BTW.

Edited March 7, 20242 yr by Reset XPDR

All right, so I made it down safely. Another happy landing! Performance = great. Avg fps 74 with a fairly decent consistency, 1% low avg 39, smooth 99% of the time, FTV <2ms at 90% (i.e. decent frame time consistency = relatively smooth). 

I had AutoFPS running for 2 hrs 20 mins. Just checked the entire log and it looks fine, no surprises that caught my attention. 

I think I'll get some sleep now as I did KDCA-KJFK-KBOS-CYYZ-KDEN-KLAX-KSFO in one sitting in the A300.

Edited March 7, 20242 yr by Cpt_Piett

Hi, I have been testing test version 0.4.2 a little this morning, and I must say I like the non expert mode changes you have made.

I will test further today, but I think I am going to be using the non-expert mode in preference to expert for most of my flights.

One wish I have:

could the window position be remebered also for a multi screen setup?

I have 3 screens, MSFS in the middle, primary screen, and I run Auto_FPS on the right screen.
Every time Auto_FPS starts, it starts at the primary screen again.

Not a big thing, but if there's a technical solution from your side, that would be great!

many thanks!!!

3 hours ago, Reset XPDR said:

I didn't like how it forced such a low TLOD Min on me if conditions were such (eg. GA, remote area, light weather) that I'd rather use the default MSFS settings I had without the app. To that end, if conditions are favourable, your TLOD Min in non-expert mode will increase automatically and stay that way on approach/landing as long as the conditions remain favourable.

That’s a great idea. Didn’t get to experience it in my previous flight as i didn’t have much headroom. But I’ll take one of my GA planes out for a spin and check it out. 

24 minutes ago, guenseli said:

One wish I have:

could the window position be remebered also for a multi screen setup?

I have 3 screens, MSFS in the middle, primary screen, and I run Auto_FPS on the right screen.
Every time Auto_FPS starts, it starts at the primary screen again.

Not a big thing, but if there's a technical solution from your side, that would be great!

many thanks!!!

I'll take a look but no promises. UIs aren't really my forte.

I have done some 1 hour or so of GA flying in some poorish weather, using the test version and with expert mode unticked. This flying involved some sight seeing and touch and goes. I have to say I like it. It was smooth throughout with all the dynamic changes being made to TLOD, cloud etc. During the latter stages of the flying I minimised the app and just flew. So, in summary, for me in GA flying the default mode without expert ticked is working very well. If I have time I will look at airliner flying later today.

22 minutes ago, Harrier77 said:

I have done some 1 hour or so of GA flying in some poorish weather, using the test version and with expert mode unticked. This flying involved some sight seeing and touch and goes. I have to say I like it. It was smooth throughout with all the dynamic changes being made to TLOD, cloud etc. During the latter stages of the flying I minimised the app and just flew. So, in summary, for me in GA flying the default mode without expert ticked is working very well. If I have time I will look at airliner flying later today.

That's good to hear. I really wanted this app to get back to it's original simple root of one setting (target FPS) to rule them all, but I got a bit caught up with the expert settings of late, so it was time to revisit it.

I have flown both an airliner and GA flight today, with the former not activating the new auto TLOD Min at all because performance conditions didn't warrant it and the latter using it for the entire flight because they did. I have not had to change one setting between these two flights (target FPS is set to 45 for VR) and have had smooth flights with great FPS and that is exactly what I was after with the original concept.

Edited March 7, 20242 yr by Reset XPDR

33 minutes ago, Reset XPDR said:

I have not had to change one setting between these two flights (target FPS is set to 45 for VR) and have had smooth flights with great FPS and that is exactly what I was after with the original concept.

I am flying in 4k PC mode on a limiting system by today’s standards. I have target FPS set to 30. With some fairly strong sim settings I get between 25 and 45 FPS in most situations. So, I think this is a good test situation for your app.

I should also add that I am using the Tobii Eye Tracker 5.

Edited March 7, 20242 yr by Harrier77

Stupid question: if I close the app inflight or during an active MSFS session, does it revert the values to what I have in the settings or does MSFS need a restart then? Then: I configured the app as such that it gets fired up when starting MSFS via exe.xml. Can this be undone without reinstallation and fiddling around manually in the exe.xml?