No Controllers recognised

[Kabouik 0]

  

On 8/21/2020 at 9:25 AM, Kabouik said:

The problem appeared again, and just replacing joy.cpl was not enough. What worked is:

 

1. Devices and Printers

2. Right click on X52 Pro

3. Properties, Hardware tab, click the Properties button while the HID line is selected

4. Change settings

5. Driver, Update driver

6. Browse my computer, Let me pick from a list, and pick the only X52 HID occurrence

7. And replaced joy.cpl as described above, not sure if that was mandatory or not

 

This was after installing X52_Professional_HOTAS_x64_8_0_213_0.exe but I guess this is not necessarily a good idea, as now my hardware driver in the properties tab has "Driver date: 2017-04-20" and "Driver version: 8.0.121.0", so maybe the later updates (X52_Professional_HOTAS_x64_8_0_213_0.exe was released in September 2018) break things. We'll see how long it holds.

I wonder if there is a way to freeze things in that state and prevent updates.

Okay, that was still not it. Sometimes Windows was still failing to open joy.cpl with this, and in those cases, FS2020 doesn't see my X52 Pro. I tried something else:

1. Add or remove programs, uninstalled the X52 software. Not sure if necessary.

2. Admin command prompt

3. sfc /scannow

This detected joy.cpl as corrupted and refetched it from the MS Store. I think now it works, hopefully it'll keep working for more than two sessions.

Edited August 22, 2020 by Kabouik

[fhcraig 5]

Here's the original thread I posted ... https://forums.flightsimulator.com/t/ch-rudder-pedals-flight-yoke-help/129959/4

Since then I've kept adding to a list of common tips and issues. These are just my "top 10". There are great Guides here in the Tips & Tricks Forum and on the MS Forum under the Guides.

The Control setup interface can be intimidating, but it actually works well once you understand the process. The hardest part is finding the correct MSFS Commands that you want to bind. Here are a few tips to help speed up the process:

• The Control Filter at the bottom of the left part of the screen defaults to “Assigned” which only shows the commands that are currently bound to the selected controller. If the controller doesn’t have default bindings, you won’t see anything! To see all the commands, change the filter to “All”. To see a recommended set of starting commands select “Essentials”. The “Search By Name” will let you narrow down the (very long!) list of commands. Helpful Name searches are “Axis” (see below) and the various views “Cockpit”, “Instrument”, “Drone”, “External”.
• To bind an input (button, switch, slider, axis) you don’t need to know the actual input number for your controller. MSFS can recognize the input just by activating it during binding. When you click on a command, it will bring up the “binding window”. Click on the space that says “Search By Input” and it will light up. Now physically activate the input on your controller. The space should fill in with the input number. Click “Validate” to complete the binding.
• All “linear” controls need to use the “AXIS” commands, not the basic commands. That is the issue you are having with your control inputs. This includes control surfaces, engine controls (throttle, etc), brakes, etc. Basically anything that needs proportional input will use the “Axis” version of the command.
• Unless you have a complex throttle quadrant with multiple throttles, make sure you bind your Throttle to the “Throttle Axis” command and not any of the numbered Throttles. This will control all throttles on multi-engine aircraft simultaneously.
• A lot of the MSFS default controller profiles use the “Cockpit Quickview” commands which snap back to center. The secret to smooth panning around the Cockpit is to use the “Cockpit Look” commands. Make sure you delete any currently assigned Cockpit View commands for the Hat and then create new bindings using “Cockpit Look”. Depending on your hat, you can map 4 or 8 directions.
• You can actually access and change Control bindings while inside the live sim (use Esc to get to the main menus). This is helpful if you are trying to fine tune or debug things.
• You can create multiple binding Profiles for each of your Controllers. This is helpful if you want to map your controls differently for different aircraft. It is also useful if you need to adjust the Sensitivity settings differently for different aircraft. Just make sure you select the correct Profile for each session by using the little scroll bar under each controller in the Controls screen..
• I have not used any external controller management or calibration applications or drivers. If you do, your mileage may vary! For sure any control input assignments you make outside MSFS will not carry through inside the sim. The CH Manager application has caused problems for some users of CH products.
• Adding an Xbox Game Controller (wired or wireless) makes controlling the Drone Cam and Slew really easy and intuitive! MSFS immediately recognizes it and sets up all the bindings by Default.

I also highly recommend these YT tutorials if you haven't seen them ...

Sim UK https://www.youtube.com/watch?v=CxVJXS6NlM0

Squirrel https://www.youtube.com/watch?v=1DXdGaRgnhU

[macwino 14]

2 hours ago, fhcraig said:

Adding an Xbox Game Controller (wired or wireless) makes controlling the Drone Cam and Slew really easy and intuitive! MSFS immediately recognizes it and sets up all the bindings by Default.

I'm unable to get this to work. MSFS won't recognize my Xbox 360 wireless Game Controller. I've tried all the tips suggested in this thread and nothing works. The Xbox Controller is recognized in the Printers and Devices control panel and in Device Manager. It is recognized and works flawlessly in P3D v5 and XP11. It just isn't seen by MSFS. What's so odd is that my non-supported PFC yoke and TQ, and my MFG pedals, are recognized, but my Microsoft product isn't. Any thoughts on how I might remedy this problem will be appreciated.

Thanks, Robert

[styckx 1,871]

I have the Xbox Elite 2 controller hooked up and it's recognized immediately and it's "almost" completely usable, except there is NO WAY to adjust the left and right trigger sensitivity curve.. It makes steering and rudder control a mess. A simple light quick tap sends your plane hard in that direction. 

[Shoepuke 0]

Has anyone gotten the Saitek Throttle Quad (not-usb) (pre-Logitech) from the Yoke system to work?  The yoke works fine, but throttle quad and the associated axis' are nowhere.  Again, this is the Quad that plugs into the yoke with PS2 looking connector.

 

[hawkmanavsim 0]

i found the video-  my cookies were disabled or i wasn't logged in..

thanks.

[andy a 17]

I have the Logitech G (Saitek) Throttle Quadrant that plugs into the yoke, but there is no pic of the quad, listing the control  levers and T1 T2 etc. The pic of the yoke is there. However I have the throttle working ok but cant get the spoilers to deploy, or the flaps lowering or raising in increments. They all work ok in P3D. I also have Logitech G Rudder Pedals , which  have switched off intermittently  at some point after take off. An unplug/replug of the usb resolves the problem. Hope there's a patch soon to resolve peripherals issues.

[Scott Smith 0]

I have the Saitek Pro Flight yoke with throttle quadrants and every other piece Saitek made for flight sim as far as instrument panel, switch panel, radio stack, etc. etc.  I can’t get any to be recognized by Flight Sim 2020. I would like to at least have my yoke and throttle quadrant work. Any advice would be appreciated.