Xbox X Controller key mapping issue

[hércules]

Hey.

I am having trouble trying to play The Crew 2 with my Xbox X Controller.

The Dpad is not working, A is down and B is up and thats not everything. Most buttons not even working out right. I play wired because my computer has no bluetooth, i saw other people had this problem but wireless, in my case its the opposite. I tried all the things that worked on other ppl but nothing worked for me. I only played 15 hours this game because this issue made me quit but i would like to be able to play again. Just in case you think or ask about it, its not my controller, I can play GTA, FH4 and many other games with my controller without any issue.

Anyone know some way to fix this?

[76561199205081135]

Hi !

I've taken note of your report, and I'm sorry to hear that controller Issues are impacting your experience in The Crew 2 !

For the purpose of our investigation, in order to isolate the Issue, I invite you to let us know if the problem persists after checking the button mapping of the controller in the Windows {LINK REMOVED}Xbox Accessories app.

I wish you a happy new year, and if you have questions, or for any other Issue, don't hesitate to let us know !


- Ubisoft Support

[hércules]

Yes it does, as i said before i did everything possible to make it work correctly again and this same controller works perfectly in every game i use it. I tried the other controller and i have the same issue with both. And when i try to change the buttons mapping it looks like the game changed them all or recognize them all wrong.

[Tyrian Mollusk]

My partner has the same issue. This is on an normal Xbox 360 controller. I have the same system and type of controller, but my Crew 2 doesn't show the issue.

Their controller works exactly as normal in everything except The Crew 2. Lots of games, and zero problems anywhere but Crew 2

They played Crew 2 normally on this same controller just a week ago.

The whole key mapping screen is messed up. Lots of controls changed to EMPTY, and attempting to set most face buttons just cancels setting the mapping instead of mapping anything. Setting a mapping to the dpad does something, but just shows a small dot instead of anything that makes sense. All the dpad directions look like the same dot, but they seem to work as the different directions, although that doesn't seem to save.

Sometimes the mappings can be sort of set to buttons, but they don't show the correct button that was pressed, and they generally won't save.

The broken controller arrangement appears to be this, based on the mapping icons that show up when that works: pressing Y is Dpad-Right, X is Dpad-Left, A is Dpad-Down, B is Dpad-Up, LS-click is LB, RS-Click is RB, Back is LS-Click, Start is RS-Click, LB is Start, RB is Back, LT is "FWD" in a black box, and RT is "BWD" in a similar black box. Can't tell what the dpad is doing, and can't find anything that corresponds to A or B.

Resetting the mapping to default did not fix it. It often doesn't even change anything.

Verifying the game files did not fix it.

Using a different 360 controller has no effect -- different controller still has the same problems.

Clearing the Documents/The Crew 2 settings folder did not fix it.

Replacing the Bindings_a176ca07.xml file in the settings folder with the corresponding file from my working Crew 2 install with the same controller did not fix it.

Again, ONLY The Crew 2 is having a problem. It should not be this hard to clear and reset whatever is broken, and the Crew 2 should never have been so insanely annoying about its mappings in the first place. I've never seen a game make such a mess out of simple bindings, and it actively interferes with enjoying the game even when it is not completely borked and unplayable like this mess you gave my partner.

[hércules]

Originally posted by Ubi-MrM:

Hi !

I've taken note of your report, and I'm sorry to hear that controller Issues are impacting your experience in The Crew 2 !

For the purpose of our investigation, in order to isolate the Issue, I invite you to let us know if the problem persists after checking the button mapping of the controller in the Windows Xbox Accessories app.[support.xbox.com]

I wish you a happy new year, and if you have questions, or for any other Issue, don't hesitate to let us know !


- Ubisoft Support

So is there any way to fix this? I even would buy a PS4 controller because my friend has one and he doesnt have issues but then i took advantage of the sales for nothing and who says it wont happen again? I really want to play this game

[joridiculous]

Best bet is to edit Binding XML manually, and set it to Read Only.

[hércules]

Originally posted by joridiculous:

Best bet is to edit Binding XML manually, and set it to Read Only.

I already tried that and it didnt work either.

[Tyrian Mollusk]

Originally posted by joridiculous:

Best bet is to edit Binding XML manually, and set it to Read Only.

Also, we can't tell what codes the file uses for some missing inputs (like whatever it thinks the dpad is doing now, since you can map those but they don't save in the xml file). I'm not sure how the xml file works, but it seems like the game ignores things there if it feels like it. It's annoyingly touchy about what it considers mapping conflicts (and the mapping model is decidedly broken, forcing a lot of unnecessary conflicts), so it may just drop things it doesn't agree with.

You might be able to use Steam Input to remp the controller to match the broken mess Crew is using, and add some keyboard keys for the dpad.

[joridiculous]

Originally posted by Tyrian Mollusk:

Originally posted by joridiculous:

Best bet is to edit Binding XML manually, and set it to Read Only.

Also, we can't tell what codes the file uses for some missing inputs (like whatever it thinks the dpad is doing now, since you can map those but they don't save in the xml file). I'm not sure how the xml file works, but it seems like the game ignores things there if it feels like it. It's annoyingly touchy about what it considers mapping conflicts (and the mapping model is decidedly broken, forcing a lot of unnecessary conflicts), so it may just drop things it doesn't agree with.

You might be able to use Steam Input to remp the controller to match the broken mess Crew is using, and add some keyboard keys for the dpad.

huh?
binds for dpad: (Controller followed by wheel)

<Action Name="DPAD_LEFT" IsAnalog="0" />
		<Action Name="DPAD_RIGHT" IsAnalog="0" />
		<Action Name="DPAD_UP" IsAnalog="0" />
		<Action Name="DPAD_DOWN" IsAnalog="0" />

		<Action Name="DPAD_LEFT" IsAnalog="0">
			<Operator Type="AND" />
			<Operator Type="AND" />
			<Channel Type="NOT" Device="TS-PC Racer" Name="UP" SpecialData="151061251" />
			<Channel Type="NOT" Device="TS-PC Racer" Name="RBWD" SpecialData="151061251" />
			<Channel Device="TS-PC Racer" Name="POV1LEFT" SpecialData="151061251" />
		</Action>
		<Action Name="DPAD_RIGHT" IsAnalog="0">
			<Operator Type="AND" />
			<Operator Type="AND" />
			<Channel Type="NOT" Device="TS-PC Racer" Name="UP" SpecialData="151061251" />
			<Channel Type="NOT" Device="TS-PC Racer" Name="RBWD" SpecialData="151061251" />
			<Channel Device="TS-PC Racer" Name="POV1RIGHT" SpecialData="151061251" />
		</Action>
		<Action Name="DPAD_UP" IsAnalog="0">
			<Operator Type="AND" />
			<Operator Type="AND" />
			<Channel Type="NOT" Device="TS-PC Racer" Name="UP" SpecialData="151061251" />
			<Channel Type="NOT" Device="TS-PC Racer" Name="RBWD" SpecialData="151061251" />
			<Channel Device="TS-PC Racer" Name="POV1UP" SpecialData="151061251" />
		</Action>
		<Action Name="DPAD_DOWN" IsAnalog="0">
			<Operator Type="AND" />
			<Operator Type="AND" />
			<Channel Type="NOT" Device="TS-PC Racer" Name="UP" SpecialData="151061251" />
			<Channel Type="NOT" Device="TS-PC Racer" Name="RBWD" SpecialData="151061251" />

[Tyrian Mollusk]

Originally posted by joridiculous:

huh?
binds for dpad: (Controller followed by wheel)

Yes, but we need the broken binding codes, not ones that would work if what the game were doing made any sense. Whatever the game is taking dpad as doesn't have a correlate on the normal controller, and I don't think the game even understands it. It shows up in-game mappings as a weird dot (the same weird dot on all directions, but it still knows they are different inputs), and when the game writes the XML file, it just leaves out the mapping codes.

[joridiculous]

what?
I have played with those settings without any problems. dpad does what dpad does both on controller and wheel. And i have edited all the "unbindables" by hand.

[Tyrian Mollusk]

Is there some part of "the game is broken" that you aren't getting? Face buttons are doing what dpad does (and I mean the games actually thinks face buttons are the dpad), and dpad is doing something else. This isn't just a remapping. The controller handling is pretty opaquely borked.

Like I said, it's not a global problem. My Crew 2 still works normally, while my partner's is broken. I don't see why you're even bringing up wheels.

[joridiculous]

Originally posted by Tyrian Mollusk:

Is there some part of "the game is broken" that you aren't getting? Face buttons are doing what dpad does (and I mean the games actually thinks face buttons are the dpad), and dpad is doing something else. This isn't just a remapping. The controller handling is pretty opaquely borked.

Like I said, it's not a global problem. My Crew 2 still works normally, while my partner's is broken. I don't see why you're even bringing up wheels.

Face buttons? You mean LB / RB`?
What ever. They do not do the same as dpad unless you mapped them to the same.

wheel was there to show config differences. I know, big brain needed but i thought you might understand.

[Tyrian Mollusk]

Originally posted by joridiculous:

Face buttons? You mean LB / RB`?

Face buttons are ABXY, on the face of the controller. LB/RB are shoulder buttons. You'll note the OP is saying "A is down, B is up". That's because the game is MISREADING the controller buttons in a scrambled fashion, putting buttons in different places, with some buttons (like the actual dpad, as opposed to the face buttons that it thinks are the dpad) just nonsense that even the game itself can't make sense of (when it writes out the xml file, these nonsense mappings just become blank entries, with no action/channel code to use hand-making a functional mapping).

They do not do the same as dpad unless you mapped them to the same.

Please go away if you are just going to ignore the actual problem and intentionally derail. It's not helpful to tell people to fix their problem by the problem not existing, nor to insult people because the game has started doing broken things from one week to the next. I already have examples of working mapping files from my Crew 2, but my partner's Crew 2 doesn't understand working mapping files, because they don't fit its scrambled input.

[hércules]

Originally posted by Ubi-MrM:

Hi !

I've taken note of your report, and I'm sorry to hear that controller Issues are impacting your experience in The Crew 2 !

For the purpose of our investigation, in order to isolate the Issue, I invite you to let us know if the problem persists after checking the button mapping of the controller in the Windows Xbox Accessories app.[support.xbox.com]

I wish you a happy new year, and if you have questions, or for any other Issue, don't hesitate to let us know !


- Ubisoft Support

The problem im having is your fault, i bought another controller, this time is a PS4 controller and the controllers are messed up again. Thanks for making me waste my time, waste my money and also thanks for crushing my desire to play this game. For things like this you will never be above Forza Horizon, thanks for your help.

[hércules]

Its a shame that good games are normally owned by people that doesnt care about the games only about the money. This issue is old as hell as many others and people continue reporting them and you continue giving the same fake ways to fix them, trying to make us thinks its our problem or something like that.