custom map crashs linux server but not a windows one
Post Reply
Quote
Re: custom map crashs linux server but not a windows one
Posted by lordnitro on Fri Aug 25th at 2:53am 2006


I have made a couple of maps without any issuses,at all...we have one of them running on "our" freedom fighters clan servers, I have made a new map called wild wild west....western based deathmatch, it will run fine on a windows server,and even my server here..but when the map is loaded onto the ff server,and you send the command to run the map it crashs the server..the server is linux ..is there some way of checking what i have may done wrong to repair this issue, and i have no errors in the map what so ever. Is it a compiling problem, i have also tried the -linuxdata command

thanks, [FF]Assn.LoRdNiTrO




.x[FF]Assn.LoRdNiTrO x.



Quote
Re: custom map crashs linux server but not a windows one
Posted by Naklajat on Fri Aug 25th at 3:45am 2006


Check the server log files if you have access to them, and see what it says happened when you tried to changelevel to your map.


=o



Quote
Re: custom map crashs linux server but not a windows one
Posted by lordnitro on Fri Aug 25th at 4:12am 2006


one of the server admin tells me that there is no error it just crashs the server,and reboots back to the default starting map dm_lockdown..




.x[FF]Assn.LoRdNiTrO x.



Quote
Re: custom map crashs linux server but not a windows one
Posted by reaper47 on Fri Aug 25th at 10:51am 2006


Please search the forums first. There is an identical thread five posts beneath.

http://www.snarkpit.net/forums.php?forum=6&topic=7110&6




Quote
Re: custom map crashs linux server but not a windows one
Posted by UnholyGemini on Sat Aug 26th at 2:11am 2006


Actually reaper, my map was working with that fix fine, right on up to the newest update for CS:S, now the same de_veikko that was working now crashes the server, and I have tried recompiling without the -novirtualmesh and it didn't work ( I thought that maybe Valve had actually really fixed the Linux problem, and the map no longer needed the -novirtual mesh, stupid me ). HOWEVER, I have NOT tried to recompile the same map with that same setting of -novirtualmesh after the update, though I doubt it will help any. Go ahead and see if my work-around still works for a recompile, just add:

-novirtualmesh

To your command line in the "Run Map"'s dialog box.

Hope you find a fix, I need one too.








Post Reply