-
Posts
4,437 -
Joined
Posts posted by NathanC
-
-
Hey @MC1,
This is possibly a combination of two known issues currently logged with the developers:
- Resource Manager can trigger app hangs and overall poor app performance when opened in larger resource-heavy documents. Actions such as re-linking hundreds of linked files concurrently can contribute to this by causing significant RAM and CPU spikes, resulting in the instability.
- Certain systems running the Windows 24H2 update with a Nvidia GPU can intermittently cause system-wide freezes when working in the apps, particularly when performing hardware intensive tasks. Disabling Hardware Acceleration under Edit -> Settings -> Performance and also ensuring your GPU driver has been updated to the latest studio driver can help to alleviate this.
I've updated the existing issues with your report.
-
-
Hi @roadcone,
Thanks for the updated doc(s) and clarification, I've inspected the PDF in Acrobat using Output preview and unchecked Process Black so only CMY separations are visible. The only elements within the PDF that aren't K-only are the Effect around each image, as well as the full colour images.
The Image edges can be updated to K only by updating the Bevel/Emboss effect 'Shadow' to K100 only black for each instance of the FX. You'll need to correct this twice, once for the FX on the group and the other for the FX on the Image layer.
Each image layer also has a white stroke with 1% Cyan, so this also needs setting to 0. I've attached a copy of your file with these amendments made for reference.
Since you're using the PDX/X-1a:2003 preset/standard, the content isn't exported with an embedded ICC profile, just generic 'DeviceCMYK', however the B&W images are K-only.
-
Looks like the toolbar and studio panels are hidden, I'd recommend following the steps below to perform a basic UI and defaults reset:
- Quit Photo 2
- Hold down CTRL and launch Photo 2 while continuing to hold CTRL
- A 'Clear user data' menu will eventually prompt, press 'Clear' at the bottom right hand corner
The app should now launch with these UI elements restored.
-
Welcome to the forums @Marcos Castro,
Issue #1 (AFD-2727) described in the linked post has been fixed and was related to Portrait images failing to repeat as brushes. However, issue #3 relating to brush repeats getting 'squashed' dependant on the aspect ratio is still logged and outstanding with the developers, based on the screenshots provided I believe you may be partially encountering this issue. However, textured brushes are designed so that they will deform the image in order to fit the curve, so this may also partially be down to this expected behaviour.
I did create a similar test brush based on a stroke with a circular end but didn't encounter the same crumpled/squished brush behaviour shown in your second screenshot, possibly adjusting the head/tail offset in the brush editor might help alleviate this if there is empty space available on each side.
-
Hi @Jorge Martins welcome to the forums,
This is more related to the 'Paste Style' function itself rather than the shortcut to invoke it.
The Flattening of these objects on PDF output is the result of the transformed gradients that have been added to the objects using 'Paste Style'. When the gradient has been pasted onto the objects using this function, the gradient has automatically re-applied itself to fit the object's shape, if you select one of these objects and switch to the gradient tool, you'll see that it has a dotted line (Correction path) to indicate this gradient transformation.
These type of 'Skewed' gradients with a correction path are considered an unsupported property by the PDF exporter, and are flattened to pixels on export. This was historically raised in a bug report, but was determined as by design by Dev/QA, and was raised as a Feature request below.
As a workaround, you can set the 'Rasterise' Setting to 'nothing' and it will preserve the gradients as close as possible to the source without flattening it.
-
Hi @evtonic3,
This is a known issue on iPad currently logged with the developers, I've bumped the issue with your report.
-
Hi @nielsh,
The double/offset line you're observing is a result of the non-pixel aligned creation of the artboard. Along the toolbar next to the Snapping menu (Magnet icon), turn on 'Force Pixel Alignment' and then draw out at an artboard again, and you should observe that the artboard is created on whole pixel values with no double/offset line.
Info: https://affinity.help/designer2/English.lproj/pages/DesignAids/pixelAlign.html
-
Hi @Iztok,
Have you read the advice from the forums members above? You have snapping set to a Candidate List of 6. From your recording, the object above is not a snapping candidate so snapping won't currently function with this object.
If you hover your cursor over the object you'd like to snap to for 1~ second, it will be designated as a snapping candidate, and the purple outline will appear, you can then snap to this object as it's included in the candidate list. Alternatively, in the Snapping menu set the 'Candidates' dropdown to 'All Layers' will remove the candidate limitation, and enable you to snap to all objects within the document.
https://affinity.help/designer2/English.lproj/pages/DesignAids/snapping.html
-
Hi @roadcone,
Since the text is all K100 as expected, and provided that no colour space or profile changes are being modified in the PDF export settings, I'm presuming the problem is the images. You mentioned that you replaced the Image resources with equivalent Images with a Greyscale profile embedded, but in the file they all appear to be sRGB, so I'm wondering if that might be part of the issue? To confirm, is the intention for the B&W Images to be CMYK with 'K' only black?
Thanks
-
Welcome to the forums @T-bone Kristiansen,
I can confirm the issue relates to the presence of clipping paths 1 and 3 within the file's metadata. I removed both of these in PS and re-saved as JPEG, and the file imported into Photo 2 as expected, with the Path 2 present. I can't see anything wrong with these paths, and they import into Photo V1 as expected, so this bug is a regression which I'll get logged with the developers.
Unfortunately, there isn't a configurable setting to stop the paths from importing. Since the batch job is also tripping up, it looks like using the 'New Stack' function may be the best workaround until the issue is fixed if the metadata can't be externally stripped prior to importing into Photo 2.
-
Bienvenue sur les forums @GD91
Pour confirmer, rencontrez-vous une erreur « Échec de l'enregistrement » ? Cette erreur affecte-t-elle uniquement le fichier sur lequel vous travaillez ou tous les fichiers ?
Je vous recommande de suivre les instructions de la FAQ pour vous assurer que l'accès contrôlé aux dossiers Windows ou un logiciel antivirus tiers ne bloque pas l'enregistrement de l'application.
Je vous recommande également d'enregistrer votre fichier dans un autre emplacement, local sur votre appareil et non synchronisé avec un service de stockage cloud.
Enfin, vous pouvez essayer de désactiver « Enregistrer l'historique avec le document » si l'erreur est apparue peu de temps après, car elle pourrait être liée à un problème au sein du fichier.
-
Hi @Gekkographics,
It's quite unusual that it only affects two pages, I can't spot anything immediately wrong that's causing this based on your screenshots. Could you possibly share a copy of the .afpub, the .PDF for comparison and confirm your selected PDF export settings? I've provided a private upload link below.
https://www.dropbox.com/request/EiboTkbAJxcHNLENd2NO
Thanks!
-
Hi @davidgall,
Since the child layers are curve objects, you could try moving them out of their nested position in the layers panel (below the parent) -> Select all four curves -> Switch to the Node tool -> Highlight All Nodes -> Move and snap -> Nest the curves again.
-
Hi @Gorgette5483,
The functionality to change the Tool handle sizes is available in the Desktop Apps (Under Settings -> Tools), but unfortunately, it's not possible to change this on the iPad apps at this time.
These are referred to as Node 'Control Handles' or 'Bezier Handles'. 🙂
-
Hi @Philip_J,
I can semi-consistently reproduce this, and it does appear to be caused by the OS shortcut to change between input language taking priority. For me, double-clicking puts the app back in focus, and I can then interact with the UI.
In Windows Settings, go to Time & Language -> Typing -> Advanced Keyboard Settings, select 'Input Language hot keys' and change the 'Between Input Languages' to a different key sequence (Or just un-assign it) and this should prevent the issue.
-
Hi @Yokoso,
I'd recommend going to the App Settings -> Performance and disable ‘Hardware Acceleration’ at the very bottom, and then close the interface and restart when prompted to. If you then re-open the document and export again to PDF, you should hopefully find that the embedded images no longer appear with these artefacts.
There is a known bug logged internally related to raster corruption on Apple Silicon (M1/M2 etc.) based Macs and the JPEG compression PDF export setting when Hardware Acceleration is enabled, but it looks like this can also trigger on downsampled images without the setting enabled.
-
Hi @Stadicus,
Ah, I understand. An alternate workaround is to convert the embedded PSD files to a raster format such as TIFF and replace them within the document, as this format is unaffected by the bug.
This is a regression over 2.5.7, so if you uninstall and roll back to 2.5.7 this issue shouldn't occur with PSDs or Afphoto files. However, it's worth noting you won't be able to open any Affinity documents created or saved in a later version.
-
Hi @crazzzybagel welcome to the forums,
I've sourced that same mockup design online, one of the main problems is that there isn't an equivalent 'Cylinder' warp mode in Afphoto which is used in the file, so this isn't mapped correctly. If you disable 'Import PSD smart objects where possible', you'll get a reproduction of the same file, but the smart object mug label won't be retained, it gets flattened to a pixel layer with the warp baked in.
As PaulEC's mentioned, manual adjustments will be required here. In the attached file I've tried to more closely match the original file by re-ordering a few layers, masking them, and also using the 'Mesh warp' adjustment to warp around the mug shape.
-
Hi @Alex_P apologies for the late response,
If you're still encountering this error in the latest update, I'd recommend checking Controlled Folder Access in the Windows Security settings, as well as allowing the Affinity apps through any third-party antivirus software, as per the FAQ below.
-
Hi @BBG3,
This is a known issue currently logged with the developers, creating masks using certain methods (such as masking based on a pixel selection) will create the mask based on the bounds of all artboards instead of the active artboard, I've bumped the issue with your report.
There is a workaround discussed in the thread below, as using an empty mask layer prevents this.
-
Hi @Daniel Gibert,
I've logged this with the development team for further review. 🙂
-
Hi @Stadicus have you tried the workaround referenced in my previous reply? By unchecking facing pages before exporting, this should prevent the content from offsetting in the output PDF.
On 5/23/2025 at 2:42 PM, NathanC said:as an alternative option I'd recommend creating a duplicate of your .afpub file -> Open the Copy -> Document Setup -> Uncheck 'Facing pages' -> Export. This will create a single-page PDF without the offset content.
----
On 5/23/2025 at 4:28 PM, matisso said:@NathanC, is there somewhere a list of all known issues that have been logged? It would be pretty helpful to have that readily available when running into an obstacle
Nothing publicly available/visible I'm afraid.
-
Visual bug in Affinity Photo 2: some underscores disappearing in filenames when running a batch job
in V2 Bugs found on Windows
Posted
Hi @immewnity,
I can confirm I've replicated and logged this with the developers, thanks for your report.