News | Forum | People | FAQ | Links | Search | Register | Log in
Mapping Help
This is the place to ask about mapping problems, techniques, and bug fixing, and pretty much anything else you want to do in the level editor.

For questions about coding, check out the Coding Help thread: https://www.celephais.net/board/view_thread.php?id=60097
First | Previous | Next | Last
Cliff1 
If it's the same one I'm thinking of, it came from the Rogue mission pack. 
Sent =D 
Just fired off a little .wad with the texture to you -- ahh, technology. 
Thanks! 
Yes the internet is a wonderful thing.

I looked through the rogue wad and didnt see it. I have had my doubts as to the completeness (that a word?) of some of the id and crew .wads out there.

Screwy thing now is worldcraft keeps telling me the .bsp for my level wasnt built. Its rather anoying... 
Stupid Question... 
about Bengt jardrup's tools. There are alot of files with the .c extention. Would I be assuming correctly that these are source files and do not need to be installed into my worldcraft tools directory? 
Yep. 
all you need are the .exe files 
Yep. 
all you need are the .exe files 
Woah... 
i double posted! 
Missing Texture 
I have a missing texture in the .bsp and it is not visible in the game. However, I have looked through the .map file and cannot find the name of the texture to enable me to change it.

I know I do not need to do anything... but I want to.

So, fellow mappers, is there a tool to check the .bsp to get the name of the texture. Alternatively, how can I easily locate this missing texture? 
If You Have 
built the bsp from a map file, just check the compiler log.

AFAIK, it's not possible to see in the bsp which texture (i.e. name) that is missing, because it's ... missing.

If you can't see it in-game, it's probably some kind of a clip/trigger texture. Surprisingly many released bsps have missing textures. 
SZ_GetSpace: 8098 Is > Full Buffer Size 
Too many entities. Right?

But does this mean to many edicts or just too many brushmodels? Or both?

And also: Am I correct thinking that ambient sounds don't count as edicts or other bad things with low limits? 
Missing Texture 
WARNING 16: Texture bodiesa3_1 not found

Thanks again, aguirRe

I usually have -verbose turned off and just did not think. (Too busy checking the �re weather whilst compiling my map file!) 
Ambient Sounds 
count as edicts. 
It's Bad 
 
Pretty Much 
every entity, except for lights which aren't switchable or have a "style" set to them are edicts. that doesn't include torches and flames -- these are "static entities" and have a limit all their own. 
Func_illusionary 
...is also a static entity, and therefore not an edict. 
What's Wrong? 
So I received a demo from a map I sended.
Unzipped it with Dzip, and placed it in my
Quake directory. Openend the map that was related to, and gave the console the option:
playdemo test1.dem

Still I receive the -can't open test1.dem- 
Here's What's Wrong 
you should put it in the /id1/ directory, not the quake directory 
I Did 
won't work. 
 
"Just fired off a little .wad"

Bet you did ^_~ 
What Does It Mean... 
What does it mean when I get a 'Reached occupant at XYZ, no filling performed' error, not in FillOutside but in GrowRegions (hull 2 to be precise)?

Cheers. 
What 
FERN I LOVE 
Rennie... 
You don't need to tell Quake that the file is a .dem, so just type "playdemo test1" 
Fr3N! 
...still lurking, good to see. Can we expect a release soon ;P (seems to be the go with some of the old krew). 
Necros&metlslime 
thanks, I'll note that 
Against All Ods 
Had the same rubbish with the Dzip file Necros sended me. Don't know what it is. After months I was able to read the demo file.
Same goes with this one. Done all I could, even without the *.dem option, but it won't work.

Think the Orges are conspiring against me, after they noticed I turned them up in a Mission pak.

But nevermind, if they catch my real name, I still have time enough to establish my firewall and jumppath... 
First | Previous | Next | Last
You must be logged in to post in this thread.
Website copyright © 2002-2025 John Fitzgibbons. All posts are copyright their respective authors.