Saitek X52 Pro Stick & Pedals, TrackIR 5 (also testing FreeTrackNoIR), Belkin n52te, Razer Lycosa keyboard, G9x mouse. And while I'm at it ... on the graphics side, Tri GTX285s, TH2G, 3 Samsung 920nw. (16:10's) I rarely play on the triple monitors, use a Samsung LN32A550 instead.
Requested Info: Spoiler:
Code:
Detected Joystick: Virtual Hid Device
0 ... X Axis [1,30]
1 ... Y Axis [1,31]
2 ... Z Axis [1,32]
3 ... X Rotation [1,33]
4 ... Y Rotation [1,34]
5 ... Z Rotation [1,35]
Invalid Joystick Axis!
type=702 (7), dwOfs=32, name=Move Up/Down
GUID = a36d02f3, c9f3, 11cf, ...
wUsagePage = 5, wUsage = 26
Invalid Joystick Axis!
type=802 (8), dwOfs=36, name=Move Right/Left
GUID = a36d02f3, c9f3, 11cf, ...
wUsagePage = 5, wUsage = 24
Detected Joystick: Saitek X52 Pro Flight Controller
0 ... X Axis [1,30]
1 ... Y Axis [1,31]
2 ... Z Axis [1,32]
3 ... X Rotation [1,33]
4 ... Y Rotation [1,34]
5 ... Z Rotation [1,35]
6 ... Slider [1,36]
Detected Joystick: Saitek Pro Flight Rudder Pedals
0 ... Left Toe [1,30]
1 ... Right Toe [1,31]
5 ... Rudder [1,35]
Last update was great. Just now getting to some free time for the week, hope to check things out in depth later on today. Thanks BIS peoples, will report back soon.
X-52 Configuration Observations. Question for lock-on.
Hello Community,
First post here, mentioning in particular for the other guys out there that bought a Saitek X-52 for their flight sims. Obviously this is relating to a few posts I've read about ARMAII interacting oddly with the mentioned model.
Apologies in advance if I missed a post about this, but the only thread I had found I was unable to access. locked??
That being said, this is for the Saitek X-52 model.(not the pro)
Initially I read individuals were having particular issues with their game crashing when attempting to remap the controls to their flight system. I have confirmed no issue on my side remapping any controls. (Again, reading that it may have been resolved in a software update) prior to me purchasing the game.
Initial config, everything worked excluding firing any weapon from the vehicle requiring me to reconfig the trigger function to fire.
Tested in single-player editor to check quick and worked great.
Then restarted the game and the settings were then gone.
The X-52 & Arma II configurations went through automatically the first time. However, upon the second launching of the game the controls were lost and I ended up being forced to manually re-configure the aircraft controls.
No problems at all when setting throttle + the Y-X-Z Axis + changing firing trigger again.
In case anyone is lost.. I was using in game mapping vs the profile editor from Saitek.
Re-mapped eject key, get-out + landing gear up + down, lastly flaps up & down on the 3 switches on the bottom of the joystick. I found it was best to set the eject to occur when the tab is pushed down. Seeing that as I was getting used to the flying I would ocassionally find myself plummeting 500+ into the ground and it was much faster to push down on the switch then to lift up. Saved me many-a-time.
So, having happily re-mapped the keys and able to fly significantly better the the WASD config prior I am content with current settings.
However, there is one area I would like to see if others have had any luck in.
I may have overlooked multiple times the ability to re-map locking on? I was trying to config the trigger button 1 to lock on if possible and when pressed fully to then allow the selected weapon to fire.
Anyone out there with a similiar setup that wouldn't mind giving a little bit more input on this would be much appreciated.
Best of luck to others that had similiar experiance!
Version 1.59.83244
Item str_disp_server_control listed twice
Updating base class RscStandardDisplay->RscDisplayLoadMission, by hsim\tkoh_beta\ui_h\config.bin/RscDisplayNotFreeze/
Updating base class ->controls, by hsim\tkoh_beta\ui_h\config.bin/RscDisplayNotFreeze/controls/
Updating base class G_Expression->RscControlsGroup, by hsim\tkoh_beta\ui_h\config.bin/RscDisplayDebug/Controls/G_Watch/
Updating base class B_Clear->RscButtonMenu, by hsim\tkoh_beta\ui_h\config.bin/RscDisplayDebug/Controls/B_OK/
Updating base class B_Clear->RscButtonMenu, by hsim\tkoh_beta\ui_h\config.bin/RscDisplayDebug/Controls/B_Cancel/
Updating base class RscButton->RscButtonMenu, by hsim\tkoh_beta\ui_h\config.bin/RscDisplayDebug/Controls/B_Clear/
Updating base class RscShortcutButton->RscButtonMenu, by hsim\tkoh_beta\ui_h\config.bin/RscDisplayCapture/controls/ZoomIn/
Updating base class RscShortcutButton->RscButtonMenu, by hsim\tkoh_beta\ui_h\config.bin/RscDisplayCapture/controls/ZoomOut/
Updating base class RscShortcutButton->RscButtonMenu, by hsim\tkoh_beta\ui_h\config.bin/RscDisplayCapture/controls/Done/
Updating base class RscShortcutButton->RscButtonMenu, by hsim\tkoh_beta\ui_h\config.bin/RscDisplayCapture/controls/Export/
Updating base class RscListBox->RscCombo, by hsim\tkoh_beta\ui_h\config.bin/RscDisplayCustomizeController/Steepness/
Updating base class RscStandardDisplay->RscDisplayDebriefing, by hsim\tkoh_beta\ui_h\config.bin/RscDisplayMissionFail/
Updating base class ->controls, by hsim\tkoh_beta\ui_h\config.bin/RscDisplayMissionFail/controls/
Detected Joystick: Joystick - HOTAS Warthog
0 ... X-Achse [1,30]
1 ... Y-Achse [1,31]
Detected Joystick: Throttle - HOTAS Warthog
0 ... X-Achse [1,30]
1 ... Y-Achse [1,31]
2 ... Z-Achse [1,32]
5 ... Z-Rotation [1,35]
6 ... Schieberegler [1,36]
Detected Joystick: Saitek Pro Flight Rudder Pedals
0 ... X-Achse [1,30]
1 ... Y-Achse [1,31]
5 ... Z-Rotation [1,35]
Error loading control bin\config.bin/RscDisplayStart/controls/CA_Progress/
Warning: looped for animation: ca\wheeled\data\anim\uaz_cargo01_v0.rtm differs (looped now 0)! MoveName: kia_uaz_cargo02
Warning: looped for animation: ca\wheeled\data\anim\uaz_cargo01_v0.rtm differs (looped now 1)! MoveName: uaz_cargo02
Detected Joystick: Joystick - HOTAS Warthog
0 ... X-Achse [1,30]
1 ... Y-Achse [1,31]
Detected Joystick: Throttle - HOTAS Warthog
0 ... X-Achse [1,30]
1 ... Y-Achse [1,31]
2 ... Z-Achse [1,32]
5 ... Z-Rotation [1,35]
6 ... Schieberegler [1,36]
Detected Joystick: Saitek Pro Flight Rudder Pedals
0 ... X-Achse [1,30]
1 ... Y-Achse [1,31]
5 ... Z-Rotation [1,35]
Warning: no idc entry inside class RscDisplayConfigureControllers/controls/CA_RscConfJoysticksButton
Array index out of range
Warning: no idc entry inside class RscDisplayConfigureControllers/controls/CA_RscConfJoysticksButton
Detected Joystick: Joystick - HOTAS Warthog
0 ... X-Achse [1,30]
1 ... Y-Achse [1,31]
Detected Joystick: Throttle - HOTAS Warthog
0 ... X-Achse [1,30]
1 ... Y-Achse [1,31]
2 ... Z-Achse [1,32]
5 ... Z-Rotation [1,35]
6 ... Schieberegler [1,36]
Detected Joystick: Saitek Pro Flight Rudder Pedals
0 ... X-Achse [1,30]
1 ... Y-Achse [1,31]
5 ... Z-Rotation [1,35]
Warning: no idc entry inside class RscDisplayConfigureControllers/controls/CA_RscConfJoysticksButton
Flushing file C:\Users\Marcel\Documents\ArmA 2 Other Profiles\EagleEye\Saved\hsim\TKOH_Beta\missions_H\ TKOH_CP_01.Takistan\continue.ArmA2OASave not possible - still open
No such side
Detected Joystick: Joystick - HOTAS Warthog
0 ... X-Achse [1,30]
1 ... Y-Achse [1,31]
Detected Joystick: Throttle - HOTAS Warthog
0 ... X-Achse [1,30]
1 ... Y-Achse [1,31]
2 ... Z-Achse [1,32]
5 ... Z-Rotation [1,35]
6 ... Schieberegler [1,36]
Detected Joystick: Saitek Pro Flight Rudder Pedals
0 ... X-Achse [1,30]
1 ... Y-Achse [1,31]
5 ... Z-Rotation [1,35]
Warning: no idc entry inside class RscDisplayConfigureControllers/controls/CA_RscConfJoysticksButton
Detected Joystick: Joystick - HOTAS Warthog
0 ... X-Achse [1,30]
1 ... Y-Achse [1,31]
Detected Joystick: Throttle - HOTAS Warthog
0 ... X-Achse [1,30]
1 ... Y-Achse [1,31]
2 ... Z-Achse [1,32]
5 ... Z-Rotation [1,35]
6 ... Schieberegler [1,36]
Detected Joystick: Saitek Pro Flight Rudder Pedals
0 ... X-Achse [1,30]
1 ... Y-Achse [1,31]
5 ... Z-Rotation [1,35]
Array index out of range
Detected Joystick: Joystick - HOTAS Warthog
0 ... X-Achse [1,30]
1 ... Y-Achse [1,31]
Detected Joystick: Throttle - HOTAS Warthog
0 ... X-Achse [1,30]
1 ... Y-Achse [1,31]
2 ... Z-Achse [1,32]
5 ... Z-Rotation [1,35]
6 ... Schieberegler [1,36]
Detected Joystick: Saitek Pro Flight Rudder Pedals
0 ... X-Achse [1,30]
1 ... Y-Achse [1,31]
5 ... Z-Rotation [1,35]
Warning: no idc entry inside class RscDisplayConfigureControllers/controls/CA_RscConfJoysticksButton
Detected Joystick: Joystick - HOTAS Warthog
0 ... X-Achse [1,30]
1 ... Y-Achse [1,31]
Detected Joystick: Throttle - HOTAS Warthog
0 ... X-Achse [1,30]
1 ... Y-Achse [1,31]
2 ... Z-Achse [1,32]
5 ... Z-Rotation [1,35]
6 ... Schieberegler [1,36]
Detected Joystick: Saitek Pro Flight Rudder Pedals
0 ... X-Achse [1,30]
1 ... Y-Achse [1,31]
5 ... Z-Rotation [1,35]
Warning: no idc entry inside class RscDisplayConfigureControllers/controls/CA_RscConfJoysticksButton
Link to 80020c0016c002a0 (Obj-182,131:672) not released
Link to 8002040016e002a1 (Obj-183,129:673) not released
Link to 8001fc0016e002a3 (Obj-183,127:675) not released
Link to 8001f40016e002a5 (Obj-183,125:677) not released
Link to 8001ec0016e002a7 (Obj-183,123:679) not released
Link to 8001e40016e002a8 (Obj-183,121:680) not released
Link to 8001e00016e002ca (Obj-183,120:714) not released
Link to 8001d80016c002c7 (Obj-182,118:711) not released
Link to 8003dc0011400042 (Obj-138,247:66) not released
Link to 8003d40011200044 (Obj-137,245:68) not released
Link to 8002140016c00297 (Obj-182,133:663) not released
Link to 8001a000164002da (Obj-178,104:730) not released
Link to 8000500011e0036c (Obj-143,20:876) not released
I find the controller settings aren`t satisfy yet. Can`t we just have similiar settings like in all other flight sims? Here is a picture of Rise of Flight response settings:
R22 pilot
SYSSpecs: IntelC2Q9650|AsusP5QSE|4GB RAM|ZOTAC GX570|Win7 64bit|TrackIR5|TM HOTAS Warthog (04671)/Saitek Pro Pedals