I was an avid MSFS user from FS 95 through FSX. As a result, I have a CH FlightSim Yoke and Pedals set - like millions of us.
I’m very disappointed that these still-available-for-purchase controllers are not set up to work with the game. After spending $130, I shouldn’t have to spend an hour mapping my controllers to the game.
I’ve ordered updated controllers (Logitech, so they are supported) simply because I can see the writing on the wall that legacy controllers are disposable as far as MS is concerned. I’m not willing to learn how to map my controllers myself - perhaps I can induce my 15 year-old son to do it for me. Until the new controllers arrive, or until the old controllers are mapped for me, the game will remain turned off.
I shouldn’t have to program controllers myself. Yes, I could learn, but I shouldn’t have to. When you get a new Surface from MS, do you have to program the touch pad yourself, or is it programmed out of the box?
Now I know why console gaming is so much more popular than PC gaming.
You are obviously younger than I, with a greater confidence in the ability to program what to me seems like a complicated task. There are multiple buttons and multiple axis for the yoke, and multiple axis for the pedals. The controller interface in the game is daunting.
I’m glad it’s easy for you. It isn’t for me. And you don’t address the main point of my post - that the game should have supported the most common yoke and pedal set in the MSFS community.
I’ve got four controllers with over 40 buttons and 14 axis and none of my controllers are in the game, but it doesn’t take that long to set them up and I probably wouldn’t like where they would put a lot of the controls anyway.
The interface is pretty easy to use, just search what you want to map, select it then press the button or move the axis you want it on then hit validate. If you can operate and aircraft you should be able to so this.
I am a retired engineer and real world pilot. I also hold a MS. I agree with the OP. It took me over an hour just to figure out how to program controllers that the sim doesn’t recognize. Here is an example of the effort it takes.
MSFS will see the controller. It will give every button or switch (in the case of an I/O controller) a number. You have to figure out what button represents what number. I used FSUIPC to determine the button and switch numbers. I then tediously set the buttons and switches ( I had to figure out how to do this because there aren’t any instructions) to control flaps, spoilers, gear, etc.
Then I flew and tried my new setup. Most didn’t work. So I went back into the Control App. It turns out that FSUIPC starts with the first button numbered 0 and MSFS starts with1. Okay, to be fair that isn’t MSFS developers fault. However, there are two columns in which you can set the functions. Neither column is named or annotated as to what is its function. I put my setup in the second column. My logic was that FSX uses the first column for the keyboard and the second column for joysticks/controllers. Evidently this isn’t the case with the new MSFS. After I added the functions to the first column they seemed to work. I still don’t know what the second column is use for. I have an idea, but since there are no instructions…
The first thing you learn as an engineer is the KISS principle. Keep it simple. In my opinion, that isn’t the case here. It seems like MS wanted to reinvent the wheel, rather than go with the conventional way of doing things that were done in the previous versions of MSFS.
Complaining for having to bang you head against a wall in frustration because the developer didn’t provide simple instructions isn’t lazy. It is an appropriate emotion.
You don’t have to figure out what button is what number, once you find the function you want click on the top box in the mapping window then press the button or move the axis and it sees it, then just hit validate, it’s quite easy to set up.
While I agree that the new controller and view commands are a bit un-intuitive and could use some simplifying, I was able to get things figured out. Granted it took some time, and I’m no computer programmer either, but that isn’t required. What is required is the willingness to learn and do a little research.
However, I too have a CH Products Yoke and it is unusable in the sim. It throws the aircraft out of control in external view and going back into cockpit view I have to reset all the trim and get the airplane back under control. Not good. No problems with my ancient MS Sidewinder stick.
Clicking on the top box and then moving the axis or button/switch did not always work for me. The axis worked fine, however many of the switches either didn’t register or didn’t keep. I am sure this is because of a lack of understanding on my part. Yet, I think it is also a point in the OP’s favor. The system is not as simple and intuitive as it should be.
For CH Yokes ( i have the eclipse that works perfectly), you have to go and download the CH Manager software from their site. Once you download that, MSFS works with it and all axis and buttons are recognized.
Huh - wonder if having some instructions come with the sim would have helped?
Likely so. But hey we all have plenty of time to look stuff up - basically everything - for this sim. After all, it isn’t TOO complicated what with ALL the features, options, procedures, equipment, planes, caches, pop-out windows & menus, tools, settings, controls, views, knobs, IFR, VFR, ATC, various cockpits, NAV, ILS, AI, G1000?, flight plans, etc. etc. etc.
It is fun becoming aware of yet another something in the sim you didn’t know you could do, or almost as fun - don’t know how to do…almost self-satisfying.
I just wish I could figure out why, after 6 days of flying the same way, my plane now shuts off 5mins into a flight 1/2 the time - guess I’ll just have to look it up
