PokerTracker

Running the Hud causes my Logitech G5 mouse to lose USB connection. It appears to happen when the screen redraws. I have a G15 keyboard as well, and it froze once. The mouse froze numerous times.

I'm running the setpoint software and G-Series Keyboard Profiler.

Does this happen if you don't start the Hud with auto-import?

Josh wrote:Does this happen if you don't start the Hud with auto-import?

Can the Hud be started without having auto-import running? It's greyed out.

The mouse and keyboard do freeze when the Hud is started manually, as opposed having "start automatically" checked.

It also only seems to happen when actually importing a file. I've left them running while not playing hands and there are no freezes.

I meant starting auto-import without starting the Hud. Sorry for the confusion. Does the freezing happen if the Hud isn't running?

Josh wrote:I meant starting auto-import without starting the Hud. Sorry for the confusion. Does the freezing happen if the Hud isn't running?

It only happens when the HUD is running, and it happens immediately after a hand import.

Importing a hand without the HUD is fine, importing a hand with the HUD means I immediately lose the mouse, every time.

As you can imagine, this makes playing with the HUD impossible.

Let me know if you need more information or want me to test something specific.

Do you have another USB mouse you can test with to see if it's that particular mouse or your USB devices in general? Keyboard too?

Josh wrote:Do you have another USB mouse you can test with to see if it's that particular mouse or your USB devices in general? Keyboard too?

Josh, I've localized the problem. It's ProgressSQL related with certain USB hubs. While the mouse and keyboard issues would always occur as listed, the occurred without the HUD sometimes as well, but far less often.

If I bypass the HUD, then neither the mouse or keyboard freeze, but I'll sometimes lose the printer plugged into the HUD. I'll try different HUBS to see if the conflict is more generic.

TLDR version, I've found a workaround for what appears to be a localized issue.

Wow, that's a strange problem. I'm glad you figured it out (mostly). Please let me know if you come up with a solution.