Bugs from 5.1 over 6.0 to 6.1: A big list

[Commando]

It is a test version, as said in the thread, if it works, it will become 6.2 or something similar. We just don't have the numbers of willing participants to thoroughly test it, which is why d is available to the public.

I'm sure GSH didn't make a full build due to file size too. The build may be under 2 mb vs. having to download a full 90+ mb file for just a lag fix.

[Fulmen]

"JUST for a lag fix"... Yeah, I can tell you don't play MP. Not against other humans anyway.

[Red Devil]

a huge lag fix.

[Zax]

a huge lag fix.

Of 2mb in stature.

That doesn't even fit on a single floppy, fulmen.

[Ded10c]

"JUST for a lag fix"... Yeah, I can tell you don't play MP. Not against other humans anyway.

This build *is* basically just a lag fix. Downloading 90mb for just that is inconvenient, so here's a 2mb version for over PB6.1.

[Nielk1]

Has not anyone learned by not that 99% of what fulmen says should not be given a reply?

[Fulmen]

This build *is* basically just a lag fix. Downloading 90mb for just that is inconvenient, so here's a 2mb version for over PB6.1.

My point was that even though technically it's a mere lag fix, the impact of a lag fix is much more. Would you rather have everyone d/l a 90mb patch which is basically the crappy patch again + the lag fix or have a few people d/l just the lag fix and the rest leave the game? Because I'm seeing a lot of players being fed up with this lag bs and quitting BZ2, some permanently.

I'm telling you, we need a lag-free patch marketed as pb6.2 so everyone in pb6.1 will get it, and we need it fast.

[Commando]

As GSH said in the other thread, test the build, if no problems are reported, it will get repackaged at pb 6.2.

[Nielk1]

I'm telling you, we need a lag-free patch marketed as pb6.2 so everyone in pb6.1 will get it, and we need it fast.

I figure this needs some correcting.

And then when said patch gets released after no one touched the so desperately needed test fix and it in fact doesn't fix the problem, how many people will bitch about the end of the game and how immediately a patch is needed "give us 6.3 to fix this NOW!"?

If one wants something soon they have to put in some effort. Nothing is free.

[Zero Angel]

Fulmen, please arrange to test 89d with your friends. I'm sure you are all smart enough to know how to copy your 6.1 folder and then install the 89d build over it.

One of the reasons you guys are getting some of the private builds is to expedite lag fix without tons of private betas where strats do not get tested out. In other words, it is the best that GSH can do right now to address the 'fix the lag' complaints and also basically a 'private' build that the public can test to see if the lag actually *is* fixed. Believe it or not you actually need lots of players to test lag successfully, and the private testers do not play as frequently as the public players, AND are not all on at the same time (different time zones), so its rare to get more than a 4p game up -- hence why this release is such a promising idea.

If you can determine that the problems are gone than a more lag-free 6.2 will be released and everyone will be a little bit happier, it may also pave the way to more frequent 'public testing beta' that gives people access to what is currently the private beta releases, in case they actually are willing to test the latest 'bleeding edge' releases and help improve the quality of the major releases.

[GSH]

I have fixed two issues related to lagouts and lag for 89d. Basically, they were the issues noted in the logfiles which I urged people to collect over a week ago. I thought it was a fairly reasonable request -- change one file, play as you currently do, and email me logfiles. To date, the only people who have done that are existing 1.3 private testers. Nobody else did anything with that request, not even a "can you explain this better."

As I've said before, lag/warp/etc is not one bug. It is a swarm of bugs. But, as a programmer, I work on one bug at a time. Effectively, it's like a sniper rifle against a swarm of locusts. One sniper shot, at best, will kill one or two bugs and wing a few more. But, I can't pull out a flamethrower and kill a ton at once. Sorry. That's why I need individual logs, because I believe that there may be more bugs than the two that have been tweaked since 1.3.6.1. If there are more, serious bugs, I may need to do another round or few of test builds before a 1.3.6.2. But, I can't do this unless there are tests.

A lot of people whined when 1.3.6.1 came out, and demanded changes ASAP. I posted a public test build after about a week. And yet, those that whiners are not willing to test things. Those that want everything perfect, and want it yesterday, and aren't willing to help : I know who you are. The future of BZ1/BZ2 is here on these forums. If you're not going to follow my clear, simple directions, you're cutting yourself off from the future of BZ1/2. Future complaints will only fall on deaf ears until you prove yourself willing to work with me. I'm in charge here, you're not. I make changes for BZ2, you do not. Accept that, and things will go better. You still have the chance to turn around and do better than you've done over the past 7+ years. You could hardly do worse.

-- GSH

[Zax]

Here's a glimpse into the private testers' life:

Start a game, any game. Wait. Hopefully arrange something.

Get one person to join. Hooray! We can now test something.

Play through the whatever, trying to reproduce whatever needs fixing at the time.

Get 2 more joiners in an insanely unlikely coincidence, have 4 in one game. Gasp!

Fill out the rest of the slots if nobody joins with other instances of BZ2 on our PCs, which goes without saying isn't remotely similar to having multiple people.

Things look smooth, great, ship it.

Public: 5 players in game, if not 5-8. Panic! No way we could reproduce that, so it shows up in public under conditions we have no way of predicting.

Good day