EDIT: Well, I think the answer to my problem turned out to be pretty simple: The mini-USB cable which connected my FSSB R3 to my USB hub appears to have been bad. I replaced it with another one (actually a short mini-USB on a USB extension cable), and now my Win11 computer can āseeā my FSSB R3. I havenāt set it up in BMS yet, but the Realsimulator DCC program was able to update the firmware, and the RS_HID program can communicate with the FSSB and see the inputs Iām making with the stick. Looks like itās okay.
I think the reason I didnāt consider the USB earlier is because I thought I had solved my USB connectivity problem with this device. The mini-USB connector inside my FSSB R3 didnāt make a tight connection, and I did some very careful bending of the pins in it, to make the connection tighter when I plugged in the cable. This was several months ago, maybe a year, and I thought I had my USB connectivity problems solved.
It just goes to show - when you think youāve solved a problem, a new one can crop up! It always pays to be vigilant.
Thanks, @Steve_U , for the information about your Realsim stick working under Win11. Looks like Win11 works well.
Hereās my original text for this post:
I just finished building a new PC and I canāt get Windows 11 to see my Realsimulator FSSB R3. (It has a TM Warthog stick mounted on it).
When I first downloaded and installed the Realsimulator software, the RS_HID program seemed to communicate with the FSSB R3 and download some settings from it, but shortly thereafter, RS_HID couldnāt communicate with the FSSB anymore.
When I look in the Windows 11 Settings for āUSB Game Controllersā and āDevices and Printersā, the FSSB isnāt showing up. But my other flight-sim peripherals are showing up: My Winwing HOTAS throttle, my Slaw Device pedals, my TM MFDs, and the cheap little monitors I use with my MFDs. I assume this also means that the USB hub which connects my peripherals to my computer is okay, too.
In the FSSB userās guide, they say they just use standard Windows HID (Human Interface Device) drivers for the FSSB, instead of writing their own drivers which would have to be updated with each new Windows release. Does anyone know if the transition to Windows 11 has caused a problem with this? Maybe there are some old drivers from the days of Win10 that I could copy over from my old computer?
Just curious if anyone else has had these connection issues with W11.