Alex W

Whilst that is useful to know, it doesn't help with the particular issues raised here. Align and mirror simply ignore the pixel alignment setting. I actually find that mirror ignoring transform locations as well and always using just the centre point of whatever you are mirroring is also pretty irritating, but that's a separate issue.

I appreciate you trying to help but whilst it sounds good in theory I can't change the relationship of the original content as this will make that blurry to start with. I'm already using a manual process to deal wit this and the point of the comment was really that when you have move by whole pixels and force pixel alignment turned on, it would be handy/intuitive if transforms and alignment respected the current pixel alignment of layers and images too, to avoid having to manually correct things. Here is an example Before mirroring a group After mirroring a group with original still behind. You can see the extents of the group and it's centre point are the same, but because of the fractional pixel size the actual pixels get offset by a fraction of a pixel and thus become burred. So far the only way I can find to resolve this is to rasterise and trim, which trims the rasterised layer to a whole pixel size and mirroring then works fine. But this is obviously destructive and doesn't work for what I need to do. I currently have to turn off pixel alignment and manually drag the mirrored version horizontally until the images look the same. It's a particular issue for me here, but more generally people may not realise that mirroring an image/layer/group which has a fractional pixel size could subtly change the way it looks... this may not matter in many cases but it could for some. Given this I actually think it should be changed so that in general mirroring or aligning doesn't change the relationship of pixel data to the pixel grid, by default, and you have to actively change the behaviour if unwanted.

M<ove by whole pixels is very useful if you are doing pixel art or using a very fine brush and want to keep detail. However using align or transforms such as mirror will not maintain pixel alignment, leading to blurring after the transform. I appreciate there are issues with odd and non whole pixel data on a layer making the centre point a non whole pixel, but it would be really handy if things like align and mirror especially could at least maintain the same pixel relationship of the image/layer to the canvas as the pre aligned/mirrored image/layer/etc, even if this means that it doesn't quite precisely align to the centre or whatever. Eg when you mirror a layer horizontally, the furthest left extent of the left side has the same relationship to the "pixel grid" as the newly mirrored right side extents. This would at help enormously to maintain consistency of the image when you apply these functions to it.

I know it's different but I don't think it's necessarily less intuitive than using save-as. As far as I see it save as was not always there for "saving as a different format", it was there to save ayour current project AS a different PROJECT - useful for making various options or using previous work as a base to do something new. I actually think it was pretty lazy of certain programs to bundle in the exporting of that file to different formats in to the save as function. And, whilst this may be common to some programs, it certainly isn't to all. I don't quite understand why you say it is an old-fashioned UI/UX, imo it's actually a more considered choice, with using save-as being an antiquated "choice". I personally don't find it at a struggle to scroll the extra few lines down from "save as" to "export" in the menu (I certainly don't find it harder to find at all) when I want to export, nor do I find it a hassle to remember to press alt as well as ctr,, shift & s as a shortcut to export my creation to a different file format. I'm not really sure what it is you are asking Serif to "spare us" from. I actually don't save my work as jpg most of the time. If I'm using affinity to create a file I want it preserved in that format in case I want to make changes to it, or use it to do something new. I do of course want to export it as jpg (or png, etc etc) at various points, but this is a separate exercise to saving my work. In my opinion it is good that the two separate functions of saving a layer based affinity file, and creating a flattened file format is separated as they are. Export is a perfectly logical choice for creating a jpeg as that is exactly what you are doing - exporting your file to something which is fundamentally different to what it is. I welcome this kind of clarity of function. I'm not really sure I see why there is any difference from a work flow perspective between choosing "save as" or choosing "export" when you want to export a jpg from your file anyway... the only thing I can see is force of habit and one additional key modifier - neither of which seem a good enough justification to present it as a big issue or poor design decision. I honestly feel like this request boils down to "I'm not used to it being called export instead save-as"... and the perception that this is a wrong choice or somehow creates a stumblingblock to creating jpgs, pngs, etc, flows from that. Choosing export rather than save-as in the (same) menu, or pressing alt as well as shift s is not "inherently any more difficult as an operation, it's only really user habit that may make it so - which really needs to be considered against the reasons why it was done differently, and the fact that it won't actually be the case for eeryone, only a certain group of people. Personally, even having extensively used photoshop, I didn't really have any issue getting accustomed to this difference. This could be because other programs I also use a lot do it already though. I personally hope Serif don't make this change as I prefer it as it is. Just my opinion but I thought it worth adding the counter-point to your request.

500% this. I can't believe brushes are still stuck with 200% spacing maximum. I really can't see any good reason why this limitation should be forced on users.

The ability to export shapefiles would be great to be able to re-project maps drawing in designer in to other map projections using other software. Also great would be a re-project map projection solution within designer!

To add to the corner issue above, this is even more frustrating if you are working with compound curves, because you actually can't add the extra control points to your shapes (or rather you can, but the rendering of the stroke on the compound path will just ignore them) meaning you are forced to destructively convert the compound path to curves, and then add your control points. It's not.... great.

Made a more detailed suggestion post about the above here:

It'd also be really nice if it could be set so that for sharp corners the image isn't stretched across the entire length of a segment when using stretch or fold (is there really any difference between these?), and instead was stretched only as far back as needed to wrap around the corner. At the moment you an resolve it by adding extra control points in, but for a lot of image based brushes like the one above you just don't want to hap pen and it can get tedious fixing it (not to mention you have to re-fix it every time you merge curves, because the ones you have added get removed).

So this is pretty weird. Following the above I've noticed that if I rasterise a group, it can go really screwy, blurring and sometimes darkening areas of the asset. However if I use rasterise and trim it works fine!

I'm just uploading now. I had to ditch the upscaled version in the end. It did finally save, but it was just a portion of the 10mb file I've uploaded, yet scaling it up by 200% ballooned the file to 3.5gb! Which might explain why it took over two hours to save. I still have the same problems with the original file I have uploaded. I also have a weird issue where rasterising a large number of the grouped assets (rasterising the group for that one asset) changes the way it looks, sometimes drastically. It seems to get more blurred, as if the image had been shifted by a fraction of a pixel.

Thanks I'll def upload it. Unfortunately I'm still waiting for it to finish saving! I do have a live box blur filter layer in each of the asset groups.

I'm getting really slow performance in a file which has a lot of layers (its basically a bunch of assets with lots of layers making up each one). The file is around 3k x 8k (resized from 1.5k x 4k) pixels in total, but a lot of that is empty space. There are approx 100 assets each with about 6-10 pixel layers and 4 adjustment layers. Zoom and pan seems to work, but the screen takes ages to refresh beyond a blurry mess. Weirdly when I zoom and pan I often see parts of image showing as if they were from several actions ago... eg if I have moved something it will appear in the old position until the screen is fully refreshed when it will suddenly snap back to its adjusted position. I am just now trying to save it after the resize (which again took ages, like nearly an hour) and it has so far been half an hour and its still nowhere near done. Is this really just my machine performance not being great? I'm running on: i5-8500 CPU @ 3.00GHz 3.00 GH 32GB RAM Geforce 1060 (6GB - drivers up to date and using studio version). 1TB M2 SSD system disk (also set as my pagefile disk, with over 300GB free) 1TB SSD document drive

Could someone tell Autodesk that 😄

Isolation could just be an additional function for the visibility in the layers panel which toggles off visibility all but the selected item (be it a layer, group, curve, whatever), and then toggle back to previous visibility settings. This would be more a layer panel feature than a groups feature, and be far more flexible than trying to address it via groups.