22 replies to this topic

[Foust]

This is a public service announcement for those who use TARGET along with windows 8.

Please avoid the 8.1 update, it will break your scripts.

The 8.1 update has changed how windows handles USB devices. This has a adverse affect on TARGET controlled devices.

Using myself as a example, I use TARGET to make the joystick act as a mouse. When TARGET creates the virtual keyboard, mouse and combined controller devices, they do not interact with the system.

My attempts to correct:

I read that the issue could be due to a new USB power savings thing. I disabled this in power management. Problem remained.

There is a known issue with windows 8.1 and certain ASUS boards and the AI Utility Suite. I uninstalled this Suite. Problem remained.

I ran the TARGET script editor in compatibility modes for windows 8, and windows vista. Problem remained.

I have a support ticket opened with Thrustmaster. I will update here with additional information and hopefully the fix.

[Darth Buddha]

The 8.1 update of Windows 8 brought a change to how the USB ports are managed by the operating system.
In order to save energy, the USB ports will be automatically disabled when there is no device connected or the connected device is on standby.
Your MFD panels do not send any signals to the PC when not being used, causing Windows to think the device is on standby and thus shutting the USB port down.
Since this change will impact a vast number of USB devices, we are currently waiting for Microsoft's official position on this update.
In the meantime, we are recommending you to open the Gamecontroller and access the Properties tab and leave it open in the task bar; this might prevent Windows from seeing the device as on standby.
We rest at your disposal for any further inquiries.

Thrustmaster Technical Support is at your disposal for any other information you may need. You can reach us online at the following addresses:
http://ts.thrustmaster.com/eng for the latest updates and FAQs
or by telephone at one of the numbers listed on the following page: http://ts.Thrustmast....php?pg=contact
Kind regards,
Your Thrustmaster Technical Support Agent, Robert
PS: To ensure the most efficient follow-up of your query, please be sure to include the reference number [424207-1382789591] of your file in the subject line of any emails you may send us later on.

Edited by Darth Buddha, 28 October 2013 - 07:11 AM.

[Foust]

Darth Buddha, on 28 October 2013 - 07:09 AM, said:

In the meantime, we are recommending you to open the Gamecontroller and access the Properties tab and leave it open in the task bar; this might prevent Windows from seeing the device as on standby.
We rest at your disposal for any further inquiries.

Has this worked for you?

[Darth Buddha]

Yes and no,,,, It's fickle

I just have not been turning on the mfd's,,, everything else works fine.

Edited by Darth Buddha, 28 October 2013 - 10:52 AM.

[Foust]

That really isn't an option for my T16000M. I will test this when I get home and update.

[Loc Nar]

Bummer... when I built my machine I could have gotten a free copy of win8, but thinking forward to fun times like this I oped for spending $100 on a copy of win7pro.

Hopefully MS comes up with a solution for this pronto, but I would hate to be holding my breath for those guys. In the meantime, is there a way to keep your device from being considered on standby?

[Darth Buddha]

I use a Thrustmaster Warthog on TARGET no issue...

[GRIMM11]

This also affected my RAT MOUS 9 gaming mouse, one button stopped functioning after the update.

[Sen]

I don't use target [whatever that is] but TY for the info on 8.1 and USB settings. . I wonder if that's why my game refuses to launch with my orbweaver plugged in??

I don't know why that would be the case, or why it's JUST the orbweaver, but it's better than the no clue I had 30 seconds ago

[Darth Buddha]

Sen, on 28 October 2013 - 02:09 PM, said:

I don't use target [whatever that is] but TY for the info on 8.1 and USB settings. . I wonder if that's why my game refuses to launch with my orbweaver plugged in??

I don't know why that would be the case, or why it's JUST the orbweaver, but it's better than the no clue I had 30 seconds ago

--> control panel
--> devices and printers
- Right click the orbweaver
- select properties...

leave it open in task bar,,,, Might help...

[Sen]

I'll have to try that. It's just weird, because I have several other razer input devices connected, but it's just THAT ONE that does it.

[Foust]

Ok I got my issue corrected. I did not get anything back from thrustmaster.

The issue did end up being the USB power saving "feature". Initially I turned off the USB power saving thing globally. However I should have know better than to believe windows global meant everything.

What I had to do was go into device manager, select the USB devices (I did them all) right click and select properties. Then to the power management tab and un-check the box that says something to the effect of allow windows to disable inactive USB devices.

Then I started TARGET and ran my script. When it created the virtual devices I did the same steps as above with those new devices.

I dont know if it persists through reboot yet, I just played while I could. Hopefully I don't have to do all this every time.

[Loc Nar]

Quote

I dont know if it persists through reboot yet, I just played while I could. Hopefully I don't have to do all this every time.

Glad to hear you got it figured out. In the unlikely event it doesn't persist through a boot cycle you can script up something in AHK to do it automatically now that you know what needs to be changed.

Weird you didn't hear back from TM, they've been good for me in the past, but I called them first and my query was sent to an address given to me by the guy on the phone, who was really nice and knew enough about their sticks and TARGET that I was impressed.

[KableGuy]

Foust, on 31 October 2013 - 04:41 AM, said:

Ok I got my issue corrected. I did not get anything back from thrustmaster.

The issue did end up being the USB power saving "feature". Initially I turned off the USB power saving thing globally. However I should have know better than to believe windows global meant everything.

What I had to do was go into device manager, select the USB devices (I did them all) right click and select properties. Then to the power management tab and un-check the box that says something to the effect of allow windows to disable inactive USB devices.

Then I started TARGET and ran my script. When it created the virtual devices I did the same steps as above with those new devices.

I dont know if it persists through reboot yet, I just played while I could. Hopefully I don't have to do all this every time.

you could write a powershell script to do this for you and stick it in the startup folder then set it to delayed start. That way you wont have to do it every time you reboot.

[Foust]

I just got a reply from TM and it was identical to the one Darth Budda copied above.

I replied with my work around steps.

[Darth Buddha]

Foust, on 31 October 2013 - 11:40 AM, said:

I just got a reply from TM and it was identical to the one Darth Budda copied above.

I replied with my work around steps.

Gonna try this out with the MFD,,,

[Foust]

It would seem that I have to go back on the solution.

After reboot and verifying USB power saving settings turned off, I still lose the joystick....

[Foust]

However...

Seems that opening the game controller properties for the combined device seemed to keep it working...

[Darth Buddha]

Yea,, It was a no go on the MFD's for me too,,, On the + side.... the driver for one of my USB hubs is now up to date..

[Foust]

This remains a issue. If I screw with it long enough I can get it to work, but I have not figured out the repeatable process yet.