Elem Posted December 26, 2017 Posted December 26, 2017 So I have just installed the Collectors Edition of CloD that I've had from day 1 of it's release but then I very quickly deleted it as it was so horrid. It is now reinstalled on my new PC and updated to BLITZ. The problem now is I have no joystick control at all. My keyboard is recognised but not my Saitek X52 Pro. Is this common or any ideas why gratefully received.
Aap Posted December 26, 2017 Posted December 26, 2017 My controls did not work at first, but was able to remap axes. Weird thing was, however, that when I tried to remap, an axis was almost immediately automatically chosen for me by the game. So I had to be really fast, before an axis was chosen automatically. Got them all mapped, though.
Sokol1 Posted December 26, 2017 Posted December 26, 2017 (edited) If you have many controllers plugged the BLIZ joystcik detection may lost some. Instead detect joystick/throttle/pedal as Joystick0 Joystick1 Joystick2... In BLITZ joystick/throttle... is detected by their real name - to try minimize Windows 10 issue. Example: Cyborg_Graphite-7BD6F401 VKBsim_Tiny_BOX_-91C0D62D With many controllers plugged the long name of some may have not time to write in ConfUser.ini during the first game loading. Try this: Unplug the X-52, start the Game, when game start loading, plug X-52, may force their detection. Verify too if in STEAM interface all options for CONTROLLER is un-ticked. Weird thing was, however, that when I tried to remap, an axis was almost immediately automatically chosen for me by the game. This is caused be a fault (spikes) potentiometer in one of your controllers, when you open the box for assign a axis, this controller send a spurious signal that is detect before the axis you intend to use. Try calibrate your controllers before make assignments, preferable with manufacturer calibration tool. Edited December 26, 2017 by Sokol1
6./ZG26_Loke Posted December 26, 2017 Posted December 26, 2017 You are not the only one Elem. Had same problem in CloD and never got it fixed no matter what I tried. Hoped it would be solved with the BLITZ version, but apparently not :-(
56RAF_Roblex Posted December 26, 2017 Posted December 26, 2017 Odd. I just installed the game and my X52 worked immediately without me doing anything extra.
DaveP63 Posted December 26, 2017 Posted December 26, 2017 (edited) Me as well. Standard X52 and pedals. Installed and working with no issues Edited December 26, 2017 by DaveP63
Elem Posted December 27, 2017 Author Posted December 27, 2017 (edited) If you have many controllers plugged the BLIZ joystcik detection may lost some. Instead detect joystick/throttle/pedal as Joystick0 Joystick1 Joystick2... In BLITZ joystick/throttle... is detected by their real name - to try minimize Windows 10 issue. Example: Cyborg_Graphite-7BD6F401 VKBsim_Tiny_BOX_-91C0D62D With many controllers plugged the long name of some may have not time to write in ConfUser.ini during the first game loading. Try this: Unplug the X-52, start the Game, when game start loading, plug X-52, may force their detection. Verify too if in STEAM interface all options for CONTROLLER is un-ticked. This is caused be a fault (spikes) potentiometer in one of your controllers, when you open the box for assign a axis, this controller send a spurious signal that is detect before the axis you intend to use. Try calibrate your controllers before make assignments, preferable with manufacturer calibration tool. Thanks for answers so far. Sokol, tried your suggestions and no joy (stick!) although I could not find the CONTROLLER options in the STEAM interface? I see though that there is an option to "import" commands. Is anyone able to send me theirs and I can try to see if that works. Edited December 27, 2017 by Elem
6./ZG26_Loke Posted December 27, 2017 Posted December 27, 2017 I see though that there is an option to "import" commands. Is anyone able to send me theirs and I can try to see if that works. I received this ini file, and it did not help me. Maybe you have better luck with it?! X52.zip
Sokol1 Posted December 27, 2017 Posted December 27, 2017 This attached .INI has joystick in old format: Joystick+AXE_Z=-1throttle This don't work in BLITZ.
6./ZG26_Loke Posted December 28, 2017 Posted December 28, 2017 Eh, when you say "This don't work in BLITZ". Do you mean the entire ini file or just the "Joystick+AXE_Z=-1throttle"?
BM357_TinMan Posted December 29, 2017 Posted December 29, 2017 I have x52pro and am running windows 7 64 Maybe it has something to do with windows 8+ What os are you running? Are you using the latest Logitech drivers?
Sokol1 Posted December 29, 2017 Posted December 29, 2017 Eh, when you say "This don't work in BLITZ". Do you mean the entire ini file or just the "Joystick+AXE_Z=-1throttle"? I mean that joystick ID is "Joystick" instead the now needed "Joystick name+code", this is valid for axis and buttons.
Elem Posted December 30, 2017 Author Posted December 30, 2017 I have x52pro and am running windows 7 64 Maybe it has something to do with windows 8+ What os are you running? Are you using the latest Logitech drivers? Win 10 and not had any issues with it. I'm trying to install the latest drivers but I'm getting the message "The requested operation requires elevation"....What the hells that? Also, what do I do with the ini. file?
6./ZG26_Loke Posted December 30, 2017 Posted December 30, 2017 What the hells that? Also, what do I do with the ini. file? You add the lines from the X52 file into the confUser.ini file in the root of CloD. Remember to make a backup of the original ini.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now