my HUD doesn't work with beta 17

[six4withafro]

when i installed beta 16 it broke the HUD. i rolled back to beta 15, no luck. now i've installed beta 17, no luck. the buttons appear on the tables, but there are no stats.

I NEED SOME FUCKING HELP WITH THIS. it doesn't look like a lot of others are experiencing this issue, which makes me wonder if i'm just screwed. without the HUD, as you're well aware, pt3 isn't very helpful.

it would appear that something went wrong when i created the cache. how do i delete it ?!? should i uninstall pt and reinstall it? (gg dbs, of course)

it's one thing for there to be ongoing problems that are fixed incrementally, and it's another entirely for new betas to break things that were previously working. W.T.F.

[six4withafro]

well, i uninstalled and reinstalled pt3. i didn't do the complete uninstall because it takes 92875 hours to recreate pt2 databases, and that's my backup software solution.

success! i'm now using beta 15, which hurts because of the import errors that were fixed in 16 and 17, but it's better than nothing.

[six4withafro]

i spoke too soon. completely fucking unusable. ghost cpu cycles, between 70 and 100% usage, full tilt freezing, unable to run other programs.

[WhiteRider]

Try Beta 16 again (or if you're playing at Stars, Beta 17).
If you still have problems with the HUD, please send your log files via the support system. If you already did this, then please be reassured that they will be investigated, and every effort is being made to make the HUD work for everyone, but these kind of issues are not quick fixes as they are often hardware related, and can be quite specific to individual systems which is hard to recreate and test.
Development Timeline.

[six4withafro]

should i be including my hardware configuration with my trouble ticket, and if so, what exactly do you want to know?

[WhiteRider]

I;m not sure exactly what Josh will want to know, but I would suggest you include your CPU, graphics card (and make sure you have the latest drivers for it), harddisk size/speed/amount of free space; at least.

Also open Task Manager -> Processes tab and note which processes are using the most CPU, particularly when it spikes.