G_Ticker: Consistency failure during network play

Bug #1483414 reported by themusicgod1
2
Affects Status Importance Assigned to Milestone
prboom-plus (Ubuntu)
New
Undecided
Unassigned

Bug Description

this seems to be the same behavior for both trusty 14.04 and wily 15.10

prboom-plus-game-server:
for either
  Installed: 2:2.5.1.4~svn4356+dfsg1-1
  Installed: 2:2.5.1.4~svn4356+dfsg1-1

prboom-plus:
for either
  Installed: 2:2.5.1.4~svn4356+dfsg1-1
  Installed: 2:2.5.1.4~svn4425+dfsg1-2

1) setup 2 players(1 localhost, 1 on a different computer) to connect to a server running prboom-game-server

2) start the server (steps 1 and 2 seem to be independent)

3) start running forward on one of the players (ie start playing)

result:

G_Ticker: Consistency failure (-5025 should be -5031)

(usually the two numbers above are (negative) should be (positive), but they tend to be many different numbers, often in the range of 5-8000).

then

fluidsynth: warning: no preset found on channel 0 [bank=0 progr=0]
fluidsynth: warning: no preset found on channel 1 [bank=0 progr=0]
...
fluidsynth: warning: no preset found on channel 15 [bank=0 progr=0]
fluidsynth: warning: no preset found on channel 16 [bank=0 progr=0]

and the client shuts down for every player *except* the first player(or possibly, the player that moved).

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: prboom 2:2.5.1.4~svn4356+dfsg1-1
ProcVersionSignature: Ubuntu 3.16.0-45.60~14.04.1-lowlatency 3.16.7-ckt14
Uname: Linux 3.16.0-45-lowlatency x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Aug 10 17:10:41 2015
InstallationDate: Installed on 2015-05-07 (95 days ago)
InstallationMedia: Ubuntu-Studio 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
PackageArchitecture: all
SourcePackage: prboom-plus
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
themusicgod1 (themusicgod1) wrote :
Revision history for this message
Михаил (m-v-bobrov) wrote :

This error caused because server and client uses different IWAD files. Please check what you use same files on a server and on a client.

Revision history for this message
Roger Morton (ttguy) wrote :

"caused because server and client uses different IWAD files" - Not in my case

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.