 |
Have you tested this with the 0.8.1 release or my snapshot (have to make sure, because there were some changes in the snapshot that altered the lightfalloff image texture creation)? |
 |
Confirmed with lights/biground1 (latest SVN) |
 |
Also confirmed for 0.8.1. |
|
|
phew, I thought it could have been introduced by me when refactoring the ShaderSystem texture handling. |
|
|
I thought I fixed this before 0.8.x, I'll have to take another look. |
|
|
Seems to be caused by the GLTextureManager defaulting to _black.bmp for undefined Z falloff textures. Shaders plugin to be modified to use the falloff from the defualt point light shader instead. |
|
|
Resolved in SVN. |
|
|
I'm getting really weird behavior here. It's like it's trying to work; I can see traces of the true light texture in each choice I make, but they're all trashed by striped bands and blue blotches: http://img294.imageshack.us/my.php?image=bluext0.jpg Brightround (and doubleround) still look right, but just about everything else looks like some variation of the above. That's just a square room with a single light in it. |
|
|
Maybe this is the "Shader Not Found" texture used as lightfalloff? |
|
|
I can't replicate this, all of the textures work fine for me. Do you have the correct default light shader listed in doom3.game? It should be lights/defaultpointlight. |
|
|
Seems so. From doom3.game: ... <defaults> <lightShader>lights/defaultpointlight</lightShader> ... |
|
|
It should be formatted like this: <defaults> <lightShader value="lights/defaultpointlight" /> I gather greebo has produced another build, so the latest version should be in that (or you can change it manually). |
|
|
That seems to have fixed it. |
- Anonymous
