Quote:
Originally Posted by MCAChiTown
Used my DriveHUD trial for 5 days now and wanted to see if others are experiencing the same things.
Upon opening BetOnline and the DriveHUD application I'm seeing both at about 100mb of memory. I fire up about 10 tables to see how good they are and I'm at about 180mb for the DriveHUD app, 140mb for the BOL client, and 40mb for the HUD. If I play a couple tables for 2-3 hours I notice that when I'm done the DriveHUD app is at about 500mb. If I play at 4+ tables for a few hours when I'm done playing it is close to 1gb of memory.
I have customized my own hud using the designer. When I load it some of the tables load to my previously saved positions. Other tables though are loading stat boxes bunched up in one area and other hud items in random positions. Even the tables that do load to my previously saved positions can be slightly off, especially if I'm using a slightly different window size. Nothing a little drag with right click held down won't fix.
When re-positioning a window with the hud running I do have a little bit of lag.
Is table data still being collected if I press stop on the hud?
These are all minor issues and I still love the product and plan on purchasing. I just want to make sure I'm not alone with these issues and if I am, what I can do to fix them.
Thanks for the feedback. What version are you currently using? This sounds like the HUD profile bug we had where it was re-loading HUD profiles into memory. This wasn't always happening, but it should be fixed in the latest version. I'm actually going to be posting a new release today now any ways as well, so maybe update and try this one. One other thing on memory though is .net reserves space as it runs things. It will sometimes look bigger than what it's actually consuming, and it will release it when it's needed by other apps. I have one laptop that it can sometimes do this on, and another it stays within a very strict profile.
As far as HUD position, on BOL if your HUD is too far off the table, it will re-position itself. Maybe this is what's causing it, but I'd need some more details, and maybe a log to see exactly.