What if they were looped at 60 fps or does it make it animate too fast? Otherwise they would need to be performing an inter frame blend to interpolate a an a water animation image.
Not sure this is helpful, but they do depend on frame rate. At lower frame rates they place ribbon points less often, possibly because the points are placed every game frame or something like that. They still last the correct amount of time but at low frame rates the lack of points means they can be quite ugly as opposed to their normally smooth nature.
It lags with every model I open.
WC3 supports textures that are not power of 2...
No it is not. You can happily make a blp texture like 111*111 and WC3 will load it, mipmaps and all. Recently it will even load textures such as 1920*1080 however it still will only load the lowest mipmap level that is less than or equal to 512 in both dimensions.
WC3 has always supported not power of 2 textures. When I first started my research into the blp format I discovered this, and that was before the latest wave of updates.
Is there a technical reason why you cannot use a texture that is not a power of 2 directly? Is it some kind of OpenGL ES limitation? As far as I am aware GPUs do not have any issue using non power of 2 textures, just they are avoided for other reasons.
I assume that is an OpenGL ES thing, since OpenGL does support NPOT textures since early 2000s.
.
4.0.9.
4.0.10.
4.0.14.
.
4.0.21.
Except WC3 does not enforce the limit... Both TGA and BLP files can be loaded as non power of 2 textures. Further more TGA files are not even subject to a maximum texture size limit like BLP files are (one can easily load a 1920*1080 sized TGA as a texture in WC3). Although it might have been the case that such textures were highly bug prone in the past, that is certainly not the case anymore as all modern supported GPUs support larger than 512*512 textures and non power of 2 textures.
Just answering your questions here. Power of two textures allow Warcraft 3 to run and look as intended, on the video hardware it was officially designed for in 2002.
3D accelerator video cards from the mid-1990s up until the early 2000s were designed that way iirc. That is as simple as that. Therefore, all the textures found in video games had then to be power of two textures, in order to comply with the technical limitations of the 3D hardware of their day.
Fine, but I am guessing that the results would be... sub-optimal on some of the video hardware the game was originally designed to run on. I am guessing there would be visual glitches / artifacts, or the textures may not load, or they may look blurry, or the game engine might eventually simply crash when trying to load such textures.
For the record, even 3D accelerator video cards from the mid-late 1990s could have support for texture size larger than 256*256.
4.0.25.
viewer.toBlob((blob) => {
let url = URL.createObjectURL(blob);
});function downloadUrl(url, name) {
let a = document.createElement('a');
a.href = url;
a.download = `${name}.png`;
a.dispatchEvent(new MouseEvent('click'));
}async function record(viewer, frames) {
for (let i = 0; i < frames; i++) {
viewer.updateAndRender();
// Note the async/await!
let url = URL.createObjectURL(await viewer.toBlob());
downloadUrl(url, `frame_${i}`);
}
}
