(Retitle) TrackIR5.exe remaining after closed
Posted: Wed Jun 15, 2011 10:42 pm
Edit: Formerly Titled "Conflict between TrackIR5 and CM Control Center Win7-64"
Peripheral arguments are never enjoyable to debug, and this one's probably going to be extra special fun.
I've got a Windows 7-64 bit computer, with a CH HOTAS setup: Fighterstick USB, Pro Throttle USB, Pro-Pedals USB, and the CM Control Manager installed to do various remaps. Whenever the computer sleeps, it loses the controllers. Annoying, but I can run the CM re-detect to fix things. However, if I have run the TrackIR software any time since the last cold boot of my computer, the detect function locks and I can't access my controllers at all, until I've done another full shut-down.
I've also just noticed that the TrackIR software fails to work correctly after a failure to redetect the other peripherals. I'm going to go run a bunch of tests and post the results.
Addendum: Testing has identified the problem.
TrackIR5 does not properly exit when I close the software, and leaves a copy of the TrackIR5.exe *32 running as a background process. Apparently this scrambles the CM Control Center, when it tries to redetect the controllers after a sleep cycle, so it hangs, which is the most noticeable problem.
Another, more subtle problem is it can accumulate many copies of itself running in the background if the process doesn't get killed between sessions. This explains why, before I rebuilt my system recently, it would sometimes use 90% of my CPU cycles, even on a dual-core machine. Multiple copies of the program would be competing with eachother and flood the CPU. This had lead me to stop using TrackIR until I finished rebuilding my computer, as I figured, it was simply resource heavy.
Peripheral arguments are never enjoyable to debug, and this one's probably going to be extra special fun.
I've got a Windows 7-64 bit computer, with a CH HOTAS setup: Fighterstick USB, Pro Throttle USB, Pro-Pedals USB, and the CM Control Manager installed to do various remaps. Whenever the computer sleeps, it loses the controllers. Annoying, but I can run the CM re-detect to fix things. However, if I have run the TrackIR software any time since the last cold boot of my computer, the detect function locks and I can't access my controllers at all, until I've done another full shut-down.
I've also just noticed that the TrackIR software fails to work correctly after a failure to redetect the other peripherals. I'm going to go run a bunch of tests and post the results.
Addendum: Testing has identified the problem.
TrackIR5 does not properly exit when I close the software, and leaves a copy of the TrackIR5.exe *32 running as a background process. Apparently this scrambles the CM Control Center, when it tries to redetect the controllers after a sleep cycle, so it hangs, which is the most noticeable problem.
Another, more subtle problem is it can accumulate many copies of itself running in the background if the process doesn't get killed between sessions. This explains why, before I rebuilt my system recently, it would sometimes use 90% of my CPU cycles, even on a dual-core machine. Multiple copies of the program would be competing with eachother and flood the CPU. This had lead me to stop using TrackIR until I finished rebuilding my computer, as I figured, it was simply resource heavy.