Dreatern Posted February 2, 2023 Share Posted February 2, 2023 So, these crashes have been happening in different (new and old) documents. The hardware acceleration is enabled. It just happens, a freeze, the software stops responding, I wait but it never responds. So when I click on the window the Windows warning pop-up (the software is not responding, it wants to wait.... bla bla bla) so I close and open it again. I can work on a document for 10min and a standard action like moving something or clicking on a layer causes it to freeze which results in a crash. Or I can work for 30min, 1h, 2h without problems, until suddenly it happens.... any action, anything at all can trigger it, even selecting an object may trigger the freeze. Sometimes I work from start to finish and nothing happens, it's completely random, but frequent. 2.0 Vanilla (unpatched) did not have this problem, I think it started from the first patch. I still have 1.0 installed, the freeze/crash does not happen there. My System Spoiler Operating System: Windows 11 Pro 64-bit (10.0, Build 22621) (22621.ni_release.220506-1250) System Manufacturer: Gigabyte Technology Co., Ltd. System Model: B360M AORUS Gaming 3 BIOS: F15b (type: UEFI) Processor: Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz (12 CPUs), ~3.2GHz Memory: 32768MB RAM I can't find the Designer 2 crash report location, the only one available here is 1.0. nor can I find information on the location of the 2.0 report Spoiler Quote Link to comment Share on other sites More sharing options...
Staff Pauls Posted February 2, 2023 Staff Share Posted February 2, 2023 when the app freezes go to task manager. Select the designer app and right click. There will be an option to create a crash dump. I think you are suffering from something we have identified and will have a fix in our next beta Dreatern and flobnoit 2 Quote Link to comment Share on other sites More sharing options...
Staff Affinity Info Bot Posted February 22, 2023 Staff Share Posted February 22, 2023 The issue "App hangs when zooming" (REF: AFD-6338) has now been fixed by the developers. This fix is included in build 2.1.0.1706 (or later) which is already available as a customer beta and will be included in the next release. Customer beta builds are announced here and you can participate by following these instructions. If you still experience this problem once you are using that build version (or later) please make a new thread referencing this one. flobnoit 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.