by Orl » Sat Jul 01, 2006 9:43 am
Cache mismatches are caused when glquake loads a texture on one map, then on another map it loads a texture that has the same texture name but at a different size. This is because glquake doesnt flush textures on map change. With normal glquake and glpro, there is no way to eliminate this problem from what i know, without hacking into the engine. Use winquake or wqpro. Or you can use them other fake quake engines like qrack, darkplaces, joequake and so fourth. I do know of a glquake engine that doesnt have the cache mismatch problem.
Cache mismatches are caused when glquake loads a texture on one map, then on another map it loads a texture that has the same texture name but at a different size. This is because glquake doesnt flush textures on map change. With normal glquake and glpro, there is no way to eliminate this problem from what i know, without hacking into the engine. Use winquake or wqpro. Or you can use them other fake quake engines like qrack, darkplaces, joequake and so fourth. I do know of a glquake engine that doesnt have the cache mismatch problem.