Ekjmss

Hi @Dan C, Now that you mention it, I'm fairly sure I have skipped the update to 2.0.4 a few times when opening the app, so it's not unlikely that my machine already had the 2.0.4 update cached as the next one. In any case, this is not a huge issue, but thank you for looking into it! :)

Hi, I downloaded V2.0 when it was released, and never bothered to update to any of the 2.0.x patches. When opening any of the applications now they still prompt me to update to 2.0.4, even though 2.1 is released. I went through and updated Designer to 2.04, and when it had finished updating/restarting, it immediately suggested I update to 2.1. Not sure if this is a bug or not, but it would be nice to just update directly to the newest version I'm running Windows 10, and installed using the (default) MSIX installer.

Hi Sean, thanks for looking into this. When exporting without a stroke it is extremely quick on my system as well, so I don't get the progress bar. The pixel layer is not strictly related to the error, but I added it in order to trigger the progress bar – it shows up when I export with both the "mainland" (no stroke) and pixel layer visible. However, when I add the stroke to the mainland layer I don't get the progress bar, even with the pixel layer, and everything hangs. Also, it seems that it is just the current file that freezes, and I can still close the file (I even get the prompt to save it) and carry on as usual. I've attached my export settings. I think it's just the default PDF for print. (Not shown is embedding "all fonts", as well as "subset fonts" and "allow advanced features" checked")

There's probably a menu command somewhere that I don't know of as well, but at least Alt+mouse scroll should let you rotate back

I have this slightly complicated vector object (a map of the US) that I want to export with an outline. The file exports just fine to pdf with no stroke, and exporting to png doesn't seem to cause any problems either, even with the stroke. However, if I try to export after adding a stroke to the object, the app just "locks up". I can still click on things (although with no effect), so its not exactly a crash, but I'm not getting the usual exporting status bar, so I figure something is wrong. Copying the object to a new file doesn't help either. See the attached file. Designer version 1.9.0.932. Edit: small edit to clarify it's a stroke and not an outline (effect). untitled.afdesign

Yep, the font is showing as "Building". Redownloading it from the link and reinstalling seems to have fixed it. Reinstalling again from the font file I originally had on my computer brings back the error, so it's probably a problem with that file. Looks like this isn't an issue with Designer then, but thanks again for looking into it

Hi, thanks for looking at this. Might just be that specific font that is causing problems then. I can reproduce it in other documents, but I didn't have any other caps-only fonts to test with. Here's a copy of the document: bugreport.afdesign

Affinity Designer 1.7.3.481 Windows 10 So I just stumbled upon what appears to be a bug in the way Designer handles all-caps with fonts that don't have any lowercase letters. I was using a font I found online (Building), with no lower case letters included. Apparently Designer substitutes the lower case letters with another font (looks like Arial, which is the default), which may or may not be good behaviour, depending on who you ask. However, when I tried to turn the text into capital letters using "Text->Capitalization->All Caps", the capitalized lower case letters remain in the replacement font (although now in upper case), and not the selected font, which is definititely not how I'd expect the program to behave. See the following screenshot. Ideally, the third line should look identical to the first one.