New PC - USB Controls Disconnected

[LawyerPilot]

Hi All,

I just installed PSX (updated to 10.29) on my new PC and cannot get the sim to detect my USB controls. I used the same controls (Thrustmaster Warthog stick and throttle) on my last PC with no issues. I suppose there's a conflict somewhere, as I have many USB devices, but the controllers work fine on XP11 and DCS. Any ideas? I think I might die without PSX. In fact, I'm quite sure of it.

By the way, no errors are logged, and I've tried the tricks discussed in the forum--namely, (1) unchecking the "USB on" box and restarting sim, (2) changing UsbUnknownIncl from 0 to 1 and (3) regenerating Default.pref. No luck.

My (regenerated) Default.pref file:

[Aerowinx Precision Simulator - Preferences]
[Version 10.29]

InstructorPg=0;2;0;0;0;0;4;0;0;0;
InstructorPos=0;0
HideMouse=0
FltDkSunlight=0
WindshieldHair=0
FpsLimit=4
Host=-
ClientPortSel=0
Port10747=10747
Port10748=10748
Port10749=10749
ReconnectClient=0
LayoutSync=0
MetarDownload=1
MetarUrl=http://tgftp.nws.noaa.gov/data/observations/metar/cycles/
UseDefaultMetarUrl=1
UsbActive=1
UsbUnknownIncl=1
OldWxrGfx=0
CustomCode=0
InstructorOnTop=0
AirConVol=70
FlchTlaTolerance=80
NdRasterAntiAlias=1
WhiteBacklight=0
Wraparound=1
ThrHuman=1
WeakAilTrim=1
YokeIndic=1
ShowTitle=1
WindshieldActive=1
AllowEventRcd=0
AllowPrintSep=1
AllowMultiMon=0
NetStart1=0
NetStart2=0
StartSitu=-
RealUtcStart=1
StartLayout=-
WdoMaximStart=1
ShowInstructor=1
AlternateJavaFont=
AlternateMacFont=
JavaLookFeelOnMac=0
USB=
UsbFlapLever=200;900;1000;600;800;300;500;-100;100;-500;-300;-800;-600;-1000;-900;
SoundOn=1
Audio1=1
Audio2=1
Audio3=1
Audio4=3
Audio5=3
Audio6=3
Audio7=3
Audio8=3
Audio9=3
Audio10=3
Audio11=3
Audio12=3
Audio13=3
Audio14=3
Audio15=3
Audio16=3
Audio17=3

[End of file]

[Hardy Heinlin]

Hi Trevor,

some variables are missing in your "regenerated" Default.pref -- by the way, what do you mean by "regenerated"?

The following lines contain no data after the "=" sign:

Host=-
StartSitu=-
StartLayout=-
AlternateJavaFont=
AlternateMacFont=
USB=


The two "alternate font" items are OK if there are no alternates entered; that means the default font is used.

But the other lines are not OK. It seems that something in your system has cropped the value because it starts with a minus sign. I have no idea what could cause this. PSX cannot do this.


Regards,

|-|ardy


Here's a sample of a normal pref file:


[Aerowinx Precision Simulator - Preferences]
[Version 10.29]

InstructorPg=2;1;4;3;1;0;2;1;10;6;
InstructorPos=1186;22
HideMouse=1
FltDkSunlight=1
WindshieldHair=1
FpsLimit=4
Host=localhost
ClientPortSel=0
Port10747=10747
Port10748=10748
Port10749=10749
ReconnectClient=0
LayoutSync=0
MetarDownload=1
MetarUrl=http://tgftp.nws.noaa.gov/data/observations/metar/cycles/
UseDefaultMetarUrl=1
UsbActive=1
UsbUnknownIncl=0
OldWxrGfx=0
CustomCode=0
InstructorOnTop=0
AirConVol=70
FlchTlaTolerance=80
NdRasterAntiAlias=0
WhiteBacklight=0
Wraparound=1
ThrHuman=0
WeakAilTrim=0
YokeIndic=1
ShowTitle=1
WindshieldActive=1
AllowEventRcd=1
AllowPrintSep=1
AllowMultiMon=1
NetStart1=0
NetStart2=0
StartSitu=-End of last session.situ
RealUtcStart=0
StartLayout=-End of last session.9pack
WdoMaximStart=0
ShowInstructor=1
AlternateJavaFont=Microsoft Sans Serif
AlternateMacFont=
JavaLookFeelOnMac=0
USB=11;10;7;8;9;12;1;21;2;20;5;40;24;39;13;19;14;18;24;0;15;0;28;0;16;0;29;0n2;0n1;
UsbFlapLever=200;900;1000;600;800;300;500;-100;100;-500;-300;-800;-600;-1000;-900;
SoundOn=1
Audio1=1
Audio2=1
Audio3=1
Audio4=3
Audio5=3
Audio6=3
Audio7=3
Audio8=1
Audio9=2
Audio10=1
Audio11=2
Audio12=0
Audio13=0
Audio14=3
Audio15=3
Audio16=3
Audio17=0

[End of file]

[LawyerPilot]

Hi Hardy,

Thanks for taking a look. By "regenerated", I mean that I deleted Default.pref and started the sim so that it created a new one. I gather that's not a sanctioned fix.   I just saw on the forum that someone else did that, so I thought I would give it a try.

I'll restore the values using your example and report back.

[Hardy Heinlin]

Hi Trevor,

these files should never be deleted:

Default.situ
Default.9pack
Default.pref


Regards,

|-|ardy

[LawyerPilot]

Ok, I promise to leave those alone from now on. 

I decided to start from scratch with a bare 10.0.0 install from the DVD with no update, original interfaces, pilots, models, etc. (previously, I installed everything in one shot before testing). Still no luck. The PSX splash screen says No USB Device Found. The USB tab under preferences says no usable device found.

I've checked device manager (controller status is OK) and even tried switching the controllers from the case ports to the USB ports on my motherboard back panel. They're working fine, but I cannot get PSX to recognize them.

Thoughts?

[jb747]

Just as a test would you download the following add-on and see if it will recognize your PSX inputs?

https://www.dropbox.com/s/6zv0n2mzda3hn46/SmartInterface_1.2.6.zip?dl=0

It replicates some of the joystick interfaces that PSX provides.

Cheers,

Jon

[Hardy Heinlin]

Hi Trevor,

please keep using the latest version 10.29. Going back to 10.0.0 will not solve your USB problem.

What's the difference between your old and your new PC? Are you using any new USB devices in addition to your old joystick? Any special USB mouse, keyboard etc.? What order are they plugged in your computer?

What's indicated in Aerowinx/Developers/USB-Detect.txt?


Cheers,

|-|ardy

[asboyd]

If you are using Windows 10 be aware that some USB 3.0 drivers can cause issues. Check around the Windows 10 forums and find a replacement or updated driver for the USB 3.0 chipset on your new motherboard.

Cheers,

[LawyerPilot]

Thanks for all the replies. I've re-updated to 10.29 per Hardy's suggestion. Here is what I've done and my findings:

1. Updated USB 3.0 drivers through device manager. The only one requiring an update was the ASMedia USB3.1 eXtensible Host Controller. Updated but no change.

2. Downloaded and ran the SmartInterface program. It says that no hardware is detected, which I suppose confirms what PSX is telling me.

3. USB-Detect.txt is blank apart from: "USB detection test:"

4. Confirmed updated drivers and firmware for the Thrustmaster Warthog stick and throttle.

Hardy, the relevant difference between my old and new PC is that I switched from an ASUS P8Z77-V Pro motherboard to an ASUS Maximus X Hero which has the following in the way of USB connectivity:

ASMedia® USB 3.1 Gen 2 controller : 1 x USB 3.1 Gen 2 front panel connector port(s)
ASMedia® USB 3.1 Gen 2 controller : 2 x USB 3.1 Gen 2 port(s) (2 at back panel, , Type-A + USB Type-CTM)
Intel® Z370 Chipset : 6 x USB 3.1 Gen 1 port(s) (4 at back panel, +blue, 2 at mid-board)
Intel® Z370 Chipset : 6 x USB 2.0 port(s) (2 at back panel, +black, 4 at mid-board)

In terms of connected USB devices:

1) Kingston HyperX gaming keyboard (wired) - to mb backpanel
2) Corsair Scimitar Pro RGB mouse (wired) - to mb backpanel
3) Natural Point TrackIR 5 - to mb backpanel
4) Steelseries Siberia 840 wireless headset transmitter box connected via optical and USB - to mb backpanel
5) NZXT Kraken X62 closed loop cooler AIO pump - to mainboard USB 2.0 header
6) Fractal Design S case front panel 2-port USB 3.0 - to mainboard USB 3.1 Gen 2 front panel connector port

I disconnected the TrackIR and the headset transmitter box from the mb backpanel and tried my joystick and throttle in those ports...thinking that perhaps I just have too many USB devices OR that my frontpanel case ports are being spastic. No luck.

I'll follow asboyd's suggestion and research the Windows 10 forums for clues on driver issues. May take some time, but I'll report back.

In case useful...not that I would expect anyone to want to read through this scroll of pain, here is the DxDiag report:

https://www.dropbox.com/s/wq7bgxwiyttluf9/DxDiag.txt?dl=0

[Hardy Heinlin]

1) Kingston HyperX gaming keyboard (wired) - to mb backpanel
2) Corsair Scimitar Pro RGB mouse (wired) - to mb backpanel

Did you use this gaming keyboard and mouse with your old PC, and was there any USB problem?


Regards,

|-|ardy

[LawyerPilot]

1) Kingston HyperX gaming keyboard (wired) - to mb backpanel
2) Corsair Scimitar Pro RGB mouse (wired) - to mb backpanel

Did you use this gaming keyboard and mouse with your old PC, and was there any USB problem?


Regards,

|-|ardy

No, they are new. I previously used a Logitech G900 wireless mouse and Razer BlackWidow Chroma wired keyboard (my son's idea because he needed 16.8 million color combinations ).

[Hardy Heinlin]

I would test another normal keyboard and mouse to check if that's the cause of the problem. It wouldn't be the first time.

[asboyd]

Try reversing the USB legacy options in your BIOS settings. I know my USB 3.0 MyBook external drive needed USB legacy turned off to work as USB 3....
Cheers,

[LawyerPilot]

I don't have them on hand, but I'll see if I can get my hands on a classic keyboard and mouse. In the meantime, I've tried just about everything (Windows drivers, older Thrustmaster drivers, Thrustmaster's TARGET software...which creates a combined HID compliant game controller).

The only thing I'm reluctant to do is disabling USB legacy in BIOS. If it causes my keyboard not to be recognized, I won't be able to get back into BIOS without a CMOS reset. And from what I've read online, I don't think USB legacy has anything to do with it since Windows recognizes my controllers and they work just fine in other simulators.

I'm certain it has something to do with how Win 10 treats the controllers, but I'm worried about sacrificing the flock.

And the investigation continues...

[Phil Bunch]

Also, you may need to check your USB hub's status.  I notice that many newer USB 3.X hubs function differently or perhaps not too well in various situations. 

It's possible for different versions of USB hub drivers, etc, to not be incompatible with a new PC and/or a new operating system.

Just a thought - I hope it helps.

[LawyerPilot]

After some trial and error, I've figured out that it is the mouse. Once unplugged, both controllers are detected. (Boy is it fun navigating the Windows environment with just a keyboard!)

I tried changing from hardware to software profile (basic profiles with no programming, no macros, etc.) and disabling the various HID-compliant mouse profiles in device manager, but no luck.

I know some programs don't allow software based mouse programming to prevent the use of macros (anti-cheat), but hardware based profiles usually do the trick. I'm going to do some more testing and see if I can get it to work before I buy another mouse.

[torrence]

Hi Trevor,

Best of luck, the good news is that the problems are almost certainly solvable.  I had similar but not identical problems a year or so ago when I switched from a Win7 environment to a more powerful rig with Win10.  An underlying issue - built into the Microsoft DNA - is that the system is always trying to 'help' you out and sets a lot of defaults for what they think 'most users' will want (across all hardware - PC's, Tablets, touch screens etc.) and these are very difficult to ferret out in the various layers of settings.  Something that I found that may help is that the system really cared which hardware USB sockets I had plugged joysticks, keypad etc. into.  Had to use the same config each time to get things calibrated.  Your mileage may vary but I'm sure there is a solution.

Cheers,
Torrence

[asboyd]

Again the mouse can be a problem if legacy USB is either on or off in BIOS settings ( I cannot remember which is the problem)
I had an issue with my mouse (same one as Win 7) but changing the BIOS setting did the trick.

Cheers,
Alex B

[LawyerPilot]

Victory is mine! Well, for the most part.

I am able to get it working by starting PSX with the mouse unplugged. PSX detects my controls and then I am able to plug my mouse back in and everything works like a charm.

I'm sure there must be some way in Windows 10 to assign priority to HID's, but I guess it's not worth the effort to research since unplugging and replugging is a snap.

Thanks everyone for all of the advice! Time to get airborne.