Opened 12 years ago

Closed 12 years ago

Last modified 9 years ago

#13 closed defect (fixed)

"Info string length exceeded" issues

Reported by: sg_tequila Owned by:
Priority: major Milestone: Smokin' Guns 1.1b3 - Engine
Component: Engine Version: 1.1b1
Keywords: Cc:

Description

On a dedicated server, it is easy to fulfill the System Info string. Then we got a lot of "Info string length exceeded" message on the console.

When this message happens, it means clients will miss some part of the System Info. This can be a real problem if the missing part is something like the gametype or the mapname...

For example, on my dedicated, as I setup the HTTP download, the SystemInfo? string contains now a big URL and I got the error. I then must reduce the size of other SystemInfo? part like the server name or any other not important info string.

Change History (4)

comment:1 Changed 12 years ago by sg_tequila

Last edited 9 years ago by Téquila (previous) (diff)

comment:2 Changed 12 years ago by sg_tequila

Milestone: Smokin' Guns 1.1b2 - EngineSmokin' Guns 1.1b3 - Engine
  • Actually, the max size of System Info string is MAX_INFO_STRING, defined to 1024 code/qcommon/q_shared.h
  • I don't think we should change this size.
  • Time to time, some new cvar was set with CVAR_SERVERINFO flag. I think we should start to review all of them. And then some clean up and just fix that problem. Also I found few ones than can be expected from ioQ3 code in the client part, but I didn't merged from ioQ3 (I think of g_enableDust & g_enableBreath) in the game part, so or with merge or we also clean the client part.
  • I'll try to prepare few wiki pages as game/cgame/ui cvars inventory which may help to decide what to do.

comment:3 Changed 12 years ago by torhu

IIRC, g_unlaggedVersion doesn't need to be serverinfo. It's purely informational.

comment:4 Changed 12 years ago by sg_tequila

Resolution: fixed
Status: newclosed

Removed this one and also g_url
Tried to shorten version
Fixed g_redteam/g_blueteam removing "name" suffix
Last committed at r419

This should be enough.
So closing the bug until 1.1b3 release and will reopen if needed.

Note: See TracTickets for help on using tickets.