Installed Steam, installed American Truck Simulator (ATS).
Ran the T150 installation program.
Plugged T150 into USB on computer. Drivers loaded. All configurations worked, and the T150 operated correctly in ATS. The T150 appears in the Devices and Printers screen as a Thrustmaster FFB Wheel.
Installed a Steam Link on big screen tv. No issues.
Purchased VirtualHere and installed.
Shared a Logitech Mouse and the T150 via VirtualHere.
Mouse works correctly.
When the T150 is plugged in, it appears on the Devices and Printers screen (in the Unspecified Section) as "Thrustmaster FFB Wheel" with the yellow triangle indicating a problem.
In Device Manager properties for the Thrustmaster FFB Wheel (USB) state:
"This device cannot start (Code 10)"
"(Operation Failed)"
"The requested operation was unsuccessful"
"Thrustmaster Install Service" is running in Task Manager, as is "Thrustmaster Device Driver Installer"
I have uninstalled everything (VirtualHere and then Steam) and reinstalled with the same problem.
I have read through the FAQs and other posts, and have not seen a solution.
Suggestions?
(System is Windows 8.1 Pro, i7-4790K, 64GB DRAM, GTX-1080TI, ASUS M7F MB)
.
It might be some win8.1 thing, do you have win10? I think you might need to update to that if possible
No way will I get near
No way will I get near WIndows 10. I have too many programs (mostly Amateur Radio related) that will not run on Windows 10.
Since the T150 loads and operates correctly when connected directly to the computer, the problem has to be VirtualHere related.
I'm also sure that I'm not the only one that has encountered this problem.
.
You are the only one with this issue, but i think most people use win10 so i think you have to use that or get a refund from valve for virtualhere
SOLVED
SOLVED
I uninstalled the FFB Drivers and the Thrustmaster Control Panel. This removed them from the Device Manager.
Unplugged the T150 from the Link.
I restarted Steam Link, then the computer.
Opened VirtualHere (which also opened Steam on the computer)
Told Link to connect to the computer.
Minimized Big Picture.
Installed and older Thrustmaster Control Panel and Drivers (TM_FFBRW_2630.exe)
When the installation program prompted to plug in the device, I plugged the T150 into the Link.
Everything installed, and I can now use the T150 through Link.
To do the final check, I opened American Truck Simulator, and configured all the Buttons on the T150.
I cannot find out how to change the title of this thread to [SOLVED} . . . . .
.
OK great, im glad its all working! Thanks for the tips i didnt know that the older version was required (I sold my T150 i used for testing , a few months ago so i couldnt test)
I'm having the same issues with my TX servo base too - Error 10
I've attempted to solve it with the above solution but to no avail.
I'm running Windows 10 so it should be working right?
.
I would expect win10 to work fine, so it always returns error 10 or do some parts of the wheel work ok?
When I first plug it in,
When I first plug it in, before I've click enable, it has the correct driver and wheel name(Thrustmaster TX GIP) , then when I click enable, the device disappears, then reappears as Thrustmaster FFB Wheel, when if I enable it, error code 10.
I have screenshots if that's helpful…
.
Ok, i think for this wheel we need to skip the reset.
Can you do this
Before you first click enable (i.e it still shows thrustmaster TX GIP) can you right click on it in the virtualhere client and select Custom Event Handler... then paste in this line
onReset.$VENDOR_ID$.$PRODUCT_ID$=
then press ok.
Now click Enable, does it work now ok? Im getting the steamlink to skip the usb reset command as that seems to reset its firmware incorrectly.
If this works can you also tell me the usb vendor id/product id of this wheel so i can pass this on to valve to put as a default setting in their link.
(You can right click Properties in the virtualhere client to see the usb vendor id and product id)
ok, awesome, I'll try that
ok, awesome, I'll try that out and get back to you. Thank you.
That seemed to work partially
That seemed to work partially, on a fresh install, a new client without the drivers installed from Thrustmaster, along with the Custom Event Handler allowed the wheel to be enabled and stay as the TX GIP, but wasn't detected in-game. I then installed the Thrustmaster drivers but that ended up disabling and disappearing the USB device inside VirtualHere, and then it reenabled as the FFB wheel again.
.
OK thats quite unfortunate, im out of ideas with this wheel, i think maybe get a refund from valve...Do you have something like a raspberry pi or some other basic embedded board? you could use that instead. If so let me know and there is another parameter that we can try (that doesnt work on the steamlink)