Thank you using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
Are you using Developer Mode or made changes in it? No
Brief description of the issue: The knobs on the 747 will not turn with either the Xbox joystick or mouse . Glareshield Brightness , Aisle Stand , and Dome . Have tried numerous times .
Provide Screenshot(s)/video(s) of the issue encountered:
Do you have the same issue if you follow the OP’s steps to reproduce it?
Yes
Provide extra information to complete the original description of the issue:
Happens also on PC (MS Store version). Also the map brightness and floodlight (both on left & right sides of front panel) don´t work. Keyboard shortcuts still work to operate cabin lights.
If relevant, provide additional screenshots/video:
A. Cannot fix what they broke during a beta, particularly when it appears to be a small thing (of course, we don’t know if it is a small thing, but why/how did something like this get broken in the first place?)
B. Have to wait for an SU to update individual aircraft
It’s especially B. that makes no sense to me. Sure, the core sim is what makes sense to be on the SU cycle, but the aircraft are separate from that and ought to be updated as needed. It’s what 3rd parties do, why can’t the MS/Asobo aircraft be treated similarly?
Do you have the same issue if you follow the OP’s steps to reproduce it?
Yes
Provide extra information to complete the original description of the issue:
Floodlight/dome knobs will not turn, and therefore floodlights cannot be adjusted in the 747. When launching a flight on the runway, the floodlights are on by default and cannot be dimmed. When launching from cold and dark, the floodlights are off by default and cannot be turned on.
This is another bug that I’m pointing out that arose in the beta, that has persisted through 6 weeks of beta testing and has not been addressed. In fact, this one hasn’t even been acknowledged.
Just another reminder that, yes, there are bugs that arise in the betas that do not get addressed by the team. While there are significant bugs that do get addressed, it’s not right to introduce small ones that go un-noted nor unaddressed and end up in the final release candidate.
Yes and Jörg seemed to be agitated by this question and went as far as saying they do fix these bugs hence the reason for delaying SU10.
As such, I’ve made a habit of noting several of these bugs that have arisen during the beta that haven’t been addressed to gently remind him that we weren’t being unreasonable when you posed that question for the Dev Q&A.
Absolutely! I was surprised to hear what was said. There are SO many examples… unreal for it to be blown off like that.
But in a way, it’s like the CEO of a big company not knowing what the apprentice in the mailroom is doing. With Jörg being the Head of Flight Simulator, the question would’ve been better handled by someone closer to the action, perhaps Martial?
Also, if the moderator would follow up when a question is miss-understood or blown off, that would be VERY helpful.
In any case, I sure wish they would make regressions a high priority and focus on them immediately after a release. So frustrating that they don’t.
Thank you using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
For anyone who wants to contribute on this issue, Click on the button below to use this template:
