Got this warning with the latest (fixed) q3map2.5.11,
Just wondered if it is something to worry about, and if so what might be
the likly cause ?
Hewster
Got this warning with the latest (fixed) q3map2.5.11,
Just wondered if it is something to worry about, and if so what might be
the likly cause ?
Hewster
I`m only guessing but you might want to check your shaders for q3map_lightmapaxis and make sure they have x, y or z after the keyword.
mmm, none of my shaders use q3map_lightmapaxis… I thought when this
is not specified, that q3map add’s “z” by default ?
Anyhow, thanks for the suggestion 
Hewster