NathanC

A similar query to this has been raised a while back in the thread linked below, I believe this is because the iPad also uses a Retina display so the same logic applies that MattP has outlined in the thread when trying to match your document to 'Actual size'.

Welcome to the forums @iamasmith, If I have interpreted correctly - there's not that i'm aware of using isolation mode since the function only works on a per group/object basis, so if I had my top container layer with objects hidden and a sub group nested into that container layer, I could use the the Alt/Opt + click to go into isolation mode on that group to reveal it again, but I couldn't then 'Expand' on my isolation selection to also include/reveal that top hidden layer.

Hi @Seneca, Many thanks for the sample file and recording, I've now reproduced the problem and logged it with the developers.

Hi @Ruyton, Could we take a look at the FITS files you're using for the stack? We can then look into what options may be available. Since the files are likely to be too large to upload to the forums I've included a private upload link below. https://www.dropbox.com/request/ZacuMSd7FHR9bmIRL4cP Many thanks

In the Snapping settings menu, disable 'Show Snapping Candidates' or change the Candidates dropdown to an option which isn't 'Candidate list'. https://affinity.help/designer2ipad/English.lproj/pages/DesignAids/snapping.html What three modes are you referring to? If it's the node snapping options (The magnet icon on the left hand side of the context toolbar) this only ever has 'Snap to Geometry' enabled by default for me, I can turn on the other node snapping modes which will persist as on for the remainder of my app session If I create new documents, and when I restart the app it just defaults to 'Snap to Geometry' again. It doesn't look like the default can be changed currently.

Hi @Villebon, Develop persona Gradient overlay can't be erased/subtracted from as it stands, the overlay erase tool will only work on brush overlays. This will be to preserve the editability of the Gradient overlay, allowing you to adjust the gradient's position later on. If you switch over to the Photo persona this will allow more finite control over gradients via the use of gradient mask layers in conjunction with adjustments.

Hi @Gianni Becattini, Thanks for following up and clarifying on my queries. I've just made up a few test documents for this scenario. I opened the same image in Photo and applied the same adjustments used in your screenshot, with the only difference being the position of those adjustments in the layer stack, one file had them above the pixel layer, and the second file had the adjustments nested into the image as child layers. After saving them out both .afphoto files had a file size of 268MB. I then created a new afpub doc and placed the first .afphoto file with the adjustments above it in the stack as a linked resource, I then exported to PDF using the (For export) preset. I then replaced that .afphoto file with my second one which had the adjustments nested inside the pixel layer and repeated the export using the same (for export) preset After comparing the file sizes of the two PDF's they were identical at 235MB, even down to the KB. It could be that there are other variables here not taken into account in my test documents, so if you could upload an .afphoto file and .afpub file where you're encountered this problem I can then confirm if the problem can be reproduced, and in addition if you could send me a screenshot of your PDF export settings for consistency that would be great. Thanks!

Hi @Fcunhaster, After placing the .afdesign file into your publisher doc, with the resource still selected change the 'Page Box' setting to 'Bleedbox' along the context toolbar. 🙂 https://affinity.help/publisher2/English.lproj/pages/Media/placeImages.html

Hi @BornInPastCentury, This is an bug that has been previously logged with the developers with blend options on adjustments getting ignored when a mask is present, I'll update the existing issue to reflect that it still affects the latest version and bump it with your report.

Hi @Patrick Bell, Assuming you're on Windows since you've referred to an .EXE file it's likely you have installed Photo via the default MSIX installer, this is a sandboxed app and requires linking the third party app to the 'Aflaunch.exe' execution alias file found in the forum post below to get Lightroom to launch the app. Although, I'd recommend removing the MSIX version of the app and instead installing the .EXE version (also referred to as the .MSI installer) of the app, this version isn't sandboxed and allows you to designate a custom installation folder, which third party apps such as Lightroom can then be linked directly to the app's .EXE file without the need of the aflaunch.exe file, you can find instructions for downloading the .EXE version linked below

Hi @Gianni Becattini, Are these adjustment layers nested/clipped onto the images within the .afpub document, or are they in an .afphoto file that has been placed as a resource in your .afpub file? I'm guessing that you're referring to the images being nested/clipped onto the image file when you say they're 'under it'? As otherwise the adjustment layers would have no affect on the image if they were lower in the layer stack/hierarchy than the actual pixel image. Without looking at your source .afpub document and images/afphoto files it's difficult to say exactly what's happening or if there's a bug. Could you possibly send me a copy of your .afpub file, along with a few of the .afphoto resources so we can look into this further? It doesn't have to be the entire file, just a cut down version or a singular page where we can observe what's happening with the file size when exporting to PDF dependant on the adjustment layer position. I've included a private upload link below. https://www.dropbox.com/request/kxNTWTPqRvRbxtLwZBbj Many thanks 🙂

If you follow my previous instructions this should leave you with a heart shape which has been split into two separate left and right half curves, at which point you can freely transform them separately to pull them apart or rotate and position them as needed.

Thanks for sending over the .ZIP, I can also confirm that your .ZIP file is corrupted. 7-ZIP reports numerous Data and CRC failed errors, and what it is able to extract is damaged and unusable. As this brush pack isn't provided by us but by a third party and the issue is with the .ZIP file completely external to the app I can only really suggest getting in contact with the creator and seeing if they're able to provide you with an alternative download link for the brush pack if the existing link only downloads a corrupted version.

What happens when you try and extract the file using 7-Zip, does it display a different error message that you can show us? If you send a copy of the .zip file to the private upload link below I can also confirm if the problem is with the file contents or an issue specific to your device. https://www.dropbox.com/request/IFsQW0T01GW0QUExRuot

Hi @tzvi20, I can see you've already been discussing this in the resources thread below: You appear to be getting a '0x80004005 Unspecified error' during the unzipping process when using the default Windows explorer compression function. Sources online indicate that this is a problem that can occur with the file explorer tool rather than it be a problem with any specific .ZIP file's contents. The most straightforward solution is to use a third party archiver such as WinRAR or 7-ZIP to zip/unzip files instead of the Windows explorer default, so it would be worth trying either of these tools to extract the file with instead. https://www.win-rar.com/start.html?&L=0 https://www.7-zip.org/

Welcome to the forums @FalX, Many thanks for providing detailed steps, I've now replicated this issue and it has now been logged with the developers.

Welcome to the forums @Josephine ray, The heart shape in your image appears to have already been cut in half, unless you're using it as a reference image? You could do this from scratch by following something like the below: Draw out a heart shape with the quick shape tool. Select the Pen tool and draw the line over the top of the heart for the cut and increase the stroke width as required Edit menu > Expand stroke to create a closed curve from the line Select the Move tool and highlight both layers in the layers panel Use the Boolean > Subtract function along the context toolbar to subtract the line from the heart shape https://affinity.help/designer2ipad/English.lproj/pages/ObjectControl/join.html https://affinity.help/designer2ipad/English.lproj/pages/CurvesShapes/expandStroke.html

Hi @soloabner, This is a known issue currently logged with the Devs, the live perspective filter when used on artboards can cause artefacts to appear in Designer. I'll bump the existing issue with your report.

Hi @Fantomas.CZ, Not anything new to share sadly, I'm now watching the improvement internally so if there's any change I'll post back on this thread.

Hi @eobet, This is a bug with expand stroke on strokes with an arrowhead set, the issue has been logged previously so i'll bump it with your report. 🙂

Hi @eobet, Looks like the curve is open on the right hand side where the two nodes are (turn off the fill on the curve and you'll see this). Use the 'Close Curve' function on the node tool with one of the nodes selected and then try using the Corner tool again. round-corner-now-works.afdesign

Hallo @Tiberius Kraemer Wie wir sehen, haben Sie uns auch eine E-Mail zu Ihrer Anfrage geschickt, die wir nun beantwortet haben.

Welcome to the forums @sbsdk, If you re-enter your Affinity ID details you originally registered the trial against and then press 'Activate' on the login screen it will then continue the existing trial period on your account. 🙂

Hi @MikeTO, I've now replicated and logged this with the devs. 🙂

Hi @PeterB., Thanks for sending over the file, it is very likely to be related to the now fixed bug referenced earlier if the document was being worked on in an earlier app version, it just wouldn't have retrospectively applied to resources already affected by the issue prior to the update, though replacing the existing resource evidently refreshes and corrects this.