Game Development Community

Crash to desktop after client connect to server

by zenasprime · in Torque Game Engine · 06/21/2004 (5:42 am) · 3 replies

We seem to be having an issue with out Mac client. After a successful connection to the server our client crashes to the desktop. Here is some of the console.log that has stood out.

The client DOES seem to connect to the server...

Connection established 1466
Entering GameConnection::onConnectionAccepted(1466)
Leaving GameConnection::onConnectionAccepted() - return
Entering GameConnection::setLagIcon(1466, true)
Leaving GameConnection::setLagIcon() - return

However there are a few errors that seem to pop up after connection...

Entering clientCmdServerMessage(4 MsgConnectionError, , You do not have the correct version of the Nemesis Client or the related art needed to play on this server, please contact the server operator for more information.)
Entering defaultMessageCallback(4 MsgConnectionError, , You do not have the correct version of the Nemesis Client or the related art needed to play on this server, please contact the server operator for more information., , , , , , , , , )

It seems there is some issue with client versions? I've updated the client so I'm not exactly sure why this is the case.

Despite this warning the game proceeds to the Nemesis Vortex demo where we encounter the mission...

Mapping string: MissionStartPhase1 to index: 8
Entering clientCmdMissionStartPhase1(7, game/data/missions/nemesis.mis, lush)
*** New Mission: game/data/missions/nemesis.mis
*** Phase 1: Download Datablocks & Targets
Entering onMissionDownloadPhase1(game/data/missions/nemesis.mis, lush)
Entering MessageHud::close(MessageHud)
Leaving MessageHud::close() - return
Leaving onMissionDownloadPhase1() - return
Leaving clientCmdMissionStartPhase1() - return
Entering onDataBlockObjectReceived(0, 104)
Entering onPhase1Progress(0)
Leaving onPhase1Progress() - return
Leaving onDataBlockObjectReceived() - return
Entering GameConnection::setLagIcon(1466, false)

At which point it crashes to desktop. Any insight into what is occurring at this point in the code? The console.log from our Windows client suggest that the next line is "Mapping string".

Would anyone like to venture a guess at what's causing this crash?

Thanks,

#1
06/21/2004 (8:03 am)
Quick update, we -think- the issue is because of out of synch client/server distros with graphics, but cannot figure out why this hard crashes instead of just warns.

It's inconsistent on windows client exe's as well--we intentionally unsynched to see if we could duplicate the error, and sometimes we got a crash, sometimes we got a warning.

Anyone seen anything similar?
#2
06/21/2004 (10:29 am)
That's very curious.

It sounds like maybe you have a bad datablock in there somewhere. Have you triple checked all of them? That popup is often a result of a datablock failing to initialize (usually due to missing/broken assets).
#3
06/21/2004 (10:57 am)
I've had a problem just like this before. I can't remember how I solved it though. I'll give it some thought today and see if I can come up with something for you.