Some GTKRadiant questions . 1) How does one go about adding custom textures to Radiant? I've garnered that it's got something to do with changing the shaderlist.txt in baseq3 (maybe?), but doing that didnt work.
2) Very noob question- I am ashamed . How does one make Nexuiz play a map in a .pk3, that is in the Nexuiz/data directory? Haven't tried to do it before.

Thanks.

Program for compilation *pk3 files- PakScape
*.pk3 structure:
file.pk3
-(folder) maps
----map.bsp
----map.jpg
----map.cfg
----dm(tdm, ctf, arena...)_map.mapcfg
-(folder)sound
----(folder)cdtracks
-(folder)textures
-(folder)scripts

torus wrote:2) Very noob question- I am ashamed . How does one make Nexuiz play a map in a .pk3, that is in the Nexuiz/data directory? Haven't tried to do it before.

Read Nexuiz/Docs/mapping.txt, that will hopefully answer all your questions

Z (Rus) wrote:Program for compilation *pk3 files- PakScape

Well, pk3s are just renamed zip files, so any zip program will do.

Well, pk3s are just renamed zip files, so any zip program will do.

I know this, but sometimes zip programs not work(lags or virus)

Z (Rus) wrote:I know this, but sometimes zip programs not work(lags or virus)

Uhm.. maybe you should change your zip program if it gives you lag or viruses! Or better do click all those link on pron sites
But to be honest i have no idea what you mean.. how should a zip program give you lag?

... and since pk3's are zip files you are using a zip app anyways, even if it calls itself something else.

torus: shaderlist.txt in baseq3 (are you using q3 ..?) is a list of shaders (not textures) that the map compilter needs to be aware off. Thinks like skyboxes and light emitting shaders. to add a texture to nexuiz, simply add it to a new (or make a mess and put it an an exsising folder inside data(baseq3 if yer using q3)/textures/ and then id shoud just work, and show up in raidant texture menu.

Playing a map in a pk3 ios no diffrent from an unpacked file. To show up in the menu yu need yer map to have .mapcfs and .txt's for its modes (see nexuiz/docs/mapping.txt) To run it w/o this you need to execute a "map youmapname" in the console.

tZork wrote:... and since pk3's are zip files you are using a zip app anyways, even if it calls itself something else.

torus: shaderlist.txt in baseq3 (are you using q3 ..?) is a list of shaders (not textures) that the map compilter needs to be aware off. Thinks like skyboxes and light emitting shaders. to add a texture to nexuiz, simply add it to a new (or make a mess and put it an an exsising folder inside data(baseq3 if yer using q3)/textures/ and then id shoud just work, and show up in raidant texture menu.

Playing a map in a pk3 ios no diffrent from an unpacked file. To show up in the menu yu need yer map to have .mapcfs and .txt's for its modes (see nexuiz/docs/mapping.txt) To run it w/o this you need to execute a "map youmapname" in the console.

You're the man. Thanks.

Some other stuff: What causes an entity to "leak," when compiling? And what may be done to prevent this?

Also, when I compiled my map the first time (BSP:meta), to check proportions, it worked (aka, didnt leak), but some of the wall faces were wonky/not there, although solid. Is this due to the kind of compile, or something I did?

And one last- I don't understand the whole sky thing. If I am building a space map, for example, I make a hollow box around the whole thing made out of caulk, texture the inside faces with a sky texture, and call it a day? On my BSP:meta compile, 4 out of the 6 faces of the inside of this box appeared as solid white. WHats up with that?

Leak is, when you don't cover a little hole with structure brush. Planes and curves (patches) are NOT structural. Also note, that you might actually turned a part of the structure hull into detail or made an entity about it.
Skies are special shaders, look at the nexuiz shaders or mines for an example. The engine sortf out the images from the shader for the sky, not you! The image in the editor can be different from what you see ingame like that. So I can figure two things:
a: you haven't provided all the textures in the directory for the shader
b: the most common thing, you forgot to place your shader in shaderlist.txt That often happens to me too. This way the compiler ignores that shader completely, so the sky won't show up at all.

leaks,
Imagine your map as something floating in space, literally. The "inside" of your map needs to be completely sealed off from this vacuum (often referred to as "the gray void") If this void can reach any entity (spawns, lights, guns etc) at any point you get a leak. And remember that detail brushes, models and paches canNOT be used to seal the map. And yes, wrapping a skybox around the map is enough to make it un-leaked.

White skybox:
Sounds like you used a skybox not in nexuiz, not supported or in some otehr way broken. and remeber it need to be listed in data/scripts/shaderlist.txt (the shader file contaning the skybox taht is)

So, my skybox must have a gap or something? Hmmm. Then where is this red line pointing to?





Thanks for all your help guys, I really appriciate it.

The red line should go straight from the leaking entity to the hole where where the leak is
What I can see from these shot's is, that you haven't got any skybox around your map.

I did infact have a skybox, but it turned out that it had a veeery small hole. huh. I just made a new one. The sky shader has also been resolved, thanks.

Two (last?) things: does anyone have an idea as to what is causing this behavior? Whenever I compile, the right wall of the red base has a triangular transparent section on it, that I cannot get rid of. It does not show up in the editor afaict. The "hole" block movement and projectiles however.






Also, why do the brushes I have defined as ladder entites become invisible when I compile? The ladder is functional, that is, I can move up it, but they are ne'er to be seen:



Thanks!

After I get that fixed, all that needs to be done is get some jumppads and teleporters going. Yeehaw! I probably should have started with a map with less complicated brushwork, but so it goes.

I'm not a mapper but i think i read several times that you need two entities for a ladder.. one invisible one that is can be climped and one visible one that LOOKS like a ladder..

Interesting. Anyone know about the other problem?

You either have a duplicate brush - then delete one of them - or found yet another q3map2 bug - then good luck, you then need to somehow change geometry (like, split the brush into two using the clipper tool, or create a func_group of it).

Or even better, but the map it's textures up here, so the more experienced mappers can have a look at into the problem..

esteel wrote:I'm not a mapper but i think i read several times that you need two entities for a ladder.. one invisible one that is can be climped and one visible one that LOOKS like a ladder..

True. You make one brush that has the ladder texture, then you create another one in front of it, preferably really thin. This one has the ladder function texture and that way it will be used as a ladder. I had the same trouble on RTCW: ET.

Try the bobtoolz brush cleanup tool. I've had the same problem before, and it often happens from vertex editing of brushes.

Tried that, and it didn't work. But, it went away when I moved the edge of the wall about 4 units over (imperceptible in game), so all is Ok. Thnks though.

No, that's not ok. I can feel this map is the same mess as Greatwall was when I looked it into the first time. Overlapping brushes are NEVER ok.
Like I said, post the map source here, so we can look into it, and can give you suggestions how to correct these mistakes.

They aren't overlapping- I moved the adjacent ones so they are flush. Still, Ill put the files up when I get home.

I didn't wanted to sound rude, but I think we can help you better if we see your problems too I remember several times when I've posted my wip map to tZork who helped me to use caulk, tought me about caves and many many stuff like that.

Still, Ill put the files up when I get home.

But I certainly appriciate any help.

http://www.momoshare.com/file.php?file=e968e819578c4dd34650aa3d701ec5ea

Here it is- took me a while to get around to upping it.
It needs some major surgery, so ye' mappers beware.
Any tips are very welcome.

A recent problem- the bottom of my "turret crouching areas" are invisible on compile. wtf? They certainly dont have overlaps, and are only in contact with 2 other brushes.

Aside from that, I cannot get the teleporters to work properly at the top of my "elevator shafts."

They teleport to the satellite, but on the red base (or was it blue?) the reentry teleporter gets stuck in a kind of recursive teleportation. Bizzare. I'm probably not doing it right.

I need to clean up the overlaps too ( )