experimental: allow factors up to 4 for hires textures
The performance drop is quite small and can completely be disabled by "hirestextures 0", if needed. May be revoked, if mappers have no use for it. Just assume this feature to stay, if textures emerge, which benefit from factor 4 over factor 2. DOCREF texture
This commit is contained in:
@@ -489,7 +489,7 @@ void _texture(Slot &s, float *scale, char *name)
|
||||
if(scale)
|
||||
{
|
||||
s.orgscale = *scale;
|
||||
s.scale = (*scale > 0 && *scale <= 2.0f) ? *scale : 1.0f;
|
||||
s.scale = (*scale > 0 && *scale <= 4.0f) ? *scale : 1.0f;
|
||||
}
|
||||
}
|
||||
|
||||
@@ -498,7 +498,7 @@ COMMANDF(texture, "fs", (float *scale, char *name)
|
||||
intret(slots.length());
|
||||
Slot &s = slots.add();
|
||||
_texture(s, scale, name);
|
||||
if(*scale < 0.0f || *scale > 2.0f) conoutf("\f3texture slot #%d \"%s\" error: scale factor %.7g out of range 0..2", slots.length() - 1, name, *scale);
|
||||
if(*scale < 0.0f || *scale > 4.0f) conoutf("\f3texture slot #%d \"%s\" error: scale factor %.7g out of range 0..4", slots.length() - 1, name, *scale);
|
||||
flagmapconfigchange();
|
||||
});
|
||||
|
||||
|
||||
Reference in New Issue
Block a user