Sean P

Ahh ok! This is indeed a known issue with development to be fixed!

Thank you very much! I've passed it on to development to investigate!

If you press WinKey+R and then paste the following line into that dialog and press OK it will take you to that location: %APPDATA%\Affinity\Designer\1.0\CrashReports\reports\ Would you be willing to attach your file to our internal Dropbox account that is only accessible by Serif Staff? If so let me know and I will make a link for you. Have you tried checking if Clipboard History is turned off?

Hi Wiredframe, This is already a known issue with development to be fixed! Thanks for letting us know however.

Are you able to attach a copy of the file that is causing the crashes along with a bunch of the most recently crash reports found in %APPDATA%\Affinity\Designer\1.0\CrashReports\reports\ that correlate to the times you are crashing please? Also what commands were you attempting to do at times the application is crashing as well? If it is normally copying and pasting I would check to see if you have Windows Clipboard History enabled. If it is enabled then please disable this as it has been known to cause crashes whilst copying and pasting.

Hi Thomaso, Thank you very much for the file. I've just been looking through it and found the cause of the crash is the 'Cloud' object with the 'Square Star' inside it. If you place an object inside another that has multiple strokes/fills and set that parent object to have an opacity of less than 100% it will cause the application to crash. For example open the attached document and then go to File > Export you will get no crash. However if you select the parent object and then change the Opacity to 90% and then go File > Export the app will crash. The good news is that this does appear to be fixed in 1.8 (tested using the current Windows Beta) however obviously this is not available to you. In the meantime you could either make the Layer Opacity 100% or just rasterise that single layer. Hope that helps you! Test1.afdesign

Hi thomaso, If you upload your file to the link below I'll try and take a look for you! https://www.dropbox.com/request/htBTSs0en5IrKORDZS9n

Hi jfcartier, This is a known issue that is with development and seems to be related to the speed at which you double click. I understand that these actions are muscle memory, however if you can try and slow the double click speed down you should be able to rename. I'll get it bumped with development though!

Hi The Titi, Is your document using an Artboard? If so does removing the artboard allow the bleed to be exported correctly?

Thank you very much for the files! I've recreated the issue with your copy of the Roboto fonts. I also tried it with the ones downloaded from Google and that was fine. It would be worth uninstalling your current ones and then downloading and installing the new ones from Google. In the meantime I'll get your issue passed on to development.

Hi Remi McGill Audiokinetic, It looks like there is a lot of null data in your file. In 1.8 we've tried to to improve error checking to stop corrupt files such as these from opening It is interesting that you mention it has been stored using Google File Stream. It has become apparent to us that Google's File Stream is actually corrupting local copies of users documents, which sounds like what might have happened here. See the article below https://www.scss.tcd.ie/joeran.beel/blog/2019/04/02/google-file-stream-a-horror-story-with-corrupted-files-and-more/ That article does suggest that downloading a copy of the file through Google's web interface and storing it in a location not monitored by Google can prove successful. You may also have some success by checking the File Versions that Google have stored and downloading them if the current one doesn't work.

Hi Joe, I presume this same document opens fine the release version of 1.7.3? Would you be able to upload a copy of your file to our Internal Dropbox account using the link below please? https://www.dropbox.com/request/lJpsXBuZGZ21IUKyBeKK

Hi MusingLounge, Welcome to the Affinity Forums! Thanks for getting in contact with us. Do you find that the software freezes or that the tools feel like they're not responding. When the software is in this state do you find that if you try to use the Vector Brush Tool it will only draw straight lines? There is currently a known issue that can occur when you change focus to a different application and then click back into the Designer UI area (not the document area). It is easiest to see when using the Vector Brush Tool, as it will only begin to draw straight lines. If you look at the video in this post this will show an example of this, all other tools will feel like they've stopped working such as the Panning and Move Tool. If this is the case for you then you can disable 'Use Windows' Ink within the Wacom Tablet's properties (I believe it is the Mapping or Calibrate tab). This should allow you to work with a tablet device without running into the issue. Please let us know if this works for you! Thanks,

Hi malayali, This is something we've seen before, but have not been able to reproduce. Would you be able to upload a copy of the Roboto font you have installed to your machine please (to ensure i'm using the same files you are). What locale and region is your machine set to? If possible could you follow some instructions so we can get an export log for the PDF export? Once you've done that could you attach that log and your resulting PDF. After you've done that does exporting with 'Subset fonts' unticked also stop the text from appearing incorrectly? 1. Create a folder called 'temp' on the root of your C:\ drive so you have C:\Temp\ 2. Run 'PDFLibLogging.reg' - this will insert a registry entry that enables logging for PDF export 3. Run Affinity and export to PDF 4. Go to C:\Temp\ and attach the PDFlib.txt file to this forum post 5. Run 'PDFLibLoggingRemove.reg' to remove the logging as this can cause slowdown and crashes if the C:\Temp file is removed. Thanks! PDFLibLogging.reg PDFLibLoggingRemove.reg

Wonderful! I'll get it passed on to development as the regular Layers Panel doesn't exhibit that behaviour when Ctrl clicking, so I don't believe the Slices Panel should (not to mention it also not being a 'Layers' panel).