BZ2 1.3.6.4z30 - Open beta & testing

[Commando]

Raknet down for anyone else?

[Commando]

It appears to be back up. Blue Banana, are you running bz2 in Wine?

[Red Devil]

it was down last night about 2 am, but was working this afternoon.

[Feldheld]

Just tried and it seems to be down.

[Red Devil]

i just sent him a message about it.

[Huib-Bloodstone]

GSH reported it to raknet and tried again yesterday

[Commando]

It was down for a bit yesterday then came back up. I'm guessing it went down again.

[Commando]

Resyncs can't be too bad as I've heard nothing from blue banana.

[GSH]

With resyncs, armory throwing powerup, etc, your best bet at a fix is this:

make it happen on my machine, on demand.

-- GSH

[Jabbapop]

With resyncs, armory throwing powerup, etc, your best bet at a fix is this:

make it happen on my machine, on demand.

-- GSH

play a game with some of us from time to time, why don't ya!

[Commando]

It has to be reproduceable as he has to make changes, see if said change fixes the resync. It's not as simple as join the game and get resync.

[Feldheld]

What better way then than joining and get resync?

[GSH]

What better way then than joining and get resync?

Because the fact that a resync happened tells me just about nothing. BZ2 is ~500,000 lines of code. A resync happening tells me that one (or more) lines of code is bad, but it does not tell me where. Make it happen on demand, on my computer, and quickly, and I can add logging to tell where the problem's happening. A resync bug usually takes hours of adding logging, needing 10-100 runs of custom executables that change each run to add more logging. And the log files can be anywhere from 10MB to 250MB, so uploading those is out of the question.

Once again, if you want to see something fixed, break out of this "Win!Win!Win!" mentality. Break off the pursuit of TheWin!(tm), and try to isolate it. If you're hunting a bug, it's better to play 50 games of 5 minutes each, getting closer to the bug, than one 250 minute game. If you want a bug fixed, then make the bug happen on demand, on my computer, and quickly. Any other way -- which has sadly been the default -- does not get bugs fixed. Am I clear?

-- GSH

[Nielk1]

What better way then than joining and get resync?

Here's an idea:
Doing X results in resyncs occuring. Not doing X, results in no resyncs.
For example, building a scavenger means resyncs from then on, but not building one does not. Furthermore, is it really "from then on" or is it only "while scavengers are around".

That is just an example, but it is the type of direction that is needed. Instead of playing the game only to win, you need to actually make a test or two when you encounter an issue. You should play ST games and note down issues you get, then go back with other players to try to nail down exactly what causes them, going over your prior serious game to sort out possible causes and then using the new, slow, testing game to try these possible triggers in a controlled way.

[Commando]

For those upset about the resyncs, or lag, in the latest beta, consider this. We have approximately 33 testers on the 1.3 team. Out of 33 testers, I may have seen three different testers over the last month, if not longer.