Jump to content
THESE FORUMS ARE READ-ONLY: Please Read Me ×

Recommended Posts

Posted

I don't remember this being a problem in previous versions. I could export a slice and it would export the entire thing even if parts of it (e.g. glows, outlines) were extending beyond the canvas.

Now, it only exports the area that is visible on the canvas BUT the size of the image remains as if it exported the entire slice. 

An example of what happens:

image.png.3b8f06d535c938b4fd9528952a0269d8.png

Posted

Hi @vybr,

This appears to work for vector-based export formats but not for raster-based export formats, though that is what I would expect...

Affinity Designer 2.6.3 | Affinity Photo 2.6.3 | Affinity Publisher 2.6.3
MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Posted

Hi @vybr,

Welcome to the Affinity Forums & thanks for your report!

1 hour ago, vybr said:

I don't remember this being a problem in previous versions. I could export a slice and it would export the entire thing even if parts of it (e.g. glows, outlines) were extending beyond the canvas.

I've checked this behaviour in both Affinity V1 and V2 and the behaviour remains consistent between these versions, and with Hangmans findings above.

When exporting to a Raster format, I would expect the exported image to be clipped to the visible canvas, as raster objects outside of the canvas are not rendered in Affinity - though the physical image size should always match the slice size set within the Export Persona, hence the 'Actual Export' result from your post is seen.

When exporting to a Vector format, I would expect the exported document to contain the complete object, to the size of the slice set within Affinity.

However, there are considerations to be made as to whether the exported Vector file should visually 'clip' the exported object to the canvas size. Essentially resulting in the visual results from 'Actual Export', but the 'Expect Export' object would be available, should you remove said clipping object in the exported vector file.

Therefore I'm going to be logging this with our development team now to request further deliberation as to the best behaviour in this circumstance.

I hope this helps :)

Posted
3 hours ago, Dan C said:

Hi @vybr,

Welcome to the Affinity Forums & thanks for your report!

I've checked this behaviour in both Affinity V1 and V2 and the behaviour remains consistent between these versions, and with Hangmans findings above.

When exporting to a Raster format, I would expect the exported image to be clipped to the visible canvas, as raster objects outside of the canvas are not rendered in Affinity - though the physical image size should always match the slice size set within the Export Persona, hence the 'Actual Export' result from your post is seen.

When exporting to a Vector format, I would expect the exported document to contain the complete object, to the size of the slice set within Affinity.

However, there are considerations to be made as to whether the exported Vector file should visually 'clip' the exported object to the canvas size. Essentially resulting in the visual results from 'Actual Export', but the 'Expect Export' object would be available, should you remove said clipping object in the exported vector file.

Therefore I'm going to be logging this with our development team now to request further deliberation as to the best behaviour in this circumstance.

I hope this helps :)

I guess with my current use case I have no use for exporting a slice with its full size but empty pixels. I'm using Designer to create game assets, so I'm naturally expecting the entire pieces/segments of an asset to be exported. If a glow extends past the canvas by 10px, I now have a full sized image with an incomplete glow. If anything, it would make sense for it to simply use the cropped size, no?

I'll just work around it by increasing the canvas size for now.

Thanks @Dan C

×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.