Sean P

Thanks leshido, I can see this now - its tricky to see without the comparison to the Effects Panel!

Hi Husbandman, Thanks for the afdesign. Unfortunately the PDF format doesn't allow for strokes aligned outside or inside, so to combat this and try to retain the 'vectorness' of the objects we have to expand that stroke on export. However as it is being expanded it is getting caught up with the known issue that some objects look incorrect when expanded or boolean 'Add' is used. You can see this by selecting one of the X curve objects that form the door and use Layer > Expand Stroke - you will see the same results as the export. The good news is that this issue has now been resolved in the 1.8.2 beta below which means when you export to PDF, the correct look of the doors are retained.

Hi Art1, We're aware of this issue which has now been fixed by development and will be made available in the next beta release! Thanks for letting us know.

Hi Diane Window 10 Desktop AD, There is a known issue with the Add command that has been fixed by development, however in the meantime you can actually combine a series of separate curves into one object without using 'Add'. Just select the objects and go to Layers > Geometry > Merge Curves.

Hi Bubily, Unfortunately this is a known issue that is with development to be fixed. I'll pass your comments along and get it bumped with them. Thanks for letting us know.

Thanks for that! It is indeed, changing the colour using the flyout in the appearance that was doing it. The stroke width is fine however via the Appearance Panel - just seems to be the colour. I'll get it passed on to development.

Hi InfoCentral, Thank you very much for the file and sorry for the delay in responding - we're currently dealing with a high volume of posts! Looking into your file it actually isn't a bug, but is happening due to a bug being fixed. If you highlight the offending C character and go into the Typography panel (Text > Show Typography) you will see that 'Caps to Small Caps' is enabled, but this wasn't actually working with this font in 1.7.3. Now that the issue has been fixed, you're seeing the character get converted to a 'Small Caps'. If you switch this to 'Normal' then your text will look correct. The issue with the PDF import and the A looking incorrect however is something I will get passed on to the development team.

Thanks for the file! I've passed it on to development.

Thanks for the files. I've had a look at the crash reports and in all instances the crashes are occuring inside nvwgf2umx.dll. This DLL file is from nVIDIA's graphics drivers, so there is something in their drivers that is causing Affinity to crash when attempting to draw the screen. Unfortunately as this crash is in their code there isn't much that we can investigate. However I would suggest uninstalling and re-installing the latest version of drivers for your graphics card.

Hi Stacy, In addition to what DM1 has said would you also be able to attach a screen recording demonstrating the crashes along with any files used to reproduce? Thanks!

Hi Vladimir Krstic and amyas, This has now been fixed on Mac and is available in the beta below. It was being caused by the issues with boolean operations.

This is indeed a known issue and is happening because those ellipses are actually path objects where both the start and end point are on the same position. Because of this they're getting ignored on import - this also seems to be the case on Illustrator as well. Inkscape does display the objects, but they're unselectable by regular methods - the only way I could select them was by using the XML Editor. I will bump the issue with development, however I would suggest also contacting Kicad and request the possibility of getting these objects out as Ellipses in the SVG instead of 0 width paths.

Hi Jorge Morales, Thanks for letting us know - I've reproduced this and passed it on to development.

Thanks for that - reproduced and will get it passed on to development. I hadn't yet seen the other thread and also reproduced using that file as well!

Hi Mitherion, Thanks for the file - I'll get that passed on.

Hi Taku33, Thanks for the files - I've replicated the issue and will get it passed onto development.

Hi Eddy-2 Thanks for reporting the issue to us - this is something that we do have logged to be fixed, so I will pass your comments on to development.

Hi Joachim_L Thanks for letting us know. I'll get this passed on to development.

Hi aleale1, Is this reproducible for you? If possible would you be able to get a screen recording showing the steps you are taking to reproduce please? Unfortunately I've not been able to reproduce it, and want to make sure I'm not missing any important steps.

Hi Sephen, Thanks for letting us know - I'll pass this onto development. There is a part of me that has a feeling this might be by design however!

Hi PedroDominguez, Sorry for the delay in responding - there are currently a lot of threads and we're gradually going through them! The document Old Bruce specified is in LAB which means it cannot be output to the PDF format. So instead of converting this to raster the document is failing to export. This is a known issue that is with development to be fixed.

Your post didn't get deleted, I separated it into it's own topic because it is a different issue to the one the original user reported. When reporting issues please try to create your own thread unless the results you're getting are almost identical to the original thread. It can be found here:

Hi Paul, This is an issue we're already aware off. However it should not be possible to create a Mitre value of less than 1 within the application. This isn't possible on the desktop, but does seem possible on the iPad so I will get that reported. Annoyingly it also happens when importing an SVG (from Inkscape) that has a mitre of less than 1. Thanks for letting us know!

Hi Anthony M. Is it crashing with a specific document, or does any document cause it to crash? If it a specific document would you be able to attach that please? Also could you go to %AppData%\Affinity\Designer\1.0\CrashReports\reports\ and attach some of the latest dmp files that correspond to the times its crashed when opening a document please? Thanks,

Hi narrationsd, Thank you for the update - unfortunately the issues previously mentioned are still open with development, however I will bump them with your updates.