What's up with the 1.40 patch?

[RMcLeod]

1.40 Patch is not going to fix any of the real issues. Like the Titan issues, recuit bug, connection lost bug, and the other things. The only thing I saw in the beta was useful was the saving the kits and is about it. If they could fix the hit detection on the weapons, SAAW issues, and others things that have been reported would be a great boost for this game.

Do not expect 1.40 to come out anytime in the near future.

I don't think the "Titan issues" or "Connection Lost" issues are something they can iron out because not everybody suffers from them, if not everybody suffers fro them it's very difficult to replicate the error, and error replication is one of the first steps in bug fixing.

Again because the recruit bug is a totally random (and for most a rare) bug it will be difficult to replicate reliably.

[The_Eliminator]

From your statements you sound like you've never written a line of code. let alone debug a few thousand lines.

erm...is this some sort of joke?

You implement each stage of the patch at once and then you rerun the patch on servers seeing at which point the patch crashes and in which part of the coding.....correct me if im wrong but that is debugging...

Oh and by the way, no one here has been saying release it now...

[Biotech2142]

Maybe is just me but I have not seen Dice around these forums for a while.

When a patch is about to be released, I remember them to be away for a while.

Maybe they are busy at CQC stage for tomorrow...

[Vreki]

I think they should build the patch again from scratch implementing everything instep by step and then see what causes the crashes in between step of the patch development, then they know which part to work on.

I cant see it being the clark buff or the scar buff and the new map is fairly easy to implement i would have thought, i think its the kit saves that is crashing the servers.

Isn't the weapons buff just a change to config files, not an actual code change?
I don't think that affects the servers.
But likewise I would think that kit saves are purely client side, no need for the server to be involved in that.

I think one of their bugfixes, or maybe the Clark-RDX is the culprit.

erm...is this some sort of joke?

You implement each stage of the patch at once and then you rerun the patch on servers seeing at which point the patch crashes and in which part of the coding.....correct me if im wrong but that is debugging...

That is not always possible.
The code may be distributed through various classes, which contains parts from different fixes. Or it may be the interaction of some of the fixes that causes the crash.
So suddenly you have 20+ builds that you need to do testing on.

Likewise you can not always see where the code is crashing.
Standard methods is to attach a debugger, but that usually requires the code to be build in debug mode, which might actually make the error go away.
Or you could log the progress through the code, but that can generate huge amounts of data if you dont know where to look.

And even better, "Crash-Code" is often a memory access violation, which can be almost impossible to track down, since it can be a very specific situation that causes it, and may originate a entirely different place in the code than where the crash occurs.

Fixing an error is usually easy, but finding it can be very hard.

If I was trying to fix this mess, I might opt for the binary search approach.
Split the fixes in two different builds, and watch which one crashes.
Split the crash build again etc. until you have narrowed it down, and then create a release minus the buggy fixes.

But we have suggested that before, and DICE never seems to be willing to cut the sick fixes from a release.

[bravespear]

Again because the recruit bug is a totally random (and for most a rare) bug it will be difficult to replicate reliably.

What exactly is the recruit bug? I haven't heard of it until now.

[The_Eliminator]

What exactly is the recruit bug? I haven't heard of it until now.

the stats servers register you as a recruit but still with all your times for various awards so you can go on servers and get various awards over again.

Its rare but does happen.

[Bardo]

you log into a server and you are a private. all unlocks gone just like when you first started the game. you also get duplicate awards you already recieved.

edit: doh! the eliminator beat me out

[Deesies]

There were a few issues with the beta that has to be addressed.

Unless you want a repeat of BF2 1.3 and having servers crash every round? :P

[The_Eliminator]

Deesies is right, just give it time, it will be released when its finished, i just wish they would tell us more about it.

[Roger Smith]

and where is wake 2142

[The_Eliminator]

and where is wake 2142

yea true, where is noobs diary 2, where is wake 2142, where i patch 1.40...........i sense a black hole in the internet continuum :shock:

[Roger Smith]

where is a decently coded battlefield game? last one was um, vietnam.

[The_Eliminator]

I think BF2142 is very well coded tbh, just a few hiccups in places, that why we have patches, no game is perfect.....except perhaps Far Cry but thats a different matter

[Roger Smith]

are you freaking kidding? this engine is packed full of bugs, its been said that its held together with glue. most games these days are getting progressivly worse coded.

[The_Eliminator]

unfortunately i agree with you about the games now days, but this is only due to the fact that they are getting a lot more complex. When you look at something like DOOM and then look at how far more advanced Crysis is that is how far development has come in a very short time. The problem is that perfectionists dont make these games, if they did then by pure OCD they would fix all the bugs.