q3map_sunEXT shadow problem
q3map_sunEXT shadow problem
.
Last edited by ykram on Fri Jan 21, 2022 8:44 pm, edited 1 time in total.
Re: q3map_sunEXT shadow problem
That's a pretty big value for q3map_lightmapFilterRadius, try something like 0 8. Other than that, I don't see anything glaringly wrong with the shader. Also check that you don't have any syntax errors in this or other shaders.
Reference:
Shader Lighting Experiment
Q3Map2 Shader Manual: Light Emitting Shaders
Reference:
Shader Lighting Experiment
Q3Map2 Shader Manual: Light Emitting Shaders
Re: q3map_sunEXT shadow problem
.
Last edited by ykram on Fri Jan 21, 2022 8:44 pm, edited 1 time in total.
Re: q3map_sunEXT shadow problem
If your revert back and comment out all the new changes, does it still work? You are using the latest version of Q3Map2, right?
The shader itself looks right, so I can't help thinking that something else is causing the problem for you.
The shader itself looks right, so I can't help thinking that something else is causing the problem for you.
Re: q3map_sunEXT shadow problem
.
Last edited by ykram on Fri Jan 21, 2022 8:45 pm, edited 1 time in total.
Re: q3map_sunEXT shadow problem
Curious... if you want, you can upload the entire shader file and I'll take a look at it.
Re: q3map_sunEXT shadow problem
.
Last edited by ykram on Fri Jan 21, 2022 8:45 pm, edited 1 time in total.
Re: q3map_sunEXT shadow problem
I tested the shader and it seems to work fine. But it looks like you solved it on your own. What was the problem?
For jagged shadow edges, try slowly increasing the filter radius value. Too much and you lose definition (your shadows will look like a big blur).
You can also combine this with an increased lightmap resolution which you can set per func_group, shader or globally using compile switches. But keep in mind that increased lightmap resolution increases your BSP size as well as taking up more texture memory, so there is a performance cost.
For jagged shadow edges, try slowly increasing the filter radius value. Too much and you lose definition (your shadows will look like a big blur).
You can also combine this with an increased lightmap resolution which you can set per func_group, shader or globally using compile switches. But keep in mind that increased lightmap resolution increases your BSP size as well as taking up more texture memory, so there is a performance cost.
Re: q3map_sunEXT shadow problem
.
Last edited by ykram on Fri Jan 21, 2022 8:44 pm, edited 1 time in total.
-
- Posts: 35
- Joined: Fri Jan 13, 2006 6:45 pm
Re: q3map_sunEXT shadow problem
Try using a value like 4 (higher res) or 8 (lower res) for the -samplesize switch during the bsp-stage of your compile.
sth. like:
Another option would be to add the _lightmapscale key to the worldspawn entity. Something like 0.125 should be really sharp, but beware of compile times then.
Maybe that helps
sth. like:
Code: Select all
"G:\GtkRadiant1.5.0\q3map2.exe" -meta -samplesize 4 -v "G:\Quake III Arena\baseq3\maps\mymap.map"
Code: Select all
_lightmapscale : Floating point value scaling the resolution of lightmaps on brushes/patches in the world. Can be overridden in func_group (or other entities) (default 1.0).
Re: q3map_sunEXT shadow problem
Check out the links I posted above. I spent quite a bit of time documenting this and you can see the resulting changes in the screenshots.