Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Hi Yiming, I found this software very impressive and enjoyed playing with it. However, when I attempted to "Export Image" in a 16 bit linear color space on Windows with v0.2a, the software wrote 0 bytes to a png and then crashed. I'm disappointed I may not be able to use Our Paint for real work due to instability. It is a very nice, unique program and I think digital art lacks things such as this. I wish you well.

(+1)

Hi! You can save .ourpaint file first. Are you able to save the ourpaint project file? Because internally it uses 16bit canvas as well…

Could you try doing it again from command line start and see if it produces any crash log? Does it only happen when you draw pretty big images?

I’ll definitely check on my side. Thanks for the feedback!

(8 edits)

(https://i.imgur.com/0cuw31L.mp4) Here is a video of me reproducing the problem. I don't believe the bit depth was important.  In the video, I first exported a smaller image. Afterwards, I exported a very very big image and it crashed. So, it seems the problem may have been the the size of the large pretty image. 

(https://i.imgur.com/0O1xZij.mp4) Here is another video where I save as a `.ourpaint` file. It crashes just as well, however the file it wrote (`i_am_testing.ourpaint`) had 178 bytes of data in it after the crash.

When I recorded the first clip, I had about 50 gigabytes of RAM available out of 64 gigabytes. Upon export, Task Manager showed OurPaint using 15 gigabytes of RAM before the crash (do note that Task Manager may lag behind).

There were 90 gigabytes of space in the drive I attempted to export to.

Perhaps automatic backups would help ease users in situations such as this? (And if the backup itself causes the program to crash, at least it crashes early in a user's session)

:)

(+1)

Wow you are indeed trying to save a huge file (in the first video the terminal actually outputs the dimension, it’s like 20000px wide…) I’ll definitely check and try handle the case of huge dimensions. I don’t really think it’s a memory problem, it’s likely that some integers overflowed because I don’t think I have used 64 bit integer in some places that could be relevant.

(What kind of usages do you need that big of an image? XD you can see the zoom level at the bottom left of the canvas, and by default it’s 50%)

Anyways, thank you very much for your detailed feedback :D

(1 edit)

(In my usage I made a few 3840x2160 paintings in one canvas, spaced apart)

:)

(+1)

Oh, then if you don’t need to export them as the “spaced apart” layout as-is, you can use the crop tool to specify a region to export. That way it shouldn’t crash. If you draw those images on different layers apart, each layer won’t be as big so you can succesfully save it.

The recent project I’ve been doing is sized at 10641x7730 and it works without any particular problem :D

Also in v0.3 there will going to be a layer moving feature so you can move individual pictures around granted you’ve painted them in separated layers.

(+1)

I have fixed the huge file saving issue and it will be available in the next version. Now saving is only limited on how much memory your machine can allocate, and when it can’t allocate enough memory, it should give a prompt and not crash :D

(1 edit)

Awesome :) Thank you, Yiming.