Sean P

Hi kevinslimp, This is something we're aware of - currently Column Guides are only appearing if your document has bleed, so if you do need them you can apply a slight bleed to your document to make them appear.

Thanks for the file - I believe you're suffering from a crash than can occur when you use the Vector Brush directly after creating a pixel Layer and then try to undo it whilst the Appearance Panel is visible. This is a known issue that is with development to fix. I can reproduce on your document by simply making the Appearance Panel visible, selecting the top pixel layer and using the Vector Brush Tool and then use Cmd+Z. Could you try closing the Appearance Panel down (or ensure it is not visible in a group of panels) for me and see if that allows you to work around the crashing please?

Hi PaRunk, Have you made sure you've changed the Controller setting on the context toolbar to 'Velocity', and also ensured your brush contains a Size Variance of something that isn't 0%? It is working for me - it also helps if you attach screenshots/video footage of the current settings you're using/behaviour you're getting!

Thanks for that! I'll have a poke around with the file and see if I can reproduce it!

Hi Jon C, Thanks for letting us know - I've passed this over to development to see if there is anything that can be done, however I did see someone report this issue with Word in a 15 year old forum post: https://www.pcreview.co.uk/threads/cannot-ungroup-an-emf-file-inserted-into-powerpoint.2066687/

Hi spinhead, If you could attach a document that exhibits this - that would be very helpful. However please be sure to enable 'Save History with Document' on the File Menu first before saving, as that will save the history with the document and that will allow us to undo the history entries you've been creating. Also do you have any Crash Reports that appear after the crashing? If so could you attach those please, you can find past ones (sorted by time) in your Mac's Console app under 'Crash Reports'. Thanks,

Hi mark-h Thanks for letting us know I've reproduced that here and will get it passed on to development.

Hi safoster71, There are the odd couple of these scattered around, however without having any idea on what steps your taking I cannot say for sure if we're aware of that particular one. If you can accurately reproduce then please do provide us with a screen recording demonstrating!

Hi BASEMO, Would you mind sharing the file you're using please?

Hi @Gear maker How often do you find it takes before the app starts doing this to you? This isn't anything I've really seen before - however would you mind sharing your file at all please?

Thanks for that! I can confirm I can reproduce that issue on Big Sur only - I'll get it passed on over to development!

Hi koryrussell, You have 'Protect Alpha' enabled. This will stop you from drawing on any area of a pixel layer that doesn't have data - so with a blank layer it means you won't be able to draw anything. If you disable this you should be ok. It is intended to help stop you accidentally from drawing into the area of a pixel layer that doesn't contain any pixel information - for example on an image that is already cut out - it prevents you from ruining your clean edges. Unfortunately it does catch a lot of people out! Apologies I didn't spot it in your first image!

Hi koryrussell, Your screenshot shows a Layer 'ghost' that can appear if you're moving a layer and change studio whilst dragging the layer, or if you try and drag and drop between documents. If you fully close the app down and reopen it does it go away? Regarding not being able to draw on a Pixel layer are you able to capture a video recording of this behaviour please. Screen recordings make it much easier for us to understand what is going on. Unfortunately your screenshot doesn't give any hint as to why you can't draw on a pixel layer.

That's great - appreciate taking the time to check that for us! I've created a link to our internal Dropbox account where you can upload the file to when you get a chance. https://www.dropbox.com/request/IWr5hPwSXuVE7A6T76Hi We can take a look and investigate then! Thanks again.

Hi Blacklick, Are you able to get some screen recordings that demonstrate these three issues please? The first one I was not able to replicate - all objects are getting selecting without an issue for me and hide/unhide as expected. I'm not sure what could be happening with the second, but a video would certainly help. Again the third I was not able to replicate - objects are being placed in the correct location to where I'm releasing the mouse - note the visual representation of the line does let you know if you're dropping it above, below or inside of a layer.

Is your bad performance limited to this file, or does it affect new documents? If it is the latter then it won't be something in the file causing it.

Just to add that I'm also using a 1080 (non-Ti) with the 457.30 Game Ready drivers and not seeing any kind of behaviour like this. Would you mind sharing that file at all? Do you get this behaviour from a new document, or less complex existing one?

Sure! I've just created a Dropbox link that will allow you to upload it to our internal Dropbox account: https://www.dropbox.com/request/DsSFIKavC2ZAYHWwGSmm

Thanks for the file! The app shouldn't be allowing you to move the guides if they're not visible (which is what is happening as carl123 has pointed out). This is something we're aware of and has been fixed in 1.9 - Guides should only be movable using the Move Tool if they're visible.

Thanks for the files - that is indeed the same crash I was getting as well. I've got it bumped with development. Thanks! Unfortunately it has likely been introduced from a change in a recent build that Designer at the time did not have!

Scratch that - I did just get a crash when trying to delete an empty category. However I'd still be interested in trying your propcol. There is definitely something incredibly wrong with assets. Creating a new category is blanking out the dropdown and then creating that category without a subcategory which means you cannot populate it.

Hi Postmadesign, Do you have a copy of the crash log that appears please? Also would it be possible for you to attach your assets.propcol file from the location below: ~/Library/Application Support/Affinity Designer Beta/user/ I've tried reproducing the crash here, but have been unable to, however I have found an issue when creating a new Asset category though!

Hi Rocketdrive, Any chance you could attach a copy of the stubborn file please? Without that we won't be able to replicate the crash.

Thanks for the video, unfortunately I can't replicate the problem you're seeing. However i'm not exactly sure what sort of object it is you're moving because I don't think its a single text object. Its hard to say from the video but the rectangle box left around it after deselection and the readouts the pen is giving is making me thing something else is going off. Could you attach a screen recording of the entire screen (please use the inbuilt Apple Screen recorder to make this easier and clearer) showing the steps you're taking from file opening, and if possible could you attach a copy of the file you're using please. See below for the results I'm getting. IMG_3404.MOV

Hi JeffreyK, Do you have an afdesign file you could attach that demonstrates this please?