Spritesheet Padding Bug, power-of-two size images

Problem Description

The exported sprite sheet of power-of-two size images have a wrong size when setting Downscaling to "High quality"

Attach a Capx

Attached

Description of Capx

The new sprites use 4 times more memory

Steps to Reproduce Bug

• Step 1 Export project
• Step 2 Open the "images" folder
• Step 3 Check the exported images

Observed Result

The 64x64 sprite is resized into 128x128

The 256x256 sprite is resized into 512x512

I have designed my game with power-of-two size images

So, this happens with ALL my images

I even have 1024x1024 sprites, that use 4MB (which it's ok) but if they are resized to 2048x2028 they use 16MB!

I think if the image has a size of power-of-two, it should not be resized

Expected Result

I expect that the sprites:

-If I have a 64x64 sprite, it doesn't have sense resizing it into a 128x128

-If I have a 256x256 sprite it doesn't have sense resizing it into a 512x512

Affected Browsers

• Exported images: (YES)

Operating System and Service Pack

Windows 8.1 Update 1 (64-bits)

Construct 2 Version ID

Release 185 (64-bits)

Afaik, C2 adds a 1 pixels border around the picture, it is documented, even though I did not remember seeing it directly in the manual.

https://www.scirra.com/tutorials/577/co ... imisations

But I think the manual says to keep sprites just under power of 2 size for that particular reason.

If your report already takes that in account, please ignore this post.

Power-of-two size images don't work well with spritesheets, because they get a 1px border added. It is documented:

[quote:umsnogvd]The optimal size is two pixels less than a power-of-two size, e.g. 30x30, 126x126 or 254x254.

So I'm not sure why you've gone and chosen exact power-of-two sizes for all your images - this will force the worst case scenario for spritesheet packing. I don't want to encourage worst-case behavior so I'm going to close as won't fix. Alternatively just use medium quality downscaling (very few people genuinely need high quality downscaling, see the manual entries on it)