These are the Support Forums for FSUIPC and related products.
These forums replace the old support forums which have been running for 20+ years. The old forums contain a wealth of information on all FSUIPC products, but are now no longer available.
Please note that you will need to Register and Login to post for support, and also to download attachments. You can view these forums without registering.
Support is also available via Discord. Please use the following invite link to join the FSUIPC Discord server:
https://discord.gg/zjwUTrxmmE
FSUIPC and Honeycomb Echo Controller
Hello. I recently received a Honeycomb Echo Controller. It's okay, great for use on a laptop. However, they designed it with a 10 minute-no activity-sleep-mode. Very annoying as, when axes are assigned within FS, some of the axes just move when it goes to sleep mode and others move when a button is activated to wake it up. So I went to assign an axis (Win11 "sees" it as DIAL), FSUIPC does not seem to recognize this particular axis. I noticed, on about page 44 of FSUIPC for Advanced Users, That FSUIPC sees XYZRUV. Is there a way for FSUIPC to see the DIAL axis, if so, how? Thank you.
Posted by: @arleeIt's okay, great for use on a laptop. However, they designed it with a 10 minute-no activity-sleep-mode. Very annoying as, when axes are assigned within FS, some of the axes just move when it goes to sleep mode and others move when a button is activated to wake it up.
Thats strange. Have you checked the USB Power Managementsettings for this device and your USB Hubs? If not, check that and make sure that the 'Allow the computer to turn of this device to save power' option is disabled.
Posted by: @arleeSo I went to assign an axis (Win11 "sees" it as DIAL), FSUIPC does not seem to recognize this particular axis.
Are you sure about this? Please se the attached document, which shows the axes and button inputs provided by this device. According to this, there are 4 axes (X, Y and Z) and the rest are buttons. Which one of these is this 'DIAL' axis?
Check to see if this 'DIAL' is recognised as buttons. If not, I don't think there is much that can be done, especially in FSUIPC4 which has been closed for development for many years.
Hello. Thank you for your reply. I did check into the power shutoff but I did not see anything showing where the computer turns off the device. Also, this really wouldn't be applicable as FSUIPC would see the other axes as I clicked on the Rescan button. FSUIPC just would not respond to the "DIAL" axis. I have that pdf but what it displays as "SLIDER X" is detected by the Win11 game controller as "DIAL." I have attached a screenshot of what Windows 11 shows for inputs by the Echo Controller. It has been my experience that all the joysticks/game controller that I've purchased, none had more than 6 axes (XYZRUV)/device. The Echo has 7. Also, and I haven't moved up to P3D or MSFS (I did try it on XBOX but was not impressed), but would FSUIPC 5,6, and 7 see the "DIAL?"
Posted by: @arleedid check into the power shutoff but I did not see anything showing where the computer turns off the device.
Check your USB hub power management properties. It must be there, if not, you are looking in the wrong place. Google if you do not know how to do this.
How about this 'Slider' axes? Is that recognised by FSUIPC7? The names you see in the windows game controllers are not important - only the letters assigned to an axis. For example, on my X-55 Rhino Throttle the windows Game controllers sees the three rotaries as 'Z axis', 'Y Rotation' and 'Z Rotation', whereas FSUIPC7 reports these as the 'Z', 'V' and 'R' axes respectively.
As far as I know / understand (without investigating further), there are only 7 axes available via the windows API.
If the axis is not recognised in FSUIPC4, I am sorry but there is nothing you can do. Aoart from maybe assigning in FSX.
Posted by: @arleeAlso, and I haven't moved up to P3D or MSFS (I did try it on XBOX but was not impressed), but would FSUIPC 5,6, and 7 see the "DIAL?"
No - the device management is the same.
However, if this really is an issue, then I would update both FSUIPC6 and FSUIPC7 to handle such axes. However, I am not prepared to do this at the moment, and I would need to purchase such a device to be able to do this. Currently that would be 3-4 days worth of sales income, which I just cannot afford at the moment. If it becomes an issue, I will investigate further, but for FSUIPC4 / FSX I am not going to look into this further, sorry.
John
One other thing to check is the drivers you are using for this device. Are you using any dedicated drivers, or windows default drivers?
In each case, try switching, i.e. if using dedicated drivers, try windows default drivers, and if using the windows defult, try the dedicated drivers.