Lock ups in spectator mode

(shazmax) #1

I’ve read somewhere that some other people were experiencing similar problems. I thought at first that my map that I was testing was causing the lockups. Anyways while I was in the test server mode running it from my batch:
“C:\Program Files\Wolfenstein - Enemy Territory\ET.exe” +set g_gametype 2 +set developer 1 +set sv_pure 0 +devmap solomon1

I quickly switched it to a standard multiplayer map (while in test server phase) that I’ve played several times such as the ammodepot_beta. It chugged a bit and I checked console, punkbuster was authenticating with master server…etc. Then I left for a bit thinking that it would be fine while in spectator mode, but then it locked up. I don’t remember it ever doing this before…why is it now recently locking up in spectator mode while I am running a test server?

(MadJack) #2

Running a test map? If so… check your min/max coords. Also, make sure you have an info_deathmatch so you can at least spectate. If you want to join, you need a Red/blue team spawn AND correct coords. (those coords have to be at least 64 units bigger than your map AND it has to be SQUARE :slight_smile:

Something like:

mapcoordsmins -256 256
mapcoordsmaxs: 256 -256

HTH

EDIT: 64, not 63 units…

(shazmax) #3

Yea everything is running tight - so I couldn’t figure out what it was. I recently was having some weird punkbuster issues (but still didn’t make sense that punkbuster would cause issues in a test server) so I updated it. Basically punkbuster was enabling itself while I was trying to do a test server and was having problems with trying to connect to the main server through a loop back. I updated the punkbuster client manually for servers and did a pb_sv_restart then after that was done I did a pb_sv_disable to disable that bad boy. I haven’t had problems of lock ups since. I’ll let you know if that changes. What a pain. <Shakes fist at punkbuster>

(MadJack) #4

shrugs

As long as it works :smiley:

(shazmax) #5

Reasons for lockups while viewing your map in ET on a server:
(Things I did that caused me painful lockups while I was learning)
-Make sure the mapcoordsmins mapcoordsmaxs values are in your worldspawn, and that you have at least 64 units extra
-Make sure when you recompile the same map that you edit the changes in the original file. (Had problems with fps bogging down to literally 10fps after I edited the same compiled file like twenty times and recompiled ontop of it.
-Make sure you have team_player deathmatch, ctf_blue spawn and ctf_redspawn in there. I never really needed to have the obj with et to load smoothly
Those are the same mistakes I made for like a few weeks while learning. Its implanted in my head now what to do and what happens when I get a lockup. The above issue was resolved after I brought back the original file, saved on top of the one I was test compiling on and was able to continue forth that way.