44 minutes ago, Sonosusto said:

It's a BETA update that is completely voluntary. Yes, having that stuck on the screen is annoying. Again, it's a beta. Not SU4. That annoying thing on the screen can be removed.

I totally agree with you, but that's not the problem. The issue at hand, as I mentioned, is the way they think and let go of new things that are totally ridiculous and unreal. If people still don't understand how it works, if there are programming errors, and those checking (if they actually do) consider this normal and accept it, even in a beta stage, then we really have a bigger issue. Unfortunately, this is not the only issue that shows their lack of understanding of this product. All we can hope for is the best, and then stuff like this pops up. Discouraging even for a beta product. 

1 hour ago, LRBS said:

This is another one for the Guinness Book by their "talented and capable" team.

They are a talented team, looking at what they have done so far. Could it have been even better? Yes, definitely.

2 hours ago, bobcat999 said:

There is nothing wrong with discussion about 'bugs' or undesirable effects in a beta, but it seems some people are prepared to accept any old tosh.  
All that insulting talk about support animals and go and touch grass etc. really seems to apply to them, as they are wounded by criticism of their sacred toy.

Everyone here can take criticism, I believe. It's the tone and the cynicism in many posts, as well as the condescending remarks regarding the developers, that may trigger some of us, including myself sometimes.

Edited November 1, 2025Nov 1 by Rimshot

19 minutes ago, bobcat999 said:

I agree.  Do it if you need to - it's for people that are too fragile to read genuinely deserved criticism of the Asobo development staff..
There is nothing wrong with discussion about 'bugs' or undesirable effects in a beta, but it seems some people are prepared to accept any old tosh.  
All that insulting talk about support animals and go and touch grass etc. really seems to apply to them, as they are wounded by criticism of their sacred toy.  Too funny!

There is a difference between constructive criticism and rude and insulting behaviour. If you show that you are rude and insulting, you will be ignored. Simple. 

19 minutes ago, Rimshot said:

Everyone here can take criticism I believe. It's the tone and the cynicism in many posts, as well as the condescending remarks regarding the developers, that may trigger some of us, including me sometimes.

Well for some of us this is kind of deserved. A few of us try to be as balanced as possible but will not hold back when we see areas where they repetitively drop the ball. As a matter of fact i just received a temp ban for suggesting that the person responsible for the UI needs supervision in the thread about the A to exit button. Maybe a touch harsh ? But i probably would not have come to that conclusion if they had not been under performing in that area since release of 2024 and instead of improvement we still see movement in the opposite direction. 

At some point frustration is going to set in and get expressed... as shown in how rapidly the votes were tallied in the latest UI blunder on their forums.

I simply replied to the mod that i disagree with his opinion and i wont correct my post. I'll just use my account over there much less as it works out better for them and for me as i have no issue with moderation but im not here for the overt protectionism of the dev team .. especially when they screw up repeatedly in certain aspects. 

At the end of the day on a whole the latest build is quite decent and i have been flying it since Friday but that does not mean that ASOBO is wholly exempt from the occasional harsh criticism if they dont listen and keep doing highly annoying things.

At the end of the day though they certainly got the message with that vote tally and we will see how they respond to this latest UI fiasco.

Edited November 1, 2025Nov 1 by Maxis

Il y a 3 heures, Shrek1970 a dit :

If you want to remove the Shift+C to exit aircraft annoying pop up this was posted by a legend over at the MSFS forums. This method keeps all other UI tabs operational.

Navigate to D:\MSFS24\Microsoft Flight Simulator 2024\Content\Packages\fs-base-ui\cookedcomps  (or where your contents folder is located)

find the file {5D8D140B-0F7E-4213-B2F7-E16727D57DDC}.html

Open the file in notepad

delete all contents and replace with

<input-bar resource-id="{5D8D140B-0F7E-4213-B2F7-E16727D57DDC}" resource-path="coui://html_ui/VFS/components/shortcutspage/shortcutspage.uxml" name="ShortcutsPage" class="transform absolute" style="width: calc(var(--unscaledScreenHeight) * 1920px / 1080); height:  calc(var(--unscaledScreenHeight) * 50px / 1080); --h-anchor: 50%; --v-anchor: 50%; --pivot-x: -50%; --pivot-y: -50%; top: calc(var(--v-anchor) + calc(var(--unscaledScreenHeight) * 495px / 1080)); transform-origin: 50% 50%; opacity: 1;"><ui-resource-element resource-id="{93025B24-B5CD-4A25-BE31-EF67B7747DDF}" name="ShortcutsBar_Left" class="transform flex flex-row justify-expand items-stretch children-spacing gap-first-item absolute" templateid="{93025B24-B5CD-4A25-BE31-EF67B7747DDF}" id="pDmnKrVg" style="height:  calc(var(--unscaledScreenHeight) * 50px / 1080); --h-anchor: 50%; --v-anchor: 50%; --pivot-x: 0%; --pivot-y: -100%; left: calc(var(--h-anchor) + calc(var(--unscaledScreenHeight) * -940px / 1080)); top: calc(var(--v-anchor) + calc(var(--unscaledScreenHeight) * 25px / 1080)); transform-origin: 0% 100%; min-width: unsetpx; min-height: unsetpx; max-width: unsetpx; max-height: unsetpx; --selfSpacing: calc(var(--unscaledScreenHeight) * 18px / 1080); padding-left: calc(var(--unscaledScreenHeight) * 6px / 1080); padding-top: calc(var(--unscaledScreenHeight) * 6px / 1080); padding-right: calc(var(--unscaledScreenHeight) * 6px / 1080); padding-bottom: calc(var(--unscaledScreenHeight) * 6px / 1080); width: auto; --gapShortcutsBar_Left: calc(var(--screenHeight) * 18px / 1080);"></ui-resource-element></input-bar>

 

Thank you very much @Shrek1970

For those who have MSFS 2024 via Steam, the path is:

....\Steam\steamapps\common\Limitless\Packages\fs-base-ui\cookedcomps

Edited November 1, 2025Nov 1 by Area

I get the impression both here and on the official forums, that a lot of beta users have only played MSFS in beta and not other products. So their knowledge of what a beta process should be is purely one sided, from my perspective Asobo/MS have long since got these beta processes wrong and these fundamental mess ups of new bugs/features are a prime example of not understanding themselves how to go about things. 

If this new UI change was deliberate, why add it now? When the beta is coming to a close? It makes zero sense, if it is indeed a bug then again the question needs to be asked - Why is there no internal testing team? No internal regression testing team? No quality control? 

I've said it before and I'll say it forever more, Asobo are extremely talented on hand, but they're very amateurish on the other hand and not seemingly learning from past mistakes & issues.

Some people keep crying. 

Other people keep flying. 

I completed two successful flights today, with the Blacksquare TBM 850 - my new favorite GA airplane.

Smooth as butter, from takeoff to touchdown.

Flight 1: EFHK (Helsinki) - to EYVI (Vilnius) - the new airport from Lisium Design

Flight 2: EYVI - EFHK

I had 6 different applications running outside the sim, with no issues whatsoever:

1. AeroTune
2. Active Sky (new beta build available)
3. REX Atmos (new beta build available)
4. FSHud
5. The Garmin Trainer software for the TDS GTN 750NXi
6. Traffic injection via FSTL

And I have a very middle of the road/lower end system, with a 3060TI

But, yeah, keep spreading fake news and misinformation about "lack of quality control" and "Asobo/Microsoft incompetence".

😉

Edited November 1, 2025Nov 1 by Ricardo41

59 minutes ago, LRBS said:

I totally agree with you, but that's not the problem. The issue at hand, as I mentioned, is the way they think and let go of new things that are totally ridiculous and unreal. If people still don't understand how it works, if there are programming errors, and those checking (if they actually do) consider this normal and accept it, even in a beta stage, then we really have a bigger issue. Unfortunately, this is not the only issue that shows their lack of understanding of this product. All we can hope for is the best, and then stuff like this pops up. Discouraging even for a beta product. 

I am not going to "ignore you" by the way. I am flying the DC6 in the latest update and do not have this on my screen. I turned off the external hud view and all is well. 

There is nothing discouraging me on this beta. It's working wonderfully.

The message disappears after a few seconds on taxi....

12 minutes ago, Ricardo41 said:

Some people keep crying. 

Other people keep flying. 

I completed two successful flights today, with the Blacksquare TBM 850 - my new favorite GA airplane.

Smooth as butter, from takeoff to touchdown.

Flight 1: EFHK (Helsinki) - to EYVI (Vilnius) - the new airport from Lisium Design

Flight 2: EYVI - EFHK

I had 6 different applications running outside the sim, with no issues whatsoever:

1. AeroTune
2. Active Sky (new beta build available)
3. REX Atmos (new beta build available)
4. FSHud
5. The Garmin Trainer software for the TDS GTN 750NXi
6. Traffic injection via FSTL

And I have a very middle of the road/lower end system, with a 3060TI

But, yeah, keep spreading fake news and misinformation about "lack of quality control" and "Asobo/Microsoft incompetence".

😉

Fully agree. Nearly everything is working just fine. Better, in fact. 

Criticisms are deserved towards asobo. This beta build deserves little of it...It makes me think people are just reading things online.

Or maybe time to find a different hobby for a few days? 

19 hours ago, MarcG said:

meh still no VR Mouse/Controller fix, the wait continues..... 🙄

I noticed that if i leave the controllers off when loading MSFS 2024 that the mouse retains full functionality in VR as long as i don't use the controllers. ... Its easy to do with Pimax, not sure of others like Quest 3 which don't require a bootup. Maybe remove their batteries?

Edited November 1, 2025Nov 1 by John-Allen

6 minutes ago, John-Allen said:

I noticed that if i leave the controllers off when loading MSFS 2024 that the mouse retains full functionality in VR as long as i don't use the controllers. ... Its easy to do with Pimax, not sure of others like Quest 3 which don't require a bootup. Maybe remove their batteries?

I've since posted that it's fixed after all 🙂

Am I the only one - again with this build as with the previous - that don't feel the need for swapping default DLSS v310.1 ? I had good performance and not yet warning of VRAM overused.

4 hours ago, Shrek1970 said:

If you want to remove the Shift+C to exit aircraft annoying pop up this was posted by a legend over at the MSFS forums. This method keeps all other UI tabs operational.

Navigate to D:\MSFS24\Microsoft Flight Simulator 2024\Content\Packages\fs-base-ui\cookedcomps  (or where your contents folder is located)

find the file {5D8D140B-0F7E-4213-B2F7-E16727D57DDC}.html

Open the file in notepad

delete all contents and replace with

<input-bar resource-id="{5D8D140B-0F7E-4213-B2F7-E16727D57DDC}" resource-path="coui://html_ui/VFS/components/shortcutspage/shortcutspage.uxml" name="ShortcutsPage" class="transform absolute" style="width: calc(var(--unscaledScreenHeight) * 1920px / 1080); height:  calc(var(--unscaledScreenHeight) * 50px / 1080); --h-anchor: 50%; --v-anchor: 50%; --pivot-x: -50%; --pivot-y: -50%; top: calc(var(--v-anchor) + calc(var(--unscaledScreenHeight) * 495px / 1080)); transform-origin: 50% 50%; opacity: 1;"><ui-resource-element resource-id="{93025B24-B5CD-4A25-BE31-EF67B7747DDF}" name="ShortcutsBar_Left" class="transform flex flex-row justify-expand items-stretch children-spacing gap-first-item absolute" templateid="{93025B24-B5CD-4A25-BE31-EF67B7747DDF}" id="pDmnKrVg" style="height:  calc(var(--unscaledScreenHeight) * 50px / 1080); --h-anchor: 50%; --v-anchor: 50%; --pivot-x: 0%; --pivot-y: -100%; left: calc(var(--h-anchor) + calc(var(--unscaledScreenHeight) * -940px / 1080)); top: calc(var(--v-anchor) + calc(var(--unscaledScreenHeight) * 25px / 1080)); transform-origin: 0% 100%; min-width: unsetpx; min-height: unsetpx; max-width: unsetpx; max-height: unsetpx; --selfSpacing: calc(var(--unscaledScreenHeight) * 18px / 1080); padding-left: calc(var(--unscaledScreenHeight) * 6px / 1080); padding-top: calc(var(--unscaledScreenHeight) * 6px / 1080); padding-right: calc(var(--unscaledScreenHeight) * 6px / 1080); padding-bottom: calc(var(--unscaledScreenHeight) * 6px / 1080); width: auto; --gapShortcutsBar_Left: calc(var(--screenHeight) * 18px / 1080);"></ui-resource-element></input-bar>

 

Thank you! Didn't have time to test (and record) the official forum's post. It works great here. Unfortunately, the HUD instruments in cockpit view that appears immediately after selecting an external view is... annoying. Anyone found a workaround (except not using once an external view)? Restarting the flight doesn't remove these instrument. Only relaunching the whole MSFS...

Edited November 1, 2025Nov 1 by vbazillio

47 minutes ago, vbazillio said:

Am I the only one - again with this build as with the previous - that don't feel the need for swapping default DLSS v310.1 ? I had good performance and not yet warning of VRAM overused.

I don't switch anymore myself, High frame rates and smooth for me. No issues