Constant "consistency failure" crashes in multiplayer

[earwigsinyourveins]

This issue occurs regularly with both Crispy Heretic and Crispy doom, and never happens in Chocolate. In Crispy Heretic it always happened at level 2 of Chaos DM (CDMbeta1.wad) halfway through a 10 minute match, never letting us finish; in doom it happened at the first seconds of e3m3 of Army of Darkness TC (aoddoom1.wad + aoddoom1.deh).

[Noseey]

I just tried to reproduce the doom one with aoddoom1 locally on my machine, but unfortunately was not successful.
Some questions:

• Did all players use the latest Crispy 7.1.0 release?
• Can you post the "start multiplayer game" settings and used parameters?
• How many players were in the game when the crashes happened?
• There were no warnings about not correctly loaded .wad or .deh for any of the players? (probably not, as it worked in Chocolate, but just to make sure)
• Does it also crash for you when locally creating a game and joining it with a second instance?

[earwigsinyourveins]

I just tried to reproduce the doom one with aoddoom1 locally on my machine, but unfortunately was not successful. Some questions:

• Did all players use the latest Crispy 7.1.0 release?
• Can you post the "start multiplayer game" settings and used parameters?
• How many players were in the game when the crashes happened?
• There were no warnings about not correctly loaded .wad or .deh for any of the players? (probably not, as it worked in Chocolate, but just to make sure)
• Does it also crash for you when locally creating a game and joining it with a second instance?

1. yes
2. server: crispy-heretic -server -servername Meatgrinder -deathmatch -timer 10 -merge CDMbeta1.wad -warp 1 2 | client (assumingly): crispy-heretic -connect <myaddress> -timer 10 -merge CDMbeta1.wad -warp 1 2
3. 2 (in all cases)
4. no, no warnings
5. no. I assume it might have something do with latency and lag spikes, need a real player to test, preferably with unstable connection

[fabiangreffrath]

Hm, could you try the -oldsync parameter? And could you please disable "uncapped framerate" on all systems involved in the netgame?

[earwigsinyourveins]

Hm, could you try the -oldsync parameter? And could you please disable "uncapped framerate" on all systems involved in the netgame?

"Uncapped framerate" is off by default, pretty sure in both cases the client had it off. Running a multiplayer game locally with 2 clients with -oldsync param does not reproduce the crash.

[Noseey]

Running a multiplayer game locally with 2 clients with -oldsync param does not reproduce the crash.

The crashes from the opening post, did they also happen during a local network session? And what version of Chocolate Doom did you compare it against?

[earwigsinyourveins]

Running a multiplayer game locally with 2 clients with -oldsync param does not reproduce the crash.

The crashes from the opening post, did they also happen during a local network session? And what version of Chocolate Doom did you compare it against?

No, crashes don't happen in a local multiplayer game where I connected to myself from the same machine, no matter if -oldsync parm is present or not. Chocolate version is 3.1.1, I believe that's the latest one.

[Noseey]

No, crashes don't happen in a local multiplayer game where I connected to myself from the same machine, no matter if -oldsync parm is present or not. Chocolate version is 3.1.1, I believe that's the latest one.

Thanks! Sorry, this time with local I meant a real local session between two PCs in LAN, but I guess that was also not the case then, so you were playing via Internet when the crashes happened. 😉

From what I see, newsync is also the standard in Chocolate Doom since commit b88a8cd, so that aspect might be compareable to Crispy 7.1.0. I will try some local sessions with another computer in my network and Clumsy to worsen the connection in several ways. Maybe I can find a specific setting where Chocolate still works, but Crispy doesn't, to get further to the root-cause.

[earwigsinyourveins]

Just tested it with internet and indeed, it still happens in the first 20 seconds of both matches, no matter the map even (first time was Chaos DM level 2, then level 3). Opponent's uncapped framerate setting was off. Connection was more or less stable, no lag spikes. After we tried map 3 in Chocolate it went perfectly fine and we had a full 10 minute match as due the timer.

[fabiangreffrath]

Was this with "oldsync" or "newsync"?

[earwigsinyourveins]

Was this with "oldsync" or "newsync"?

crispy-heretic.exe -server -servername Meatgrinder -deathmatch -timer 10 -merge CDMbeta1.wad -warp 1 3

[earwigsinyourveins]

Tried with -oldsync. No difference.

[Noseey]

@earwigsinyourveins: can you try to join my server?:
Nevermind, maybe we can set something up during the weekend.

At least in the tests I did with Clumsy, no crashes happened to me during a LAN game with excessive load.

Do you also have these crashes with other opponents / playing other .wads?

[earwigsinyourveins]

@earwigsinyourveins: can you try to join my server?: Nevermind, maybe we can set something up during the weekend.

At least in the tests I did with Clumsy, no crashes happened to me during a LAN game with excessive load.

Do you also have these crashes with other opponents / playing other .wads?

We only tested Chaos DM so far. And yes, these crashes happened with different people. Will test stock maps soon

[rfomin]

Do you have any DEHACKED files in the autoload folder? For example, the "Doom Minor Sprite Fixing Project". Even the smallest modification can lead to a desync of the network game.

[earwigsinyourveins]

Do you have any DEHACKED files in the autoload folder? For example, the "Doom Minor Sprite Fixing Project". Even the smallest modification can lead to a desync of the network game.

No autoload folder.