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

NathanC

Staff
  • Posts

    2,522
  • Joined

Everything posted by NathanC

  1. Hallo @SusanneS @Hangman Ich konnte keinen früheren Hinweis darauf finden, dass dies ein Problem ist, aber ich habe das Problem in einem separaten Dokument repliziert, als ich Textrahmen/Tabellen, die ein angeheftetes Objekt enthalten, in eine Musterseite kopiert habe, was zum Absturz der App führte. Ich habe dies nun bei den Entwicklern protokolliert, vielen Dank, dass Sie sich der Sache angenommen haben. Beim Testen habe ich festgestellt, dass der Absturz nicht auftritt, wenn die Musterseite von allen vorhandenen Seiten gelöscht wird. ---- I wasn’t able to find any previous reference to this being an issue, but have replicated the issue on a separate document when copying pasting text frames/tables containing a pinned object on a master page causing the app crash. I’ve now logged this with the developers, many thanks for looking into this. During testing I did note that if that master page is cleared from any existing pages, the crash will not occur.
  2. This isn't expected functionality and you're correct that this is the bug that's logged with the developers, i've tagged the thread with the issue so once a fix is available in a later version the thread will be updated.
  3. Hi @poolprof, Sorry to hear that, If you do not wish to share the file publicly, I have provided a private upload link below and we'll take a look at your file. https://www.dropbox.com/request/iweym5MHb9Hnp34c0Q2q
  4. Hey @SpotColour, I've just checked and confirmed this one has been logged previously so i've now bumped the existing issue. Many thanks for the additional info @Hangman @Return 🙂
  5. If you want to roll back to 2.0.4 on Mac, remove the 2.1 app first by drag and dropping it over to the bin from applications and then clear it, and then move the 2.0.4 DMG file onto your SSD and then double click to open it, and then drag and drop the Afphoto Icon over the 'Applications' folder as prompted to on screen to install 2.0.4. You should then be able to launch it from Applications.
  6. Hi @Nordseher, This error is typically caused by the firewall blocking local traffic, I would first suggest checking your firewall settings to make sure local traffic is not getting blocked to ensure that the apps can communicate with one-another. It's also possible for this error to occur when you have another affinity app open in an unresponsive/frozen state and then try opening another, this will require that the app be force closed/allow it to finish what it's doing before you can open another app. I've linked the relevant FAQ below for reference.
  7. Hey all, It looks like this is caused by changing any of the advanced export settings prior to the batch export to PNG, this causes the Matte to default to white which cannot then be changed back to transparent unless you use any of the default export presets which will correctly use the transparent matte. This is the same in the standard export dialog. It doesn't appear to affect MacOS even when changing the advanced settings. I'll be updating the logged issue with the developers to reflect this behaviour and will bump it with your reports. As an alternative workaround, after defining your PNG export settings within the advanced settings area, click on the matte and change the dropdown to 'Swatches' and then click on the transparent fill option shown in the screenshot below, visually the matte will still show as white, but when you export it should export with a transparent background.
  8. Sorry it's taken me some time to come back to this, i've just checked up on the logged issue and it's been determined as by design, Artistic text bounding boxes are only intended to cover visible text and will not include any non-visible characters such as spaces/line breaks. For example, the shape of the bounding box will change to cover descenders whereas a standard text frame's bounding box will not.
  9. Hi @UweN, I've been able to successfully replicate this on Windows and it has now been logged with the developers, many thanks.
  10. Hi @Fernando Ribeiro, I've replicated this issue and it has now been logged with the developers, thanks for providing detail. 🙂
  11. Hi @dantaylr, Unlike regular groups, constraints groups will clip content off that exceeds the area of the bounding box which is defined by the nodes. As such, strokes aligned to the outside/centre exceed the bounding box, and causes the area to get clipped. This is logged with the developers to be improved so that objects inside a constraints group can exceed the bounding box, similar to a standard group. I've bumped the existing Improvement with your report.
  12. Hi @pipkato, As far as I can tell nothing stands out to me as incorrect about your install process, I've just followed the same on V1 with Nik Collection 5 and the plugins are launching from Photo as expected. Without launching the Plugins from Photo, have you checked that you can run the Nik collection apps as standalone applications? If they're also failing to launch as standalone apps, have you checked in the console app for any crash reports relevant to the apps?
  13. Hi @ch22, Thanks for following up, i've since been able to consistently re-produce the crash and found that it's currently logged with the developers (Affects mac only), so it's nothing specific to your device/environment. The bug happens when you have the layers in a collapsed state with a clipped/mask layer and then drag it and hover over the parent stack without letting go of your mouse, it causes an app crash. The reason I couldn't produce it before was because I wasn't hovering it, I was just instantly drag and dropping the clipped/mask layer over to the parent layer without leaving any time to hover as shown in your recording. I've bumped the existing issue with your report. The easiest way to workaround this is to instantly drag/drop the layer, or have the layer expanded as you've found.
  14. Hey @Alex_M, This looks like an incredibly similar banding issue to what you've reported previously in the thread below, which as mentioned by Lee is currently logged with the developers. how was the image exported to JPEGXL originally? Was this via XNView or a different encoder? I'll add any additional details to the existing report.
  15. Hi @Clau_S, I've replicated this issue across the three apps on Windows and logged it with the developers.
  16. Hi @romeosoroka, Which keyboard shortcuts are you trying to use shift as an additional modifier key with? This is allowed in certain sections of keyboard shortcuts but not others. For example, Shift cannot be assigned as a part of a keyboard shortcut in the 'Tools' shortcut section because it would conflict with the 'Use shift modifier to cycle tools' setting within the Tools preferences.
  17. Hey all, I've logged this with the Documentation team for investigation, After changing my Regional/Language setting to Italian, clearing my browser cache/history and then restarting, both the Language option and the dropdown menu still show English (UK).
  18. I'm on Windows 10 currently so the apps and features settings looks slightly different to your screenshot, but the easiest way I've found to distinguish between the MSI and the MSIX apps is if it offers me the option to 'Move' and 'Advanced options', that is the MSIX (Or Microsoft Store) app, if it just says 'Modify' and gives me no further options other than uninstall that is the MSI/EXE app. If you click on the Ellipsis (...) see what options you're offered.
  19. Uninstalling the apps does not remove locally stored assets, document presets etc. as they are stored in a different local folder dependant on if it's the .MSIX or .MSI app (Info on locations in FAQ below). So if you uninstalled one, you could always copy over the files from the other directory if you noticed certain things were missing.
  20. Hi @max张 welcome to the forums, So we can investigate this further, could you provide us with a copy of the original .afpub document prior to export along with your exported PDF for comparison so that we can investigate further? I can provide a private upload link if needed Many thanks in advance
  21. Hi @krbo, This issue is currently logged with the developers, so I've bumped the existing issue with your report. 🙂
  22. I've just noticed that this tapered brush effect occurs when force pressure is enabled in conjunction with Shift + clicking. In light mode MacOS there's a UI bug logged with the developers where the 'Force brush pressure' button along the context toolbar does not appear to be visually pressed in when it's enabled. Try toggling this button and try again.
  23. Fantastic Guide @DM1, though as Walt mentioned I have moved the thread over to Tutorials as it fits better here 🙂
  24. Hi @RedSnapper, Not that it should make any significant difference for selection refinement, but based on your screenshot you're editing a non-destructive RAW layer, if you were to right click> rasterise this layer first and then create and refine your selection and apply, does this make any difference? It might also help if you could provide the original image along with a screen recording that demonstrates the issue. Many thanks 🙂
  25. Hi @Artworkzzz, This might be because you have a dynamics controller enabled on your current brush (might be Velocity on size jitter for example), in the brush editor (double click your current brush in the brushes panel) and then switch over to the 'Dynamics' tab and ensure the sliders are all set to none/0%. https://affinity.help/photo2/English.lproj/pages/Painting/pixel_modify.html
×
×
  • 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.