been looking at the -external switch when compiling for q3, what is the use for this switch?
i have searched this forum and other forums and google for infos on this, my understanding of this is the bsp uses the maps/<mapname>/lm_nnnn.tga on loading from what i can see when looking @ ET, but q3 doesn’t
is this something that isn’t to be used with q3? or are the other reasons for saving the lightmap externally?
also, why save them externally? allows for larger LMs? LM manipulation?
ta muchly 
Only ET supports external lightmaps. This was done so we could support larger lightmaps without breaking backwards compatibility. Also they could be JPEGed, making the PK3s smaller if need me.
y
awww, i see
its quite confusing tho, as there is
-external <–
–> ET only
-lightmapsize N (forces -external switch?) <–
then there is q3map_lightmapsize N N (forces external again but gens a shader?) /maps/<mapname>/lm_nnnn… which works with q3 but only via a autogenerated shader?
my confusion was ppl on the q3w q3map feedbk thread were talking about externals in q3 yet, i was told ET only supported them
aww, working via q3map2_<mapname>.shader for me terrain… although it is quite dark q3map_lightmapgamma 2.0 seemed sorted it tho O_o
ta muchly
Did you try jpeg-ing a lightmap? Results are nice and bizarre - a fast way of adding noise 
heh, nop haven’t tried jpgs yet, aye artifacts with add noise… depending if you compress O_o
add my own noise to me terrain lm tho, dunno about the look tho:
was a Lm messabout, looks good in some places and in others… just looks like baaaaad Dithering
