^2 texture size and @3 bitmaps

totebo

Guys,

I have a delicious dilemma: My game uses repeated textures (that need to be ^2), and it also uses the automatic @2, @3 system to pick the right image.

The issue is that repeated textures don't work with ^3, which means I have to create images that are either ^4 or ^2. Both options mean an increase in filesize, since I would either have to duplicate the ^2 images, or add the extra redundant pixels for ^4. OR not include the images and default to @1, which means blurry textures.

What would you do?!

Niclas

totebo

Will you look at that. After tinkering a little while I came across the solution: If Gideros can't find a @3 file it will try to revert to @2 first, then @1. So in this case, I'm happy to go with @2, so I simply removed the @3 files. Problem solved.

Gideros, you're nice.

totebo

Suggestion.

This page:
http://docs.giderosmobile.com/automatic_image_resolution.html

Says:
When Gideros cannot find the alternative image to load, it loads the base image.

It could say:
When Gideros cannot find the alternative image to load, it loads the image closest in resolution, ie. if @3 is missing it will load @2 if it exists.

jdbc

You can also try to use only double size images and setScale(0.5) for all your images. Most of times works well. I mean when images is @1 Gideros will scale it to the right size if you use double size images.

ar2rsawseen

Really?

I remember previously it always was returning to the base size.
Are you sure it is picking up @2?
Maybe someone changed the behavior and I missed that O:-)

totebo

Yeah, I tested it by changing @2 and removing @3. @2 was definitely loading. Admittedly it was a quick test, but, I'll try it again just in case.

totebo

I tried this again, and my previous experience was correct; the "closest best fit" bitmap is loaded when the actual @n is missing. Genius!