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
Skyboxes 
I am looking for 'pretty' skyboxes of setsets and/or sunrises - think happiness as opposed to doom laden. Can anyone point me in the right direction (and I don't mean go west young man) 
Setsets? 
sunsets: the letters aren't even next to each other on the keyboard 
In Here You Will Find Some Mike 
89.154.61.112 
Thanks 
Some More 
Quick Question 
When making quake 1 maps with gtkradiant 1.5, where do I put the texture files? And do I leave them as .wad or export them to a different file format? 
 
You need wad files directly in your quake directory, e.g.: Z:/Quake/id.wad.
You also need to set the key "wad" with the path to the wad in the worldspawn. 
 
z:/quake/id1/id.wad 
Lightmaps 
Do clip, skip and trigger textures affect lightmaps? 
Not 100% On All Of Them 
Trigger textures certainly do - the map compiler has no idea what the classnames on your entities mean and has to assume that you want the option to render them (in fact some speedrunning mods have the option to show triggers in practice mode). Scaling textures that you know won't be seen by massive percentages ought to save some maps. 
 
skip does as well.

from what i understand, the skip'd faces are still in the bsp file, but they are moved to a point after a marker that tells the engine not to draw them, so they are loaded, just not drawn. 
 
skip and trigger generate lightmaps.

clip does not.

Theoretically qbsp.exe could be modified to natively understand skip; and then it would be possible to truly remove them from the bsp, reducing lightmaps and marksurfaces. But the current skip tools available merely hide them from rendering using a hack. 
Thanks Digs!! 
 
Compilers 
Is there a Q1 compiler which works with func_group entities?

I am currently using TreeQBSP v2.05 (10/04/2007) modified by Bengt Jardrup, but it leaks if I have any func_group entities in my map. 
 
i know that aguirre's txqbsp does. just add -group to enable the support. 
 
I assume you are talking about this version of qbsp? (http://user.tninet.se/~xir870k/)
The program (qbsp) tells me -group is not supported, I checked the readme file and it has no mention of it. Are you using a special version not listed on his homepage? 
 
the file you want is the txqbspbjp.zip which contains his txqbsp. This one supports -group.

it's only his treeqbsp that does not support -group. 
Options 
Ok that was confusing, I looked at the website and saw qbsp to be newer and assumed it was the correct one to download.

The txqbsp does not support -oldaxis and -transwater switches, I assume this ok? 
 
aguirre's txqbsp uses -altaxis and automatically builds transparent water (you can disable this with -nowatervis) 
I Never Really Understood 
why he maintained 2 slightly different forks of bsp in parallel. It's not as if there were any obvious reasons given regarding why we should use one over the other. I use Tx, for reasons that I can't actually remember now, but I'm sure were valid at the time. 
 
tx supports everything tree does, but also supports floating point coordinates. unless there's anything else, there's really no reason to use treeqbsp. 
I Thought 
that Tree supported floating point in exactly the same way that Tx does. That's what it says in the readme files anyway. 
 
oh maybe it's the 'etp' thing then? enhanced texture precision? 
Again 
supported in both, according to the readmes. In fact, going from the readmes, the main features list of both tools appear to be identical. 
 
geez, maybe they are then? the only difference would be txqbsp supporting -group then and different switch name for old/alt axis... 
First | Previous | Next | Last
You must be logged in to post in this thread.
Website copyright © 2002-2024 John Fitzgibbons. All posts are copyright their respective authors.