HUD

[Valvally]

Hello, sorry for my poor english :)
I have not displayed correctly HUD. I play ipoker, so I have to press the "treat as 9 max" every time I open a new table.
But sometimes the stats overlap one on another. Saves only the restart. How do I fix this?
PS: Stats, which put on top does not go away even when close the table.

1.jpg

Open table. Launched HUD

(116.76 KiB) Downloaded 1460 times

2.jpg

treat as 9max

(119.4 KiB) Downloaded 1491 times

5.jpg

Closed table window

(311.98 KiB) Downloaded 1488 times

[WhiteRider]

iPoker have both 9 and 10 seat tournament tables and do not specify the table size in their hand histories, so until they do this you will need to tell the HUD when you're playing at a 9 seat table.

Do you have a normal Windows PC or are you running Windows in a virtual machine on a Mac or something? The only times we've seen HUD displays left behind like that have been in VMs where the graphics drivers don't correctly handle the Windows translucently functionality which PT4 uses.
If you're on a normal PC please make sure that your graphics drivers are up to date.

[Valvally]

I use a normal Windows 7. Do you mean the video card driver?

[kraada]

If those video card drivers are out of date it can cause problems like that - please make certain they are up to date as that may fix things for you.

[Valvally]

I updated the drivers for my video card, but it did not help me. Because of what disabled services in Windows 7 it ​​can happen?

[kraada]

Please try turning off 'allow translucency' and 'allow vector scaling' - you can find these options in the Hud --> Edit Hud Options --> General Settings page on the very bottom left. That may help make things work better for you.

If you still have that problem with those boxes unchecked please let us know.

[Valvally]

I turning off 'allow translucency' and 'allow vector scaling' but I still have that problem.
May be I have wrong version PostreSQL? (My version is 9.1.2)

[kraada]

The PostgreSQL version shouldn't cause that particular kind of problem, but I would recommend upgrading at least to 9.1.3 - there was a bug in 9.1.2 that was fixed in 9.1.3 that is relevant to us.