Notpron Forums

Allright, insult me if you wish, but i just had to say this =)

We all noticed a slight difference in online gameplay when deathball 2.1 came out, and it really felt shitty, whether it's the same thing that happens every time a new version is out or it's really bad, i'd just like the following things to be fixed, or even just rerolled to like they were in 2.0:

1. FPS rates in Cube - I've always played ut2k4 on minimum (everything) in order to pull out 90~120 fps on my GeForce4 Ti4600 during online gaming, and i've been pretty used to play 5on5 matches in Cube at that smooth rate. After mr. DavidM decided to go fix what wasn't broken, i have between 40 and 50 fps.. I have to live with bad ping and constant packet loss, but at least i'd like to play withouth slowdown

2. SmallCube's Map - Yet another thing fixed when it wasn't broken. Did anyone really complain at all about the map size? Or did you just change it to microscopic size withouth asking, gee, let's see, the community, first? Back to normal size please =)

3. Catch radiuses, strange goals - On the first couple of pickup i played on 2.1 it became somewhat evident that something was wrong. Everyone withnessed balls going _directy thru_ the keeper, not only on the replay but it looked a bit obvious during the play itself. I suggest you verify everything related to the catch radius, specially of keepers, if you changed it since 2.0. I remember you testing it with me and others in the first betas, and i wasn't convinced back then...

4. Volley bug back? o_0 - Yes it's back. It's not lag mr. davidm. If it was lag, it would volley when i holded down/bashed my primary fire button right in front of a ball withouth any movement at all... When this happens i also can't fire the ball when i catch it. Or it fires with a weak power and overcharge direction after i release fire button when charging. And passing/releasing with secondary fire either doens't work or it comes out a long time after pressing the button. Investigate and fix this please

5. Why can we still bounce then volley instantly? Is it not obvious that several people abuse the fact that not only it adds extra speed to the volley but it also allows easy "noob-cannon"-like aiming?

Cheers.

yep at holy_shit

keeper radius and bounce volleys i totally agree, smallcube i dont and fps i dont

fps = i have a mofo'ing mx400 16 or 32 mb whateva i dunno its shit, and i had 20/30 fps on very first 2.0, but after a while its gradually creeped up (i r pwn) its now at 60 so nah...

keeper = well mr m ive said all i had to say before.. its still there. but good job fixing the close ups.

volley bug = i aint experienced it, i dunno dont flame me

small cube = its better smaller, i prefere wastelands cuz its smaller. but the radar is a fuckup, it wasnt like that before, y know?! bring back old smallcube

bounce is just a anoyance to keepers cuz he knows he cant keep and he likes to see me moan !

I use to have an inconsistent fps in 2.0, now it is better. Smallcube is a matter of taste - some servers have old smallcube on them.

However a 2.1b to fix bugs should be done. You've got the spawn bug, volley bug is back and apparently 2.1 is not friendly at all to install on a dedicated server. And there are still minor bugs (shoes on corpses, goal post beacon changing colour in middle radar etc) that could be ironed out.

I got a GeForce FX 5600 Ultra and I experience slight FPS loss on Cube only, not SmallCube really... volley bug I experienced it at least a half-dozen times, keeper I've seen the ball sneak through when it appeared caught, and one other big one... DA FUCKIN SOLDIER BUG!!! lol

Of course I'd like to see a quick patch too.

But I also wanna see an effective one - ie it fixes more problems than it creates.

If I remember correctly, the public beta testing period for 2.1 was only a couple of days at most. I remember thinking that this simply wasn't enough time. But I believe there was some kind of deadline for the Editor's edition right?

Anyhoo, most newcomers are being put off but the severity of some of these server bugs and the public servers have been dead because of them.

If a relatively quick patch cannot be made, I'm in full support of rolling back to 2.0 until 2.1 is truly ready.

if not a quick patch now a smaaalll patch now to fix spawn bug, its being abused, tbh i cant wait for the new version before adding to another abused pu

I personally think a 2.1b shouldn't be released until the problems with the enhanced locking code are fixed

And seeing as that could take a while, I wouldn't mind waiting a bit longer I guess.

ps: First one that voted the 2nd option? o_O
Don't you think you're overreacting?

Why can't we just get a new Deathball.u file every so often to fix these minor bugs? I thought that's why the autoupdate engine was created in the first place...

what holy said !

Messy wrote: I personally think a 2.1b shouldn't be released until the problems with the enhanced locking code are fixed

And seeing as that could take a while, I wouldn't mind waiting a bit longer I guess.

ps: First one that voted the 2nd option? o_O
Don't you think you're overreacting?

no.

if u wanna join a 5v5 pu, u can bet it will be abused with the lame bug. a small patch just to fix the spawn bug for now

I agree with holy 100%

Minor things but need to be sorted (although I need to upgrade my comp anyway so maybe the fps issue isn't so huge).

Shev: I'm sure the 'pro'-community can be responsible enough to not childishly abuse that bug and use common sense so as to not spoil it for everyone? :\

48 hour ban on #dbpickup imo if someone abuses it.

edit:

Esorcismo wrote: Why can't we just get a new Deathball.u file every so often to fix these minor bugs? I thought that's why the autoupdate engine was created in the first place...

idd :< I was excited hoping DB would autoupdate to 2.1 too ;p
Guess it's not meant for such huge updates either though, then again..where are the small updates it will be used for then? O_o

Maybe this is the appropriate time to start using it?

The autoupdate was removed in 2.1.

the bugs are there cuz 90% of the community literally couldnt be arsed to beta test. and they wont go if the same dont help again this time.

who cares why they are there, just fix them and release a patch please , and can you make 1.2s replays available as an option of replay length, 4 seconds is waaaay to long