Lee_T

I Think the problem you are experiencing here is down to the way the shape is created, every stroke has a beginning and an end, even on closed shapes. Additionally, using the corner tool and crossing them over, you are forcing two nodes to occupy the same position and they will not merge, this is by design. For a "perfect" arch, I would recommend using the Donut tool and converting the result to curves followed by extending out the edges. This should remove the process of overlapping geometry. It's also worth bearing in mind you can force the position of the start/end of a curve by creating the shape manually instead of using a quick shape. Lee

I can only relay my own experience but I've noticed any benefits the studio driver give tend to be quite short lived in terms of performance and stability due to those less frequent updates. In the past I've tested Nvidia's studio drivers for any effect on audio latency and I've never had a swing either positive or negative in the audio latency results from the studio drivers on various audio interfaces, as obviously the Interfaces driver has far more control over ensuring latency is low. What I have had though is a negative effect on 3D/Video performance/stability using the studio drivers. Again this is only my own experience but a reason I switched to the main branch of driver for my personal machine. With direct regard to the issue you are having though, the video card drivers attempts to drive latency low can be the cause of visual defects like this. Even though you don't have Nahimic it may be worth adding the flag --no-hw-ui to the application following the instructions @GarryP passed on. If this doesn't work, as this is a redraw issue handled by the video card, I would suggest that this is at least tried the retail driver before delving further into any other troubleshooting especially as it can easily reverted if it's not the issue.

Hi B3n, Welcome to the forums! Have you tried this with the regular GeForce drivers? Lee

Hi Janekoke, welcome to the forums! Would you be willing to share either the file and/or a video/image with a detailed description of what exactly is happening? https://www.dropbox.com/request/Dsm8fOfMtJdK2BYAr777 Thanks, Lee

Hi Rickey, Could you try resetting Designer's settings? (hold control whilst booting the software), then just press clear without changing any of the default reset options. Lee

Thanks for the file, I'm able to replicate this end as well, it's hard to nail down which feature is causing the crash as it leaves no report, but I'd suggest exporting as a PDF to import as a workaround. I tested this on your document and it seemed to work fine. We're always investigating issues with importing IDML's so this file will help us narrow down what causes the crashes so thank you for supplying it. Lee

Hi HeatherTeller, Welcome to the forums, In you export settings, ensure these particular settings are set as shown below. Lee

Hi and welcome to the forums, If the files are dated two days ago in your operating systems file information then they weren't saved, so unfortunately it's likely you'll have to rely on your backups. Lee

Hi Thomahawk, I'm not quite sure I follow the problem you are having. Would it be possible to send the file you are having issues with and reply with some step by step instructions on how to recreate your issue alongside some information on what you are expecting as a result vs what's happening. https://www.dropbox.com/request/ugWaFbygWiVOYV569aBV Thanks, Lee

The limitation comes from the fact that Adobe's .ai files are proprietary and Affinity pulls the information from the PDF stream embedded within the file, which is a bit of clever workaround and works for most things. Unfortunately this scenario isn't one of them, it generally brings over the gradient but some features in that particular gradient/layer style aren't included in the PDF.

It looks like your stroke's that have been clipped have been converted to vector shapes with a default colour as it cant pull over the stroke gradient to a vector. This is normal behaviour so will just need a little bit of adjustment post import I'm afraid. I can certainly appreciate the logo as a motorsport enthusiast. Great work! Lee

Hi Jill, Welcome to the forums. Would it be possible to supply us with the IDML file causing the issue so we can try and replicate it? https://www.dropbox.com/request/ugWaFbygWiVOYV569aBV Lee

Hi Roboko, RMA (roughness/metalness/ambient occlusion), the most common channel packing method, is possible using the RGB channels but not using the alpha channel. I've dug out one of our old videos that may help you out with your workflow: https://player.vimeo.com/video/205028961/ Hope this helps, Lee

Hi Liv42t, Welcome to the forums! Would you mind sharing both your PDF and the affinity document created with it so we can investigate this issue? Lee

As Bruce mentioned, your test file TSV is missing a header row with titles for the data merge such as FirstName, LastName etc etc, whilst this won't solve the issue it will certainly make managing your project easier. You can edit this in Excel/Google sheets etc. Looking across your document, your first frame at the top left has fields associated with it, but the remaining entries on each page are manually typed. They all need to be fields, you could do this manually but it would take a while, so I would advise taking a look at this small tutorial which includes an efficient method of replicating frames across the document for a merge. https://affinity.serif.com/en-gb/tutorials/publisher/desktop/video/494072789/

Hi, This has previously been reported and escalated as a bug, thanks to bringing it to our attention anyway! Lee

Other than what has already been suggested I'm afraid not. You are running an old version of Affinity Designer on hardware that isn't quite up to the task you are assigning it. We can't assist with the Apple's App Store licensing issue you are having, but If you wish to test it on the latest version, a trial is available from our store. https://affinity.serif.com/en-gb/designer/ (bottom of the page) Lee

It might be worth creating custom Assets from your logo versions to avoid the issues you are having. As Walt suggests, linking the original document isn't the best approach. This quick video below shows the workflow for creating your own custom assets.

Hi Chasm, To create a coloured background on Affinity Publisher, Select the master page (1), create a rectangle (2) coloured and scaled to cover the page (3), lock the background layer (4). This will now apply to all created pages using this background colour, to add additional pages with different background colours, create new master pages and repeat the steps listed above. To view and alter the Colour Chooser, double click the selected colour (A) and enter the hex code (B) If you hold 'i' and drag your cursor around your screen you will see the selection update on the colour chooser. (this will work whether the colour chooser is in view or not). Hope this helps, Lee

This post by forum user thomaso may help you achieve what you are looking for:

I've had a look at the project, there are around 350 layers on this with almost all of the layers containing all of the FX enabled. I would have to say that this is more of an efficiency issue rather than an application issue because at the moment I feel you are pushing your GPU's ram to it's limits and most likely over them. It's especially important to be efficient with slightly older hardware. The crash file doesn't really give us a clear indication of where the problem lies other than it was unable to draw a shape. I would advise rasterising and flattening layers you have committed, Splitting the second artboard to a separate file will help a lot too. Remember that file size of a vector document is no real indication of complexity or the system load required. On an additional note, I would advise updating as you are running Designer 1.8.4. Lee

Would you be willing to share your file so we can look into what might be causing the issues for you? https://www.dropbox.com/request/HJKo0n75qzYdccBoZjXf

Hi RetroDesire, which application are you using to work on this? If you have it Designer is ideal. There are probably a million ways to achieve this look in designer, but personally I would create the entire near side of the stairs using the pen tool and fill it with a gradient that's not quite aligned with the stairs from bottom right to top left, then add a darker outline to the shape. For the steps themselves I'd probably do one of the vertical faces and one horizontal face in the same way as above. With both selected you can use ctrl-j to duplicate the steps and then drag them roughly into position then hit ctrl-j a few more times and it will duplicate again and again using the same offset until you have a wonky set of stairs that you can just use the node tool to pull into place. (if you really want it tidy you can use the snapping tools to ensure each step is touching perfectly. If you want to recreate it almost exactly, you can place this image on top of all other layers and reduce it's opacity to give you a guide to work from. Hope this helps! Lee

As the background texture in your image is just a bitmap image not a vector, this can be placed directly rather than embedded as an afdesign document. If you double click the background texture it will open up in a new tab, change to design persona and copy the background item using ctrl-c, flick back to your original publisher file in publisher persona and paste the item, then remove the embedded .afdesign document. Do this for both of them and export as normal, then right click to rasterise them both (they are already raster images) and it should resolve the export issue. Alternatively if you have the image as a file, you can just place it in your document manually instead of using the embedded afdesign at all.

Thanks for that. If you export the document as a PDF using the preset "PDF Flatten", this resolves your issue. Hope this helps, Lee