7 minutes ago, Richard Sennett said:

What are using for a monitor ? 

No disrespect to you but you have a 4090 and sim looks terrible - boy they have some work to do 

I never saw this coming I thought we would be a bit better than 2020 and move on from there - boy I was wrong - sim looks very milky / washed out also especially in the cockpit depending what aircraft you are flying -  be nice if they will acknowledge it and address it - prob never happen 😞 Fenix isint to bad 

4K G-Sync TV. 

I've heard others mention the milky/washed out look as well. I only fly a few aircraft and the cockpits look good - rarely fly default aircraft. 

I did have a flight around Bryce Canyon earlier today - and I didn't like how the ground textures looked. Washed out is a good term I guess. 

EDIT: Wait a minute - you're talking about my screenshot?  The sim usually looks good to my eyes - but I agree that particular screenshot doesn't look good in terms of the ground. 

Edited January 14, 20251 yr by Cpt_Piett

In sim def looks better than screenshots - I noticed that - I have new Samsung 48" OLED 4K tv its awesome - wasn't cheap though - 55 is to big - I had a Samsung 4k tv 55

Gave it to my mother just to big 48 is perfect - thanks for sharing Buddy 🙂 

3 hours ago, Reset XPDR said:

 

The behaviour of FPS Cap is described below. In short, your TLOD is going up to 300 on the ground because your system has sufficient performance overhead to be able to do so, so why wouldn't you want it to be doing that?

 

Because, even thought my FPS is high and GPU Mem is within limits, there is still stuttering on view change in the cabin during plane setup. So I still prefer for the TLOD to be low on ground. I'm fine with keep using "FPS Sensitive" 

Just finished Oslo-Heathrow in the A319, non-expert IFR, FPS Cap (target 62 this time, default TLOD 200). Pretty much perfect, even with lots of BATC traffic. Test5 is awesome!

44 minutes ago, vincentrouleau said:

Because, even thought my FPS is high and GPU Mem is within limits, there is still stuttering on view change in the cabin during plane setup. So I still prefer for the TLOD to be low on ground. I'm fine with keep using "FPS Sensitive" 

Are you sure you are not just experiencing this?

• Even when the seek process is finished, you may get stuttering when you first pan the view in external view as MSFS scenery to the side and behind you may not have loaded in for your higher than usual TLOD, which is simply because of the way MSFS caches scenery in to memory. ie. it would still happen with high TLODs manually set by you without AutoFPS controlling them.

 

30 minutes ago, Reset XPDR said:

Are you sure you are not just experiencing this?

 

 

No, its not caching. Using hotkeys,successively  switching between  from say overhead view to EFB view  i find I get to much stuttering. That i why i hate motion blur in any game. That is the first feature I turn off in any game. Whereas at say TLOD 75, i cant see any difference with any higher TLOD. And even in drone view spotting planes. I tend the maximize stutter free panning. 
 

But as I say, I am super happy with “Fps sensitivity” mode.

Edited January 14, 20251 yr by vincentrouleau

18 minutes ago, vincentrouleau said:

No, its not caching. Using hotkeys,successively  switching between  from say overhead view to EFB view  i find I get to much stuttering. That i why i hate motion blur in any game. That is the first feature I turn off in any game. Whereas at say TLOD 75, i cant see any difference with any higher TLOD. And even in drone view spotting planes. I tend the maximize stutter free panning. 
 

But as I say, I am super happy with “Fps sensitivity” mode.

OK, fair enough. FPS Sensitivity mode does seem more suitable for you.

11 hours ago, vincentrouleau said:

I must admit that I am getting overwhelmed by all the configuration.

+1 

I would like at this point to see a poll to determine how many total users understand all the facets and interacting aspects and how they interrelate with both MSFS2024 and with MSFS2020. I have successfully enjoyed this application for a year or so. But the past ten days have bewildered me. 

I believe those of us not using Lossless Scaling are particularly in W0X0F (that is W zero X zero F).  Look it up (I am a former USAF meteorologist).  You will get a laugh at the comparison. 

I need a much better understanding of the FPS cap and how then to relatively structure my TLODs and OTODs.  This application needs a progressing documentation, not a "here is what I ....."  This is now on screen 161 and it has spun up quickly over the past 10 days.  I personally have backtracked those days and read and read and just become more and more confused.  That much less reading the discussion, primarily among less than five participants.  

How many are out there using this with significant understanding?  I love what it has provided for me over a great period of time now. But it is past time to slow down and allow users to actually understand, and to catch up.

 

39 minutes ago, fppilot said:

I would like at this point to see a poll to determine how many total users understand all the facets and interacting aspects and how they interrelate with both MSFS2024 and with MSFS2020. I have successfully enjoyed this application for a year or so. But the past ten days have bewildered me.

It's 100% understandable that it's very difficult to stay up to date with this thread. The dev is pushing out updates with the goal of improving the app. IMO it keeps getting better and better - so far the latest test version is the best IMO. 

Still, it's perfectly possible to stay on the latest release version, skip all the test versions, and just go for the next release version. 

As I've mentioned before, we do need to discuss these test versions and give feedback to the dev. And btw it's always possible to check the changelogs and the very comprehensive readme. 

16 minutes ago, fppilot said:

+1 

I would like at this point to see a poll to determine how many total users understand all the facets and interacting aspects and how they interrelate with both MSFS2024 and with MSFS2020. I have successfully enjoyed this application for a year or so. But the past ten days have bewildered me. 

I believe those of us not using Lossless Scaling are particularly in W0X0F (that is W zero X zero F).  Look it up (I am a former USAF meteorologist).  You will get a laugh at the comparison. 

I need a much better understanding of the FPS cap and how then to relatively structure my TLODs and OTODs.  This application needs a progressing documentation, not a "here is what I ....."  This is now on screen 161 and it has spun up quickly over the past 10 days.  I personally have backtracked those days and read and read and just become more and more confused.  That much less reading the discussion, primarily among less than five participants.  

How many are out there using this with significant understanding?  I love what it has provided for me over a great period of time now. But it is past time to slow down and allow users to actually understand, and to catch up.

 

You do realise that installing, running and discussing the test builds is entirely voluntary, so you if you are not understanding what is going on you can choose not to participate, skip reading anything test related and just read the release notes when the new version gets formally released?

The whole point of these test builds is to get progressive and constructive feedback on the proposed changes and roll the lessons learned into either new test version or draft documentation. Would you have me just do it all on my little lonesome and just put out what I feel is best for everyone without any indicator of suitability for others? I certainly hope not.

And as for these bewildering changes you speak of, all I have done in the 0.4.4.3 test phase is to fix LSFG detection after it was recently broken through an update of the LSFG app and add one new option to the TLOD Automation Method, which isn't actually a new option as it is just a specific configuration of Auto TLOD which has been around since Apr 24. So I've effectively given you an extra preset configuration on one drop down menu and a few minor UI fixes and that is bewildering?

The feedback I have had in these last 10 pages is invaluable in shaping how I will document this new preset. And like with any option I put in the app, if you don't understand it even after reading a couple of succinct dot points on how to best configure it, then simply don't use it.

In short, if you don't want to help out with the test versions then don't, but please don't snipe at the efforts of myself and others who are willing to help out and make this app better for all. I strongly suggest you stop reading this thread from this point onward and just wait until your app tells you there is a new app version available.

12 minutes ago, Reset XPDR said:

In short, if you don't want to help out with the test versions then don't, but please don't snipe at the efforts of myself and others who are willing to help out and make this app better for all.

That is not at all where I am at.  I love this app.  I am just finding it very difficult to understand the recent progression, perhaps due to a climate where it seems it is supposed to be intuitive. If that is an issue then for all sanity take it private with a control group until finished.  I am by no means sniping or demeaning, totally the opposite.  Just a better handshake and realization of how complex it has become to understand, and thus evaluate, would go very far.  

24 minutes ago, Cpt_Piett said:

And btw it's always possible to check the changelogs and the very comprehensive readme. 

My bad I guess.  The readme is not a part of the DL/Install that i am aware of and I neglect to seek it out separately.

Following some very useful feedback during the 0.4.4.3 test phase from @Cpt_Piett about default MSFS settings not always restoring correctly, I have changed where the app gets its default MSFS settings from to be from the UserCfg.opt file in lieu of MSFS active memory, which should be a more reliable method of obtaining these settings.

As such, 0.4.4.3-RC1 is now available for download here. If I have done it correctly, you should not notice anything different than Test 5, other than your default MSFS settings being more reliably saved and restored.

We are now getting close to formal release. My thanks go out to everyone who has provided constructive feedback during this testing phase. Documentation in the readme will be the main beneficiary of this feedback as the actual functionality changes are pretty minor.

Edited January 15, 20251 yr by Reset XPDR

Thanks so much 

57 minutes ago, fppilot said:

I am just finding it very difficult to understand the recent progression, perhaps due to a climate where it seems it is supposed to be intuitive. If that is an issue then for all sanity take it private with a control group until finished. 

That would be counterproductive as most of my regular testers are very familiar with the app and would not necessarily reveal a lack of intuition. It is by having it out here amongst regular users that I get the best feedback like this. Yes there was initially confusion about how best set the app up in this new mode, but from that I have developed the four dot points in the last few pages that seems to have placated everyone except you and will be going in to the readme in a more polished form.

I'm sorry to say but your recent comments have not been constructive as it is more about you not being able to follow a discussion that most others seem to than what is actually being discussed. To be frank, this is not the first time you have stated you had trouble following what is happening with a test build, which is why I still genuinely suggest you stay out of all such discussions in the future.

 

Edited January 15, 20251 yr by Reset XPDR