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

Affinity 2.0.4 crashing while working with brushes/clicking on the UI


Recommended Posts

  • Staff

Hi Nomad, 

I know you say there are no crash dumps, but are there any crash reports in the folder below?

Is this working on a particular document/workflow and are you able to recreate this with hardware acceleration disabled?

Lee

 

Link to comment
Share on other sites

Hi,

 

I specifically said there are no crash reports generated, I am aware of the folders. Last one is from March in my case, not related to this imo.

If i disable hw acceleration I might as well quit altogether . This software uses less than 10% of my 4090 as it is, I don’t want to use my cpu exclusively working with high megapixel images. It’s very slow as it is. See my other posts in the benchmark threads, bug reports on slow msix version etc. 
 

only 1 , maximum2 cpu (very rarely) threads are used of the 32 available. I consider this a bug in itself, can’t call this a feature. 

I’d like the software to use my hardware, not crash and fall back on cpu emulation. How about Cuda support in 2023? I won’t say Optix that’s asking too much. 
 

All the best,

Your neighbourly Raccoon

 

Link to comment
Share on other sites

19 minutes ago, Nomad Raccoon said:

bug reports on slow msix version

Have you tried installing the EXE/MSI version instead?

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1

Link to comment
Share on other sites

1 hour ago, walt.farrell said:

Have you tried installing the EXE/MSI version instead?

Yes, but everything else is still true. It’s faster only marginally from end user perspective, and around 15-20% faster from the synthethic benchmark perspective. It still hangs when it loads anything, hangs when the app starts up, freezes from time to time and crashes sometime as described initially. Mind you most of these were not problems in V1, or to a much smaller extent ( hangs especially )

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.