map test freezes

(ghostcarrot) #1

when i test my map it freezes when opening limbo menu or using classselector :frowning: i used to be able to test it but not anymore. i can test other maps without any problem but the one i need freezes. is there anyway to fix this?

(murka) #2

possibly the mapcoords are missing. you can fix it by updating ET or by applying mapcoords.

(Dinius) #3

You should be able to both open limbo, join a team etcetc without setting mapcoords…

Are you getting an error message? and does this happen when u join a team? e,g, spawnpoint related or just when u open+close limbo too?

(th0rn3) #4

I dont know why, but on some computers you dont have to set mapcoords, and on some you have to set em

(ghostcarrot) #5

it freezes when opening limbo. and i used to be able to test it…

(Dinius) #6

Yes we’ve heard :stuck_out_tongue: But what about an error message?

(ghostcarrot) #7

nope there are no errors

(kamikazee) #8

This only holds true if you’re using W:ET version 2.60 or above. Older versions always crashed, which was a royal pain in the ass.

Either update your mapping W:ET version or check your mapcoordsmins and mapcoordsmaxs setting on the worldspawn entity.

(Dinius) #9

xD I’d never ever dream of taking 255ers into consideration when making a post -> and never will :stuck_out_tongue: :stuck_out_tongue:

(Paul) #10

http://www.splashdamage.com/forums/showthread.php?t=16380
Same problem with me :slight_smile:
And i can’t use et 2.6 because a populair server don’t have 2.60

(Dinius) #11

Theres tons of popular 260b servers…

(Apple*) #12

IMO: You should add the Team spawnpoints and the
info_player_deathmatch again, and compile the map again then put the bsp
etmain/maps load ET Bring down the console and -> sv_pure 0, g_gametype 2, devmap <mapname> :smiley:

(kamikazee) #13

[QUOTE=Scary;175198]And i can’t use et 2.6 because a populair server don’t have 2.60[/QUOTE]So you are actually making two mistakes:

  • you use a version of W:ET which can be used to overtake your computer (2.55 contains vulnerabilities), and
  • you don’t use a different copy for mapping and playing.

To check if your maps don’t use textures/shaders from other maps, you should always map with an etmain folder containing only your own-made pk3’s and nothing else. To do so, it’s best to copy your W:ET folder because moving your maps to a mod folder is not a viable solution.

(stealth6) #14

[QUOTE=kamikazee;175228]So you are actually making two mistakes:

  • you use a version of W:ET which can be used to overtake your computer (2.55 contains vulnerabilities), and
  • you don’t use a different copy for mapping and playing.

To check if your maps don’t use textures/shaders from other maps, you should always map with an etmain folder containing only your own-made pk3’s and nothing else. To do so, it’s best to copy your W:ET folder because moving your maps to a mod folder is not a viable solution.[/QUOTE]

pwnd ^^
2.55 = time to update

(th0rn3) #15

You can download a patch here from splash damage downloads

(kamikazee) #16

[QUOTE=stealth6;175244]pwnd ^^
2.55 = time to update[/QUOTE]Ehr, no. Making someone learn something new is not the same as pwning someone’s ass.

(ghostcarrot) #17


thats what i get in console when i join team

(kamikazee) #18

That’s a strange error you posted there. Did you install the 2.60 update before applying the 2.60b update from the zip file?