Re: Tileset editing bug
Reply #3 –
First and foremost, I've tried Sphere Studio and I don't like it. One thing I've always liked about Aegis was that he was very keen on UI/UX, and he did a good job on the editor. Sphere Studio's layout is much more restrictive than the windowed approach in the Vanilla editor.
In terms of the bug, I've found that these bugs don't happen in v1.4, so if all else fails I can use that version. Looking at the memory usage, in v1.4 when I draw a line it seems to allocate a new image's worth of memory (eg: for a 2x2 tile box, it would create 4*16*16*4 = 4k, no extra memory when only one tile is selected), and then with the next line, it'll allocate another 4k of memory and so on, until I select a new tileset rectangle, at which point that allocated memory will be deallocated. However, in v1.5, while the extra memory is still allocated for each pixel edit (line, pencil, etc.), after changing the tile rectangle, the extra memory is freed. As well, if I stay on a single tileset rectangle in v1.4 and keep modifying it, I can easily get to 100mbs of memory, and then free it down to 4mbs, but in v1.5, the crash starts happening at around 20mbs of allocated memory.
For the tile insert, it literally happens every single time I try to insert a tile or image/frame in a spriteset. There's no randomness to it all.