Feedback - JS Issue - CH Manager

[GOPHUR]

Bump. This isn't going to get fixed without your help.

[eigenman]

OK so I need your help. RAMP says "works for me".

So what does he need to do differently?

I have the same issue. The game is not detecting the CH Control Manager Device 1, hence no JS or rudder. I have Windows XP so it's not a Win 7 issue.

I have a CH Fighterstick and Rudder Pedals. To operate them both in game you need to map these to the single CH Control Manager Device 1. The game will see both JS and Rudder pedals as a single device this way. Much easier to deal with.

Tell Ramp It's not the button mapper. It's mapping the JS and Rudder pedals to a single CH Managed device. Windows will see the mapped devices as 1 JS device instead of 2 separate devices (JS & Rudder) in the Game Controllers Panel in the main control panel in Windows settings.

If he is seeing CH Fighter Stick and CH Rudder Pedals explicitly in the Game Controllers Panel then he's not setting it up right. You should only see CH Control Manager Device 1.

Start with the software uninstalled. Uninstall the CH software if you have to and unplug all CH products.

Steps:

1) Plug in both the fighterstick and rudder pedals.

2) Install the CH software. (Only way I know for it to work)

3) Bring up the CH Control Manager and map both devices in Mapped mode to one CH Managed device.

4) When active in mapped mode you should see only 1 device in the Game Controllers Panel in Windows --> CH Control Manager Device 1

Start the beta and see if you can use either JS or Rudder. Right now the game won't detect my CH Control Manager Device 1 mapped device. Have to have this or it's a real pain to get both JS and rudders going at same time.

It's this mapped mode device that can no longer be detected by the game. Incidentally it was working at some point in the beta because I was flying in the beta last month.

[eigenman]

So I went in game(beta) to try the work around listed by Juuba. This works.

(Windows XP)

So basically you should see only 1 device in the Game Controllers panel in Windows Settings Control panel. ie CH Control Manager Device 1.

If you select this device and then hit Advanced then select CH Control Manager Device 1 as the preferred device, it works again. Not sure why this is needed. It works without selecting it as the preferred device in 1.30 just fine.

So not a big deal since we can get it to work but might cause you some support headaches.

[je5ter]

I still use mine as three seperate devices but they are mapped.

[GOPHUR]

So can I call this good as fixed or what. Seems to be working for us just fine on XP and Win7.

[dangler]

I have somewhat the same problem with different devices. I have Windows XP, thrustmaster stick, saitek throttle, and saitek rudder pedals.

Only the preferred device seems to get recognized by the game. I can change my preferred device around to all three one at a time and only that one stick is recognized in game.

[dangler]

After much joystick detection, restarts, and cfml deletions I finally have it set up and working with my joysticks numbered the correct way.

[juuba]

So can I call this good as fixed or what. Seems to be working for us just fine on XP and Win7.

Yeah, kinda =)

What did you guys do with the Joystick functions/routines whatever, that changed from 1.30.x to 1.31.x ?

What does Windows perform when we click through the sticks as preferred?

Does it write some lines in registry that enable the game to see the sticks?

Why won't them sticks work until we do the click-around?

[loosmoos]

S! gents

noticed that i had same probs to use Jstick in Beta but saw when i checked settings in Windows XP(game Pad in controlpanel)----- had my stick installed as normally but then saw in "Advanced settings" that field were empty, checked that and saw my Stick were there so i activated it there 2 and VOILA...can use Jstick in BETA!!!!

Edited May 30, 2010 by loosmoos

[Whiplash]

I had same issue with my Saitek x52 as suggested here under the preferred device tab in advanced setting in control panel it was'nt set to my controller I selected it as preferred and it worked.

[GOPHUR]

Weird. I just got a Saitek X52 PRo and it was all plug and play.

[eigenman]

Weird. I just got a Saitek X52 PRo and it was all plug and play.

I guess the real issue is that windows doesn't set the controller as the preferred device automatically. Even if it's the only device, the beta doesn't detect it unless it's set to preferred. You may want to try checking the preferred device drop down and see if it's set for you already.

[juuba]

I have the same issue. The game is not detecting the CH Control Manager Device 1, hence no JS or rudder. I have Windows XP so it's not a Win 7 issue.

I have a CH Fighterstick and Rudder Pedals. To operate them both in game you need to map these to the single CH Control Manager Device 1. The game will see both JS and Rudder pedals as a single device this way. Much easier to deal with.

No you don't need to map them in one stick. I tried it, and it almost worked.

I describe the way I got my 3 mapped devices working in Win7 in the previous page.

(click them through as preferred devices, hit OK, then re-set #1 as preferred and OK-OK close)

Mapped mode just enables the CH scripting mode, needed for inputting key presses instead of DirectX-joystick button presses.

You can ofc try to Map all controls in one "combined stick". But for me, it didn't work properly, some axees didn't register, cannot remember now which it was.

EDIT:

It was the "toe brakes". They didn't work when I combined all the CH set in "1 combined joystick". I guess we run out of axees

- X/Y for normal stick, Z for the throttlewheel

- rudder X, toe brakes Y and Z

- Throttle Z, minimouse X/Y

9 axees if I counted correctly

Anyway..

I can't even remember what the problem was clearly anymore..

I guess.. it was.. that the game does not recognize the CH Mapped mode (mapped mode here does not necessarily mean "all functions mapped in one stick" - just the "programmable mode")

This mode swaps the "Plug n' Play" detected joysticks (in windows control panel) as "CH Control manager Device 1" (and 2 and 3).

Still, the controllers themselves are (supposedly) DirectX controllers, and only game so far that I've had problems with is this one.

*scratch head*

Only after clicking them sticks through as preferred, the game suddenly does detect them.

Edited June 1, 2010 by juuba

[juuba]

OK so I need your help. RAMP says "works for me".

So what does he need to do differently?

Was this directed at me?

I dunno what he needs to do

Maybe:

• get a clean windows installation.

• Connect CH sticks, install the Control Manager, configure sticks with it:
  • start the wizard, select "Yes" for scripting support, then click the controllers we have (CH Fighterstick USB, Pro Throttle USB and Pro rudders USB)

  • Don't combine the sticks as one, but set as Mapped mode (not the Direct mode)

  • no need to configure anything, but maybe set one hat from throttle as the trim (I,J,K,L) and one button from joystick as "m" for open map (e.g some POV hat, push left)

  • save the "ww2ol.map", download it in the sticks with the button on the top row (now the windows will re-detect the sticks, play some disconnect/connect audios *plimplom*...)

  [*] start the "CMCC" program and download the "ww2ol.map" once more. (more *PLIMPLOMs* - controller icon is "crossed" for mapped mode)

  [*] Load game, try to work the controls.

(even if the sticks don't work, the keypresses did get sent in my case so the Windows did "work the sticks")

At least this is the logical way that my sticks didn't work at first.

(i'm typing this from memory, will have to re-check the configuration of the sticks, but approximately this way it is done)

When the sticks don't work, open Windows control panel and configure the USB controllers (from Start-menu.. type "USB" -> click "Configure USB controllers")

Then I set all 3 of my "CH Control Manager Devices" as preferred, first the #1, then OK. Then I reset the preferred to #2, hit ok.. Then set it again to #3, ok. Re-set #1 as preferred, OK, OK close.

After this the sticks worked in game.

Only controllers 2 and 3 were swapped. (Throttle and rudder, swapped around, compared to 1.30.x)

Edited June 1, 2010 by juuba
editing^n

[sasquach]

Just read last few messages re: CH sticks. Don't know what you all are trying to do but you don't need the CH Control Manager to program them, works without... CM might even muck things up. The only problem is that the CH Joystick doesn't get assigned as JS #1, and the Throttle ends up assigned all the stuff for flying the plane. Your joystick will appear as JS #2 or 3. The problem is in Windows which doesn't make the Joystick primary. I've had this happen in other programs also, so it isn't just caused by CRS. To fix this in Windows go to the game controller properties in Control Panel and set the Joystick as the PRIMARY controller. (I don't know what setting each control as primary in succession is supposed to accomplish.) Then it will be recognized as joystick #1 in WW2OL. If you don't do this you will have to reconfigure all the settings in the game to the proper joystick... a pain.

I suspect the cause of this is that miniature joystick on the CH Pro Throttle. Windows may see it and think that the Throttle is the main joystick.

sasquach

[juuba]

Just read last few messages re: CH sticks. Don't know what you all are trying to do but you don't need the CH Control Manager to program them' date=' works without... [/quote']

So you're saying that I should just toss the programmability?

(sure, I paid $200 for the stick and another $200 for the throttle, not to mention the rudder...I coulda just bought another Saitek set *wink*)

e.g mapping a keystroke ("i" for trim nose down) to happen when I push "Throttle Hat 1 Down" and same keystroke to happen 10 times in a quick burst if I press the same button with my "shift" key (joystick pinky button).

This macro sh*t is just light, some people might end up with much more advanced "programs" in their setup.

CM might even muck things up. The only problem is that the CH Joystick doesn't get assigned as JS #1, and the Throttle ends up assigned all the stuff for flying the plane.

And this is where the 1.31.x comes in. Something's changed, since the 1.30.3 works just fine.

Your joystick will appear as JS #2 or 3. The problem is in Windows which doesn't make the Joystick primary. I've had this happen in other programs also, so it isn't just caused by CRS. To fix this in Windows go to the game controller properties in Control Panel and set the Joystick as the PRIMARY controller.

(I don't know what setting each control as primary in succession is supposed to accomplish.)

Somehow, after clicking through all the "CH control devices" they are working in game. *shrug*

Then it will be recognized as joystick #1 in WW2OL. If you don't do this you will have to reconfigure all the settings in the game to the proper joystick... a pain.

I suspect the cause of this is that miniature joystick on the CH Pro Throttle. Windows may see it and think that the Throttle is the main joystick.

sasquach

Hmm, I just re-read your post, after morning's coffee..

So you're saying we should be able to program the stick as usual without the CMCC?

I gotta inspect that more..

Edited June 3, 2010 by juuba