Jump to content

NathanC

Staff
  • Posts

    4,437
  • Joined

Posts posted by NathanC

  1. Hi @MartinHH

    Since gradients applied to mask and pixel layers are destructive, you could use a quick shape as the mask instead which is non-destructive:

    1. Create a rectangle quick shape to the size of the canvas bounds
    2. Select the Gradient Tool and add a black to white gradient on the shape
    3. Edit either of the gradient stops and change the opacity to 0%
    4. Offer the shape to the Gaussian Blur's thumbnail to mask it
    5. You should now be able to non-destructively edit the Gradient stops to adjust it's position as required.

     

  2. Hi @WaveF,

    I can confirm i'm able to re-produce this on MacOS by following your steps, so I'll get this logged with the developers.

    51 minutes ago, WaveF said:

    ( It has to be an Image object in this case. Btw, there's a blue outline showing outside the transform box when using Pixel object to do so. Is this by design? )

    Yes, this outline indicates the original bounds of the masked object.

  3. Merci, je ne vois aucun problème spécifique à ce fichier. Je peux interagir et modifier librement les calques de pixels sans pics de mémoire, et l'utilisation est normale tout au long de la session.

    L'option « Limite d’annulation » contrôle la durée de l'historique accessible pendant cette session d'application. 1024 est la valeur par défaut, et nous déconseillons généralement de la modifier, car son impact est généralement négligeable.

  4. Bonjour @reivax500,

    Affinity commence à paginer vers un fichier temporaire « personabackstore.dat » lorsque la mémoire RAM disponible est insuffisante pour stocker des objets tels que des images. Ce fichier temporaire devrait être automatiquement vidé au redémarrage de l'application, libérant ainsi de l'espace.

    En plus de désactiver l'accélération matérielle comme mentionné par Carl, je recommande d'augmenter la limite d'utilisation de la RAM au même niveau que la mémoire disponible de votre système et de minimiser l'exécution des applications en arrière-plan afin de libérer des ressources lorsque vous travaillez dans Affinity.

    Le problème pourrait également être lié au fichier sur lequel vous travaillez dans Photo. Si vous pouvez partager une copie du fichier où vous rencontrez des problèmes lors des retouches, nous pourrons l'examiner.

  5. Hi @PeterFitz,

    10 hours ago, PeterFitz said:

    However, now whenever I want to do an update, I have to follow the same procedure — download the EXE and install manually. It's not a huge hassle, but it's a bit more trouble than the auto-update method I get with Photo and Publisher, which I installed at a later date.

    Is it possible to change Designer's update method to match the auto-update like the other two apps?

    It sounds like you have a used a mixture of installation methods (MSIX and MSI/EXE) for the three apps. If Designer is re-directing you to the 'Downloads' page when an update is available, this confirms that Designer has been installed using the MSI/EXE method, which can only be updated manually from the website. Publisher and Photo will be installed using the MSIX method, which is a more automated update process and does not require a manual download.

    I'd therefore recommend uninstalling Designer 2 via Windows Settings -> Installed apps and then downloading and installing the MSIX(x64) version from the page below, this is the first option in the download button dropdown.

    https://store.serif.com/update/windows/designer/2/

  6. Hi @Ton Ouwehand,

    Native Affinity files are not a compatible format with the Panorama feature so won't appear in File explorer, only raster based formats are supported. See the list of supported formats below:

    • JPG/JPEG/JPEGXR 
    • TIF/TIFF
    • PNG
    • GIF
    • WEBP
    • DNG
    • HEIC/HEIF - (no depth maps)
    • Supported RAW files
    • TGA
    • BMP
    • EXR
    • HDR

    This is currently logged with the Docs team to better reflect the compatible formats in the help documentation.

  7. Thanks, looks like the Curves adjustment is getting cropped on the right-hand side, exposing the original pixel content underneath. In the .afphoto file I swapped Curves for HSL and the effect was similarly cropped. However, if I clip the adjustment layer to the pixel layer underneath, the issue doesn't trigger when exporting the host .afpub to PDF.

    The presence of the second linked .afphoto file (Backcover.afphoto) also appears to be part of the problem as the issue only triggers on export when that linked resource is also present, though I'm not sure why at this stage.

    As the problem is re-producible using your file, I'll log this with the developers for further review.

  8. Welcome to the forums @WonkoTheSane,

    It's possible that they have the 'Align to nodes of selected curves' Screenshot 2025-07-09 at 08.50.19.png snapping option enabled on the Node/Pen tool context toolbar. This aligns any moving node to another node on the same or a different curve, and will show the Red/Green dimension lines to indicate the distance.

  9. Hi @blackxacto,

    This is a known issue with the Apple Photos 'Edit in' extension, it can intermittently fail to successfully round trip and save the changes in Apple Photos, I've bumped this issue with your report.

    After selecting an Image in Apple Photos, Right Click the Image -> Edit With -> Affinity Photo 2 to open the Image directly in Photo instead of using the 'Edit In' extension. This workflow should avoid the save errors.

  10. こんにちは、

    これはエクスポートプレビューウィンドウのバグです。画像サイズが大きい場合、プレビューが生成されず、ウィンドウに透明な部分だけが残ることがあります。現在、開発チームに報告しています。

    プレビューが表示されなくても、画像のエクスポートが失敗するわけではありません。コンテンツのエクスポートは可能です。

  11. Hi @Erus,

    This is a known bug currently logged with the development team, attempting to export with a custom palette to GIF or PNG will fail to complete the preview generation, and will also show an error when attempting to export. I've updated the existing issue to reflect that it's still an issue in the latest version and bumped it with your report.

  12. Hi @ianrb,

    It's likely that you're running into a known bug currently logged with the developers. Clicking anywhere within the empty space in layers panel while actively recording a macro will trigger an immediate app crash, this will hopefully be fixed soon.

    Interacting with Layers within the panel (such as renaming) shouldn't cause the crash, but I understand it's fairly easy to unintentionally click in the empty area in the panel.

×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.