Log in

View Full Version : Export image to a file ignoring assets in directories



Kelrugem
October 12th, 2025, 12:46
Hi :)

I just found some bug regarding exporting images to a file:

I exported some image and I realised that some assets were not shown, and I played around a bit: An asset simply lying in the data directory gets exported properly, but when I use an asset which is in another directory in the data directory itself, then it won't export, leading to that the exported image is only partially created depending on how the assets are saved.

Maybe important: I am speaking of my own assets, I did not test assets from the art subscription :)

Best wishes

Kelrugem

pindercarl
October 12th, 2025, 19:03
Hi :)

I just found some bug regarding exporting images to a file:

I exported some image and I realised that some assets were not shown, and I played around a bit: An asset simply lying in the data directory gets exported properly, but when I use an asset which is in another directory in the data directory itself, then it won't export, leading to that the exported image is only partially created depending on how the assets are saved.

Maybe important: I am speaking of my own assets, I did not test assets from the art subscription :)

Best wishes

Kelrugem

Are you referring to exporting to module? Or, exporting to image using the control in the image window?

Kelrugem
October 12th, 2025, 20:42
Are you referring to exporting to module? Or, exporting to image using the control in the image window?

the latter, so directly exporting the image in the image window :)

pindercarl
November 22nd, 2025, 21:45
the latter, so directly exporting the image in the image window :)

Sorry for the delay, I'm taking a look at this one. I'm not able to reproduce the issue, but I'm also not sure I fully understand it either. When the export image, visible layers are just written to an image file and saved (with any metadata as an XML file) in the campaign images directory. It doesn't matter where the image layer originates. If it is rendering to the screen, it should render to the image. If it was a VERY big image, you might run out of GPU memory and then it wouldn't render. Any additional details? Maybe a screenshot of the image that is not exporting? Thanks.

Kelrugem
November 23rd, 2025, 15:49
Sorry for the delay, I'm taking a look at this one. I'm not able to reproduce the issue, but I'm also not sure I fully understand it either. When the export image, visible layers are just written to an image file and saved (with any metadata as an XML file) in the campaign images directory. It doesn't matter where the image layer originates. If it is rendering to the screen, it should render to the image. If it was a VERY big image, you might run out of GPU memory and then it wouldn't render. Any additional details? Maybe a screenshot of the image that is not exporting? Thanks.

Thanks, and no worries regarding answering late :) I just tried again and now it works; so either it got fixed somehow in the meantime, or I had indeed a too large file as you suggested :)

Sorry for possibly bringing up a non-issue :)