I don't understand, how does thousands of effected people uploading this thing help at all, it's not like it's an isolated bug, it effects nearly or exactly everyone oO?

Chewits

Northern Ireland1200 Posts

December 27 2008 16:17 GMT

#142

On December 27 2008 04:50 Nightmarjoo wrote:

Show nested quote +

I don't understand, how does thousands of effected people uploading this thing help at all, it's not like it's an isolated bug, it effects nearly or exactly everyone oO?

It doesn't effect everyone.

LonelyMargarita

1845 Posts

December 27 2008 23:44 GMT

#143

On December 27 2008 04:50 Nightmarjoo wrote:

Show nested quote +

I don't understand, how does thousands of effected people uploading this thing help at all, it's not like it's an isolated bug, it effects nearly or exactly everyone oO?

It affects a few people, but everyone it affects you hear complain about it. It doesn't affect me, so I haven't posted in the threads about it, nor have thousands of others it doesn't affect. If everyone assumes "oh well there's enough people affected that I don't have to send them my info," then not enough will actually do it, and the problem will never get fixed by Blizzard. Take the 5 minutes to send them the info so you don't have to worry about getting banned for using R1CH's fix.

All I get is the piecemeal graphical loading and the /r bug, which I believe everyone has and they obviously know about. They've probably fixed the /r bug and don't care about the slow loading, but are waiting to fix everything to release a new patch.

nataziel

Australia1455 Posts

December 28 2008 11:11 GMT

#144

R1CH is a fucking legend

d(O.o)a

Canada5066 Posts

December 30 2008 15:43 GMT

#145

Wow r1ch; blizzard got owned so hard.

HeavOnEarth

United States7087 Posts

January 04 2009 00:50 GMT

#146

On December 24 2008 12:20 Hittegods wrote:

Show nested quote +

Laptops running at 100% CPU usage consume more power and generate more heat. Those two features are usually not wanted.

This.

overheat FTL

R1CH

Netherlands10341 Posts

January 04 2009 05:33 GMT

#147

On December 23 2008 09:33 AdamS wrote:
Can you guys go to the B.net forums and send in the dxdiag and msinfo that Dat asked for? We are having a hard time recreating this issue and it would help us immensely if we can find out exactly what hardware you are running and what background processes are running.

thanks!!

/AdamS

Blizzard Tech Support

http://forums.battle.net/thread.html?topicId=13769997583&sid=3000

I missed this post until someone on IRC mentioned it - there is nothing hardware or software specific that causes this issue - it's simply a bug in the BW code. Not everyone will notice an issue with this patch because a) most people don't play at a competitive level and will not notice a tiny lag problem and b) on older PCs, BW doesn't have as much idle time to sit in the "wait" loop. I'll CC this to the email posted on the Blizz forums, but the basic problems are as follows:

1. Using Sleep without calling timeBeginPeriod:
Unless another application on the system calls timeBeginPeriod(1), calling Sleep(1) will sleep from anywhere to 1-15ms. Sleeping 1500% longer than you intended is not good for delays

.

2. Too many Sleeps:
In patch 1.16 there is a Sleep period added during the message loop processing as well as a Sleep period added if the elapsed time between two frames is short. This second one is unnecessary as as long as there is a Sleep(1) somewhere in the main loop, 100% CPU usage is reduced. 116fixer removes this secondary Sleep.

3. Sleep of 5ms instead of 1ms after the message loop:
Additional delay is added by sleeping for 5ms after the message loop. As mentioned above, 1ms is all that is necessary to prevent 100% CPU usage.

4. Sleep of 5ms instead of 1ms in the bnet menu loop:
The battle.net interface feels laggy due to the inclusion of a 5ms Sleep instead of 1ms.

5. /reply and /r errors in the bnet interface:
These are simple typos (missing / before the string) and are easy to fix.

SpiritoftheTunA

United States20903 Posts

January 04 2009 08:33 GMT

#148

I emailed your post off to blizzard as he requested in his forum post just in case you didn't.

uppTagg

Sweden473 Posts

January 05 2009 14:58 GMT

#149

The basic issues stated by R1CH above sounds very noobish to me :S

All the thread-coding I've done is in java and I even coded a thread-loop without a sleep(1) by accident and I felt that was a very obvious noob mistake by me when I figured it out and added that sleep... (the game ran smooth on my macbook but the problem became apparent on slower comps where the framerate sucked because of that loop)

From my small experience with threads, even I know about points 2-5 above (I never knew about timeBeginPeriod.. interesting ^^) and it's o_O to me that someone at a company like blizzard would make those mistakes..

Also, bleh for assembly ;< gj R1CH! ^^