Cyborg Evo + other controllers in BF 1942

[Acen Jay]

Big problem with the Cyborg Evo, it doesn't work when other game controllers are plugged in, like the Nostromo N52 Speedpad and Logitech Dual Action gamepad. I've done my research, and other joysticks such as the Logitechs have no such problem. Is there any way a new driver release can be made to fix this?

This joystick would be the best out there if this is made possible. The only complaints I've read about the Cyborg Evo on other forums is the drifting left, fixed by the latest driver release, very hard to find dead zone on throttle, fixed by DeadBander, and the fact that it won't work when other game controllers are connected.

The Logitechs seem to work fine with other game controllers connected, I've read you can set the dead zone for throttle, but that they tend to drift left, which I don't know if it has been fixed. Also read that they don't last that long, maybe a couple months.

[UKSupport]

Hi,

It's not something that can be fixed with a driver. The issue is to do with the order in which Windows lists the devices in Game Controllers. Every game controller has a unique identifying number made up from a VID (vendor ID) and a PID (product ID). This is so that when you plug it in Windows looks for a driver that's associated with that number. Now Windows lists the devices numerically based on this VID and PID number. Logitech's VID is 046D whereas ours is 06A3 - as our VID is numerically higher Windows will list it after the Logitech. I'm not sure of the VID of Belkin but it will be "lower" than ours and hence Windows will list it before the evo.

Attached is a file which can be used to swap around the controller IDs of the game controllers you have plugged in. Use it to swap the Cyborg so that it is on controller ID 1 and the Nostromo is on ID 2 and see if that helps.

[Acen Jay]

Game controllers in Windows Control Panel only lists the devices in alphabetical order.

I already tried the JoyIDs utility after seeing another person trying to troubleshoot the same problem in another forum, but it didn't work for me either. Here's the link:

http://www.fpscentral.com/forums/showthread.php?t=77055&highlight=joystick

I tried unplugging the Speedpad and starting a game like the person did in the thread, and sure enough, both the Speedpad and the joystick worked. Once a new map loaded though, back to the same problem, with the joystick not detected in-game unless the Speedpad was unplugged. Also tried disabling the HID-compliant game controller in the Device Manager for the Speedpad, but there is a big loss of functionality for the Speedpad as Custom Profiles with key assignments won't work. Too much of a hassle.

I'm sure that Saitek devices probably work together in the same game, and both a Saitek joystick and Saitek gamepad for example would be detected in a game like BF1942/Vietnam. If the Saitek joystick won't work in conjunction with other brand devices though it creates quite a hassle.

Any suggestions for a fix are welcome. I may have to look for a different joystick if the problem can't be resolved though.

[UKSupport]

I'm having trouble finding it but I do remember finding a post on a forum somewhere that said you could fix this by changing a line in one of Battlefield's files. Can't find it at the moment though - maybe you can look too in some of the usual Battlefield forums? If I find it I'll let you know.

[Acen Jay]

I appreciate it. Let me know if you find it. I'll also do some searching in the BF forums I visit too. Any ideas on some good keywords that may help in the search?

[UKSupport]

Do a search for Nostromo or Cyborg...

[UKSupport]

Ah - found it.

http://www.bfnation.net/forums/viewtopic.php?t=5455&highlight=multipler+controllers

[Acen Jay]

Did a search on:

http://www.forumplanet.com/planetbattlefield/

The magic key word in the search was air.con, and here is the magic post:

Edited by Airnate on Feb 2 2004 4:13PM
I did a search in the Battlefield 1942 directory and I don't see any common.con files. Also, where do I need to place the user.con file? If I only copy 'air' commands into the user.con file, how would it know to look for 'infantry' type commands in the same file? Not saying I'm doing that, but I'm just curious. Shouldn't this have to be called something else or placed in a sub-folder? I'm sort of confused by this. I'm glad you got it working this way, so I'm asking your help to get me up and running. Thanks. Looking forward to your reply!

[added Feb 2 2004 4:12PM]

Update: I'm going to edit the file, and simply choose the read-only option in the properties for air.con. This might work. I'll post back here shortly.

[added Feb 2 2004 4:46PM]

Solution:

Hat Switch Problem Solved! Air.con Now Saves Edited Information!

Well after looking around on some different forums, and piecing everyones problem regarding the hat switch, I found that when you edit the air.con file it automatically gets over-written by the v1.6 patch every time the game is opened, (we all know that now). Well what I did was right-click the air.con file and checked the Read-Only box. Alright, then I went into game, and checked my controls and saw they were all messed up! Thats ok. I launched game to try them anyways, and they don't work. Now here comes the good part! For some reason when I checked the Read-Only option on air.con it created another file here:

C:\Documents and Settings\ Your Computer Name \My Documents\Battlefield 1942\mods\BF1942\Settings\Profiles\ Your Profile Name \Controls

I just did a simple search on air.con. This directory could vary depending on what Operating System you have. I have WindowsXP. Now what I did was, since what I edited in the original Battlefield 1942 Directory was still saved, I copied the air.con file from there and pasted in my Document and Settings Directory making sure it was still Read-Only in both directories. After you do this, start the game up and notice the Air Controls are somewhat making sense again. Now try joining or creating a game, and "bamm!" it works! Hat Switch along with all axis, controls, buttons, throttles, etc work just like v1.5! I hope this all works for you as a temporary solution while we have to deal with this v1.6. Enjoy!

[added Feb 2 2004 4:47PM]

Bumping for other players to see. I guess editing doesn't Bump threads? Might want to make a sticky of this.

Here's a link to the thread where the post is:
http://www.forumplanet.com/planetbattlefield/topic.asp?fid=5557&tid=1279164&p=1#13697139

Looks like the problem may be partly due to EA's patches. Hopefully this post here will help a lot of other people who want to use two game controllers for Battlefield. Peace!

[Drayu]

Not sure why I never noticed this thread, but you don't have to use joyId to fix the problem. Just go into the air.con and change the IDF_Controller number appropriately. eg, if you have two controllers and your evo is listed second, then it is IDF_controller 1 and the other controller is IDF_controller 0

[r|p]

Not sure why I never noticed this thread, but you don't have to use joyId to fix the problem. Just go into the air.con and change the IDF_Controller number appropriately. eg, if you have two controllers and your evo is listed second, then it is IDF_controller 1 and the other controller is IDF_controller 0



I dont have the IDF_Controller listed in my air.con file. The problem Im having is that when I go to see if all my buttons are working, when I move the stick, the trigger, and buttons 3,2, and 4 light up. I have the N52 nostromo as well.

[r|p]

Sigh.......looks like im going back to Logitec :(

[Drayu]

How do I keep missing this thread!

Sorry man, and don't go back to logitech just yet. You will inevitably have the same problem with two controllers b/c it is a BF issue, not logitech or saitek.

Do this. Post your air.con file in an attachment here. Let me fix it for ya. I will make it so that the stick controls all axis functions. I would then map everything else using the respective profiling software.

[r|p]

Ok...I took the original one back....now the button dont light up when NOT pressed......but still in-game calibration wont work....now I found 3 air files.....sending custom controls.


rem *** Controlmaps ***

rem *** Player Input ***
ControlMap.create AirPlayerInputControlMap
ControlMap.addKeysToAxisMapping c_PIThrottle IDFKeyboard IDKey_W IDKey_S
ControlMap.addKeysToAxisMapping c_PIYaw IDFKeyboard IDKey_D IDKey_A
ControlMap.addAxisToAxisMapping c_PIPitch IDFGameController_0 IDAxis_2 0
ControlMap.addKeysToAxisMapping c_PIPitch IDFKeyboard IDKey_ArrowUp IDKey_ArrowDown 1
ControlMap.addAxisToAxisMapping c_PIRoll IDFGameController_0 IDAxis_0 0
ControlMap.addKeysToAxisMapping c_PIRoll IDFKeyboard IDKey_ArrowRight IDKey_ArrowLeft 1
ControlMap.addButtonToTriggerMapping c_PIAltFire IDFMouse IDButton_1 c_CMPushAndHold
ControlMap.addKeyToTriggerMapping c_PIAltFire IDFKeyboard IDKey_Numpad0 c_CMPushAndHold 1
ControlMap.addKeyToTriggerMapping c_PIMenuSelect1 IDFKeyboard IDKey_1 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIMenuSelect2 IDFKeyboard IDKey_2 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIMenuSelect3 IDFKeyboard IDKey_3 c_CMNonRepetive
ControlMap.addButtonToTriggerMapping c_PIFire IDFMouse IDButton_0 c_CMPushAndHold
ControlMap.addKeyToTriggerMapping c_PIFire IDFKeyboard IDKey_Space c_CMPushAndHold 1
ControlMap.addKeyToTriggerMapping c_PIMouseLook IDFKeyboard IDKey_LeftShift c_CMPushAndHold
ControlMap.addKeyToTriggerMapping c_PIMenuSelect4 IDFKeyboard IDKey_4 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIMenuSelect5 IDFKeyboard IDKey_5 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIMenuSelect6 IDFKeyboard IDKey_6 c_CMNonRepetive
ControlMap.addAxisToAxisMapping c_PIMouseLookX IDFMouse IDAxis_0 0
ControlMap.addAxisToAxisMapping c_PIMouseLookY IDFMouse IDAxis_1 0

rem *** Additional variables***
game.setAirKeyboardSensitivity 0.500000
game.setAirMouseSensitivity 0.750000
game.setAirMouseInvert 1

rem *** Common Player Input ***
ControlMap.addKeyToTriggerMapping c_PISayAll IDFKeyboard IDKey_K c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PISayTeam IDFKeyboard IDKey_L c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIUse IDFKeyboard IDKey_E c_CMPushAndHold
ControlMap.addKeyToTriggerMapping c_PIMenuSelect9 IDFKeyboard IDKey_9 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIMap IDFKeyboard IDKey_M c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIZoomMap IDFKeyboard IDKey_N c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIShowScoreBoard IDFKeyboard IDKey_Tab c_CMPushAndHold
ControlMap.addKeyToTriggerMapping c_PICameraMode1 IDFKeyboard IDKey_F9 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PICameraMode2 IDFKeyboard IDKey_F10 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PICameraMode3 IDFKeyboard IDKey_F11 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PICameraMode4 IDFKeyboard IDKey_F12 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIToggleCameraMode IDFKeyboard IDKey_C c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIRadio1 IDFKeyboard IDKey_F1 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIRadio2 IDFKeyboard IDKey_F2 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIRadio3 IDFKeyboard IDKey_F3 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIRadio4 IDFKeyboard IDKey_F4 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIRadio5 IDFKeyboard IDKey_F5 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIRadio6 IDFKeyboard IDKey_F6 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIRadio7 IDFKeyboard IDKey_F7 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIRadio8 IDFKeyboard IDKey_F8 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIScreenShot IDFKeyboard IDKey_PrintScreen c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIToolTip IDFKeyboard IDKey_T c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIShowMapVote IDFKeyboard IDKey_Insert c_CMPushAndHold
ControlMap.addKeyToTriggerMapping c_PIVoteYes IDFKeyboard IDKey_7 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIVoteNo IDFKeyboard IDKey_8 c_CMNonRepetive
ControlMap.addKeysToAxisMapping c_PICameraX IDFKeyboard IDKey_Numpad6 IDKey_Numpad4
ControlMap.addKeysToAxisMapping c_PICameraY IDFKeyboard IDKey_Numpad8 IDKey_Numpad2

[r|p]

Hello? Ive been w8'ing :D

[Drayu]

Hello? Ive been w8'ing :D


Um.....only gave me an hour....lucky I even logged on this late ~12am ANyways, see in your air.con where it says IDF_Controller under the axis. If you have two controllers plugged in, you need to change that from 0 to a 1.

Enjoy

[r|p]

Sorry...just want to get this workin. Ill try it when i get home from work tonight.

[r|p]

Actually....i had some time so I tried it....didnt work :(

[Drayu]

Actually....i had some time so I tried it....didnt work :(


Ok, unplug the nostromo. Get into BF, set up your controls as you like them, save it, play a bit, and then get out and send me the air.con. I will modify it, send it back and then you can plug in both. There maybe a little process that we have to go through to get it to work, but dude, we will get it. Just stupid BF not wanted to recognize two controllers.

[trowan]

I was able to get my new Cyborg Wireless Evo to work with my Belkin n50 by modifying all of the *.con files described in the forums here. Works great - except when I plug in my Logitech Cordless Rumblepad 2 (used for Madden, GTA, etc). Then I'm right back to the Evo not working (the n50 will still work). Is there a known fix for this?

Being the lazy person that I am, I really don't want to plug/unplug devices any time I want to play a game, so if there isn't a fix, does anyone have any experience using a USB switchbox with multiple gaming devices? I was thinking of getting one of these -

http://www.ramelectronics.net/html/usb_switchboxes.html

- specifically, the USB-DSU-2BC model. I would hook up the Evo & Rumblepad to it and switch as needed before starting a game. Anybody think it will work?

[Drayu]

yeah....unplug it....or you have to modify the air.con again to reflect a third controller...but then...when you have only two in...you would have to modify it again. I say..if it is usb...unplug it. makes life easier...especially if you aren't going to use it.

[trowan]

or you have to modify the air.con again to reflect a third controllerI'm at work now, but I believe I set the Evo controller to "IDFGameController_1" when the Evo and n50 are the only devices connected. I'm not sure what you mean by the above qoute; would I change the IDFGameController_1 to something else, change a different value, or add new statements?

[Drayu]

I'm at work now, but I believe I set the Evo controller to "IDFGameController_1" when the Evo and n50 are the only devices connected. I'm not sure what you mean by the above qoute; would I change the IDFGameController_1 to something else, change a different value, or add new statements?


yes...you would have to change it to IDFGameController_2 if you have three controllers plugged in.

[trowan]

yes...you would have to change it to IDFGameController_2 if you have three controllers plugged in.I was afraid you were going to say that; I actually tried that yesterday with no luck.

[Drayu]

I know that is the correct method, as I use it b/c I have MANY sticks hooked up currently, 5 to be exact. Hmm...you may have to go into the whole process that is used for the x45/52 for it to work.

[trowan]

I know that is the correct method, as I use it b/c I have MANY sticks hooked up currently, 5 to be exact. Hmm...you may have to go into the whole process that is used for the x45/52 for it to work.
Maybe I did something wrong; do I just change the "IDFGameController_1" to "IDFGameController_2" in the .con file, or is there more I need to do in the .con files?

[Drayu]

Maybe I did something wrong; do I just change the "IDFGameController_1" to "IDFGameController_2" in the .con file, or is there more I need to do in the .con files?
That should be it. You can also post your air.con so I can look at it. You may want to try the directions in the readme for the x52 (check the common fixes thread for the sticky). You can also watch that video. If you do that with your stick, BF won't be able to overwrite any files, as it likes to do :D

[r|p]

rem *** Controlmaps ***

rem *** Player Input ***
ControlMap.create AirPlayerInputControlMap
ControlMap.addKeysToAxisMapping c_PIThrottle IDFKeyboard IDKey_W IDKey_S
ControlMap.addKeysToAxisMapping c_PIYaw IDFKeyboard IDKey_D IDKey_A
ControlMap.addAxisToAxisMapping c_PIPitch IDFGameController_0 IDAxis_1 1
ControlMap.addKeysToAxisMapping c_PIPitch IDFKeyboard IDKey_ArrowUp IDKey_ArrowDown 1
ControlMap.addAxisToAxisMapping c_PIRoll IDFGameController_0 IDAxis_0 0
ControlMap.addKeysToAxisMapping c_PIRoll IDFKeyboard IDKey_ArrowRight IDKey_ArrowLeft 1
ControlMap.addButtonToTriggerMapping c_PIAltFire IDFGameController_0 IDButton_2 c_CMPushAndHold
ControlMap.addKeyToTriggerMapping c_PIAltFire IDFKeyboard IDKey_Numpad0 c_CMPushAndHold 1
ControlMap.addKeyToTriggerMapping c_PIMenuSelect1 IDFKeyboard IDKey_1 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIMenuSelect2 IDFKeyboard IDKey_2 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIMenuSelect3 IDFKeyboard IDKey_3 c_CMNonRepetive
ControlMap.addButtonToTriggerMapping c_PIFire IDFGameController_0 IDButton_0 c_CMPushAndHold
ControlMap.addKeyToTriggerMapping c_PIFire IDFKeyboard IDKey_Space c_CMPushAndHold 1
ControlMap.addKeyToTriggerMapping c_PIMouseLook IDFKeyboard IDKey_LeftShift c_CMPushAndHold
ControlMap.addKeyToTriggerMapping c_PIMenuSelect4 IDFKeyboard IDKey_4 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIMenuSelect5 IDFKeyboard IDKey_5 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIMenuSelect6 IDFKeyboard IDKey_6 c_CMNonRepetive
ControlMap.addAxisToAxisMapping c_PIMouseLookX IDFMouse IDAxis_0 0
ControlMap.addAxisToAxisMapping c_PIMouseLookY IDFMouse IDAxis_1 0

rem *** Additional variables***
game.setAirKeyboardSensitivity 0.500000
game.setAirMouseSensitivity 0.750000
game.setAirMouseInvert 1

rem *** Common Player Input ***
ControlMap.addKeyToTriggerMapping c_PISayAll IDFKeyboard IDKey_K c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PISayTeam IDFKeyboard IDKey_L c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIUse IDFKeyboard IDKey_E c_CMPushAndHold
ControlMap.addKeyToTriggerMapping c_PIMenuSelect9 IDFKeyboard IDKey_9 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIMap IDFKeyboard IDKey_M c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIZoomMap IDFKeyboard IDKey_N c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIShowScoreBoard IDFKeyboard IDKey_Tab c_CMPushAndHold
ControlMap.addKeyToTriggerMapping c_PICameraMode1 IDFKeyboard IDKey_F9 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PICameraMode2 IDFKeyboard IDKey_F10 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PICameraMode3 IDFKeyboard IDKey_F11 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PICameraMode4 IDFKeyboard IDKey_F12 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIToggleCameraMode IDFKeyboard IDKey_C c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIRadio1 IDFKeyboard IDKey_F1 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIRadio2 IDFKeyboard IDKey_F2 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIRadio3 IDFKeyboard IDKey_F3 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIRadio4 IDFKeyboard IDKey_F4 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIRadio5 IDFKeyboard IDKey_F5 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIRadio6 IDFKeyboard IDKey_F6 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIRadio7 IDFKeyboard IDKey_F7 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIRadio8 IDFKeyboard IDKey_F8 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIScreenShot IDFKeyboard IDKey_PrintScreen c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIToolTip IDFKeyboard IDKey_T c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIShowMapVote IDFKeyboard IDKey_Insert c_CMPushAndHold
ControlMap.addKeyToTriggerMapping c_PIVoteYes IDFKeyboard IDKey_7 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIVoteNo IDFKeyboard IDKey_8 c_CMNonRepetive
ControlMap.addKeysToAxisMapping c_PICameraX IDFKeyboard IDKey_Numpad6 IDKey_Numpad4
ControlMap.addKeysToAxisMapping c_PICameraY IDFKeyboard IDKey_Numpad8 IDKey_Numpad2

[Drayu]

rem *** Controlmaps ***

rem *** Player Input ***
ControlMap.create AirPlayerInputControlMap
ControlMap.addKeysToAxisMapping c_PIThrottle IDFKeyboard IDKey_W IDKey_S
ControlMap.addKeysToAxisMapping c_PIYaw IDFKeyboard IDKey_D IDKey_A
ControlMap.addAxisToAxisMapping c_PIPitch IDFGameController_1 IDAxis_1 1
ControlMap.addKeysToAxisMapping c_PIPitch IDFKeyboard IDKey_ArrowUp IDKey_ArrowDown 1
ControlMap.addAxisToAxisMapping c_PIRoll IDFGameController_1 IDAxis_0 0
ControlMap.addKeysToAxisMapping c_PIRoll IDFKeyboard IDKey_ArrowRight IDKey_ArrowLeft 1
ControlMap.addButtonToTriggerMapping c_PIAltFire IDFGameController_1 IDButton_2 c_CMPushAndHold
ControlMap.addKeyToTriggerMapping c_PIAltFire IDFKeyboard IDKey_Numpad0 c_CMPushAndHold 1
ControlMap.addKeyToTriggerMapping c_PIMenuSelect1 IDFKeyboard IDKey_1 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIMenuSelect2 IDFKeyboard IDKey_2 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIMenuSelect3 IDFKeyboard IDKey_3 c_CMNonRepetive
ControlMap.addButtonToTriggerMapping c_PIFire IDFGameController_0 IDButton_0 c_CMPushAndHold
ControlMap.addKeyToTriggerMapping c_PIFire IDFKeyboard IDKey_Space c_CMPushAndHold 1
ControlMap.addKeyToTriggerMapping c_PIMouseLook IDFKeyboard IDKey_LeftShift c_CMPushAndHold
ControlMap.addKeyToTriggerMapping c_PIMenuSelect4 IDFKeyboard IDKey_4 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIMenuSelect5 IDFKeyboard IDKey_5 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIMenuSelect6 IDFKeyboard IDKey_6 c_CMNonRepetive
ControlMap.addAxisToAxisMapping c_PIMouseLookX IDFMouse IDAxis_0 0
ControlMap.addAxisToAxisMapping c_PIMouseLookY IDFMouse IDAxis_1 0

rem *** Additional variables***
game.setAirKeyboardSensitivity 0.500000
game.setAirMouseSensitivity 0.750000
game.setAirMouseInvert 1

rem *** Common Player Input ***
ControlMap.addKeyToTriggerMapping c_PISayAll IDFKeyboard IDKey_K c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PISayTeam IDFKeyboard IDKey_L c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIUse IDFKeyboard IDKey_E c_CMPushAndHold
ControlMap.addKeyToTriggerMapping c_PIMenuSelect9 IDFKeyboard IDKey_9 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIMap IDFKeyboard IDKey_M c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIZoomMap IDFKeyboard IDKey_N c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIShowScoreBoard IDFKeyboard IDKey_Tab c_CMPushAndHold
ControlMap.addKeyToTriggerMapping c_PICameraMode1 IDFKeyboard IDKey_F9 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PICameraMode2 IDFKeyboard IDKey_F10 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PICameraMode3 IDFKeyboard IDKey_F11 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PICameraMode4 IDFKeyboard IDKey_F12 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIToggleCameraMode IDFKeyboard IDKey_C c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIRadio1 IDFKeyboard IDKey_F1 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIRadio2 IDFKeyboard IDKey_F2 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIRadio3 IDFKeyboard IDKey_F3 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIRadio4 IDFKeyboard IDKey_F4 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIRadio5 IDFKeyboard IDKey_F5 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIRadio6 IDFKeyboard IDKey_F6 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIRadio7 IDFKeyboard IDKey_F7 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIRadio8 IDFKeyboard IDKey_F8 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIScreenShot IDFKeyboard IDKey_PrintScreen c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIToolTip IDFKeyboard IDKey_T c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIShowMapVote IDFKeyboard IDKey_Insert c_CMPushAndHold
ControlMap.addKeyToTriggerMapping c_PIVoteYes IDFKeyboard IDKey_7 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIVoteNo IDFKeyboard IDKey_8 c_CMNonRepetive
ControlMap.addKeysToAxisMapping c_PICameraX IDFKeyboard IDKey_Numpad6 IDKey_Numpad4
ControlMap.addKeysToAxisMapping c_PICameraY IDFKeyboard IDKey_Numpad8 IDKey_Numpad2



Ok I made changes to it, just copy paste it. Just one more thing, you don't have the throttle mapped? Any reason why? And what controller is this again, the wireless or not?

[trowan]

That should be it. You can also post your air.con so I can look at it. You may want to try the directions in the readme for the x52 (check the common fixes thread for the sticky). You can also watch that video. If you do that with your stick, BF won't be able to overwrite any files, as it likes to do :DHere is my air.con that works with the Evo Wireless & n50 if you want to point out my mistake. Thanks.

---------------------------------------------
rem *** Controlmaps ***

rem *** Player Input ***
ControlMap.create AirPlayerInputControlMap
ControlMap.addAxisToAxisMapping c_PIThrottle IDFGameController_1 IDAxis_2 0
ControlMap.addAxisToAxisMapping c_PIYaw IDFGameController_1 IDAxis_3 0
ControlMap.addAxisToAxisMapping c_PIPitch IDFGameController_1 IDAxis_1 1
ControlMap.addKeysToAxisMapping c_PIPitch IDFKeyboard IDKey_ArrowUp IDKey_ArrowDown 1
ControlMap.addAxisToAxisMapping c_PIRoll IDFGameController_1 IDAxis_0 0
ControlMap.addKeysToAxisMapping c_PIRoll IDFKeyboard IDKey_ArrowRight IDKey_ArrowLeft 1
ControlMap.addButtonToTriggerMapping c_PIAltFire IDFGameController_1 IDButton_2 c_CMPushAndHold
ControlMap.addButtonToTriggerMapping c_PIAltFire IDFGameController_1 IDButton_3 c_CMPushAndHold 1
ControlMap.addKeyToTriggerMapping c_PIMenuSelect1 IDFKeyboard IDKey_Y c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIMenuSelect2 IDFKeyboard IDKey_U c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIMenuSelect3 IDFKeyboard IDKey_I c_CMNonRepetive
ControlMap.addButtonToTriggerMapping c_PIFire IDFGameController_1 IDButton_0 c_CMPushAndHold
ControlMap.addButtonToTriggerMapping c_PIFire IDFGameController_1 IDButton_7 c_CMPushAndHold 1
ControlMap.addKeyToTriggerMapping c_PIMouseLook IDFKeyboard IDKey_LeftShift c_CMPushAndHold
ControlMap.addKeyToTriggerMapping c_PIMenuSelect4 IDFKeyboard IDKey_O c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIMenuSelect5 IDFKeyboard IDKey_P c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIMenuSelect6 IDFKeyboard IDKey_T c_CMNonRepetive
ControlMap.addAxisToAxisMapping c_PIMouseLookX IDFMouse IDAxis_0 0
ControlMap.addAxisToAxisMapping c_PIMouseLookY IDFMouse IDAxis_1 0

rem *** Additional variables***
game.setAirKeyboardSensitivity 0.500000
game.setAirMouseSensitivity 0.080698
game.setAirMouseInvert 0

rem *** Common Player Input ***
ControlMap.addKeyToTriggerMapping c_PISayAll IDFKeyboard IDKey_J c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PISayTeam IDFKeyboard IDKey_K c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIUse IDFKeyboard IDKey_End c_CMPushAndHold
ControlMap.addButtonToTriggerMapping c_PIUse IDFGameController_1 IDButton_5 c_CMPushAndHold 1
ControlMap.addButtonToTriggerMapping c_PIMenuSelect9 IDFGameController_1 IDButton_4 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIMenuSelect9 IDFKeyboard IDKey_Space c_CMNonRepetive 1
ControlMap.addKeyToTriggerMapping c_PIMap IDFKeyboard IDKey_Q c_CMNonRepetive
ControlMap.addButtonToTriggerMapping c_PIMap IDFGameController_1 IDButton_1 c_CMNonRepetive 1
ControlMap.addKeyToTriggerMapping c_PIZoomMap IDFKeyboard IDKey_N c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIShowScoreBoard IDFKeyboard IDKey_LeftAlt c_CMPushAndHold
ControlMap.addKeyToTriggerMapping c_PIShowScoreBoard IDFKeyboard IDKey_Tab c_CMPushAndHold 1
ControlMap.addKeyToTriggerMapping c_PICameraMode1 IDFKeyboard IDKey_F9 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PICameraMode2 IDFKeyboard IDKey_F10 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PICameraMode3 IDFKeyboard IDKey_F11 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PICameraMode4 IDFKeyboard IDKey_F12 c_CMNonRepetive
ControlMap.addButtonToTriggerMapping c_PIToggleCameraMode IDFGameController_1 IDButton_14 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIRadio1 IDFKeyboard IDKey_F1 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIRadio2 IDFKeyboard IDKey_F2 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIRadio3 IDFKeyboard IDKey_F3 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIRadio4 IDFKeyboard IDKey_F4 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIRadio5 IDFKeyboard IDKey_F5 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIRadio6 IDFKeyboard IDKey_F6 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIRadio7 IDFKeyboard IDKey_F7 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIRadio8 IDFKeyboard IDKey_F8 c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIScreenShot IDFKeyboard IDKey_PrintScreen c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIToolTip IDFKeyboard IDKey_Backslash c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIShowMapVote IDFKeyboard IDKey_D c_CMPushAndHold
ControlMap.addKeyToTriggerMapping c_PIVoteYes IDFKeyboard IDKey_A c_CMNonRepetive
ControlMap.addKeyToTriggerMapping c_PIVoteNo IDFKeyboard IDKey_S c_CMNonRepetive
ControlMap.addKeysToAxisMapping c_PICameraX IDFKeyboard IDKey_Numpad6 IDKey_Numpad4
ControlMap.addKeysToAxisMapping c_PICameraY IDFKeyboard IDKey_Numpad8 IDKey_Numpad2

[r|p]

No i use my N52 for throttle. BTW thx..... ill let u know if it works. :D

[Drayu]

TRo-


It looks good, not sure why it wouldn't work. You tried just dropping that into the air.con, on the profile you use? You didn't make it read-only at first? If that didn't work and hold, did you follow the steps that I go through on the readme for the x45/52 (same as in the video)? You have no other controllers plugged in? You are sure they are both listed in the control panel?

[desertdevil]

I cannot get my joystick to work when my n52 is plugged in. I edited the air.con file the way it was posted in here. When I load the game and try the joystick it still doesn't work. When I went back to the air.con file all the changes that were made through editing were not there. I tried again and it still doesn't work. It is like the changes were never made to the file. Even when I look at the cotrols in the game it doesn't show the joystick being setup. If I unplug the n52 i can set up my game using the joystick and it works fine. But the minute I plug in the n52 it quits.

Can you help pls?

[Drayu]

ok, this is what I didn't want to happen..hmm....you are going to have to do the same fix as the x45/52 has to do. It entails making the original air.con read-only, playing a game, going into the BF folder in my documents that gets created, and copying a "fixed" air.con into that folder and making it read-only.


Check out the video and readme in the common fixes thread under either x45 or x52. I will see if I have an Evo air.con lying around that I can put into a file and upload.

[trowan]

It looks good, not sure why it wouldn't work. You tried just dropping that into the air.con, on the profile you use? You didn't make it read-only at first? If that didn't work and hold, did you follow the steps that I go through on the readme for the x45/52 (same as in the video)? You have no other controllers plugged in? You are sure they are both listed in the control panel?I followed all the instructions with the read-only stuff. The air.con file I create works fine as long as the only devices connected are the Evo & n52. If my rumblepad is connected, the Evo doesn't work.

I ended up ordering a 4-port USB switchbox (http://www.cyberguys.com/templates/searchdetail.asp?T1=104+0459&dept=tch3&search=1sb01&child=)
for $12. I figured I would be able to use it with other controllers; I've been thinking of getting a wheel/pedals for some racing games. A friend of mine who plays a lot of these says he in constantly plugging/unplugging devices to get them to work.

[Skull6]

Drayu, FIVE input controllers? Let's see...2 hands + 2 feet + YOUR NOSE = 5?!!! (I'm keeping it clean...this is a family-oriented program, as I see it.) :D

[Drayu]

just testing different configurations with most of them. I don't use them all at the same time.

[Skull6]

I figured as much. Jes funnin...

[desertdevil]

I followed the video and replaced the air.con file and my joystick worked...
But none of the buttons functioned and the twist control I use for rudder did not work either. :mad:

i went into the control settings of the game and could not correct this problem. The Joystick wasn't even showing in the settings. Seeing how there is no software for this particular joystick made by Saitek I am unable to make the adjustments needed. :mad:

After much frustration and alot of cussing I have given up on Saitek. I have since returned the joystick for a refund and will purchase a logitech joystick. i have several buddies who own logitech joystick and use there N52 controllers in conjunction with them in Battlefield 1942 with no issues. I don't understand why theres will work and the Saitek will not.

Good luck to all those reading these forums trying to find a fix...

[Drayu]

The fix is easy. Just have to have patience, and a little willingness. And for the record, there is software that comes with the Evo. But alas, have fun with your new stick.

[xferboy]

I've run into this problem as well with BF1942, and was able to edit my way through the .con files to get my joystick to work. Then with one of the most recent updates that stopped working (I was probably doing something wrong).

What I found ended up working was:

Keep the HID Compliant Game controller (with the ID of: HID\VID_050D&PID_0815&MI_00&COL01\7&22B194CE&0&0000) disabled. But you say the key mappings don't work then.....

well, everytime you boot your machine, re-enable it and then disable it again! When you re-enable it, it picks up it's settings (I only have on set of settings, so I don't have to worry about different profiles) and when you disable it, I retains them for when you play.

Fairly simple. If you need to edit your profile, you do have to re-enable in order for the Load out manager to see the Nostromo.

If you find it a little cumbersome to open the Device manager and enable/disable everytime, there is a simple solution for that.

MS has a wonderful (and dangerous as hell at the same time) little utility called devcon.exe. It's used to control dev's through a command line. You can pick it up from MS's site. I've created a little batch file that I keep on my desktop (I guess I could include it in my StartUp folder, but I haven't) and everytime my machine has been restarted and I want to play, I just launch that.

Here's the guts of the batch:

devcon enable HID\VID_050D*

devcon disable HID\VID_050D*

Works like a charm.

Now if Belkin would just make drivers for the N52 for XP64 :(

thanks all, have fun with this!

[neddycgoon]

Hows this for funny.I just bought a Cyborg evo and while in town saw and purchased a nostromo n52.Can anyone here figure out why I joined this forum and posted in this thread lol.
For anyone who cares its not just BF1942 on my pc.Its every game requiring use of a joystick.The only way I can use the evo is if I disable the nostromo in the device manager.If I leave the nostromo enabled and just unplug the n52 from my pc the evo still doesnt work.The answer is probably just a matter of getting xp to recognise the evo first but I have no idea how to do this.Its a real shame as flight sims with these 2 controllers combined would be just fantastic I reckon.

[bm_kessler]

Just looking for an easy fix to the x52 vs n52 conflict... not even trying to use them simultaneously necessarily (the x52 has more buttons than I can figure out what to do with yet even without switching modes)... however for some stupid reason, I can't disconnect the n52 without my computer instantly rebooting (same result if I try the "safely remove" option).

I suspect the problem has something to do with most software only being written to accept input from one game controller and for some really stupid reason Belkin defined their device as a game controller. If they had someone smart working their marketing department, they would have defined it as a revolutionary new input device to promote two handed productivity, useful not only for game players, but people who edit images in photoshop, spreadsheets in excel, etc.... something akin to 3dConnexion's Spaceball ("... delivers the comfort and efficiency of a proven two-handed work style...")

Alas, the marketers at Belkin haven't been so bright...


But that said, rather than plugging and unplugging, or activating and deactivating devices, does anyone have any idea how Windows prioritized game controllers? Is there a way I can make the x52 the primary game controller, so software that won't see both will see the x52 first?

[I imagine it goes beyond the scope of this forum, being a Saitek forum, to ask if anyone has any idea how to sever the n52 from the game controllers while keeping it as a valid input device.... but I think I'll be going to Belkin to make similiar inquiry presently.]

[UKSupport]

Hi,

You can find an explanation of how Windows prioritises game controllers in my first post of this thread:

http://www.saitekforum.com/showthread.php?t=7896

As you'll also read there, there's nothing that we can do about this, however, editing the air.con file of BF1942 as is mentioned in this thread and Drayu's numerous threads does work.

[Drayu]

Are you using the n52 and x52? If so, this is the wrong forum thread :D Also, look in the x52 thread or the common fixes thread. I believe that there is a sticky for this fix specifically :)

have a great one.

[Cpl. Mitch]

My ST290Pro is very sluggish in BF1942 and the following are in my air.com file:
game.setAirKeyboardSensitivity 0.500000
game.setAirMouseSensitivity 0.750000

Would setting these to 1.0 reduce the sluggishness?

Also, has anyone found where joystick control of tank turrets can be added?

Thanks,

[Davis_DS]

I have been having the sam issue with battlefield using the Belkin Nostromo n52 and the Saitek ST290 Pro.. I renamed all the controller Ids from 0 to 1 and backed it up with the User.con file, Loaded BF 1942, The controls are labeled correctly, but when I load a game, the ST290 is still not recognized!, HELP!!

[Davis_DS]

using user.con did not work, but changing controller from _0 to _1 worked for the air controlss. When I jumped out of the plane and used ST290 pro's Button 4 (programmed for the parachute) I fell to my death.

FIX:
The Parachute is a common command which is specified in Air.con, Infantry.con, & Land.con (THEY MUST MATCH). Since I allready set the air.con to read-only and ran BF1942 the new directory in "My Documents" already existed. Changes made as Follows...

1. Set all ORIGINAL files to writeable! (..\Mods\bf1942\Settings\Profiles\DS\Controls\Air. con ...)

2. Plug in your saitek controller ONLY (no nostromo n52)

3. Load BF 1942 and set the default controls.

4. Add your joystick commands where ever you want (common, land/sea, etc)

5. Save and close (don't need to play the game)

6. open Air.con first and change IDFGameController_0 to IDFGameController_1

7. Common controls are at the bottom of Air.con make changes accordingly.

8. Copy common section and paste into Infantry. con and Land.con so they match
9. Make changes in Infantry.con and Land .con for controller from _0 to _1 as applies.
10. Save Air, Infantry, and Land.con files and change property to READ-ONLY.

11. Copy Air, Infantry, and Land.con files to "My documents>BF1942>etc"

12. Plug in your nostromo n52 load BF 1942, and play...

You will notice that the controls in BF 1942 will be labeld as if it where the default settings. Alas when you load a game your joystick will work.. Since the nostromo n52 maps mouse and keyboard controls no changes should be made to BF controls, just mask the default controls to your nostromo with the profiler.. ENJOY!!

oh yeah

ControlMap.addKeyToTriggerMapping c_PIMouseLook IDFKeyboard IDKey_LeftShift c_CMPushAndHold
ControlMap.addAxisToAxisMapping c_PIMouseLookX IDFMouse ...
ControlMap.addAxisToAxisMapping c_PIMouseLookY IDFMouse ...

this section controls your mouselook in the cockpit.
Change to:

ControlMap.addKeyToTriggerMapping c_PIMouseLook IDFKeyboard IDKey_LeftShift c_CMPushAndHold
ControlMap.addButtonsToAxisMapping c_PIMouseLookX IDFGameController_1 IDButton_7 IDButton_9
ControlMap.addButtonsToAxisMapping c_PIMouseLookY IDFGameController_1 IDButton_6 IDButton_8

this makes it function for the st290 pro...

[Dimento]

Its a damn shame that i'll have to give up using a superior joystick for a far inferior one simply because of this stupid bug. A shame, but still the case.

[Drayu]

It is a shame that the BF series has this problem. Did you guys ever get it worked out? If not, I would be happy to help ya....just let me know.

[saleenvp]

im using an x52 and a p2500 rumble, but the p2500 doesnt work (when i go to the control menu, click on what i want to edit, and press the button on the controler, it does nothing). Is this related to what you guys are talking about? how do i fix it? i tried the joyids thing but it didnt work.

[Drayu]

this is related, you have to edit the air.con file to tell the game to use IDF CONTROLLER_1