Still waiting here as well. Obviously Xbox X players are not important for Microsoft. They won’t give my money back either. It’s a complete ripoff. I’m not able to play the game. I bought the Aviator Edition for almost 300 CAD, so I’m totally ■■■■■■. BTW I’m using a simple wired mouse on my Xbox, no fancy gaming mouse.
When is Microsoft going to solve this problem???
1 Like
The bug is logged so Microsoft is aware. 300+ votes so I am sure that a fix will be coming. Hopefully soon.
The most baffling thing to me is, we dont get an update, explanation, nothing… oh well. I give up. Im obviously wasting my time. Forum is about as much use as the sim.
I just want to remind folks that Asobo are on annual leave.
Full staffing returns next week.
1 Like
Appreciate that. Apologies, but im really fed up. It has been out a month.
1 Like
Should not have been released on Xbox with this problem, there is no way that they couldn’t have known about this issue.
1 Like
It’s obvious that you don’t have an Xbox and you’re speaking from complete ignorance. I’ve tried it with a basic wired mouse with only the 800dpi option and it still does the same thing. It’s an error that occurs on the Xbox when you connect any mouse, whatever it is. To give an opinion you should first have an Xbox and check, don’t make things up.
5 Likes
Yup, I’m not reinstalling this dumpster fire and will stick with 2020 until this bug’s fixed. It’s impossible to fly anything more complex than a bug smasher with this mouse look bug. It’s utterly baffling to me how they’ve managed to miss this mouse issue, I really don’t see how they could’ve. It’s not lost on me that those godawful suits at Microsoft made a seemingly desperate cynical “business decision” to try and cash in and release MSFS before the holidays. They obviously couldn’t have cared less about just how terrible of a state the sim was in as long as they already had dollars/euros in hand from presales.
Worse - And I know that this might sound harsh to our Franco/European friends at Asobo - but how, in good conscience, could they give themselves that “pat on the back” for a “job well done” and then all gleefully go on leave for a month while the rest of us are all still stuck with a sim that barely functions as advertised or as promised (don’t even get me started on “Career” Mode).
It’s almost as if they’ve said:
“We’re so happy you gave us your hard-earned cash ahead of time sight unseen. Wasn’t release day great?!”
“Oh, those bugs? Well, it must be your setup that’s causing them, and totally not due to our complete lack of a competent QA staff.” Oh well, enjoy setting up your controllers, and we’ll see you next year (maybe).*"
I don’t care if it’s against the law for them to work during this time as the onus is still on them to rectify the situation as they were aware of all of these bugs well ahead of time.
Sorry, just blowing off steam and I know this is a rant in a sea of rants.
3 Likes
They will have just run a test script, on a test rig. Like they did with FS2020 for Xbox and only after release realised WASM didn’t work.
My best guess, is it’s something to do with the continua’s input setting in the view binding. But on Xbox it’s locked on, and even creating a new profile it’s the same.
DPI is held on windows input device setting’s.
It dose nothing to the mouse. Also mice are working fine in any other title that supports there use (msfs2020 for example) so the issue is 2024 code.
I don’t have xbox yes, but I’m trying to help.You don’t have to be a complete ■■■.
And no I’m not making things up, although I don’t have an Xbox I did the DPI test on PC and it causes the bug so I’m assuming xbox has the same issue.
If you tested a 800 DPI mouse on XBOX and still have this issue, fair to you at least you tested it out and will help the devs debug more.
No. DPI is held on the mouse, most mice even some office ones allow you to change the stored DPI. Here is some relevent info from a quick google search. Also yes the issue is 2024 code I’m not disputing it. Hopefully the devs fix the issue in the next patch because it is clearly a problem.
-first: i haven’t insulted you like you have done (there you show the kind of person you are). second: you make up things from the moment you give a supposed solution without having the xbox or testing said supposed solution on xbox, since the source code of the game varies from pc to xbox, and you without having the xbox make up the solution. and third: you only had to read to know the error we are talking about and that asobo has not done anything to correct it since day one.
Yeah I think this conversation with you is pointless, you don’t understand my viewpoint, and I think you think I don’t understand your viewpoint. Also you did insult me by calling me ignorant when I’m just trying to help. but ok.
I’m using a non gaming mouse, the same one I currently use on Xbox for flight sim 2020 and it doesn’t work.
3 Likes
Try the fix I mentioned above and see if it works for you.
We appreciate the help, but sorry, it just does nothing for Xbox. Believe me, we’ve tried everything.
4 Likes
in my case, on PC-Steam-
there is some mouse acceleration, you can test this by:
slowly moving the mouse from left to right a certain distance. (camera spins around 2-3 times)
Then repeat the same distance from left to right but this time do it fast. (camera spins around 10+ times)
that is literally how mouse acceleration works.
Well it’s a Logitech B100 mouse, with a native DOI of 800.
The error is as follows: mouse works fine for selecting things in the cockpit, for example gear up, flaps etc. But when you press the right mouse button to enable freelook all hell breaks loose.
So it can’t be a hardware problem. Mouse works fine, freelook is completely broken.
6 Likes