roboto35126

I looked all the forums to see if this has been suggested yet, but having Affinity Designer "automatically" selecting the node tool whenever I convert text to curves, is really annoying. Especially since I have to switch to the selection tool in order to use the convert feature. Can this at least be an option I can turn off?

So, I don't have a crash report in the location shown under the MSIX version. Of course, I don't have the folder at all under the EXE version. I did make sure the Hardware Acceleration is unchecked. I've rebooted my machine just to be sure and so far, that seems to have fixed it, but I have more work to do on this design, so I'll post back if I see it anymore. I assume that the update to 2.2.1 re-enabled that settings, since looking back to my other post, this was the same solution for another issue in the previous versions, so it was already disabled prior to the update.

So, I just upgraded to the newest version 2.2.1, but now Designer is back to crashing whenever I am trying to use the Contour Tool. Just to verify, I created a simple square object. Converted to curves and ran the Contour tool. The mouse started slowing down as I pulled the tool and finally just crashed the app. Now even going back into the file, if I try to do anything to the square, the app will crash again. Not getting a crash report, but the setting to upload them is checked. Won't have my email attached, since that setting if off be default. Anyway, I'm in the US, central time and it's 10/23/2023 around 8AM, if you can find a report from that time frame.

Not sure if anyone has tried this, but saw it on another post about crashing issues. I un-checked this option and it seems to be better, so far: Task manager is not showing High Usage for power or CPU. Maybe this will help, I dunno...

I haven't been able to find a reason for it. I have a laptop and my gaming rig, but both have the same issue after about 20 minutes of working on a design. I compared them side by side on the same design last night, so not sure it's a hardware issue yet. Both my boxes are running on Win10, Pro & Enterprise, so can't talk much to how the issue would be on Win11. I was hoping to upgrade to Win11 this weekend, to see if the OS might help it. Disappointed to see that it happens on Win11, maybe even worse. Still, I love the product and will just deal with it until Affinity can find a solution. I just save a lot and restart the app when it starts getting laggy and unresponsive 😩

Yeah, I ran V1 and v2 side by side on my desktop gaming rig like I've always done with v1, but v2 is significantly slower on basic operations. Just selecting objects imbedded in another object, is really bad for instance. So slow, that when trying to CTRL select an object with embedded objects to duplicate it on Windows, v2 selects the inner object and copies it and not the whole parent object. Resizing, node functions, everything takes longer to start working, just weird. Not sure if it's due to how the application is written to work within the Win10/11 "app" structure, but noticed that the install for the app moved from Program Files to the User, .affinity hidden folder. Something is not the same as before, for sure. Guess I'll go back to v1 until this gets fixed...UGH!!!!