If you are having problems with PT3 30.6, report them in this thread.

30.6 sucks pretty bad IMO. Nothing personal, I'm not angry -- just a fact.

HUD crashed after 5 minutes of 2 tabling rush.

PT3 crashed when I tried to create a new folder (file requester) as I was trying to export session data for 2009 taxes.

also, since I upgraded, my table stats disappeared.

I tried marking them as "popup only", <click apply>, "table stats", <click apply> but that did not resolve the problem.

Please report your problems so that we can investigate.

Same here (party) old hud layouts gone, wont load at all (the hud) pt3 itself keeps crashing (seeing what i can do now), such is life.

also have a blank profile, maybe thats whats wrong?

Updating PT3 doesn't affect your layouts, etc. Are you sure you installed to the same location, with PT3 closed down?
Try rebooting and then re-run the Beta 30.6 installer.
If you still have trouble please report your problems so that we can investigate.

If you are experiencing crashes, it's imperative that you send us the crash log reports. Without these, we cannot locate the source of the crashes.

Trust us, we want these crashes resolved as badly as you do, but since we cannot replicate them, we are at your mercy. If you don't submit the logs, we can't solve the problems.

Definitely report these problems. We haven't received a single crash report from Beta 30.6 yet.

If you create a ticket with logs, please post the ticket number here so we can look at it ASAP.

My crashes aren't even producing logs any more and my problems are getting worse with each new beta

My HUD stopped automatically refreshing player stats with Beta 30.6

Ticket #82362.

Don't know if the logs I've provided are sufficient for you to find the problem, but I hope so. Let me know if you need any other info.

The following would really really pay dividends:

add an automated crash collecting bug reporting UI to PT3.

It could work like this:

• PT3 crashes
• I restart PT3
• I go to help>send crash info
• A window pops up asking me if I want to send the current crash logs, and other relevant info about my system to PokerTracker support
• the popup asks me to describe what I was doing when the crash happened
• I enter said description and click OK
• PT3 collects all the relevant files and ships them to PokerTracker support

The key point here is the effort required for me to provide the info is very low. This makes it more likely I will do this. It also does not require I go read some document on what to collect and how to file a bug report -- it walks me though the procedure and automates much of the drudgery.

It'd be a LOT easier - great idea

OK, I started PT3 (30.6) with logging enabled and played for a few hours (2 x Rush) with no problems.

I haven't noticed a performance problem so I'll keep running it with logging enabled and file a bug report the next time the HUD or PT3 crashes.

BTW, I started PT3 and started auto-import / HUD without my virus checker (McAfee) complaining. Previously McAfee was neutralizing tiltcommunicator when I started the HUD/auto-import so hopefully McAfee has fixed this.

EDIT: I'm still not seeing table stats so I guess I will file a report for that.

as mentioned above, automatic crash reporting is standard in a lot of applications on os x. e.g. PokerCopilot automatically gets crash reports sent to the developer any time the software crashes unexpectedly.

Well I'm glad to hear things are working somewhat better. Please do file that report though it will help.

I'll definitely talk to our development team about the feasibility of this. I don't know how easily our support system is set up to receive the automated system so there might be more backend work that needs to go in that way before we can even think about the front end for users though.

currently you ask for a laundry list of items for a bug report. The new front end could start by collect only those things you currently ask for.

You could simply create a zip file with all the desired information and the last step could be the user fills out the standard PT3 bug report on the web site and attaches the zip file. The time consuming part for the end user who doesn't have to deal with bugs day in and day out is learning (and then forgetting) what to collect. If just this aspect were automated that would help a lot. I've read over the "how to file a PT3 bug report", filed a report and then completely forgotten the process because I go a long time before seeing another bug.

If the new procedure were:

• PT3 crashes
• I restart PT3, click help -> collect bug data
• PT3 creates a zip file with all the information about my system you guys want
• PT3 gives me a link to click on that takes me to the bug reporting UI (or where ever you want me to enter the system).
• I fill out a bug report and attach the zip file.

Think about where the low hanging fruit is. The hard part for me isn't the sending the stuff to the PT team the hard part is knowing what to collect and collecting it.

I'll definitely have a developer look at this thread and I completely agree that it's a great idea.

giving the horse one more kick before I go ...

Think of programs that have so called "wizards" to help n00bs through common procedures (MS Word resume creation wizard). The idea is here is to create the easiest (for SW dev) wizard that gets the user over the data collection hump.

This wizard might quiz the user on the type of problem they are having (hand import problems, HUD problems, recent crashes) and then collect appropriate data. Presumably support would want a "kitchen sink" option (i.e. collect everything) that they could direct a user to use.