Jump to content
You must now use your email address to sign in [click for more info] ×


  • Posts

  • Joined

Posts posted by NathanC

  1. Hi @Secret Goldfish,

    On 12/3/2023 at 1:44 AM, Secret Goldfish said:

    When I draw with a vector brush in Designer, the chosen brush will still be used for each new stroke √

    .....but if I leave the vector brush to use another tool (ie direct selection/pen tool) and then go back to the vector brush it acts inconsistently and sometimes remembers the last brush in the category used and sometimes does NOT remember the last brush used ....and instead just appears to choose (randomly) another brush in the same category. X

    After quite some trial and error of switching between every tool in my toolbar combined with drawing and altering different objects I can't re-produce a problem with this, for the entirety of the app/document session my original brush selection was always maintained whenever I switched back to the tool, I've tried a few different categories and the brush selection remained consistent. Could you try and possibly capture this issue on a screen recording?

    On 12/3/2023 at 1:44 AM, Secret Goldfish said:

    hen I draw with a vector brush and do not use the pressure controller (turned off), the pressure attributes inside the brush properties in the chosen brush (ie size/opacity) get turned off in each individual stroke made ........and then have to be turned on manually for each stroke before a custom pressure profile can have any effect

    The brush properties should probably remain unchanged (even with the controller turned off) and just the pressure profile flattened instead when choosing 'none' in the pressure controller.

    I'm not sure I follow with this one or at minimum I can't replicate this. I created a new solid vector brush in a new category with a 75% size variance and 50% opacity variance, I select that vector brush with my controller set to 'Pressure' along the context toolbar the size/opacity adjusts accordingly with the pressure applied in line with the graph of my chosen profile. If I change the context toolbar controller to 'None' the brush stops responding to pressure, if I then change this back to 'Pressure' it then applies the same opacity/size variances originally set, the action of changing my controller has in no way changed my variances on my custom brush.

    Could you possibly provide a recording/screenshots demonstrating this issue as well?

    Screen record FAQ:

    Many thanks

  2. Hi @markphoto,

    I'm not able to replicate a problem with this with 2.3's print dialog. If you want to try using 2.3 again could you remove your existing apps from your Mac and then download and install using the .DMG files rather than use the in-app updater and then confirm if it prompts the print dialog?

  3. Welcome to the forums @fcs_77,

    SVGS generated in matplotlib failing to import into the Affinity apps correctly is a known issue that has been previously logged with the developers, so i'll bump the existing issue with your report.

    Was your second SVG file exported from affinity, originally created in Affinity? The text appears to be comprised of text layers that are all strangely fragmented apart which appears to be the problem. For example 'capacity' at the bottom of the graph is split into two separate text frames 'CAPAC' and 'ITY' and they overlap with one another dependant on the font used/substituted. I noticed this as I didn't originally have Montserrat installed so the fonts were subbed with Arial so the issue wasn't visible on the SVG when viewed in a Web Browser or the App. However, as soon as I installed the Montserrat font (A slightly different version to your embedded 'MontserratRoman') the issue became visible when using the standard Regular variant, but the Thin variant showed the text as expected.

    To avoid all these formatting issues it might make more sense prior to exporting out to SVG to re-write graph labels as singular art text/text frame objects, that way the bottom and left text labels won't end up overlapping if it gets substituted for another when opened across different devices/apps.

  4. Welcome to the forums @Ryansamul,

    Have you tried exporting to a different location or directory on your device, for example if you're exporting to a Network/External/Cloud drive, try saving to a directory which is on your local disk. If it also occurs when saving to your local disk, check that you have sufficient storage space available for the exported file.

    If it's still prompting the error, could you provide a copy of the affinity file you're attempting to export along with a screenshot of your PSD export settings? I've provided a private upload link below if you do not wish to share it Publicly.


  5. 9 hours ago, evtonic3 said:

    My raster brushes disappeared on ipad

    9 hours ago, evtonic3 said:

    How can a new install not include the default brushes?

    This does unfortunately sound like your local brushes file has corrupted if the default brushes are not available, on iPad it can be reset to default by doing the following:

    1. Close all Affinity apps
    2. Open Photo/designer 2 and quickly double tap on the screen during loading
    3. A 'Clear user data' menu will prompt, tick 'Reset Brushes' and then press 'Reset'

    The brushes should now have been restored to default and you can re-import/download brush packs from your Account

  6. 3 minutes ago, der_gent said:

    When disconnecting a display that has open windows on it from a mac device, the window will automatically be transferred to the remaining display and resizes there.

    But this is not, what i consider as a bug.

    It sounds like you may be running into this known bug that's currently logged with the developers, the FAQ also contains a workaround in the event this bug is encountered when changing active displays.


  7. Welcome to the forums @will_barbo,

    How are you applying the perspective function to the art text object? If you're in Photo 2 and use the Perspective tool, this automatically rasterises the art text as it's a destructive Pixel filter. If you opt to use the non-destructive Perspective Live filter, this won't immediately rasterise your art text layer as it's a live filter, but if you export out to a vector format such as PDF or SVG, it will automatically rasterise the text on export since it has a filter applied, you can check this by re-importing the PDF file back in to the app or using a PDF viewer to inspect the object, it will be a raster image type layer.

    If you wanted to apply a perspective warp to art text you would need to use the Warp Group > Perspective function available in Designer 2, on export this will convert the art text to curves, losing text editability but will preserve it's vector properties.

    Vector warp info: https://affinity.help/designer2/English.lproj/pages/ObjectControl/warp.html



  8. Thanks for sending those over, I'm getting a pretty generic error from two and the other two of the reports fail to debug, however the scenarios that you have described when the app runs into a crash do point towards a GPU driver/rendering issue.

    As you've already ensured that your drivers are up to date and Hardware Acceleration is disabled within the app, could you try doing a clean install of your drivers by using a tool such as DDU (linked below) to wipe your existing GPU drivers, reboot and then re-install the latest available, before rebooting and trying a stitch again in Photo 2?


  9. Hi @zgwangbo,

    I've since tested this on a M1 Macbook Air running Ventura 13.5.1 and using the trackpad the dialog always prompts as expected in 2.3, if possible could you try using a mouse for comparison just to confirm it's nothing odd to do with the trackpad/trackpad settings?

    Failing that, could you try resetting your Snapping presets in one of the apps by doing the following:

    1. Close all affinity apps
    2. Hold down CTRL and launch the app while still holding CTRL
    3. A 'Clear user data' menu will appear, in addition to the already ticked boxes tick 'Reset snapping presets'
    4. Press 'Clear' and the app will now launch, try opening the snapping menu again

    If both of the above don't work I can only think it's a problem specific to Catalina, so I'll see if I can get this tested on a Mac running Catalina.


  10. Willkommen im Forum @Jürgen Kemmerer

    Beziehen Sie sich auf die Option "Nach Name sortieren" im Kontextmenü der Asset-Unterkategorie? Wenn ja, funktioniert sie bei mir wie erwartet.

    Ich habe eine neue Anlagenunterkategorie erstellt und 4 Objekte zur Anlagenkategorie hinzugefügt. Dann habe ich diese Assets umbenannt: '1', 'A', 'B', 'C' und sie dann per Drag & Drop verschoben, um ihre Position zu ändern. Mit der Funktion 'Nach Namen sortieren' im Kontextmenü habe ich sie dann wieder in die numerische und alphabetische Reihenfolge gebracht.

    Wenn dies bei Ihnen nicht funktioniert, könnten Sie mir eine exportierte .afassets-Datei zur Verfügung stellen, in der dieses Problem auftritt, sowie eine Bildschirmaufnahme?

    Bildschirmaufnahme FAQ:

    Herzlichen Dank!

  11. Welcome to the forums @Buglagur,

    There's a known bug with the Canvas rotation past 90° or lower than -90° causes the grid to disappear/fail to redraw, I can see in your screen recording that your canvas has been rotated at some stage so it's possible that you're encountering this bug. If you were to reset your rotation to 0° in the Navigator panel (Double tap the value) and then zoom into the canvas to force a redraw, does the grid then re-appear?

  12. Hi @zgwangbo,

    I've also tested this in both 2.2.1 and 2.3 and I was able to access the snapping preset context menu without any issues, I also didn't have have any presets prior to updating, this was on an M1 running Sonoma 14.1.1.

    What MacOS version are you using, and not that it should matter but are you using a standard mouse or a MacBook trackpad?

  13. 1 minute ago, MikeTO said:

    Hi Nathan. I replicated it on my first attempt today with 2.3. My steps were: I filled a frame with filler text and expanded it, drew a rectangle and dragged it over the frame, text wrapped it using Tight, pinned in as Floated, and then copied and pasted the frame.

    Ah yes my mistake as I had not been following the exact same steps after updating giving the impression it was fixed. I was drawing the rectangle immediately over the text frame without transforming it, and then subsequently wrapping, floating and then copy/pasting the frame which wasn't triggering the bug. I'll get this logged, thanks.


  • 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.