Jump to content


  • Posts

  • Joined

Everything posted by MEB

  1. Hi @Tim vanH, Welcome to Affinity Forums Do you mind sharing the 3 exposures + the output you are getting for us to check/test please? I can provide an upload link if you wish to keep the files private - just let me know.
  2. Hi @sSlvio Go to menu Apple > About This Mac. Take a screenshot of that dialog and post here. If it has a serial number left it out or paint with black over it to hide it.
  3. Hi @sSlvio, Welcome to Affinity Forums Are you running macOS Ventura on Apple M1 (or M2) based systems? There's a known issue where exporting from these systems will crash the application when running the latest Ventura Beta 4 (22A5311f).
  4. Thanks for all feedback everyone. Seems opening PDF & Ai files affects both Intel and Apple Silicon based systems, whereas the general Export issues affects Apple Silicon based system only. Is anyone experiencing crashes in Ventura Beta 4 on Intel based machines when exporting? Thanks. This is being logged to be looked at.
  5. Hi @AffinityMakesMeSmile, Yes, this is a known bug in Ventura. See this thread. Thanks for your feedback.
  6. Hi @Mr TTT, Welcome to Affinity Forums Currently there's no Blend Tool in Affinity Designer. There's quite a few threads (like this or this one) requesting and discussing ways to get a similar look but these workarounds don't offer the same granularity/control as a true Blend Tool would. You may want to add your voice to one of those threads requesting this feature. Thanks for your feedback.
  7. Hi @Ertagon, Welcome to Affinity Forums If you wish to select and copy/paste from an Image layer there's no need to rasterise it. Go to menu Edit and use Edit > Copy Merged (macOS) or Edit > Copy Flattened (on Windows) instead of the regular Copy, then Paste as usual to get just the selected area in a new layer. There's a few advantages in having Image layers (besides pixels layers) - you can learn a bit more about their differences here. Hope this helps a bit. I'm logging the issue with the different names given to the same command so both OS's match.
  8. Hi @Schwelli, @Brauni, Welcome to affinity Forums Can you confirm you are running macOS Beta 13 (22A5311f) build please? Are you running it on Intel or Apple Silicon based systems (M1 & M2 chips)? Are you using File > Export command or the Export Persona to export files? Thanks.
  9. Hi @EmmyH, Welcome to Affinity Forums Do you mind attaching a sample affinity doc file that when exported as PDF display those issues for you please? I can provide an upload link if you wish to keep the file private - just let me know. Thanks.
  10. Hi @Willy Pimentel, @ThierryMbp15, Thanks for your report. I confirm the app is indeed crashing in Ventura when opening a PDF (and in a few other cases as well). I'm checking if we already have this logged and will do so in case it's not. macOS Ventura is not officially supported at this point.
  11. Thanks for the DNG @ms.fuentecilla. I confirm this is indeed the same exact issue that's logged with us. I already updated and bumped the report and will be adding your files there for testing. Thank you for your support.
  12. Hi @dougie11111, Welcome to affinity Forums Can you give us more details please? Typically you only have to drag the layer over the thumbnail of the group layer in the Layers panel (until you see a vertical blue marker/line on the right side of the thumbnail) to nest it to the group (typically for adding masks or live adjustments/live filters to the group). Do not confuse this with clipping which is dragging a layer over another in the Layers panel but over the layer's label/name area (so excluding its thumbnail which is reserved for nesting/masking as explained above). Here's a video tutorial explaining the differences between the two positions.
  13. @ms.fuentecillaThanks for the additional details and file. Can you attach the DNG exported from Pure RAW 2 as well please - that's the file you are actually opening in Photo after processing in Pure Raw 2, so we need it too. Are you using a Mac computer? If so you can work around this issue setting the RAW Engine in the Develop Assistant to Apple (Core Image RAW). The Apple engine renders the DNG correctly (no magenta issues).
  14. Yes, you are describing the issue I was referring to. Files being saved as DNG (RAW) from DxO PureRaw/DeepPRIME technology do show magenta in highlights areas. Do you mind sharing the original RAW file from your camera and the respective DNG edited and exported by DxO Pure RAW 2 please? I will add them to the existing report and bump it up to bring this to developers attention again. I can provide an upload link if you wish to keep the files private - just let me know. Thank you.
  15. Hi @janvangastel, Welcome to affinity Forums There's still now way to do this with Overlays in Develop Persona but you can do it in Photo Persona using an exposure adjustment (or two if you want use one for the subject and another for background) along with much more robust masking functionality. Hope it helps a bit.
  16. Hi @Imonobor, No, there's no way to do this in Affinity dinamically. Actually as far as I'm aware no 2d illustration vector software is able to do what you want. You have more chances to find this type of function on a 3d based software then on a vector based illustration app. You can however draw an hexagonal grid from scratch in Designer and eventually use a custom grid to help you snap the hexagons in place as you see fit.
  17. No worries @DavidBaxter. We all have been there! Glad to know that at least it's sorted for now. Let us know if you experience the issue again. Thanks for your support.
  18. Hi @DavidBaxter Welcome to affinity Forums Do you mind attaching a sample PEF file to be inspected please? Thank you.
  19. Hi @ms.fuentecilla, If you are referring to highlights areas being rendered with a magenta/reddish when exporting DNG's generated by DxO DeepPRIME technology this is a known issue that's already with development. Can you give us a few more details (how are the image being sent to Photo/format etc) and eventually attach a sample file showing the issue please? Thank you.
  20. Hi @Eroica, This is an issue with Affinity Designer which is not parsing the file correctly. I believe we already have a similar case logged. I'm checking it out and adding your file to our report (or filling a new one if none exists yet). Instead of SVG try to export as PDF from matplotlib. Thanks for raising the issue.
  21. Hi @Helmar, Thank you for raising the issue again. This is still not working indeed - the issue/report remains open. I've bumped and updated the report to bring this up to developers attention yet again. I'm sorry for the inconvenience this is causing you. Hopefully this time...
  22. Hi @dayod4, Welcome to affinity Forums Can you provide a few more details and ideally the file you are working with please? I can provide an upload link if you wish to keep the file private. Just let me know. Are you working with artboards? If so make sure they are using integer values for their dimensions and for their X,Y coordinates. You can check this in the Transform panel (make sure you are using pixels as document units to check this). You may have to go to Preferences, User Interface section, Decimal Places for Unit Types area and increase the pixels value to 3 or 4 so you can seee mor decimal units in the Transform panel and eventually catch cases where the coordinates or dimensions may have a zero in the first decimal place (234,005 px for example). Delete the decimal parts in the Transform panel in these cases.
  23. Hi @msbaek, Have you tried to changing the screen resolution and then set it back to the original resolution again? Does it fix the issue?
  24. Hi @Klaas Oosterloo, Welcome to affinity Forums Please go to menu Edit>Preferences, Performance section and untick "Enable OpenCL compute acceleration", restart the app and try export again. Does it fix the issue for you?
  25. Hi @dr_who, This is already logged with the development to be looked at. I've bumped/updated the report to bring it up to devs attention again. If you use an integer value for the Radius of the filter it shouldn't blur the output when you rasterise the layer/group. Thanks for your feedback.
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.