Data Integrity Check Problem

[Zarel]

From what I hear, it happens randomly, so I guess try until it fails?

It should always fail pretty quickly, if there's nothing after 5 minutes, you should be safe.

[Zarel]

NO FURTHER ACTION NECESSARY.

I just fixed the bug that caused this problem.

Thanks for your help!

[Singapura99]

You are welcome!

Glad I could be of assistance.

Thanks for fixing it!

[Michal]

Ok, we tried to play 4-5 times in a row, and we got kicked. Today, on beta9.
Here's mine netplay file, crashes from saturday around 18:30 are related to this bug.

I've also found something related in the rpt file (I forgot to clean the file once in a while so it got messy, I extracted only this crash-related info:

[Zarel]

Yes, the problem wasn't what I thought it was.

I've disabled the kicking entirely for the next version; I'll re-enable it only when I'm sure I've fixed it.

[KenAlcock]

Okay.

On your Linux machine, launch the game with command line options:

./warzone2100 --debug all --debugfile ~/warzonedebug.txt

1. Host a game, wait for the data integrity check failure to occur. If it doesn't, retry and relaunch until you get a game that fails.

2. Upload ~/warzonedebug.txt.

3. ...

4. Profit!

Q1: Will these parameters work in the Windows version as well?

Q2: Where will the warzonedebug.txt file actually end up?

Q3: Please document things like how to obtain a debug file in short step-by-step how-to on either (or both) the FAQ web page, or the How to Report Bugs web page.

[Zarel]

Q1: Will these parameters work in the Windows version as well?

Yes, but you'll have to remove ./warzone2100 and you have to replace ~/warzonedebug.txt with C:\whatever

Q2: Where will the warzonedebug.txt file actually end up?

C:\whatever

Q3: Please document things like how to obtain a debug file in short step-by-step how-to on either (or both) the FAQ web page, or the How to Report Bugs web page.

I think I mentioned before, but I don't do this since for the most part it's a ton of hassle that doesn't help. Unless I'm specifically asking for such a file, such a file will mostly have useless information. :/

[Saberuneko]

I have the same problem, but with a WinXP hosting the game, and a Win Vista, connected on LAN.

Both computers use Beta9.

Code: Select all

NETPLAY log: Sun Jan 31 16:10:43 2010

-----------------------------------------------------------
Player leaving game 	: NET_DROID 	:1		Sun Jan 31 16:14:01 2010
-----------------------------------------------------------
Player leaving game 	: NET_DROID 	:1		Sun Jan 31 16:17:58 2010
NET_DROID: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_DROIDINFO: received 8 times, 144 bytes; sent 5 times, 23040 bytes
NET_DROIDDEST: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_DROIDMOVE: received 43 times, 602 bytes; sent 3 times, 10752 bytes
NET_GROUPORDER: received 18 times, 288 bytes; sent 0 times, 0 bytes
NET_TEMPLATE: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_TEMPLATEDEST: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_FEATUREDEST: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_PING: received 22 times, 44 bytes; sent 19 times, 5648 bytes
NET_CHECK_DROID: received 31 times, 5425 bytes; sent 105 times, 1585920 bytes
NET_CHECK_STRUCT: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_CHECK_POWER: received 17 times, 85 bytes; sent 59 times, 75520 bytes
NET_PLAYER_STATS: received 4 times, 160 bytes; sent 0 times, 0 bytes
NET_BUILD: received 21 times, 567 bytes; sent 2 times, 13824 bytes
NET_STRUCTDEST: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_BUILDFINISHED: received 8 times, 152 bytes; sent 0 times, 0 bytes
NET_RESEARCH: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_TEXTMSG: received 3 times, 173 bytes; sent 1 times, 4352 bytes
NET_UNUSED_18: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_UNUSED_19: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_PLAYERCOMPLETE: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_UNUSED_21: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_STRUCT: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_UNUSED_23: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_FEATURES: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_PLAYERRESPONDING: received 2 times, 8 bytes; sent 2 times, 2048 bytes
NET_OPTIONS: received 38 times, 4876 bytes; sent 0 times, 0 bytes
NET_KICK: received 1 times, 37 bytes; sent 0 times, 0 bytes
NET_SECONDARY: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_FIREUP: received 2 times, 0 bytes; sent 0 times, 0 bytes
NET_ALLIANCE: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_GIFT: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_DEMOLISH: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_COLOURREQUEST: received 0 times, 0 bytes; sent 2 times, 4 bytes
NET_ARTIFACTS: received 2 times, 114 bytes; sent 0 times, 0 bytes
NET_DMATCHWIN: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_SCORESUBMIT: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_DESTROYXTRA: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_VTOL: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_UNUSED_39: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_WHITEBOARD: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_SECONDARY_ALL: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_DROIDEMBARK: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_DROIDDISEMBARK: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_RESEARCHSTATUS: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_LASSAT: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_UNUSED_46: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_AITEXTMSG: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_TEAMS_ON: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_BEACONMSG: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_SET_TEAMS: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_TEAMREQUEST: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_JOIN: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_ACCEPTED: received 2 times, 2 bytes; sent 0 times, 0 bytes
NET_PLAYER_INFO: received 48 times, 1692 bytes; sent 0 times, 0 bytes
NET_PLAYER_JOINED: received 4 times, 4 bytes; sent 0 times, 0 bytes
NET_PLAYER_LEAVING: received 2 times, 10 bytes; sent 0 times, 0 bytes
NET_PLAYER_DROPPED: received 1 times, 4 bytes; sent 0 times, 0 bytes
NET_GAME_FLAGS: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_READY_REQUEST: received 0 times, 0 bytes; sent 2 times, 1024 bytes
NET_NEVERUSE: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_REJECTED: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_UNUSED_62: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_UNUSED_63: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_UNUSED_64: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_POSITIONREQUEST: received 0 times, 0 bytes; sent 2 times, 4 bytes
NET_DATA_CHECK: received 0 times, 0 bytes; sent 1 times, 120 bytes
NET_HOST_DROPPED: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_FUTURE1: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_FUTURE2: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_FUTURE3: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_FILE_REQUESTED: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_FILE_CANCELLED: received 0 times, 0 bytes; sent 0 times, 0 bytes
NET_FILE_PAYLOAD: received 0 times, 0 bytes; sent 0 times, 0 bytes

And I cannot play on LAN using the 2.2.4, (the last that worked on lan play)

[Zarel]

This has already been fixed. There's no need to report any further problems.

[Saberuneko]

This has already been fixed. There's no need to report any further problems.

When?, I just downloaded and intalled that beta9 on the vista 10 minutes before posting this problem, because I just started the game and the other computer got kicked in seconds...

So, Zarel... You mean it "was" fixed before? Or you mean that it "is" fixed now?

[KenAlcock]

This issue occurred in beta 9. They have a fix worked out, but we won't see until the next beta.

[Zarel]

This issue occurred in beta 9. They have a fix worked out, but we won't see until the next beta.

This is correct.

(Well, we didn't actually fix it, but we did make it so you no longer get kicked out when the check fails.)

[Saberuneko]

Ok, thank you very much!

[crux]

This issue occurred in beta 9. They have a fix worked out, but we won't see until the next beta.

This is correct.

(Well, we didn't actually fix it, but we did make it so you no longer get kicked out when the check fails.)

What is this then?
http://developer.wz2100.net/changeset/9602

[stiv]

// bug in memcmp?

Heh.