Wednesday at 02:26 AM2 days I recently migrated MSFS 2024 to a new PC. I reinstalled MSFS 2024, and all of my controller drivers. When I booted into MSFS and looked for my controllers, they all appeared with their bindings as per previous installation. Thought I was good to go.But I noted right away that the controllers were not communicating with MSFS at all. Nothing happened when clicking buttons, moving assigned axes etc.I checked with the Game control panel and all of the controllers show up and all of their axes and button register and respond to controller inputs. So they are installed and working. Anyone else experience this when migrating to new PC? Any ideas how to fix this beside from redoing all of my bindings?Using Logitech Game Pad, and TCA yoke and throttle quadrant.Thanks,Greg Greg Clark
Wednesday at 02:14 PM2 days When you put hardware on a different PC (or the same PC with a fresh install of the OS), Windows generates new GUIDs used to identify each hardware controller. It seems likely that the configs MSFS stored in the cloud are tied to the GUIDs on the old machine.Try binding something like an unused button to something innocuous like smoke on/off and see if the MSFS controls UI recognizes the input. If not, I suspect you'll need to rebuild your configs. Bob Scott | President and CEO, AVSIM Inc ATP Gulfstream II-III-IV-V Sys1 (MSFS20+24/XPlane12+11): AMD 9800X3D, water 2x240mm, MSI MPG X670E Carbon, 64GB GSkill 6000/30, nVidia RTX4090FE Alienware AW3821DW 38" 21:9 GSync, 2x4TB Crucial T705 PCIe5 + 2x2TB Samsung 990 SSD, EVGA 1000P2 PSU, 12.9" iPad Pro Thrustmaster TCA Boeing Yoke, TCA Airbus Sidestick, Twin TCA Airbus Throttle quads, PFC Cirrus Pedals, Coolermaster HAF932 case Sys2 (P3Dv5/v4): i9-13900KS, water 2x360mm, ASUS Z790 Hero, 32GB GSkill 7800MHz CAS36, ASUS RTX4090 Samsung 55" JS8500 4K TV@60Hz, 3x 2TB WD SN850X 1x 4TB Crucial P3 M.2 NVME SSD, EVGA 1600T2 PSU Fiber link to Yamaha RX-V467 Home Theater Receiver, Polk/Klipsch 6" bookshelf speakers, Polk 12" subwoofer, 12.9" iPad Pro PFC yoke/throttle quad/pedals with custom Hall sensor retrofit, Thermaltake View 71 case, Stream Deck XL button box Sys3 (DCS/P3Dv4/ATS/ETS): AMD 7800X3D, MSI MPG X870E Carbon, Noctua NH-D15S, 64GB GSkill 6000/30, EVGA RTX3090 Alienware AW3420DW 34" 21:9 GSync, Corsair HX1000i PSU, 4TB Crucial T705 PCIe5 + 2TB Samsung 970Evo Plus, TM TCA Officer Pack, Saitek combat pedals, TM Warthog, TM RS300 FF wheel/pedals, Coolermaster HAF XB case
Wednesday at 03:34 PM2 days Author Thanks Bob. In retrospect this makes sense and would explain why MSFS is not linking to the "same" Controller which is does not see as the same one. My previous PC is also on Windows 10. I dread having to rebuild the profiles and relearn how to do it. Since I do have the mappings, perhaps I can try scanning for each button axis and axis and move the button or move the axis and see if that will re establish the connection to the setting, without having to start from scratch.Greg Greg Clark
Create an account or sign in to comment