Game Development Community

Dedicated Server issue, not loading the correct mission file on player connecting - resolved

by Jules · in Torque 3D Professional · 02/23/2010 (2:35 pm) · 4 replies

What would cause the blank.mis file to be loaded up instead of the mission specified on the dedicated server? I've had one Windows 7 machine, join the server - but spawns the player into blank.mis file?

Edit:

@ Rene- GGs website crashed earlier... [not related] as I have my own master server.

About an hour ago I ran the game and connected to the right mission, just now I tried it and I connected to the blank room mission via the Join Server. On the console it reads...

LOADING MISSION: levels/Blank Room.mis

Earlier in the console it read after player dropped out, Resetting Server defaults...
Missing file: core/defaults.cs

core/defaults.cs under server is located under core/scripts/server/defaults (no .cs) file as I removed that, there is a .cs.dso file though.

So it appears when a player exits the game, it doesn't know what mission file to reload. Perhaps the last player in the game? Possible bug?

Edit 2:

Could be related to this..

// increment the mission sequence (used for ghost sequencing)
$missionSequence++;
$missionRunning = false;
$Server::MissionFile = %missionName;

After the game ends is it moving to the next mission file?




#2
02/23/2010 (10:39 am)

That indeed is indeed most peculiar. Are you sure the dedicated server is loading the correct mission?

The client loading a different mission could pretty much only happen if the client jumps from connecting to the server to spinning up its own server since the client never loads mission files.

Could you post the relevant section of the client console.log?
#3
02/23/2010 (10:40 am)
Oh man... what's up with the forum? The posts all end up with wrong timestamps...
#1
02/23/2010 (2:38 pm)
The only thing I can think of is that their graphics card is not supported or settings are wrong, and so it bombs out to the blank.mis file. Clutching straws here!
#4
02/23/2010 (7:13 pm)
As I thought. It was related to this in missionLoad.cs in core/scripts/server.

// increment the mission sequence (used for ghost sequencing)
$missionSequence++; <<<-------------------
$missionRunning = false;
$Server::MissionFile = %missionName;