Page 1 of 1
compiler for cod4 blows
Posted: September 21st, 2008, 4:29 pm
by Rezil
Goddamn cod4compile tools. Here's what it says before it startscompiling bsp:
Code: Select all
Expression:
EPairList_HasKey( mapent->epairs, "origin" ) || !strcmp( classname, "worldspawn" ) || !strcmp( classname, "func_group" )
Module: I:\Program Files\Activision\Call of Duty 4 - Modern Warfare\bin\cod4map.exe
File: .\map.cpp
Line: 1538
If I ignore it, it doesn't compile the bsp. If I press try again it crashes and if I skip it it just keeps poping the same message up. -.-
Any clues as to what's causing this? I think it has something to do with me maknig func_groups but I can't be sure.
Re: compiler for cod4 blows
Posted: September 22nd, 2008, 2:37 pm
by Drofder2004
It looks to me like something in your entity list has "bad pairs".
Basically, pairs are for example
"classname" and "player"
"targetname" and "objective_a"
etc
Check your "worldspawn" entity for any bad pairs.
If all else fails, here is something to try.
Select everything on your map, copy and paste this in a new map.
Before doing this hide all your entities, spawns, moving platforms, everything.
Re: compiler for cod4 blows
Posted: September 22nd, 2008, 7:39 pm
by Rezil
Hey Drof, thanks for the reply.
Yeah that's probably it. I posted the same thing on modsonline and got a simmilar answer. I guess I'll check my entities for any bad pairs.
Also, I already tried selecting the entire map and pasting it in a new file. Didn't help.
EDIT:
Ok, after chaning the 'origin' texture to 'caulk', nothing was changed. I then tried to ungroup everything except triggers and script_brushmodels. Still didn't work. I then ungrouped EVERYTHING(no filters, selected all and ungrouped). Fixed the epair_haskey thingy. BUT now I have a new error:
Code: Select all
Expression:
comparison
Module: I:\Program Files\Activision\Call of Duty 4 - Modern Warfare\bin\cod4map.exe
File: .\materials.cpp
Line: 188
I'm pretty sure this has something to do with the custom textures from cod2. I knew it was too good to be true. Something has to go wrong... Right now I selected everything again and used one texture on everything. If it works, I'll have to fix the texture prob, if it doesn't,...well, the time to port the map has just lengthened.
