3 hours ago, fluffyflops said:

because its a gamer community now and not a simmer community.  The two groups are completly different. 

Simmer community is still playing a game! They just take themselves more serious! LOL

If you are that upset over this minor non-issue, like this A330 dude, then you are neither a gamer nor a simmer; rather, you are someone who has lost control over a substantial portion of his life. 

Aaannnnnyway. Despite all the Pacino "Hoaaah!" around here I just enjoyed another 4 flights without any issues. Another one with the DC-6 using GPS this time, BS Duke Turnine from KTTD (freeware scenery) to KEUG (freeware scenery), BS BonanzaV2 for pattern work and the Fenix 320 from LFPG to Madeira. 

I swear: flight sim people can be amazing, polite and humble and then you have a complete regression for some that have to complain about every little thing. You participated in a beta and complain about one tiny bug. 

If you have a CTD, sound issues, major LOD issues or something about performance then at least say something here. If its about the annoying bug on the screen before you taxi. We've heard you.

Ad nauseam. 

22 hours ago, Tuskin38 said:

jfc there's no talking with you people.

It's.. a.. beta

It didn't go out to the 'general public' it went out to people who consciously opted into an optional beta.

We all understand it's a beta.  Bugs are to be expected.  But I 100% disagree with you if you think bugs that effect EVERYONE and are obvious the second EVERYONE starts a flight (so would be impossible to miss with even rudimentary in-house testing) should be expected - even in a beta.

22 hours ago, lwt1971 said:

A full set of regression tests of all scenarios would've caught this, but since it's an interim beta build, such comprehensive testing is understandably not done. 
 

Did you really just imply this bug would only be noticed in-house if they did a full set of comprehensive regression testing?  We all expect a certain amount of instability and/or bugs in a beta release.  I wouldn't expect a bug that hits 100% of the user base in the face the instant they start a flight to even make it into an alpha build.  I have to assume the development team did their beta compile and sent the new release on its way without even running the new build once in-house.  

Forget it. not worth beating this very very dead horse. 

Edited November 4, 2025Nov 4 by JonathanC

1 hour ago, Ricardo41 said:

If you are that upset over this minor non-issue, like this A330 dude, then you are neither a gamer nor a simmer; rather, you are someone who has lost control over a substantial portion of his life. 

That is a ridiculous statement. It is absolutely clear (based on the number of votes to get that message bar removed) that plenty of simmers do not like it, and find that it affects immersion. Are you saying that (at least) a thousand people have something wrong with them? What may be a "non issue" to you is obviously not a "non issue" to many others. Why can't you just accept that, instead of insinuating that anyone who is upset by it has "lost control over a substantial portion of their life"? 

By the way, guys......PlumCrazy is spot on with his analysis. The fact that it is a beta release is totally irrelevant. If you have a bug that is guaranteed to be seen by anyone who simply loads a plane and enters the cockpit, then how was it missed? Are we really saying that the developers did not check it even once before releasing it to the community beta testers?

Edited November 4, 2025Nov 4 by Christopher Low

3 minutes ago, Christopher Low said:

That is a ridiculous statement. It is absolutely clear (based on the number of votes to get that message bar removed) that plenty of simmers do not like it, and find that it affects immersion. Are you saying that (at least) a thousand people have something wrong with them? What may be a "non issue" to you is obviously not a "non issue" to many others. Why can't you just accept that, instead of insinuating that anyone who is upset by it has "lost control over a substantial portion of their life"? 

How many of them are still in SU3 and not moved to the beta. I for one voted and I am still in SU3. Knowing it was in a beta though I wasn't going ballistic and making clickbait videos to cause a scene not needed. "REMOVE THIS NOW" Wait it out to see what happens even so wait for a community mod like any other normal person would. Its just narcissist behaviour.

2 minutes ago, Christopher Low said:

By the way, guys......PlumCrazy is spot on with his analysis. The fact that it is a beta release is totally irrelevant. If you have a bug that is guaranteed to be seen by anyone who simply loads a plane and enters the cockpit, then how was it missed? Are we really saying that the developers did not check it even once before releasing it to the community beta testers?

You do realise how bugs can happen even when checked. It could of been checked signed off what ever, release the patch and well its broken. Being that it was said to be for photography mode or what ever. It's possible an oversight happened. If you can't hack bugs in a beta happening then you shouldn't be involved in the beta simple really.

56 minutes ago, PlumCrazy said:

Did you really just imply this bug would only be noticed in-house if they did a full set of comprehensive regression testing?  We all expect a certain amount of instability and/or bugs in a beta release.  I wouldn't expect a bug that hits 100% of the user base in the face the instant they start a flight to even make it into an alpha build.  I have to assume the development team did their beta compile and sent the new release on its way without even running the new build once in-house.  

Without really knowing the sequence of events of how this change got merged, before or after whatever set of tests they run before releasing an interim beta build, whether it was missed during testing, whether it was seen and deemed not a show-stopper for an interim beta build, etc etc... without knowing any of these you really can't make assumptions can you, let alone make bold assertions like "without even running the new build once in-house".

My point still remains, this bug creeping into an interim beta build does nothing to my confidence in them as a software development team, regardless of the pontifications and assumptions of the clueless few around here.

Andi if your definition and expectations of quality for alphas and betas differ from Asobo's, well it is what it is. By Asobo's definition of beta builds, especially interim beta builds, new bugs and regression bugs are to be expected. Deal with it, or don't use Asobo's betas.
 

18 minutes ago, carlanthony24 said:

You do realise how bugs can happen even when checked. It could of been checked signed off what ever, release the patch and well its broken. Being that it was said to be for photography mode or what ever. It's possible an oversight happened. If you can't hack bugs in a beta happening then you shouldn't be involved in the beta simple really.

How can this particular bug happen when checked?  It's not like the bug is present under a certain specific scenario or for users with specific hardware or settings enabled.  This bug is present for every single person who enters a flight - in a flight simulator.  Either the specific beta build was run/tested by zero people in-house before release or it was noted and deemed not significant enough to stop the release.  Neither scenario is a good look for Asobo...

4 minutes ago, lwt1971 said:

Without really knowing the sequence of events of how this change got merged, before or after whatever set of tests they run before releasing an interim beta build, whether it was missed during testing, whether it was seen and deemed not a show-stopper for an interim beta build, etc etc... without knowing any of these you really can't make assumptions can you, let alone make bold assertions like "without even running the new build once in-house".

 

If the change was merged after "whatever set of test they run before releasing..." then it supports the theory no testing was done in the released code in-house.  You seem to think that is fine.  I will continue to say that is sloppy software development practice (yes, even for released beta builds).  If the released code was tested, yet in-house "testers" didn't notice this bug, I am at a loss for words.  As a VR user of the sim (I guess I should say game at this point), if the bug was noted in-house and deemed not significant, then I am at an equal loss for words.

We shall agree to disagree...

 

21 minutes ago, carlanthony24 said:

You do realise how bugs can happen even when checked. It could of been checked signed off what ever, release the patch and well its broken. Being that it was said to be for photography mode or what ever. It's possible an oversight happened. If you can't hack bugs in a beta happening then you shouldn't be involved in the beta simple really.

The infamous "flaps" bug happened because they signed it off and it crept in (somehow), it took a community member less than 24 hours to fix and yet we still had to wait 10 days for the major game breaking bug to be fixed by Asobo alongside complete silence from them on the matter, which was unacceptable at that time. 

Besides that, the sheer number of bugs that have gone through beta and into release builds over the years, other times like SU7 for 2020 when there wasn't even a beta but a major game breaking bug for VR/TrackIR users that was released to the public (still not fully fixed), all that and more suggests they don't have an internal testing team or one at least up to the task of finding the obvious issues that most of us see immediately.

That's why this UI issue wasn't a suprise that it happened to me, which is fine because at least they're going to fix it during the beta, but it really shouldn't of got "through" at this late stage in the first place. 

I'm more annoyed we had to wait 6+ weeks for the VR mouse/controller issues to be fixed, which stopped many people actually wanting to beta test in the first place. That's the sort of thing they need to get a grip on.

2 minutes ago, PlumCrazy said:

How can this particular bug happen when checked?  It's not like the bug is present under a certain specific scenario or for users with specific hardware or settings enabled.  This bug is present for every single person who enters a flight - in a flight simulator.  Either the specific beta build was run/tested by zero people in-house before release or it was noted and deemed not significant enough to stop the release.  Neither scenario is a good look for Asobo...

You don't get it even when checked you release a patch and in that time something can break. The bug isn't present for every single person because not everyone is on the beta. Obviously things would be tested you can't help when you release and something breaks when it releases. E.G I could release a livery its been checked by a number of people. I release it to everyone. The tail is just white or some other kind of text is missing but wasn't when checked. I now need to find out the cause of this issue which at times is not simple. 

Like you said maybe it wasn't deemed not significant to hold the beta release, in this day unfortunately you have to live with things you don't like. I certainly wouldn't keep back a beta build over this trivial thing especially if the update is bringing good things to people who are struggling like performance issues. I don't know how long it will take to fix the issue. I then fix said issue and it brings another bug with it maybe performance takes another hit. It is a never ending cycle.