Random (6max) hands

[SQQTED]

Attaching the entire hand history file to a support ticket is the best thing to do.

I have not had any more problems since that day with auto import on the 5/16 build. I am almost certain it was my internet connection problems I was having that day. Keep up the great work!

Thanks,

SQQTED

[zippy]

SQQTED,

If you can attach some of these hands that are importing properly ....

So it's gotten to the point that it's noteworthy when things work properly?

I'm about to file a ticket. I had a PC crash and when I set up my new computer, I had to re-import all my hand histories. When I did this, two sessions showed up as less than full ring. One appereared as 2 max, the other 6 max. Both sessions were full ring and I verified by looking at the HH.

Today I played a session that was full ring, but auto-imported as 6 max. And sqqted, it wasn't my Internet connection on any of the instances.

It's worth noting that I play at Stars and FT and this has only occured with FT.

[WhiteRider]

Which version are you using, zippy?
Beta 12 decides the size of the table by looking at how many players are in the first hand.

[zippy]

Which version are you using, zippy?
Beta 12 decides the size of the table by looking at how many players are in the first hand.

I'm using B12. Indeed it appears the TWO of the THREE sessions were short handed when I sat. Thethrid one, Reno on 5/24-25 was 9 handed.Out of curiosity, this IS considered a bug in B12, right? I can't imagine you designed it this way...

[WhiteRider]

Yes, we agree a better way needs to be found to do this. The problem is that the table size information isn't in the hand histories for some sites, so there is no way of actually telling from a single hand what size the table is.

[zippy]

The problem is that the table size information isn't in the hand histories for some sites,

It's there for FT.

[WhiteRider]

Yes, that's true, and I think a bug was introduced which means that the 'adjust qualifying tables limits' logic was being used even when it isn't needed - this will be fixed in the next release.

[zippy]

Yes, that's true, and I think a bug was introduced which means that the 'adjust qualifying tables limits' logic was being used even when it isn't needed - this will be fixed in the next release.

Was this fixed in B13? I haven't upgraded yet, because B12 is working ok for me and I'm tired of being a beta tester.

[WhiteRider]

Yes, the logic is now only applied when the option is checked, although the logic itself hasn't been changed yet.

[zippy]

I "upgraded" to B13 and the problem persists. No, I will not open a ticket. No I will not send logs or hand histories. i've done that several times and it seems like you guys just ignore the feedback and keep releasing crap.

This is getting ridiculous. You're ABUSING your customers. I've never felt so ripped off in my life. FIX YOUR GODDAMN SOFTWARE.

Oh by the way, as I type this PT3 has created no less than FIVE icons on my task bar. LOL what a debacle.