Jump to content

Recommended Posts

Posted

I'm slightly unsure how to report this as it's reproducible in the retail version of Affinity Photo 2.3.1 but I can't see it either logged as a bug or subsequently in the bug fix list for the 2.4.0 Beta (unless this is a fix from an earlier version of Affinity Photo that I've missed) though it appears not to affect the 2.4.0 Beta so I'm unsure if this was a known bug internally which has been fixed in the latest Beta...

Steps to Reproduce

  1. Create a new Affinity Photo document using an Image Placement policy of 'Prefer Linked'
  2. Place a multipage PDF file
  3. Make copies of the placed PDF
  4. Change the Passthrough mode for the Placed PDF from Passthrough to Interpret for each instance of the Placed PDF
  5. Change the respective page for each instance of the Placed PDF to display a different page from the multipage PDF file
  6. Save the File
  7. This results in an instant crash in Affinity Photo 2.3.1 (but not in the Affinity Photo 2.4.0 Beta) or Affinity Designer or Publisher 2.3.1

 

Affinity Designer 2.6.3 | Affinity Photo 2.6.3 | Affinity Publisher 2.6.3
MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

  • Staff
Posted

Hi Hangman,

As this doesn't currently effect the beta this issue doesn't need logging however I will monitor this issue just incase.

Thanks
C

Please tag me using @ in your reply so I can be sure to respond ASAP.

Posted

Hi @Callum,

No problem, I was slightly unsure whether it even needed a mention since it doesn't appear to be an issue in the 2.4 Beta... was it actually a known and/or logged issue in 2.3?

Affinity Designer 2.6.3 | Affinity Photo 2.6.3 | Affinity Publisher 2.6.3
MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

  • Staff
Posted
23 minutes ago, Hangman said:

Hi @Callum,

No problem, I was slightly unsure whether it even needed a mention since it doesn't appear to be an issue in the 2.4 Beta... was it actually a known and/or logged issue in 2.3?

I can't find any previous logs regarding this but it seems as though this was inadvertently fixed by a change made in 2.4.

Please tag me using @ in your reply so I can be sure to respond ASAP.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

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