CH configs to share anybody?

I've got mine at 5%, no curve, which seems to compensate well for that microstick's tendency not to center perfectly when released.

I'm hoping that once A4 goes live, the annoying tendency for E: D to occasionally forget some of my axis will be gone. Granted it's a minor matter to go into the first combat scenario and test everything out, but it's still annoying.

Just 5%? Hmm, I wonder if I'm doing something wrong and my CH Control Manager adjustments aren't actually being taken into effect. Hmm, apparnetly yes!

My "mapped mode" button is grayed out. What's up with that?
 
Apparently I hadn't hit the oddly named "download" button.

Now I'm even more impressed at the CH hardware as it was working that well without any response curve adjustments.
 
It works brilliantly in the current alpha. If you're impatient, try combining them into one huge controller. When premium beta arrives, you no longer have to.

I just did it and it works quite well, only there is 8 axis limitation and I have 9 hardware axis (but in fact I only need 6 for ED, so not a big deal) and I am missing bindings for one 8-way hat, but this is also something I can live without for now.

Good to hear in last alfa it is working well, as it means they worked on it and I can have all possibilities in Beta.
 
Apparently I hadn't hit the oddly named "download" button.

Now I'm even more impressed at the CH hardware as it was working that well without any response curve adjustments.

I also did not make any curve adjustments, only callibrated my new pro throttle and set minimal deadzone for the thumb joystick. It feels almost perfect out of the box without having to fiddle with anything.
 
Last edited:
Apparently I hadn't hit the oddly named "download" button.

Now I'm even more impressed at the CH hardware as it was working that well without any response curve adjustments.

It isn't oddly named. CH's hardware have microprocessors in them, and they can communicate with each other. Furthermore, they're programmable. When you hit download, the control manager takes your profile and the script file, compiles them, and downloads them to your HOTAS setup.

Unless you need to know where the mouse cursor is for some reason, you don't need to have the Control Manager open while playing. The hardware themselves do all the work. :)
 
It isn't oddly named. CH's hardware have microprocessors in them, and they can communicate with each other. Furthermore, they're programmable. When you hit download, the control manager takes your profile and the script file, compiles them, and downloads them to your HOTAS setup.

Unless you need to know where the mouse cursor is for some reason, you don't need to have the Control Manager open while playing. The hardware themselves do all the work. :)

Oh, they remember it? Now it makes more sense. Still feels like it should be called "upload" then.

I'm doing something wrong though, since the buttons on the stick and throttle are being detected as the same button in game now that I've made a profile. It's very unfortunate. Same with some of the 4-way hats. I know others don't have this problem, so I'm messing something up.

The Stick, Throttle and Pedals are showing as CM Device 1, CM Device 2 and ..3 in the Control Manager. All the axis work fine without any conflict. I wonder if I should avoid using the mode switching button on the Fighterstick as one of my buttons?
 
Being a beta premium backer, I'm using a full CH setup (fighterstick, throttle, pedals) in Alpha 1. A few pointers:

-Combining into a single device seems to be the only reliable method to get it to work.

-To the earlier poster who still saw multiple devices even after doing this this, I suspect you still need to put it into 'Mapped mode'. You may have the map file loaded, but if you're in 'direct' mode, it will still be outputting multiple devices.

-I use some deadzone on the throttle (to find the 'zero' centre since I use FA off most of the time), and some deadzone on the ministick to account for the fact that it sticks a little near the centre.

-I don't have trackir, so I use the ministick button to toggle the ministick operation between translate and headlook. Most of this has to be set gameside.

-I can post the CMC and MAP files this evening if anyone is interested. The CMC requires some additional inputs to be done gameside, since they aren't mapped by default.

-My MAP (as with most of my other maps) uses the throttle index hat as a 5-way mode 'shift' switch. It defaults to mode one, but will go into modes 2-4 or shift if the hat is held in a position. There's no real need for this in alpha 1.1 given the number of possible keypresses, but I suspect this will change.
 
I believe there's a problem with E: D remembering multiple controllers, AND some of the secondary axis that are available. This is especially true in alpha 1.1, but I've had to make sure everything's working correctly in alpha 3.4 from time to time.

Here's hoping they've fixed the problem in alpha 4.

edit:

-My MAP (as with most of my other maps) uses the throttle index hat as a 5-way mode 'shift' switch. It defaults to mode one, but will go into modes 2-4 or shift if the hat is held in a position. There's no real need for this in alpha 1.1 given the number of possible keypresses, but I suspect this will change.

That's clever. I use my throttle's triggers for that sort of functionality myself. Pinky trigger is shift, ring finger trigger is alt, and middle finger trigger is ctrl. But with my current setup, alt is "flight assist off" (right now just alters how the throttle works), and ctrl is "special functions".
 
Last edited:
I'm doing something wrong though, since the buttons on the stick and throttle are being detected as the same button in game now that I've made a profile.

HI Adept, your posts (amongst others) made me get hold of a CH setup (although without the pedals), they're great so a big thank you :)

If you haven't already sorted this I'm in premium beta and got the stick and throttle working using a CH profile, but I had to remap the throttle buttons using the manager, eg. going into the throttle page, clicking button 2 on the throttle then selecting button 18 from the drop down list to change the assignment, button 3 to 19 etc. I did this with all the throttle buttons and ED now sees a single controller with buttons numbered 1 to 32. I don't know if there's a way of doing this automatically, hopefully that makes sense.

Maybe I'll bump into you on the 30th, Cheers
 
I've got myself the fighterstick and pro throttle combo, how are you guys using the UI panels and freelook (no dk2 yet) with these?

I've got lateral thrusting on the ministick and when shifted (with the stick's pinky switch) it doubles as yaw control, seems to work nicely. No actual modes in use (yet).
 
I now have all the bits for my HOTAS. CH Fighterstick, Pro Rudder Pedals and Pro Throttle. I think there are several alpha players using CH stuff, so I'd love to hear how you guys have set them up.

I also found out how to use the pre-set response curves when combining all the controllers into one virtual device, but I think I won't need to do that in the later alpha builds (and premium beta build to come). I'd also like to hear what kind of response curves you guys have used on the things, and whether you use the throttle for both forward and back, or just forward and modify with a reverse gear toggle.

Hey Adept

I have a CH Pro Throttle combined with Logitech Extreme 3D Pro.

For the CH Throttle, I have the analog hat as vertical and lateral thrust.

Upper POV hat up/down is targets, left/right is hostile targets.

Middle hat is direct access to UIs in cockpit (never use it now that I've assigned 1,2,3 on my keyboard to those) - suggestions??

Lower POV hat is left/right subsystems, up Lights, down Landing Gear.

Front right button = boost
Front mid button = FA toggle
Front left button = hardpoints toggle

Throttle = continuous and full range.

Let me know if you want the Logitech bindings also.

Cheers!

O-Dog
 
Thanks, but I've been playing for a while now, and have everything bound. I appreciate you taking the time though. I'll edit the 1st post to make it clear I have what I need.

Good call getting the Throttle to go with your stick btw. :cool:
 
I've got myself the fighterstick and pro throttle combo, how are you guys using the UI panels and freelook (no dk2 yet) with these?

I've got lateral thrusting on the ministick and when shifted (with the stick's pinky switch) it doubles as yaw control, seems to work nicely. No actual modes in use (yet).

Hmm... if I'm understanding you correctly, doesn't that mean that you won't be able to yaw while holding lat thrust, and vice versa? If I may, you might want to re-think that, as performing lateral strafs requires yawing while... er, lateraling - the same as vertical strafs require pitching. I think you may be severely limiting your full range of maneuvers with that setup.
 
Last edited:
Hmm... if I'm understanding you correctly, doesn't that mean that you won't be able to yaw while holding lat thrust, and vice versa? If I may, you might want to re-think that, as performing lateral strafs requires yawing while... er, lateraling - the same as vertical strafs require pitching. I think you may be severely limiting your full range of maneuvers with that setup.

Well, I do have yaw on roll enabled in normal flight mode, so that helps a bit, but you're right, I dont have full yaw available while holding lat thrust. Although I can easily give it a bit of extra yaw in the mix by pressing the shift button while lat thrusting.

Any ideas on how to map the throttle and fighterstick to enable using both at the same time? Without buying the pedals that is. :)

And I'm still not sure what's the best way to map buttons needed to move in the UI panels, I've got the 2 8-way POV hats basically unused but what do you use for selecting the menu items?

Does anyone have updated maps for PB1/PB2 they could share? :)
 
Back
Top Bottom