BoeingSpeedbird

I simply do not understand the quality assurance process. It took me less than a minute to identify the first problem last night, and then a further two minutes to identify an additional two bugs. Questions have to be asked internally at Asobo/Microsoft as to how this can happen, especially annoying as Xbox had the”update” a week later than PC, which I assumed would be for testing/checking. Does the testing not actually happen on an actual Xbox or there is no testing at all - the only understandable explanations for this.

No external lights are working. This has to be a joke.

And no cockpit floodlighting or dome lighting.

1.2.1 just dropped for Xbox. My excitement has quickly turned to disappointment as I cannot select the first SID in the dropdown menu on the MCDU for departure out of EDI. Aaaaargghhhh.

Ok. So, no indication of likely timescale then.

Inibuilds - any indication of when the updated 1.2.1 might arrive for Xbox? Been almost a week since PC folks had their update.

People have only been reporting this as a problem on Xbox until now.

Xbox or pc, and is this A350?

Does anyone have working glareshield lighting in Xbox for a350?

Ah, wasn’t aware that the list doesn’t apply to Xbox (perhaps I’ve missed where it states that), so helpful to know. Anyone at Inibuilds with an Xbox who loads in the a350 will see the engine problem. I presume testing is done by the development team on an actual Xbox.

The 1.2.1 hasn’t arrived for Xbox, but no mention of the engine fan blades fix in the list of 1.2.1 fixes. If it’s not fixed, then I don’t understand why this wouldn’t be.

Update here 1.2.1, but spinning fan blades still broken. Disappointed.

Still not sorted on latest update 1.2.1

Just above the red writing.

This has been reported as a bug repeatedly since the last update.