Sweetness! 1 bounce would already be a great start. 

One or two bounces would be fantastic. It could save a lot of trouble. As it is now, for indoor areas I probably place 3 to 5 fills for every actual light. 

1 bounce with light diffusion would be cool. 

Personally I'd suggest adding a "_bounce" key to light entities; default if there's no key is no bounces (makes sense to keep defaults same as stock Q1 tools) and the value specifies the number of bounces.

That way lighting could be easily recreated at any time and by other tools without needing to know the command-line options that were originally used. 

weird, I don't use notepad++ but it should have a "goto line" feature that should take you to the right line. Anyway, I don't think "Brush With Duplicate Plane" is a serious warning, it's more a warning that the editor saved some redundant data.

It's not that I can't find exact line which correspond to log output - notepad++ shows line numbers. Problem is compiler treats line numbering differently.

I think I found the problem - it doesn't count comment lines.

Tested on my map backup.
Compiled as is
*** WARNING 03: line 45402...
added a bunch of commented out lines("//asdasd") , in the beginning of the file and line number didn't change in the log.
Then I replaced commented lines with empty lines, just a line break. No spaces, tabs etc
Now log says
*** WARNING 03: line 45406...

If it is the case, then every line with entity/brush number gets ignored and line numbers 'shift' from what you would get in text editor. 

Sorry for little OT.
There is nice BSP importer for Blender. I would love to bake static Lightmap there and export it back to BSP.

In overall some lightmap import option would be great. I know it's hard, because BSP is just fragmented mesh "dump" and lightmap is low res, but we can think about some solution. 

You could create external LIT files � but that requires writing an exporter plug-in for Blender. 

hmmm.... any link to proper LIT documentation? 

Hmm being able to read and write the lighting from and to BSP would be a rather fantastic addition but then you run into a world of pain if you want more light styles supported. how to handle flicker lights and so forth because those get layered on top and limited to the polygons they affect if I remember correctly.

As for the _bounce you could do that or just add it to the compiler as a global option. Same goes with bounce multiplier and saturation. How much energy is maintained when it bounces and how much color is picked up when it hits the surface. In Unreal you can tweak these values so its more saturated and propagates lighting further by not losing as much energy on the first bounce. 

yeah, I know about light styles being problematic in this situation. I'm going through source to fully understand how it works. 

As for the _bounce you could do that or just add it to the compiler as a global option.

Then make it a worldspawn key, so that way lighting could be easily recreated at any time and by other tools without needing to know the command-line options that were originally used.  

There is a port of the half-life 1 radiosity lighting tool to quake 1 you could look at? It does bounce and phong but lacks modern features from these tools... It's called q1rad. No link sorry I'm mobile 

 

Beta builds are moved here for now, if anyone wants to try the update phong shading.

The documentation isn't updated yet, but the readme.txt has the details on phong. basically set "_phong" "1" on func_detail/func_group/func_wall etc. 

beer@ericw.com 

Does this one include lit water support? 

Yes, spike added it, but it's untested.
There are these command-line options:
[-lightturb] [-lightwater] [-lightslime] [-lightlava] [-lighttele]

-lightturb just is a shortcut for water + slime + lava + tele. 

This is just crazy, so much advancements to ole Quake! Thank you all for the efforts, really...can't be said enough. 

btw, the key for phong shading has changed since the version you were using, you no longer need to give the texture name. The main improvement of this new version is having an angle cutoff, so it won't smooth around 90 degree corners by default (the cutoff is 89 degrees.)

Another new feature: when using phong shading I suggest setting "_anglesense" "1" in worldspawn, this affects all lights in the map that don't override "_anglesense".
This will make phong shading more visible and generally increase contrast.. it makes the angle that light arrives on a surface matter more than the quake default. 

I'm not sure I will change compilers unless I am really compelled to 

 

Does it apply phong shading to the whole brush? Not sure if this is desirable behaviour.

The thing I want most is a more tolerant or forgiving compiler like txqbsp 

 

whats your problem?? 

my brushwork sucks and I guarantee once my map is properly "sealed" it will leak like an incontinent old man who just drank 30 litres of water.