8,163
edits
XML:TXMP: Difference between revisions
TXAN should be used for traditional effects like fire and smoke that don't have repetitive elements
Paradox-01 (talk | contribs) (Mr. B's Dance Troupe takes a break, they are on Slurm withdrawal) |
Paradox-01 (talk | contribs) (TXAN should be used for traditional effects like fire and smoke that don't have repetitive elements) |
||
| Line 163: | Line 163: | ||
# For animated textures, OniSplit can only import TGA files. | # For animated textures, OniSplit can only import TGA files. | ||
# AdditiveBlend should only be used on things that are supposed to glow otherwise you might think that it ignores vertex shading. In case of the billboard at the right, that was an improvement. Now it's a transparent OLED billboard. | # AdditiveBlend should only be used on things that are supposed to glow otherwise you might think that it ignores vertex shading. In case of the billboard at the right, that was an improvement. Now it's a transparent OLED billboard. | ||
# Long animations in high quality (512x512, RGB) will produce very big oni files. The not-edited billboard gif is 1.7MB, the oni file is 273MB. That's because TXAN can use high quality and stores also all repetitive frames. The compressed oni (zip) was still 66MB which is still unreasonable large for people with small internet bandwidth. The billboard could possibly broken up into the 3 static and 3 transitional images. You would then need a [[XML:ONLV#Texture_exchange|BSL loop]] to keep the animation going. So the conclusion is to use animated images with lower quality settings and avoid repetitive elements. | |||
[[Creating_image_animations|HERE]] are a few information on how to create an animated texture within a graphics program. | [[Creating_image_animations|HERE]] are a few information on how to create an animated texture within a graphics program. | ||