Unexpected crash

[pranjan]

This is a unique bug I am facing here...

See the first image ...



Now see the second image where how my players killing each other...



Also one thing noted that the player becomes gray just before attacked. After this game crashes.

Here is the rpt file generated by the exe...
RPT file

Please help someone...

[pranjan]

One of post told me that this would be video driver cause so I updated latest driver from intel. Again the same problem occurred.

Out of topic question: How can I upload images in this forum (I uploaded on my site and then link ).

[KukY]

NEXUS takes over your structures on that level,but not your units,as much as i know.
NEXUS took over your unit,that's all. I have no idea why game crashed.

[i-NoD]

Ok, I have some idea on how to fix 5 similar crashes (projectile issue). Could you please attach your save game, so I can check it?

[pranjan]

Just wait for few moments.

[pranjan]

Download the complete saved games data files from here...
Warzone_2100_2_2.zip

Thanks!

[i-NoD]

You shouldn't mess with Heavy Plasma cannon - most likely Nexus has implanted a logic bomb in it
This particular firefight was causing troubles

wz2100_shot_009.jpg

Anyway should be fixed in next release.

[Zarel]

Anyway should be fixed in next release.

...erm, wrong branch. Next release is in branches/2.2_net/. Did you get the mailing list messages about that? (And you should really be fixing trunk as well as current branch.

[Buginator]

Anyway should be fixed in next release.

...erm, wrong branch. Next release is in branches/2.2_net/. Did you get the mailing list messages about that? (And you should really be fixing trunk as well as current branch.

QFT

[i-NoD]

...erm, wrong branch.

Where did I write about submitting in 2.3b1? Whatever.. it's already backported. Beside there were no word on dropping 2.2 branch upon 2.3b1 arrival or am I wrong?

[Buginator]

...erm, wrong branch.

Where did I write about submitting in 2.3b1? Whatever.. it's already backported. Beside there were no word on dropping 2.2 branch upon 2.3b1 arrival or am I wrong?

You didn't want that to go into the next beta? Why?

As for dropping 2.2 branch, I don't have any more plans to keep that updated, it is just too much work to work with trunk + 2 branches (well, there is also lua, but that is another story)

After the tag from 2.2_net to 2.3.0b1 the main branch I will be trying to fix is 2.2_net. If at some point the netcode doesn't work out, we can always backport to 2.2 then.

I'll throw a message on the ML to make this clear.

[Zarel]

Where did I write about submitting in 2.3b1?

I checked the commit log. I noticed your only commit was to a branch we no longer support.

Whatever.. it's already backported. Beside there were no word on dropping 2.2 branch upon 2.3b1 arrival or am I wrong?

2.3 is a relatively minor improvement, so the 2.3 final should be out reasonably quickly. I was far more annoyed by how we dropped 2.1-branch so early. :/

[pranjan]

Well, I ddnt understand what you guys are talking about. Something firefighting
Let me tell you one thing... inspite of bugs, the game is rocking and credits goes to you guys.
Welldone!!!