Does anyone know why some editors have different texture projection axes which made it necessary to have -altaxis/-oldaxis on QBSP? Was it just a mistake or was there some reason for it? 

Note : TreeQBSP behaves slightly different than other QBSP variants. To make it behave more like
the others, the following command line can be used :

qbsp -oldaxis -oldleak [mapname]

In most cases, the new style leak line (default) is considerably easier to follow in Quake,
but if it doesn't seem correct (e.g. the line goes right through solid brushes) you might
want to try the old style line. You can always use the "-leakdist #" option to reduce the
amount of dots in pointfiles. If Quake cannot load the entire pointfile, use the Quake
command line option "-particles #" to increase the capacity.

Also, transparent water is not default (like in TxQBSP), but can be enabled via the
"-transwater" option. Beware of the performance hit in some maps.

Some lighting problems might occur when using most light tools together with a compiler
that supports enhanced texture positioning (e.g. QuArK ETP or Valve 220 Hammer). Light 1.27
and TyrLite 0.94 (see Tyrann's site below) or later versions support ETP. 

I'm not sure about this, but I suppose it was a programming error on some editor. The algorithms for both variants are exactly the same except for a < in one and a <= in the other. This is TB's implementation which is basically the same as the one in the compilers and in Radiant:


unsigned int bestIndex = 0;
float bestDot = 0.0f;
for (unsigned int i = 0; i < 6; i++) {
float dot = faceNormal.dot(*BaseAxes[i * 3]);
// no need to use -altaxis for qbsp
if (dot > bestDot) {
bestDot = dot;
bestIndex = i;
}
}


BaseAxes is an array of 3-tuples of vectors. This is the version to use without -altaxis/-oldaxis. The other version has dot <= bestDot. 

So it looks like the original treeqbsp had the 'wrong' projection code as well? Or the creator used an editor with the wrong projection and thought it was the correct on..? 

I've just noticed that one of my trigger_once has an 'angle' set to '-2'. This has crept in somehow but is entirely wrong.

The effect is that the player does not seem to activate the trigger without "wiggling" at the place where the trigger is sited, and it will not be obvious to the player that a wiggle is needed.

Can I remove this field directly from the .bsp file - I do not want to remove the trigger? I seem to remember that you can edit the bsp provided that... you don't alter the file length, or something like that?

The player does not actually pass through the trigger, they simply touch the trigger (it's against a wall).

I can change it in the editor of course but this is the level that took a gazillion hours to compile so I am trying not to compile again. 

You can remove the field and then run qbsp with the -onlyents commandline. 

I don't know who started this, but I suppose that some editor got it wrong and the original author of Tree tried to fix it. Or maybe he just got it wrong. It's super annoying, though. 

Remember to run light -onlyents as well if you have switchable lights in the map. 

Wow, now I understand why when I did onlyent compiles all the lights were screwed. Awesome tip, should be in quake wiki! :D 

I thought qbsp ran on the map file, and output a bsp file that you then had to run vis on to optimise visuals.

If I run -onlyents on the modified map file don't I end up with a bsp that still requires vis to be run on it? (That's why I was hoping that I could just manually modify the entity in the bsp file and leave all the compiled visual stuff alone.) 

No, because the entity lump is seperate from the BSP lump. It can update the entity keys/values without throwing away the BSP info. 

I found the entry in the bsp file, changed the '-2' to '00', saved it and ended up with the same file length. Ran it and it worked, so I guess the answer is that you can. 

I am clearly not understanding how this all works.

qbsp: takes a map file and turns it into a bsp file?
light: takes a bsp file and applies the lighting as defined in the entity list saved within the bsp file?
vis: takes an existing bsp file outputs a visually optimised version of the bsp file? 

yes, but each of those compilers puts their data into different parts of the bsp, so when you do -onlyents on qbsp, you're telling it to only update the entity list and not touch the lighting or vis.
and when you do -onlyents on light, you're telling light to only redo the lighting on switchable lights and update their connections with the entity list. 

The vis data is a separate part of the file, like the light data.

You can replace the vis data, just the same as you can replace the light data.

The vis data does not modify the BSP tree.

Or am I wrong? 

Does that mean when I run qbsp with -onlyents, it isn't outputing a NEW bsp file, it is only updating an existing bsp file with the revised entity data?

Is there anything wrong with the way I did it, which was to directly edit the bsp file? Admitedly, the 'angle' field is still there but is now contains a zero value, which seems to have solved the "wiggle" problem straight away. 

Does that mean when I run qbsp with -onlyents, it isn't outputing a NEW bsp file, it is only updating an existing bsp file with the revised entity data?
Correct.
Is there anything wrong with the way I did it, which was to directly edit the bsp file? Admitedly, the 'angle' field is still there but is now contains a zero value, which seems to have solved the "wiggle" problem straight away.
There's nothing wrong with that, it's just more work. 

also, btw, when you put an angle onto a trigger, it makes it so the player has to be facing 90 degrees to that trigger, so the wiggle is really just you accidentally pointing slightly downwards so that it was less than 90 degrees from the straight down angle and the trigger would fire. 

Thanks necros, now I've got it and your last comment is the last piece of what was puzzling me: I didn't even realise that triggers could angles. 

Are there any good guides around for optimising a map? My Deck remake is fairly detailed, maybe too detailed(!)... I'd rather optimise it than to start chopping detail down.
UT had occlusion brushes and such, will using skip textures on the void-facing brushes make a difference (is this what you're supposed to do??)... 

Anyone got a copy? The link up-thread is dead. 

func_detail entities should help. As for optimizing the map itself ... is it actually slow? It's hard to make a machine run slow with Quake these days. 

It's hard to make a machine run slow with Quake these days.

It really isn't. 

Is there a way to add up 2 .lit files?

I've been playing around with Q1Rad a little and I like the area lights and indirect shadowing it gives.

I've got a light_environment for the sky and light emitting slime as ambient lightsources but I wonder if these can combined with lightmaps from Bengt's light tool for the pointlights?
I like the idea of having bounced area lights to supplement the crisper lighting from pointlights. 

maybe it's my machine? I find I have to tweak settings a bit on some of the newer custom maps. I've started using RMQ as my main engine a lot of the time because it usually always gives me a solid framerate (plus I love them coloured coronas)