I have a problem with the game:
I changed the controls for the game and now every time there is a cutscene or tutorial where i have to push buttons
my controls don't work , instead i have to change them to default and after the tutorial / cutscene is over i have to change them back.
Anyway to fix this without using the default controls?
No I know what he means - the controls are utterly screwed. If you try to change your key for Fire, or for interact, they work ok while you are doing general exploring.. but when you get into a mission scene, or try to use a vehicle mounted gun, or select a choice of Practice/Novice/Expert for side quests - nothing works.
If you change Fire from being the default of left mouse button, in a mission you'll find you now cannot shoot (notably, from a vehicle for example).
This control key mapping issue for the PC has been present since the game release, and through FOUR patches, and Ubi claims they fixed this in the most recent patch! How are you not getting this right yet Ubi?
Jesus Christ! don't you guy's get it! It not a mapping problem. They have reneamed the keys for a six-axis (Xcrap controller) to keyboard keys period. They didn't bother with writing controls for the PC version. Period. It's the whole reason for all the terrible crap this game has to offer. The mouselook is a renamed keyboard key to simulate an axis on that Xcrap controller.
That's the whole reason the menu doesn't work properly. Haven't you noticed that if you don't double click at exactly a certain speed it doesn't work when you are trying to sell stuff? That's because you are attempting to match the speed at which a six axis controller does it with one click.
And the mouse? Same thing. The idiots made our w,s, a, d simulate the axis for a controller. On 100% or off. Period. I'm listening to these idiots say there's nothing wrong with my mouse and all I can say is "bless your little heart." You deluded stupid little port puppet.![]()
Most those mappings can be fixed by unpacking actionmapxxxxxx.xml files from common.dat and editing them and then repacking the edited xml files in to patch.dat.Originally Posted by nikola-assassin Go to original post
Where most the problems come from with key mapping is Ubi just forgets to remap imports into an Action Mapping.
For example in post #4 Envomni72 mentions mapping Fire button to Interact and how it fails when using a mounted weapon.
Of coarse Ubi didn't add a "common_weapons_remap" Import to the Action of "common_using_mounted_weapon", which would fix the issue.
When you look through the actionmapxxxxxx.xml files there are many imports in actions that Ubi hasn't added.
It's quite an easy thing to miss basic imports in to actions when working out all the whacky combination off keys users will use.
Which in turn causes havoc with mapping in general.
But in all truth, 4 patches in to the life of the game and not to have all those basic key mappings fixed correctly is just straight out lazy on ubi's part.
Since most those key mapping fixes are a 1 line copy and paste here and there throughout the actionmapxxxxxx.xml files.
It's very obvious the devs have no clue and don't follow through properly on their job when you read comments like these in the actionmapxxxxxx.xmlIn a proper release the dev would not need to leave comments in files like this if the dev actually went back through the code properly and found answers instead of a hope for the best half @ss work around.<!-- I hope this isn't used in MP, as Z is the support weapon... conflicting keys. -->
<!--Removing this as it conflicts with controls and nobody knows why it's there!
<!-- Note: This should probably not be here as it's for single player only, and it's not possible to import the single player remapping here or it will break multiplayer. I'd remove this, but I don't want to risk breaking something. -->
What they just wait till enough customers b!tch about it before they'll even fix it, if there's not enough b!tching then we'll just ignore it.
Or hey lets wait for some user to find the error for us and then we make fix it later, maybe not.
It's straight out shameful neglect on Ubi's part.
What I say above is not my personal opinion, it's just straight out facts.
Most these bs key mapping issues I can and have fixed myself.
But since Ubi
1. Doesn't pay me
2. Doesn't offer any tools to deal with their archives
3. Doesn't listen to minority users.
Then I'll be fooked if I'm going to do their job for them.
There is a way using 3rd party software, but I don't think it'll offer the benefits of the proportional steering you get with the controller.Originally Posted by carl70 Go to original post
In other words when you move the joystick to steer or accelerate it's will be all on or all off, just like the keyboard.
You could use GlovePie or JoyToKey to map your control pad to the keyboard and mouse in windows.
In the game setting use the Keyboard/Mouse input.
yes i had this problem with mafia 2 but there was a program i used for far cry 2 and mafia 2 and it worked fine for both them games the programe is called x360ce emulator i have tried my wheel already to see if driving is better and its fantastic driving the cars and jeeps around the island but when i go to get out of the car the wheel controls me walking and shooting and its just not good i need my keyboard to work as wellOriginally Posted by smashly66 Go to original post
Your not getting what I'm saying.
You map your joypad/steering wheel to your keyboard/mouse in windows with GlovePie, not in the game itslef.
Then in the Game Options->Controls-> Control Type you select Keyboard and Mouse to use.
As I said though you won't get proportional steering using your joypad/steering wheel when doing it this way.