Dan C

Hi @tariq, Thanks for your report. Affinity Staff members have confirmed in multiple posts here on the forums, many of which are in the above linked thread, that we've been working to investigate this issue and informing Apple of our findings - as well as providing updates to our users during this process, though I'm sorry to hear you feel this way regarding this issue. As I understand it, this is not the cause. I can verify that we do not believe this is related to the 'My Account' or web components of the Affinity apps and we are not looking to remove these from future versions at this time. In regards to the official cause and latest updates for this issue, I have since posted in the aforementioned thread to inform all of our users who have reported this previously. You can find this post below - I hope this clears things up.

We have investigated this problem thoroughly, and unfortunately have found it to be intractable due to our application file size and the security that Apple builds into all it’s operating systems. To support the different hardware Apple now makes, since 1.8.6 we have distributed a Universal Application (compiled for Apple-Silicon and again for Intel based macs) within the same .DMG installation file. These Affinity applications are consequentially almost twice as big as previous, but we have to provide both versions to support all types of current macOS hardware. It seems the time required by YARA/Gatekeeper anti-virus checking, which occurs when first launching the app, is exponential with file size and therefore this delay out of our control - because we need to serve up a universal app through the mac App Store, and currently provide the same Universal App download from the Affinity Store. The reason it happens every time you restart your mac is that the YARA/Gatekeeper system may have been improved since last time it checked our application, so it does not “save” the fact our application has already been checked. Other applications are likely much smaller files and so start quicker. Unfortunately due to the above reasons, we do not currently have an option to reduce this start-up delay as it is intrinsically built into macOS security protocols and not controlled by Affinity directly - though we have informed Apple of this and will continue to monitor this in future macOS updates. We may investigate an option in the future to provide separate installation files on macOS for each hardware type, from the Affinity Store directly - though we do not have any direct plans for this currently and unfortunately it would not change the behaviour experienced when using the mac App Store version. Our apologies for any inconveniences caused due to this.

Hi @Eliasxvz, Welcome to the Affinity Forums I have followed the steps in your post and from my testing this appears to be working as expected currently - 2023-05-12 11-45-03.mp4 Have I misunderstood your report, or skipped a required step in my above recording in order to replicate this please? A screen recording showing this behaviour may help me to better investigate this issue, if you're unsure how to take a screen recording, please check out our FAQ linked below - Many thanks in advance

Hi @Amber_Mtl, Thanks for your report and I'm sorry to see you're having trouble! I can confirm that there is a known issue in 2.0.4 that can cause crashing when zooming and re-rendering, especially in 'heavier' documents and I believe this is what's being shown in your screen recording. This issue has been resolved in our latest beta version, 2.1 - which we're hoping to release shortly. If you wish to try this version in the meantime, you can download and install it alongside your retail version, using the information found here - Please note I recommend using a copy of your 2.0.4 document within the beta, as once it has been saved in v2.1 you will no longer be able to open the file in 2.0.4. I hope this helps

Hi @pbass, Currently the Delete options in AFD iPad are either the Trash icon, or the Quick Menu option as you've mentioned above, unfortunately there's no additional setting to enable a different delete gesture at this time. I'm not seeing this on my iPad here, though it may be due to your Accessibility settings within iPadOS. Please navigate to iPad Settings > Accessibility and try disabling the Zoom option here, as it may be conflicting with the gesture within Designer. If you're still having trouble with this gesture after disabling the aforementioned option, please ensure you are using a relatively fast movement of your 3 fingers downwards, as otherwise the Quick menu may not show. I hope this clears things up!

Thanks Bruce, that's certainly interesting! I'll add this info to the development log with the users file

Many thanks for providing these for me! One of the main causes of crashing is outdated Graphics Card drivers. Please visit the manufactures link below to download the latest driver available - https://www.intel.com/content/www/us/en/download/762755/intel-6th-10th-gen-processor-graphics-windows.html?wapkw=UHD 620 Note: you may need to go direct to your PC manufactures website for the driver, if you see a warning regarding 'OEM drivers' when trying to install from the above site. Once downloaded and installed, please restart your computer and then launch the Affinity app again, then try exporting once again. If this continues to crash, can you please confirm what location you are trying to export to? (ie local disk, cloud folder, network/USB drive) Please do let me know how you get on here

Thanks for linking this video - the issue shown their has been resolved in our latest beta version 2.1 according to our developers, so hopefully this should no longer be required following the 2.1 release

Hi @Juc1, Thanks for your file provided, this is certainly helpful! With the object selected, navigate to Layer > Geometry > Separate Curves. You should now see the Curves object in the Layers Studio is separated into multiple Curve objects, which can be separately edited as required. I hope this helps

Hi @mallaig, Welcome to the Affinity Forums I can confirm the purple outlines shown in your screenshot are Snapping Candidates, which can be toggled on/off in the Snapping settings - You can find out more about Snapping here - https://affinity.help/designer2/English.lproj/index.html?page=pages/DesignAids/snapping.html?title=Snapping I hope this helps

Hi @Petar Petrenko, If I've understood your current document setup correctly, any FX applied to a Text Frame object will apply these FX to all of the text within the frame, including the decorations and this is expected behaviour. If you don't wish for these FX to apply to certain areas of text/decorations, I'd recommend creating a separate Text Frame / Artistic Text object which does not have these FX applied, for your decorations etc. I hope this clears things up

Vielen Dank für die Bereitstellung dieser weiteren Informationen und Bildschirmaufzeichnungen. Das ist auf jeden Fall hilfreich. Ich kann bestätigen, dass ich dieses Problem hier reproduzieren konnte und habe es bei unserem Entwicklungsteam zur weiteren Untersuchung und zur Behebung in einem zukünftigen Update protokolliert. Ich hoffe das hilft

Hi @Giggly, Your Vector Brush Size Variance is currently set to be controlled by Pressure, though your Curve has no Pressure applied - therefore the size remains consistent throughout the stroke. You will either need to add Pressure to the Curve using the Pressure graph in the Stroke Studio, or change the Controller in the Brush Editor to change how the Size Variance is calculated. I hope this helps

Thanks for providing that for me! I've tested this in both 2.0.4 and 2.1 beta and unfortunately the issue is present in both versions - this bug appears to be caused by the Pressure Profile applied to the curve, as removing this allows the shape to be expanded as expected. I'll be logging this as a bug with our developers now, I hope this helps

HI @GenewalDesign, Thanks for your report! Are you able to please provide a copy of this document with the curve before it has been expanded? If you wish, this can be a 'cutdown' file with only the affected curve(s) present. Many thanks in advance

Thanks for confirming that for me and I'm sorry to hear these options weren't working as expected - though I am glad to know you found a workaround to recover the file. In regards to the cause of this, are you able to attach a copy of your PDF file that was opened to create this document originally? If you'd like a private upload link for this PDF file, please do let me know. I assume the same issue does not occur when using File > New, or when importing other PDF files (as this is the method you mentioned above to 'rescue' this document)?

I can confirm this, it appears to be a Windows bug only. Unfortunately not - with either Smooth or Smart nodes, the 'hole' continues not to print. I'll be sure to update the development log with this info

Hi @Necrons, Welcome to the Affinity Forums Thanks for your report and file provided! I too have tried the above suggestions (alongside a few others) and thus far have been unable to print this from Windows with the hole included - unless I rasterised the layer or export to PDF and print this document externally, as mentioned by Return above. I'm unsure of the cause of this currently and therefore will be logging this as a bug with our developers now for further investigation. In the meantime I'd recommend exporting to PDF, then printing the file externally in order to workaround this issue. I hope this helps!

Hi @Johnnyyyy, Thanks for your report and your files provided - I can confirm that I've also been able to replicate this issue here and will get it logged with our development team now. Interestingly unpinning these images also resolves the issue, which I'll be sure to include with the development report. Out of interest, was this file imported from a different format into Publisher, or was the document created directly within the app from scratch? Many thanks in advance!

Hi @nickbatz, Unfortunately there's no direct functionality built into Affinity to perform this with one command, my apologies. I'll move this thread to the feedback section of the forums to be considered for a future update

Hi @sammybee, Thanks for your report and I'm sorry to hear you're having trouble! Can you please open the Affinity app and navigate to Edit > Preferences > Performance and provide a screenshot of your settings here for me? Secondly, can you please provide a screenshot showing your export settings when this crash occurs? Many thanks in advance

.MOV files cannot be 'embedded' within a post here on the Affinity Forums, which is why the users screen recording shows as a downloadable link. (and there is no issue with using this format for the Affinity Support team to download and view) Other formats however, such as .MP4 can be embedded directly for 'playback' within a post. (this can be tested by downloading a .MOV file and simply renaming it to .MP4, then attaching to a post as normal) I have edited the original post to include an MP4 version of the video, such that it can be viewed directly within the browser and does not require downloading. Please keep further replies in this thread on topic for OPs issue within Affinity Publisher. __________________________________ @Troy1969, As you've mentioned this works as expected in other files - are you able to attach a copy of the .afpub file where this is occurring to your reply here so that I can investigate this further please? If you'd like a private upload link for this document, please don't hesitate to ask

Hi @SuSa333, Welcome to the Affinity Forums I can confirm that this add-on kit is provided as Affinity Assets, meaning they can be found in the Assets Studio. If you cannot see the Assets Studio currently, please navigate to Window > Assets from within Affinity Publisher 2 and enable this option. You should now see these Icons available here - I hope this helps!

My apologies for the delayed response here and many thanks for providing your document in the separate thread! I can confirm that I have been able to replicate this issue with your file and I have logged it as a bug with our development team for further investigation. Unfortunately, thus far within my testing I have been unable to find a workaround to resolve this issue, my sincerest apologies. Should our team have any further information to share regarding this issue, I will be sure to respond here ASAP. I hope this helps

Thanks for confirming that for me and for the file provided - my apologies for the delayed response here. I can see that there are no Text Styles currently applied to these text frames, however your document uses 2 different Leading settings across text frames. The top text frame uses 'Exactly - 9pt' and the bottom 2 text frames use 'Default - [11pt]' - Is this the difference you are referring to? If so I'd recommend setting all text frames to use the same Leading settings across your document and you should find these are retained when opening the file on any system. I hope this helps