Jump to content

NathanC

Staff
  • Posts

    4,415
  • Joined

Posts posted by NathanC

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

  2. Hi @Beevor OLindy,

    The Studio presets and corresponding data are stored within the .plist files along with other app settings and preferences. the location of this file is detailed in the FAQ below, I'm therefore not too sure which preset folder you're looking at or copying files to.

    If the existing presets have stopped working following the OS upgrade, they'll likely need to be cleared and re-created from the menu unfortunately.

  3. Welcome to the forums @Vincent Lacroix,

    If the apps are consistently crashing when either creating a new document or opening an existing file, please follow the guidance in the FAQ below to ensure your graphics drivers are fully up to date and Hardware Acceleration is disabled.

    If the issue persists, please provide a screenshot of your Edit -> Settings -> Performance window and also provide a few recent crash reports as per Garry's advice above.

  4. Hi @Iztok,

    As discussed previously in your similar thread below, providing a lone crash report without any additional information or context doesn't give us anything conclusive re-produce or log. If you're able to reproduce the crash, please provide any relevant steps required as well as the necessary files so we're able to investigate further.

     

     

  5. Welcome to the forums @Kiralee

    These brush glitches/artefacts when brushing along with the corrupted brushes panel preview is a known issue specific to the V1 iPad apps on devices running iOS 17 or later, if the issue occurred overnight this is likely the result of an iOS update. This bug is fixed in V2, but is still outstanding on V1 iPad since these apps no longer receive regular updates.

    Unfortunately, there are no known workarounds since it’s not possible to simply roll back the iOS version, so I can only recommend upgrading to V2.

  6. Thanks looks like it's related to a known issue logged internally. When exporting using the 'All Pages' area mode, Odd-page PSD and Affinity files are incorrectly offset on the page, causing it to appear blank in the output PDF. Until this issue is fixed, 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.

    It's good to hear that deleting and placing a resource in again fixed the issue within your file, albeit strange since the issue is still outstanding in 2.6.3. I've bumped the issue with your report.

     

  7. Hi @fakepoet welcome to the forums,

    Are these cover designs 'Image' type layers, or any other type of embedded resource? I can't see anything wrong with your export settings, so I'd recommend disabling 'Hardware Acceleration' found under Settings -> Performance. Once this has been disabled, close the menu and restart the app when prompted to and then try the export again.

    If you're using an Apple Silicon (M1/M2/M3/M4) based Mac, we're aware of issues relating to the H/A setting causing raster corruptions on PDF export dependant on the JPEG compression setting on certain systems, so you may be encountering this issue.

  8. Hi @LostInTranslation,

    This is a known issue specific to Type 1 (PFM/PFB) fonts currently logged with the developers. Dependant on the font, certain glyphs will either show a blank space or the incorrect character. This issue is a regression over 2.5.7, so you can optionally uninstall and roll back to this version if you don't have an equivalent TTF/OTF version of the fonts. However, any files saved in 2.6.3 won't open due to the version incompatibility.

    https://store.serif.com/en-gb/update/windows/publisher/2/

  9. Hi @Stadicus,

    Just to 100% confirm, was your app updated to 2.6.3 at the time the issue was triggering? If you still have a copy of the .afpub document where the original issue is triggering on PDF 'All Pages' export, feel free to upload it to the private dropbox link below and we can review this internally. If the PSD file(s) are linked, please also include those in the upload.

    https://www.dropbox.com/request/xq7KONFOATMao3923vYk

    Thanks!

  10. 11 minutes ago, thomaso said:

    @NathanC, would be possible to avoid a static layout (e.g. 5 rows with fixed positions / fixed cell height) but make DataMerge consider variable text lengths and accordingly generate flexible cell heights? … with or without (extensive) changes to the data source document?

    Not as far as I'm aware, the merge layout cells won't dynamically respond and re-size based on text length, If the text exceeds the size of the text frame when generating this will result in a text overflow. It's a good point though as it wasn't something I had considered when setting it up, this require some manual adjustments post-merge. Would certainly make for a good feature request.

  11. Hi @stek,

    2 hours ago, stek said:

    Example: 

    Draw 2 text boxes.

    Then drag box 2 and it will not snap to box 1 at all - doesn't even attempt and doesn't show any possible snaps (ie. no part of box 1 turns red to show a snap).

    Deselect box 2 and select box 1, then immediately deselect box 1 without moving or editing it in any way.

    now drag box 2 and it will snap to box 1 as expected. all possible snapping options now appear on screen.

    I've not yet successfully re-produced this issue on MacOS or Windows so far, provided I have the Bounding box snapping options enabled and the Candidates Set to Immediate or All layers the text layers snap to Vertical and Horizontal targets as expected.

    If you're able to re-produce the issue, can you provide a screen recording demonstrating this, and also showing your current snapping options?

    Thanks

  12. Hi @Karlrex,

    Looks like the 'Leica Fotos' app requires a tether to a supported camera in order to test this process so I'm unable to replicate this internally currently, but if you could provide the following info we can get this logged based on the info provided:

    • Which Leica Camera model are you using?
    • Does the issue also trigger when opening the .DNG file directly in Photo 2 from Photos or Files? (I.E not through the 'Leica Fotos' app)
    • Can you provide a screen recording demonstrating the issue?

     

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