pingplreport is flooding the console

[in2ishun]

The console is filling up with a "command unknown pingplreport". Server is running Darkplaces. Client (for me anyway) is JoeQuake GL.

Any ideas on how to stop this or reduce the amount of times it happens?

Legitimate messages are scrolling by too fast because of this event.

[Baker]

1. Does this only happen when a JoeQuake client is connected?
2. Does this happen when a DarkPlaces client is connected?
3. I assume you are using the "Quake" protocol with DarkPlaces otherwise JoeQuake couldn't connect to it.

It could be ...

The mod you are running, possibly maybe the client (I sort of doubt this) or a typo/bug in DarkPlaces server. I know I've seen some interesting "junk" print to server console logs

[in2ishun]

I haven't narrowed it down yet, though I've certainly noticed it more with Joe Quake. I'm thinking it's probably a client-side issue and the server isn't being flooded with messages. I mean, if it's saying that it's an "unknown" command, that would have to be client-side, right?

I'll try to narrow it down and post back here with my findings.

[Baker]

Yeah, don't try to guess because a lot of times guesses are wrong with these kinds of things

Find out what the answers are to the 3 questions I listed above, and let's add #4 "What mod are you running, if any?"

I think I know the problem but I don't want to suggest something without knowing for sure.

[in2ishun]

1. Unknown. I started happening when I started using JoeQuake as opposed to ProQuake. If I remember correctly, ProQuake would show this message in the console occationally. JoeQuake has fits where it will show up (in the messages area when I'm playing) once a second. If I get killed and decide to chat for a bit, then come back, it seems, for a while, that these messages don't show up at all. Then they return, once a second.
2. Using the darkplaces client manages to crash my machine to bios. I have asked other people with this client and they don't seem to complain about it.
3. Yes. Quake protocol.
4. No mods, just custom maps. This event is map independent and it's consitent across all maps.

[Baker]

Hmmmm.

Ok, I tried some things.

I would recommend using DarkPlaces April 12, 2007 build (Download).

I started a simple dedicated server:

c:\quake\darkplaces.exe -dedicated 8 +sv_protocolname QUAKE

I connected JoeQuake 0.15 and DarkPlaces client to the server and I didn't have this print to the console.

If you aren't using the April 12, 2007 build, I'd recommend trying that one.

I think you are using either an older one or a newer one.

/Note: Also, you may just find that this one doesn't crash on your machine as a client *IF* you were using an older one. An issue with OpenGL calls was fixed that crashed some machines (but I have a Radeon laptop that runs JoeQuake just fine but still won't run this DarkPlaces so may be it can't run as a client.)

[in2ishun]

Hmmmm.

Ok, I tried some things.

I would recommend using DarkPlaces April 12, 2007 build (Download).

I started a simple dedicated server:

c:\quake\darkplaces.exe -dedicated 8 +sv_protocolname QUAKE

I connected JoeQuake 0.15 and DarkPlaces client to the server and I didn't have this print to the console.

If you aren't using the April 12, 2007 build, I'd recommend trying that one.

I think you are using either an older one or a newer one.

/Note: Also, you may just find that this one doesn't crash on your machine as a client *IF* you were using an older one. An issue with OpenGL calls was fixed that crashed some machines (but I have a Radeon laptop that runs JoeQuake just fine but still won't run this DarkPlaces so may be it can't run as a client.)

Ok... actually I believe I'm using that build on the server.
"DarkPlaces-Quake build 17:35:10 Apr 12 2007"

Honestly I'm thinking this has to be a client-based issue with Joe Quake. the messages I'm seeing flood across the screen aren't showing up in the server console at all. I'll download JQ again and double-check any documentation I can find for this strange behavior.

[LordHavoc]

Actually, this is produced by the server in response to the "ping" command, it is additional information meant for a darkplaces client (it shows packet loss percentage, and more reliably updates pings without the need to parse the player names, which avoids issues with weird player names).

One way to hide it is to add this alias:
alias pingplreport " "

That should make it ignore the command.

I always intended to have a better solution to this problem, like the client sending "pings" instead (a different command that gets only a pingplreport, and only works on DP servers), but that would potentially get the client kicked off of a server that doesn't support it, and wouldn't get any pings on a non-DP server, so I just made the DP server send the additional info in response to a ping command.

The real solution is to make JoeQuake and other clients support this command - it is useful information that is not available otherwise - but I understand the annoyance with the spamming of the console.

I only have one idea for a workaround which is to disable the sending of this command on non-DP7 protocol servers... But that has the drawback that no clients would get this information then.

[in2ishun]

Actually, this is produced by the server in response to the "ping" command, it is additional information meant for a darkplaces client (it shows packet loss percentage, and more reliably updates pings without the need to parse the player names, which avoids issues with weird player names).

One way to hide it is to add this alias:
alias pingplreport " "

That should make it ignore the command.

Ok... that seems to have done the trick though without other people in the game I'm not really able to test it. It seems to only happen with other people in the game and me getting killed. I haven't been able to isolate the event to a specific time, but it's fair to say I haven't really concentrated on it in the middle of a match.

I only have one idea for a workaround which is to disable the sending of this command on non-DP7 protocol servers... But that has the drawback that no clients would get this information then.

Without knowing how critical it is for a client to receive this information, would it be possible to maybe add an option for server admins to disable this functionality in lieu of a "a better solution to this problem". Maybe clients *need* this info, maybe they don't, I'm not the expert here.

In an aside, and somewhat related, I took another screenshot of similar activity that just occurred a bit ago. In addition to the pingplreport, for a very brief time, I got another message flooding the console that seemed to stop the minute another player sent a text message into the message area. I took a screenshot in case no one believed me. It says "0 unconnected" and went to the console every other time that "unknown command 'pingplreport" did. Maybe related, maybe not.

The errors seem to be getting stranger and stranger.

(new screenshot attached)

[LordHavoc]

Ok... that seems to have done the trick though without other people in the game I'm not really able to test it. It seems to only happen with other people in the game and me getting killed. I haven't been able to isolate the event to a specific time, but it's fair to say I haven't really concentrated on it in the middle of a match.

It happens whenever the scoreboard is shown - such as when you die - the JoeQuake client asks for pings during this time.

The packet loss counters are certainly not a high priority, but nice to have.

In an aside, and somewhat related, I took another screenshot of similar activity that just occurred a bit ago. In addition to the pingplreport, for a very brief time, I got another message flooding the console that seemed to stop the minute another player sent a text message into the message area. I took a screenshot in case no one believed me. It says "0 unconnected" and went to the console every other time that "unknown command 'pingplreport" did. Maybe related, maybe not.

The errors seem to be getting stranger and stranger.

Unfortunately I don't know what I can do about the "0 unconnected" lines, that is JoeQuake misparsing the normal quake ping reports, perhaps it doesn't expect to see unconnected clients listed, but I was pretty sure the ProQuake code did handle those when I read it.

That is the server apparently producing a ping report that JoeQuake doesn't completely understand, it is this very reason (hard to parse ping reports) that I added the pingplreport, it is more reliable information for the scoreboard.

I guess I'll have to disable the pingplreport, and make the DP client send the "pings" command (which sends pingplreport instead of things like 0 unconnected) only on DP7 protocol (since most DP7-using versions of DP support the command).

I was worried about sending the "pings" command to nexuiz 2.2.3 servers but it seems they're fine with it (I only have to keep compatibility with the previous version of nexuiz, not with really old servers).

Made a new DP beta today (20070523beta1) which has the change, so hosting a server with that should avoid the console spam.

[in2ishun]

LordHavoc, adding that alias command to my running version of JoeQuake did the trick. However, I've snagged a beta from you to run on the server (darkplacesenginewindowsonly20070526beta1) assuming that change was also incorporated into this version.

I'll give feedback if I notice anything peculiar. What form do you want the feedback? Email? This thread?

[LordHavoc]

I'll give feedback if I notice anything peculiar. What form do you want the feedback? Email? This thread?

This thread of course, I get an email every time someone posts.