Slick Forums

Hi guys,

I'm trying to make health bar with 1px wide slices... but for some reason whenever I try to draw an image that's less than 3px wide, the pixels get all whack.

The image I'm loading is a .gif. I tried .png too and that doesn't fix it.

Attached is a screenshot of what it looks like when the .gif is 2px wide, and another screenshot of when it's 3px wide.

As far as I can tell there's nothing wrong with the file. I exported it via Save For Web in Photoshop CS6.

Also, I'm using g.scale() and I have a nearest neighbor filter on the image; Although taking those off doesn't fix the problem.

Why would you ever need a Image that small?
Why not just draw a small rectangle in the right color?

_________________
For every new problem, a new source of solutions has come to exist.

I can think of a couple advantages:

• Using sprite sheets, it allows you to minimize state changes and flush more data at once to the GPU. i.e. Using startUse/endUse/drawEmbedded, or Image.draw() and VertexArrayRenderer. In simple terms: it can lead to better performance.
• Drivers may implement line/polygon rendering slightly differently, i.e. with anti-aliasing, one pixel differences, etc. For the sake of consistency, it's better to just use an image.

And of course you may want a 1x2 or 2x1 image with different colours, so you could stretch it into the shape of an "embossed" horizontal/vertical rule:


I'll look into the issue.

Forgot about embossing.

Anyway when i said "Draw a small rectangle" i meant fillRect(), that draws a quad just like the images do, so if there's any one pixel differences, they'll happen on images as well anyway.

_________________
For every new problem, a new source of solutions has come to exist.

Thanks for the help!

Yeah the reason why I was using an image is because I actually want it to be multiple colors and not a solid rectangle.

Right now I'm using 3px wide images but drawing them so that they overlap, and then the bar only grows 1px at a time. It's not perfect, but barely noticeable unless you know it's happening, so it should do for now.

I wonder if it could be to do with not using power of two textures, I'm pretty sure that's where most texturing issues arise?

Yep -- if he used a power of two texture (2x2 for example) then it should work.

Still a bug in Slick, though -- I'm getting weird colours, plus it seems like Slick doesn't consider 1x1 a valid texture size.