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/sho...light=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/viewt...+controlle rs

[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/planetbat...4&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]

Originally Posted by 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

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

[Drayu]

Originally Posted by r|p

Hello? Ive been w8'ing

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