No, there's no way around it as everything below 32 is buggy atleast onsome maps. In the future mappers could of course take the lower settings in considerations when texturing/doing the lightning etc. but currently I'd suggest using atleast 32.
Kinda offtopic but I sure hope drex doesn't mind :p
Got a question myself... anyone knows what "net_forcelatency" does? Is it similar to pushlatency (timenudge)?
Would love to hear what other people experienced with settings this to negative values as it didn't seem to have the same sideffects for me as the q3 tn.
According to the upset chaps guide it pretty much the same as the timenudge. ONLY this works the otherway around. The higher u set the value, the more prediction it does. If you set it to a negative value it'll have the same result as a positive value like in q3.
So, for default everyone plays with timenudge -10 :)