jpg hijack Q:
So say I had a jpg pic. Should I load it in to photoshop and re-save as a png? Or has the dammage been done since it started as a jpg?
The damage has been done.
To be safe you should probably just save all of your artwork as .png to begin with. Or .bmp. But .png supports alpha transparency, and Construct imports the alpha just fine and converts everything to .png anyway so, yeah, no reason not to use .png.
> As for removing the sprite from the game and the .exe not changing size... did you remove all instances of the sprite, or just one copy of it?
All. Definitely all. In my simple test, there was only one layout and one object.
These were the sizes of the .exes in the test project:
Completely empty layout: 657kb
Layout with large sprite: 3.54MB
Layout with large sprite deleted: 3.34MB
In my large project, the file sizes didn't change at all when I removed several huge objects.
That definitely sounds like a bug. Try this: Delete the large sprite, then save and close. Then reopen the .cap and export an .exe and see what that filesize is. It could be that it's just a memory issue with the IDE. It does still have to save the object in memory in case you want to undo the delete, after all... maybe something is getting fudged between that and exporting a build.
At any rate it's probably going to have to go to the tracker, but getting as much info as you can on what's going wrong will help the devs figure it out.