Maybe a dumb ?. Can I use the CH yoke and my joystick at the same time. I would like to use the buttons on the joystick along with the flight yoke. Bob McDuff

Yes you can, but you need to ensure that the control axes of the two devices don't conflict.There are at least two ways to do this - either within FS or by using CH Control Manager (the latter only works if both devices are USB). If you're not familiar with CHCtlMgr then doing it in FS is the easiest way to go.My experience with CH USB devices is that FS will, by default, assign more than one device axis to the same FS axis, so go through and make sure that (for instance) you don't have the stick and the yoke both wanting to control Ailerons and Elevators. Another thing that I'll bet will happen is that both devices' throttle axes will be mapped to the FS Throttle - again, if it does this you'll have problems and you'll need to decide which one is the throttle.Once you've done that then you can assign all of the buttons any way you want.Dave Blevins

Great, I'll give it a go. I do have CH control manager, but havn't messed with it much. Thanks, Bob McDuff

In addition both yoke and stick must use the same connection, you cannot use a USB stick with a gameport yoke or t'other way around.

I pluged the CH yoke in one usb and the joystick in one usb. Now when I go to FS2004 settings>assignments it shows both the yoke and joy stick.It looks like i can assign controls for both.Not sure about all the axis stuff though! I'll keep messing Bob

Hopefully to save you a bit of head scratching, I'll toss out a few nuggets of semi-truth. I hope I have all of this right... CHCtlMgr and its Help content use some terms in multiple ways that can be confusing - i.e. "direct" vs. "DirectX" and "mapped" vs. "maps". It took me a while to get my head around these things as a result. Direct (not DirectX!) mode means that the stick/etc. is talking directly to Windows, and effectively neither ChCtlMgr or the programmability of the Pro Throttle/Fighter Stick are "in play" - the devices are merely "dumb" usb controllers, albeit with lots of buttons and axes, which are always known to Windows with their Windows-assigned controller numbers.Mapped mode puts ChCtlMgr in-between your USB CH devices and Windows, allowing (1) taking advantage of the downloadable programmability of the Pro Throttle/Fighter Stick, and (2) re-mapping of buttons/axes to other things - using Maps! (As far as I'm concerned Mapped Mode and the Maps that you can *use* in Mapped Mode are two different things - even though they use the same word.)Maps allow that re-assignment of the buttons and axes on the devices to other things. Normally, those buttons and axes are known to Windows as DirectX (not Direct!) controllers, but you can reassign them to either other DirectX controller numbers or to either individual keystrokes or keystroke macros.Note that when you switch to Mapped mode, the CH devices that you see in Game Controllers are removed, and "CM Devices" are added, and your system will make the USB dismount/mount sounds if they are enabled.You can either have a 1-to-1 correspondence between your CH controllers and the CM devices - i.e. a stick and yoke would be come CM Devices 1 and 2 - or you can combine more than one device into a single one. This can be useful for games that don't understand the concept of multiple controllers. I use a map with a single CM Device for Orbiter, as a for-instance - it's almost totally keystroke controlled and I find it easier to just have one device in that case. On the other hand, I have a map with three CM Devices for FS2004, because a single CM Device has a maximum number of axes that is less than what my hardware setup (CH Combat Stick/Pro Throttle/Pro Pedals) has.So that's my CHCtlMgr 101 discourse. Perhaps all of this will be intuitively obvious to you when you start playing around with it, but it sure wasn't to me.cheers,dB.

Bob,One additional note - if you do a bunch of axis and button assignment in FS2004, and then start using CHCtlMgr to create Mapped devices, you will lose all of your assignments since FS sees new CM Devices as separate things than the non-mapped devices it saw before. So you'll have to make those assignments again in FS's Control Assignments (or else do a bunch of copy-pasting in fs9.cfg, which I strongly discourage unless you are quite familiar with that file and how it's set up).I use a *bunch* of assignments - every button and every axis that I have does something - and this is a pain in the butt the first time you do it. So I suggest that you either decide to use CHCtLMgr, and its maps, or not. That way you'll only have to do the assignments once.dB.