0

I'm using RmlUi 6.1 with the OpenGL backend, and any TGA image I load — either in an <img> tag or as a decorator — renders incorrectly. Instead of displaying normally, the image looks torn, stretched, or split into four parts, like this:

screenshot showing tearing


Example code:

Using an <img> tag:

<img id="bg" src="testimage.tga" />

Or via RCSS:

body {
    decorator: image("testimage.tga" fill);
}

In both cases, the image is visible but heavily distorted.


What I’ve tried:

  • Exported as uncompressed 24-bit and uncompressed 32-bit TGA (with and without alpha).
  • Used several tools to convert (ImageMagick, online converters, etc.).
  • Confirmed the same result with multiple images and formats.

RmlUi’s documentation mentions support for uncompressed 24-bit or 32-bit TGA files, but no matter which I use, the output looks broken as in the screenshot.


Question:

Is there a known issue or limitation with TGA decoding in RmlUi 6.1’s OpenGL backend, or is there a specific export setting (byte order, origin, etc.) required for TGA files to display correctly?



2
  • Did you open an issue with RmlUI? Commented Oct 12 at 0:27
  • @PaulMcKenzie I haven’t yet. I can definitely do that, but I thought it was more about the image itself rather than RmlUI. I don’t know much about how images are saved, but it seemed like it could be something specific, like a wrong byte order or something. Commented Oct 12 at 10:53

1 Answer 1

0

I found the problem. In the image there was a flag set to read from bottom-to-top instead of top-to-bottom and another left to right flag was wrongly set

Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.