CTD During Campaign Alpha 9

[Ug0tserved]

First off i would like to thank the people behind this project for remaking one of my all time fav games back in the days bigger and better then it ever was

The reason behind this post is a critical error i have found in the Campaign Mission Alpha 9 when you load your units onto the the Transport and then click to start the mission itself. The game would normally load a short video sequence and then start the Mission but instead it just gives me a CTD without any error messages. I dont have any other graphic problems, crashes, glitches etc in skirmish or campaign, in fact thats the only bug i have encountered so far. Opsys is Windows XP, Gefore 9800GTX with the newest Drivers and everything.

Now i DO understand its rather bold to come here and make my first post a "complaint" about something but its a rather serious thing that i sadly cant fix myself ... Version was 2.2.4 aka last Stable release. Ticket has already been made, http://developer.wz2100.net/ticket/1723, with the savegame to replicate the Bug as well as the stderr and Warzone2100.RPT attached. I would really appreciate if somebody could give it a short look...

Regards

[Crymson]

Did you try with 2.3 beta 12? 2.2.4 is very old, and it may have been fixed already.

[Ug0tserved]

Nvm >.< guess thats what i get for playing with antiques right? ^^ Just got the 2.3 Beta12 and it works like a charm. Wil give the rest of the Campaign a run to see if i find anything else. Thx for the Help

[Crymson]

Nvm >.< guess thats what i get for playing with antiques right? ^^ Just got the 2.3 Beta12 and it works like a charm. Wil give the rest of the Campaign a run to see if i find anything else. Thx for the Help

Doesn't really make sense why they keep 2.2.4 around, since too much has changed in the code base, and all they ever say in the tickets is to update to 2.3 and see if the problem is still there.

[Zarel]

Doesn't really make sense why they keep 2.2.4 around, since too much has changed in the code base, and all they ever say in the tickets is to update to 2.3 and see if the problem is still there.

Because 2.3 still isn't stable. When you're updating 2.2.4 to 2.3, you're basically trading old bugs for new bugs. We think there are still more new bugs than old bugs, which is why we only recommend upgrading to 2.3 if you hit a particularly bad bug in 2.2.4.

[Crymson]

Doesn't really make sense why they keep 2.2.4 around, since too much has changed in the code base, and all they ever say in the tickets is to update to 2.3 and see if the problem is still there.

Because 2.3 still isn't stable. When you're updating 2.2.4 to 2.3, you're basically trading old bugs for new bugs. We think there are still more new bugs than old bugs, which is why we only recommend upgrading to 2.3 if you hit a particularly bad bug in 2.2.4.

Are you saying that 2.3 beta 12 has more bugs than 2.2.4?
My money is that no dev is currently working on 2.2.5 right?

[Zarel]

Are you saying that 2.3 beta 12 has more bugs than 2.2.4?

Yes, that is true.

My money is that no dev is currently working on 2.2.5 right?

Yes, that is true.

[Crymson]

Are you saying that 2.3 beta 12 has more bugs than 2.2.4?

Yes, that is true.

I think you haven't played 2.2.4 in a very long time. It has more bugs in it than the latest beta releases.

[Zarel]

I think you haven't played 2.2.4 in a very long time. It has more bugs in it than the latest beta releases.

None of them have been reported...

[Per]

None of them have been reported...

Trac contains 95 hits for 2.2.4 and svn/2.2. I think downstream distributors have given up reporting bugs from their trackers since we have told them we no longer support 2.2, as I see 2.2.4 bugs being reported in them every now and then without anything getting forwarded to us.

Also keep in mind that the whole reason why we started making 2.3 in the first place was because we gave up on fixing the bugs in the old 2.2 network code (the dpid mess), and instead backported the large network changes from trunk to a new 2.2/trunk mix.

[Buginator]

die 2.2.4, die!

And we have (basically) given up fixing anything from 2.2.x for a long time...Too much has changed in the code base, and I doubt any of us even have 2.2.x on our systems anymore.

It isn't worth keeping 2.2.4 alive, and we should strongly encourage everyone to try the latest 2.3 series.

[Zarel]

Trac contains 95 hits for 2.2.4 and svn/2.2. I think downstream distributors have given up reporting bugs from their trackers since we have told them we no longer support 2.2, as I see 2.2.4 bugs being reported in them every now and then without anything getting forwarded to us.

Okay, many have been reported, but still fewer than the newer betas. At least in 2.2.4, they're mostly generic crash bugs that usually don't come up, and sync problems that aren't that bad most of the time. 2.3 bugs seem to interfere with play a lot more.