Warren, yeah, for sure, the threading is amazing.
Lunaran: lol, you prompted me to take a closer look at the "-gate" switch, and seems it was broken in�tyrutils (was calculating a bounding sphere that was too large). I was wondering why using like "-gate 25" wasn't speeding up maps with lots of delay 2 lights. I think I fixed it.. 

 

I've been using -gate 10 forever... are you saying it's done nothing forever!? :( 

I asked several times in the past about what exactly the "gate" number referred to and what was the range. I never really got a good answer. My working theory is that it's the rgb value of the lightmap, 0-255. So if you set -gate to 20, everything below that is pure black? Or am I totally wrong. What always threw me off was that many references state the default value is 0.01 or some other nonsense. 

Gate -10 seems to light faster than gate -1.
A tiny bit. 

-gate 10 versus -gate 1. 

I think it's been broken since it was added to tyrutils in 2013. If you have a map with lots of delay 2/5 try the devbuild in #158.
On jam6_ericwtronyn I get a huge speedup, like:
No gate: 60s, gate 5: 7 seconds 

Wow, yeah, map I'm working on went from 18secs to light to 8 seconds (only option was -gate 10) nice! 

...though it seems -gate 10 is a bit high of a setting now that it actually works, lost a lot of detail in my lighting :D

Still, nice that it actually works! 

2 times faster now with -gate 10. 

so, what does the number after gate actually mean then? 

When you specify "-gate X": for each light, the util calculates the distance at which a surface would be lit up by that light to an intensity of 'X'. The intensity units are the same as the bsp file, so 127 is full brightness, 255 is 2x overbright. The distance calculated is used as a bounding sphere, so beyond the sphere the light casts 0 brightness. 

Scampie + mfx, awesome it is giving a speedup for you guys!

If you just have a delay 2 light in a large box room, "-gate 10" should give a visible seam where the brightness changes abruptly from 10 to 0. Might have to turn up the quake gamma to see it clearly. It's possible I still messed up the formula so i might try rewriting it in a more straightforward way. 

I found -gate 3 worked well for my situation. Still a large speedup and I keep some of the subtle lighting effects I was doing. 

i remember -gate 1 got a great speed up on old rigs in aguirRe's tools. like from 10 minutes to ~10 secs. Was is different now? 

127 is full brightness, 255 is 2x overbright.

That's what I was wondering, thanks. 

Tyrann just added -gate more recently to his tool (2013), and it looks like there was a bug causing it not to give as much of a speedup as it should have. but it's fixed in the most recent dev build of my version of tyrutils. 

https://github.com/ericwa/tyrutils-ericw/releases

Highlights are Spike's addition of Hexen 2 support, fixed -gate, a new "_surface_spotlight" key which automatically sets "mangle" on surface lights to turn them into spotlights. 

and -gate really speeds up the light process 

Also, a question: Does surface lights follows the shape of the fullbright texels, or maybe the luminance of each texel? 

The "surface lights" I implemented are nothing fancy like that, all it does is handle cloning & positioning copies of point lights. It's just a shortcut around a lot of copy&paste really. It works best with runic light fixtures where it'll reliably put a single point light on each light fixture.

The q2/q3 light utils have "real" surface lighting, where the light-emitting surfaces are divided into radiosity patches, and then the area of these patches is used in the lighting calculation. See here in the q3 tools. I think the patches took their colour from an average of 32x32 texels or something.

I did experiment with that code in my tool but didn't have the greatest results, it was slow, tended to cause "hot spot" artifacts on the walls around a lava surface, and generally didn't look very good in Quake. 

:) Thanks for the info.

Idea: Interpret the fullbright texels as transparent, and put the surface's point light behind the surface. This way, you can use the algorithm of the alphamasked texture shadows to shape the light.

The results will be more akin to spotlights, so it would have to be optional.

It would be useful for stuff like windows. 

That seems like a really fun feature... I'm going to make a crazy disco ball of spotlight lasers 

mankrip, windows like http://triptohell.info/moodles/junk/fte-20150311190731-0.jpg really needs .lit2 type stuff :s 

That screenshot is nice!