WARNING: Marksurfaces 32768 exceed normal engine max 32767

hehe, nothing more. 

After adding more geometry:

------ FinishBSPFile ------
WriteBSPFile: maps\zer_1.bsp
15012 planes 300240
32592 vertexes 391104
16573 nodes 397752
23431 texinfo 937240
26005 faces 520100
26942 clipnodes 215536
10200 leafs 285600
32750 marksurfaces 65500
116817 surfedges 467268
62745 edges 250980
106 textures 2015088
lightdata 0
visdata 0
entdata 61566

Skipped 147 surfaces
Writing File Format : BSP29
DivideWindingsOn : 0 / 0

All is good. 

Quaddicted says that DarkPlaces, QuakeForge, and experimental builds of FTE support BSP2 (along with the latest QuakeSpasm). I know I used FTE to play Something Wicked a while back. 

You can scale up textures to reduce lightmaps.

Anyone - does this work with the sky?

If you have rocks or any hidden surfaces you can mak big savings. Or completely 100% shadow areas in some places maybe too? 

 

 

Otherwise czg is a massive poo poo head for upscaling the sky in rub2m3. 

i didn't think lightmaps are saved on the sky.

i do it out of habit because older compilers would split the sky faces if you used a 1.0 scaled texture. scaling the sky to 10x or whatever made the compiler split only when the max face size was reached.
new compilers do this automatically though no matter what scale you use. 

I caused crashes on some old void maps in BSP1 a long time back by not scaling up the sky textures.

Now I habitually scale trigger, skip, clip and sky brushes to texture size 666. 

Now I habitually scale trigger, skip, clip and sky brushes to texture size 666.

It seems like such an easy thing to get compilers to do automatically (apart from trigger), I'm surprised none of them do it. You could add a switch to turn the behaviour on if you were being cautious, but I'd personally vote for a switch to disable this feature were it to exist. 

#define TEX_SPECIAL 1 // sky or slime, no lightmap or 256 subdivision

// some surfaces don't need lightmaps
if (texinfo[f->texinfo].flags & TEX_SPECIAL)
{
// non-lit texture
return;
}


in LightFace() (ltface.c) 

I'm using quark to replace textures within BSPs and they've all worked,
but when i tried to replace a teleport texture, ingame the texture doesn't animate and appears odd 

does the texture name start with *? it must, if you want it to have water properties. 

how do i make the texture start with "*" ? 

In texmex and rename it. 

https://www.quaddicted.com/files/tools/texmex_34.exe 

hmm, i thought you used to be able to do that in quark, sorry. 

oh you can!

when you have the texture wad loaded in quark, click the + to expand all the items. you can slow double click or press F2 to rename textures that way. 

Let's say you have an FGD ... is there a way to default a value for something like "delay" to "5" if it's set up as a choice field?

delay(choices) : "Attenuation" =
[
0 : "Linear falloff (Default)"
1 : "Inverse distance falloff"
2 : "Inverse distance squared"
3 : "No falloff"
4 : "Local minlight"
5 : "Inverse distance squared B"
]

That would save me some time ... 

worldtype(choices) : "Ambience" : 0 =
[
0 : "Medieval"
1 : "Metal (runic)"
2 : "Base"
]


That 0 sets the default. 

what is worldtype? 

I love you with mouth. THANK YOU! 

Also, world type sets the key style to be used.

I think that's all though. 

I'm not sure if there's logic to handle this, but I think if you set a default value and don't change it, the editor will not write it to the map file, and if the fgd default is different from the actual default, you'll get the wrong result. 

So in this case with the lights, the editor will not write out "delay" "5" on any lights, because it sees they're the default value and what's the point of writing a default value.