Jump to content

Kabouik

Frozen-Inactivity
  • Content Count

    10
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

Profile Information

  • Gender
    Male

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    Yes
  1. No, I had to set everything up sadly. I got it to a working state now, but am not sure whether I forgot really useful functions. I still haven't mapped all keys, I'm keeping some free in case I later realize I need more commands on the controller.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. I found what was my problem with the X52 Pro not showing up at all in FS 2020 (despite working in other sims and showing up in W10's Devices and printers). I noticed that right clicking on the X52 icon in Devices and printers and then trying to open "Game controller settings" wouldn't do anything. Same when trying to execute joy.cpl directly. Turns out my joy.cpl was corrupted, I'm assuming because of a driver but can't confirm. Therefore, I moved it to a backup folder (in case this wouldn't be the problem) from C:\Windows\System32, and then copied the original C:\Windows\SysWOW64\joy.cpl and pasted it in C:\Windows\System32 to start fresh. Rebooted, connected the X52 Pro, right clicked and opened the game controller settings successfully. At this point, the first time I launched FS 2020, my HOTAS was detected. Hope this helps others. I think I was the only one not to have my X52 Pro detected at all, but never know.
  7. I found what was my problem with the X52 Pro not showing up at all in FS 2020 (despite working in other sims and showing up in W10's Devices and printers). I noticed that right clicking on the X52 icon in Devices and printers and then trying to open "Game controller settings" wouldn't do anything. Same when trying to execute joy.cpl directly. Turns out my joy.cpl was corrupted, I'm assuming because of a driver but can't confirm. Therefore, I moved it to a backup folder (in case this wouldn't be the problem) from C:\Windows\System32, and then copied the original C:\Windows\SysWOW64\joy.cpl and pasted it in C:\Windows\System32 to start fresh. Rebooted, connected the X52 Pro, right clicked and opened the game controller settings successfully. At this point, the first time I launched FS 2020, my HOTAS was detected. Hope this helps others. I think I was the only one not to have my X52 Pro detected at all, but never know.
  8. Thanks for your answer JiminPT. Unfortunately, I can already see the device in Devices and Printers, and other sims like IL-2 CLOD Blitz and DCS World work fine with this joystick, so there must be something specific to MFS2020 anyhow. However, I did try to open the properties to check this joystick testing window and see if axes and buttons were working correctly, but no window appeared when I did so (just the basic, generic, device properties and hardware info). I found it surprising too but since the joystick works in other sims, I didn't dare to reinstall the driver. I guess this is the next thing I will try tonight. I posted a more comprehensive description of my issue here too.
  9. My X52 Pro (listed as officially supported my MFS2020) is not detected at all in the sim. The OS sees it, and so do other simulators like IL-2 CLOD Blitz or DCS World, so there must be something else specific to MFS2020 that I haven't found how to solve yet. I have tried unplugging/replugging the USB cable multiple times, while in game (tried different menus) or before running the game, selecting a profile from the system tray icon or not, rebooting, no dice so far. Occasionally, when plugging the HOTAS while in the controller options in the sim, MFS2020 will crash. This does not seem to occur while in other menus, although it'd need to be tested more rigorously. In any case, this suggests that something is indeed happening when I plug it and MFS2020 somehow is impacted, but still no HOTAS showing before the crash. An Xbox pad is correctly recognized and immediately listed when plugged in. I have tried disconnecting it too before my attempts with the X52 Pro, but no effect. The sim is installed from the (atrocious) MS Xbox client, which also came with its own issues for downloading and installing MFS2020 (but at least, now that part is done!). If anyone encounters the same issue or has any idea, please let me know.
  10. My X52 Pro is not detected at all in FS2020, even after trying to plug it in only when on the welcome menu as advised here. I'm kinda clueless, because the OS does see the joystick.
×
×
  • Create New...