Target Compiler Slow when coming out of Windows sleep modus

[Lange_666]

I noticed that since the last Windows update (20H2) the target Compiler is slow when compiling a script after the computer wakes up out of sleep.

Starting Windows dark and cold (or reboot) does not give that problem.

 

Seems to be this line: if(Init(&EventHandle)) return 1; // declare the event handler, return on error

[Lange_666]

Update: happens not only with a Windows coming out of sleep, just noticed it happened on a fresh boot too. The only cure i found so far is rebooting (which doesn't always help now).

Takes about 21 second for a script to compile when it's slow, about 2 secs when it's not. Once compiled the scripts run fine.

It hangs here:

USB HID device "Throttle - HOTAS Warthog"(USB\VID_044F&PID_0404\6&2035DA6D&0&2) selected

USB HID device "RIGHT VPC Stick TMW Grip"(USB\VID_044F&PID_0402\6&2035DA6D&0&1) selected

It takes quite a while before USB HID devices are selected. There's a slowdown before each one. After the 2nd USB HID is "selected" the script goes through until the end without slowdown.

If i stop the script while in the slowdown, it gives a message that it stopped on this line: if(Init(&EventHandle)) return 1; // declare the event handler, return on error

[Weegie]

The only way I know of at least partial remedy to this is to into Device Manager and ensure that Windows can't take control of the USB to shut it off under the Power Management tab (if you haven't done so already).

 

I also noticed that during some of the Windows updates Windows can re-enstate the this option forcing you to go through all the USB devices again to turn off the "Allow the computer to turn off this device to save power" option

[Lange_666]

Good tip there Weegie. Normally i check the power management after a major update because it also sets quite a few other things back to default but since this was a minor update and it didn't change back the stuff like the desktop fonts etc, i didn't bother to look at the rest (like USB settings). Seems Windows took the privelegde to change part of those settings back to default anyway.

[Davee]

Good tip there Weegie. Normally i check the power management after a major update because it also sets quite a few other things back to default but since this was a minor update and it didn't change back the stuff like the desktop fonts etc, i didn't bother to look at the rest (like USB settings). Seems Windows took the privelegde to change part of those settings back to default anyway.

 

I have USB settings to remain on but still have this issue also. For quite some time. I have re-installed Target, re-installed Firmware and no change. For quite a few months, I did not have this issue and had to re-install Windows. Then this all happened. Stuck!

 

[Lange_666]

Yep, setting USB to not be affected by power management didn't do the trick. Still having the issue. Only got Win10 20H2 a few days ago, didn't had the problem before the Win 10 update.

[Lange_666]

Also, when the compiler is slow, it will combine both stick and throttle but keep them separated also. This means you have 3 controllers in DCS instead of one. The stick, the throttle and the combined one.

If the compiler does a quick job, there is only the combined one to be seen in DCS.

[Lange_666]

Forwarded the issue to Thrustmaster Support.

[Top Jockey]

Yep, setting USB to not be affected by power management didn't do the trick. Still having the issue. Only got Win10 20H2 a few days ago, didn't had the problem before the Win 10 update.

 

That's one of the motives I'm not yet much inclined to change to Win10.

 

Obviously I keep concerned about eventual security issues with my Win7... but I don't stand that microsoft decides totally at their on will, to change stuff on my PC without my consent.

[Lange_666]

It's more like setting stuff back to default, mostly stuff you don't have direct access too anymore without a registry change (or a tweaker program which does the registry hack for you).

[Svend_Dellepude]

Unplug and replug controllers. Should fix the issue. It's a long standing issue that sometimes happens after a regular boot up too.

[Lange_666]

No it does not. Since i have the Warthog, around a year now, i didn't have to do that once (neither did i had to do it with the Cougar which i owned for 17 years).

Never in that past year the Target Script Editor would hang/pause 10 secs before each "USB HID device "xxxx - HOTAS Warthog"(USB\VID_044F&PID_0404\6&2035DA6D&0&2) selected".

Unplugging and re-plugging could do the trick but as long as until the next reboot (or coming out of sleep) and then what...? Unplugging replugging again?

[speed-of-heat]

I noticed that since the last Windows update (20H2) the target Compiler is slow when compiling a script after the computer wakes up out of sleep.

Starting Windows dark and cold (or reboot) does not give that problem.

 

Seems to be this line: if(Init(&EventHandle)) return 1; // declare the event handler, return on error

 

Run the compiler, then run windows store... it works don’t know why, then close the store

[Lange_666]

Good find there spead-of-heat, nice work around.

Now still the BIG question... Why?

[speed-of-heat]

No, idea, but also killing the store process works too ...

[Davee]

No, idea, but also killing the store process works too ...

 

That was the original remedy. Store interferes somehow with Target. Which makes me now just realize that store may have been restored by Windows update. I will take a look and post back.

 

OK: Here we go.

Yes, Microsoft Store is back on my computer. However, it is because I reinstalled W10 last month and forgot to remove the Store. Completely removing Store solved the problem for me over the last year so I did it again.

 

Here is the link on how to do it.

 

 

This does work!

 

Cheers

[Lange_666]

Removing Windows Store is no option in Windows 10 i guess (i also have FlightSimulator 2020 so...).

Terminating the process is something i only can do through the Windows 10 settings it seems (but it works).

Also, it looks i can't preventing it from startup either, at least i can't find a solution for now.

[Davee]

Removing Windows Store is no option in Windows 10 i guess (i also have FlightSimulator 2020 so...).

Terminating the process is something i only can do through the Windows 10 settings it seems (but it works).

Also, it looks i can't preventing it from startup either, at least i can't find a solution for now.

 

Method is right above your post. :)

 

[Lange_666]

Yeah but as i said, i have MS Flightsimulator 2020 installed and updating (and license) go through the MS Store. So that's not an option.

It worked before with the Windows Store installed so it should work now too.

 

What bugs me the most is that part of the time it works with the Store installed, like just now. So uninstalling is like removing your entire arm if you only have a little pain now and then in pinky finger.

[Davee]

Yeah but as i said, i have MS Flightsimulator 2020 installed and updating (and license) go through the MS Store. So that's not an option.

It worked before with the Windows Store installed so it should work now too.

 

What bugs me the most is that part of the time it works with the Store installed, like just now. So uninstalling is like removing your entire arm if you only have a little pain now and then in pinky finger.

 

Yes, that is an issue alright. Gotta keep it installed as a necessity. TM hasn't moved to much over the years with software upgrades and I don't think listens to requests. Cheers

[speed-of-heat]

this works quite well as part of a s script:

 

C:\Windows\System32\taskkill.exe /f /im WinStore.App.exe

[Lange_666]

Can it be put into a Target script directly?

 

Had a go already but no joy. I'm only an adapter when it comes down to Target scripting, although i start from scratch for my profiles from a blank .tmc file, but without C (or derivates) knowledge. Going to retire soon and from then on i have a lot more free time available and one thing on the to do list is working my way into C (or a derivate) a bit. Part of my work contains PLC- and robot programming so some basics are already present.

[speed-of-heat]

not tried that , i just use a script file top launch the target compiler

[Svend_Dellepude]

Good find there spead-of-heat, nice work around.

Now still the BIG question... Why?

 

Yeah. Forgot about that one. I got all of my controllers in the same USB hub which has a power switch. Powering it up after boot does the trick too.

[Lange_666]

Now this is the 3th day in a row where i didn't had the problem at all and every time i booted the computer or let it come out of sleep, i'll let the Target Script Editor run a script just to see what it does.

I haven't updated anything nor did Windows Update updated anything besides the Defender updates. I just wonder why it works one day and not the other or why it worked for a year, then behaved badly for a few days and now works again?