Bodog sng very buggy

[zubs1aa]

You are the only one reporting these kind of problems at the moment, so your log files (along with hand history files and screenshots) would really help.

He's probably the only one playing them

[ihatepostgreSQL]

You are the only one reporting these kind of problems at the moment, so your log files (along with hand history files and screenshots) would really help.

He's probably the only one playing them

haha, i think you are right.

and pretty soon i might have to leave buggydog because PT sux on it!


honestly i only played on bodog and bodog was the only reason i bought pokertracker.

i always thought pokertracker sucked that bad on every website till i played at full tilt... speechless...smooth...near flawless...then went back to bugdog and i asked myself wtf am i doing here and why do i keep coming back!

and here i still am...

i am the only person in the whole world that uses PT and plays bugdog sng's.
that is why i play at bodog (most the players dont use any hud at all they are all blind as bats
and even the ones that use PokerTracker on the sng have it so bugged out that it is better not to even use it!)




they say a picture says a 1000 words.

well i said over a 1000 words so there is my screen shot.

i do not understand you guy do not believe me?

someone made the hud on bodog, so someone knows what they are doing, if someone is able to make a hud for bodog they do not need anything more from me other than to know there is a problem. and a few 1000 words.

sincerely,

postgresql is not that bad once u get to know it.

(all you have to do is click here and here then it is fixed, i had to do that atleast one more time since you guys helped me with it last time)

[kraada]

I'm afraid I don't see a screenshot in your post. Could you zip it up and attach it to a support ticket?

[ihatepostgreSQL]

haha and has anyone tried to see the previous hand through bodog last hand feature?

haha bodog is so cool

they going to keep the fish/donk blind as bats as long as they can.

bodog does not want winning players because they cash out and they have to deal with all that mess.

bodog only wants donks/fish that lose money

bodog wants to keep everyone dumb

PT is just a big help seeing the last hand but it could help so much more.

[ihatepostgreSQL]

I'm afraid I don't see a screenshot in your post. Could you zip it up and attach it to a support ticket?

i think u missed the part about a picture is a 1000 words and i spoke way more than a 1000.

good day.

[zubs1aa]

well i said over a 1000 words so there is my screen shot.

i do not understand you guy do not believe me?

someone made the hud on bodog, so someone knows what they are doing, if someone is able to make a hud for bodog they do not need anything more from me other than to know there is a problem. and a few 1000 words.

I am sure they believe you but yo uarent helping them solve the problem. You are doing teh equivalent of saying to the car dealer "my car is broke, fix it" but not giving them more info.

If yo usend them the logs, hand histories, screenshots etc on a ticket.... they really will help.

[ihatepostgreSQL]

i am just not good with computers and would rather explain it than to ruin some type of file.

maybe if i was more computer literate.

if there are any type of question i could answer with words i would be more than happy to.

i keep coming back and giving updates of what is going on and i try to explain in details that would be helpful to get the problem solved, so if there is any type of question, i am more than happy to.

good day.

[kraada]

All you need to do is, when starting PT3, use the Logging Enabled link on your Start menu.

After you have these problems, go to this link. In the reference field, put the link to this thread so that the support technician can find your description, and click "Browse" next to Attach File. Find the C:\Program Files (x86)\PokerTracker 3\PokerTracker.log file, click Ok, then Attach. The file should show as attached. In the main text box you can just type "see thread" if you'd like - what we really need to see is these logs to figure out exactly what is going wrong in PT3 for you since this doesn't seem to be happening to anybody else. Trying to debug the software from a description alone is nearly impossible in most situations no matter how good the description is - if I myself find a bug when we're doing alpha testing, I still always give my logs to the developers, because it is the easiest way for them to see what needs to be done. For the record, I do believe you're experiencing what you say you are - but without the logs there's little more I can do.

[ihatepostgreSQL]

last time i did a few changes and PokerTracker was out for a year!

i tried fixing it so many times for so long and so many hours... (it was scary and embarrassing)

i gave up on it and thought to give it one more try many months later and so i did.

i put many hours into it and many days...

then one day "my new love" at the time saved me from all the pain i was having.

all he said was "click here and click here"

i did as he said and clicked there and there and tried to run poker tracker and IT WORKED!


listen all i want to do is click here and click here and then have bugdog working like full tilt.


i mean the only reason i made this user name was to get pokertracker and postgresql working on bodog just to find out how buggy it is.

i feel silly having this user name now that all i had to do was click here and click here to make postgresql and pokertracker work.


good day.

[ihatepostgreSQL]

All you need to do is, when starting PT3, use the Logging Enabled link on your Start menu.

After you have these problems, go to this link. In the reference field, put the link to this thread so that the support technician can find your description, and click "Browse" next to Attach File. Find the C:\Program Files (x86)\PokerTracker 3\PokerTracker.log file, click Ok, then Attach. The file should show as attached. In the main text box you can just type "see thread" if you'd like - what we really need to see is these logs to figure out exactly what is going wrong in PT3 for you since this doesn't seem to be happening to anybody else. Trying to debug the software from a description alone is nearly impossible in most situations no matter how good the description is - if I myself find a bug when we're doing alpha testing, I still always give my logs to the developers, because it is the easiest way for them to see what needs to be done. For the record, I do believe you're experiencing what you say you are - but without the logs there's little more I can do.

thats all?

maybe someone on the team can play 12 sngs back to back and find out themselves.

good day.