Jump to content

level lever gets stuck


srg

Recommended Posts

Many thanks for providing that for me!

I've been unable to replicate this here in my testing thus far - can you please confirm:

  • Does this happen in any document, or only certain ones?
  • What version of macOS are you running?
  • What are your mac specs?
  • Under Affinity Photo 2 > Settings > Performance, what are your settings?
Link to comment
Share on other sites

20 minutes ago, Dan C said:

Many thanks for providing that for me!

I've been unable to replicate this here in my testing thus far - can you please confirm:

  • Does this happen in any document, or only certain ones?
  • What version of macOS are you running?
  • What are your mac specs?
  • Under Affinity Photo 2 > Settings > Performance, what are your settings?

It happens occasionally and it happened with previous version of AP and macOS

Problem with metal computing seems to have been here for years. How is that possible?

Screenshot 2023-08-11 at 8.53.19 AM.jpg

Screenshot 2023-08-18 at 12.47.03 PM.png

Link to comment
Share on other sites

Thanks for providing that for me - I've tested this on both an Intel and 'M' based mac in Photo and I'm still unable to replicate the behaviour unfortunately. Can you provide a sample document that shows this on your end, to see if this allows me to replicate?

On 8/18/2023 at 5:48 PM, srg said:

Problem with metal computing seems to have been here for years. How is that possible?

AFAIK, Metal rendering is used for the canvas within the Affinity app and I don't believe it affects the UI, as shown in your recording - therefore I do not think that Metal acceleration is related to this report :)

Link to comment
Share on other sites

Thanks for confirming, unfortunately without being able to replicate this issue internally and without a sample document showing this issue we'd be unable to report this to our developers at this time.

However to be certain, I have requested that other team members internally test this across a range of macOS devices to see if we can trigger this issue, allowing us to report it to our dev team.

Although I appreciate you cannot provide a document which shows this, do you recall the most recent steps before this issue occurs? It may be that the workflow you are following before the issue appears is the trigger, which I may not be following exactly here.

Thanks once again!

Link to comment
Share on other sites

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.