Sean P

Hi Debraspicher, I've been around with the Rusty Nibs brush sets but have not been able to make the app crash. Do you remember what exactly it was you were doing when the crash happened? Were the brushes installed manually via an afbrushes or via the My Account dialog. Finally would you be able to go to %UserProfile%\.affinity\Photo\2.0 (Beta)\CrashReports\reports\ and attach the .dmp file that matches the time the app crashed above please? Thank you,

Hi garrettm30, Just to let you know the file was triggering some firewall rules on the forum and this has now been resolved! Hopefully any further images you try should now upload!

Hi Lecho, Would you be able to create a new thread for this issue and attach a video detailing/reproducing the issue you're getting and attach any supporting files (ideally so we can also open them in 2.3.1 to compare) you've used. Thanks!

Hi AP- Thanks for letting us know - I can reproduce that here and will get it passed on to development.

Hi Ronny, What do you mean by New Beta adds increments with 4 decimal places? This shortcut behaviour for [ and ] is intentional. By default [ and ] will change the value relative to what it currently is. This means that the larger the stroke is, the more it will increase. Meaning you can easily just hold the keys down to change it by a large amount relatively quickly if you just want to eyeball things. You can use Shift+[ or ] and it will scale by an absolute amount of 1px for every key press. Arguably this isn't the most useful value for if your line or document is set to something else. This behaviour is not new to 2.4 and hasn't changed from what I can see.

Thanks for the feedback Ronny. We do already have some of these logged, however I will get the others passed onto the UI team for consideration.

Hi Dazmondo77 This is currently working as intended. Layers that were not present when the state is captured are not included or considered when updating the state. You will have to delete and re-add the captured state to then include them. The Update option will only update that visibility of objects already present in the captured state to its current setting.

Thanks for that - I cannot reproduce the issue on a Parallels VM with fresh installs of either Monterey or Ventura, however I can reproduce it on a Parallels VM with a fresh install of Sonoma 14.0, so it certainly looks to be a Sonoma only issue and a regression from 2.3.1.

Hi Paul, Thanks for letting us know I can reproduce this here on 2 machines (both Sonoma without MS Office installed) using both your document and a new document. Both Italic and Bold Italic TNR are being exported out incorrectly as you're seeing - I did a quick try using Arial and that seemed OK. It does look to be a regression in this build so I will get it logged. Which version of macOS are you using? I'll check to see if this is ok on earlier versions of macOS too!

Hi Old Bruce, This is working for me in both 2.3.1 and 2.4.0.2222 using a Full Size Wired British Keyboard also set to British within macOS. What physical layout are you using and what is your macOS set to? HomeKey.mov

Hi VectorWhiz, Looking at that image it looks like your installation of Windows has some issues with permissions. The error you're seeing is a Windows error that does relate to permissions. A cursory Google search does show a series of posts on the Microsoft site regarding these. Looking at a previous post from yourself I can also see that you have modified the permissions for the 'WindowApps' folder yourself. These folders are for Sandboxed apps which is where the MSIX apps install to. Microsoft prevent access to this folder for security reasons and modifying this yourself will cause further problems, which it does look like you're now encountering. We would never recommend users to modify these permissions and are unable to support those who do. Ultimately there isn't anything we're able to do with this as it is an operating system permissions issue you're encountering, rather than the software.

Thanks Ronny! I'll get this passed on.

Thanks garretm30, I've reproduced that here and will get it logged. What is even stranger is that all of the other entries are also using what looks to be the wrong font size when compared to Layer Tag as well! I will pass on your PNG issue to the web team and see if they're able to see what is going on, although it might be more of a problem on Invision's side with the forum software.

Hi Poziomka, Thanks for letting us know - we've reproduced this and got it logged.

Hi Panchdara, I will get this passed over to development, as I do feel both methods (retaining the whole selection vs selecting what was only cut) have their benefits. So it would be nice if users could switch between the two.

Hi traceymaria01, I'm not able to reproduce that behaviour here! Are you able to make a screen recording demonstrating this behaviour please and attach it? If your demonstration uses a file, would you also be able to attach that please as it may be object specific.

Whoops - I did indeed forget to attach the screenshot! Sorry about that!

Thanks - this is how the Tools Panel and Toolbar look like with your file. Does this resemble what you were expecting? I'm not seeing the Cat Tool in place of other shape tools.

Thanks - none of those files relate to the Tools Panel. Would you be able to go to ~/Application Support/Affinity Publisher 2 Beta/ and attach the personas.dat file please?

Thanks Loukash, This is an issue we're aware of and is with development however it is not new to 2.3.1 - it is actually present in 2.2 and 2.3.

I was referring to where all your user data is stored on the Mac, and the fact that is a different location to the retail build as they don't share the same data (essentially treated as two different applications). Are you 100% sure the incorrect tools didn't show up when you loaded 2.3.0.2165 to check for updates? The issue I mentioned above affected 2.3.0.2096 and was subsequently fixed in 2.3.0.2106. If you modified your tools in 2.3.0.2096 to 'correct' the bug that was introduced, this would have been undone (an unavoidable side effect of the fix) in 2.3.0.2106 when we fixed the cause of the bug, however it does seem odd to me that you wouldn't have noticed this between 2.3.0.2106 and 2.3.0.2165, but obviously I don't know how much you would have used the Publisher Beta in that period. I will try a customised UI Tools layour on 2.3.0.2165 and perform an upgrade to 2.3.1 and see if the customisations are kept.

It is logged that the behaviour is different, but I am checking with dev to verify if this behaviour is intentional.

Thank you for your report - this is something we do have logged, and as Hangman says the stroke can be removed using the Text Frame Panel which is not present in Designer or Photo. 感谢您的报告 - 这是我们确实记录的内容，正如 Hangman 所说，可以使用设计器或照片中不存在的文本框架面板删除笔划。

Thank you very much for the video, whilst these are incredibly useful it is also useful for us to put a description of the problem you are seeing with steps to reproduce it. Please feel free to write it in your native language and we can use Google Translate to try to get a better understanding of the problem. I've watched your video and I can't tell from it what the bug you're seeing is? All apps are using different files so the side by side comparison between all your apps doesn't make much sense to me. I've opened your file in 2.3.0 and 2.3.1 here and it looks the same side by side.

I can't say for certain, but it sounds as though your Publisher's User Data was caught in the crossfire from this bug below in the run up to the 2.3.0 release. What happened, was that a list order of tools within the code changed, which caused havoc on changed shortcuts and tool panels. Unfortunately I cannot say what the last beta build you were running was, and even when you last run that (i.e when your Beta User Data was changed), looking at the changes in 2.3.1 I can't see anything that would interfere with the Tools layout either.