Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs

Pixel Fx Designer

Design pixelart effects and render them to .png sprite sheets or .gifs. · By CodeManu

PNG export (spritesheet) not at all like render, very broken

A topic by Lance created 70 days ago Views: 216 Replies: 7
Viewing posts 1 to 4

Just yesterday I got the software and was trying to get an effect rendered as 32x32 frames. See below.


The Scale settings etc are as follows:


The outcome is a very bizarre looking effect, check it out.


It is supposed to look like this:


The spritesheet this effect produces is also absolutely broken, trying to get the spritesheet in, say Pyxel, produces the following animation:



I can't really use the software like this. I tried exporting a 100x100 frame animation, but this also has the same very shaky and weird effect. Is there a setting I'm missing?

Hi, parameters looks correct, don't know what can be.

Have you tested with 128x128 ? THat weird thing happens too with the default canvas?

I will send to CodeManu to check the export for issues.

Hello, thanks for the quick reply. The 100x100 standard canvas are giving the correct results (spritesheet and GIF as well). Anything smaller than this doesn't work., I'm afraid.

I'm on Windows 10, 64bit. I am not using any DPI scaling or any other artificial scaling. I'm running the latest gpu drivers (AMD RX 580).

Hope this can be resolved. Thank you.

So, same parameters, just canvas size does that? 

Ok, thanks for the report! will try to fix!

Yeah, same parameters. I just changed the canvas size so it's 100x100 per frame. Thank you for looking into it!

Developer

Hi there,

This looks indeed weird, it might be due to rounding the canvas size in order to get the 32x32 frame size. Could you check if this issue occurs when using a 400x400 canvas?

Hi, I had already tried that earlier and it did work when putting canvas size to 400x400 so it outputs a 100x100 sized frame.  

I've tried it with different settings, here's the output frame sizes and whether the animation is broken or not:

32x32 - fails 

48x48 - fails

60x60 - succeeds

62x62 - fails

64x64 - fails

65x65 - suceeds

75x75 - succeeds

100x100 - succeeds

Developer(+1)

So that definately has to do with size rounding, I've added it to the todo list and should be fixed in the next update. Thanks for the report!