Projected 2.6.1 Live Date

[Vern1701]

In other words, KJ missed a variable causing the PTR version to work on the Live servers. The actual post can be seen here:

http://www.ownedcore.com/forums/diab...ml#post3794162 (Unable to draw overlay if in "fullscreen" mode, yet I use windowed fullscreen)

It helps to reference the right post (the original one) when answering a legitimate question...

[User5981]

It helps to reference the right post (the original one) when answering a legitimate question...

What would really help at first would be people with reading skills.
People telling you how to answer a question while they could to do it before you but never did are also really "gifted"...
...Aaaaaannnnnd I'm done with that retarded teenager forum, bye all.

[ch25]

TurboHUD is collecting stats and using the PTR version with Diablo 3 live is ruining all the stats, that's why.

Why not just disable dashboard to stop collecting and let app running till update?
No stats anyway, but people could play.

[Vern1701]

After all the work KJ did to set the dashboard up? I think not. Don't ask when it will be ready, either.

[Ripperino]

Aaaaaannnnnd I'm done with that retarded teenager forum, bye all.

...........bye

[ch25]

After all the work KJ did to set the dashboard up? I think not. Don't ask when it will be ready, either.

I play other games now, so no fire in a pants.
Disabling dashboard for a while is no biggie. Just stop collecing. It is not atomic plant.

[stenbey]

Aaaaaannnnnd I'm done with that retarded teenager forum, bye all.

thanks god. u wont be missed

[DeepTerminal]

Can someone please explain what the dashboard is about? I'm genuinely curious. Also thanks for KJ for working on it.

[AL3x3y0]

. .

[Vern1701]

The dashboard collects user statistics and sends them to a separate server for KJ to analyze and improve upon the program. This is done anonymously for the user's protection, but could be used, in extreme cases, to weed out cheaters. Its main use is to verify the statistics and catch bugs that creep into the program for KJ to fix. This project is done on KJ's free time as a service to augment the base UI in D3. I hope this answers both questions.

[Buzzy62]

Saw this and thought it MIGHT be of some use....

Updated list of changes for legendary items - patch 2.6.1

[Vern1701]

KJ is working on it, I promise!

[cherouvim13]

I won't lie, I check almost every hour if the new version is up :P

Patience is a virtue

[KillerJohn]

Why not just disable dashboard to stop collecting and let app running till update?
No stats anyway, but people could play.

I am so happy that people knows better what should I do than me

(spoiler: no, I am not happy)

[KillerJohn]

New version will be up in a few days. I have to update the plugin interfaces due to missing stuff, also I am already in the middle of some refactoring, for example the burnt-in Waypoint element will be replaced by a plugin, free to change, and the cooldown-expired-speaker burnt-in code will be moved to a plugin too. Also the 64 bit release of the PTR build was broken, reading wrong realm name from the client, slowing it down, and causing a memory leak, potentially causing PC freeze/lockup/crash on the long run. Also this bug caused the Dashboard to collect insane amount of wrong data, which is sent back to the HUD instances (however this anonymized data is not display on the UI yet), but as it turned out the number of realm trackers went over 10.000 instead of 200 (because the realm names were broken), which means all HUD downloaded megabytes from the Dashboard Server, causing huge network traffic on both sides. Also I found some smaller bugs in the code regarding performance, and I detected some old bad design decisions I made years ago, and I want to get rid of them before 2.6.1 LIVE release of HUD "hits the shelves".

I hope this is enough information to stop complaining about "but it worked so why disabled it?".