-
Posts
16 -
Joined
-
Last visited
Profile Information
-
Location
United States of America
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
Aeromachinator reacted to a post in a topic: Designer v2.1.0 still very laggy when zoomed in and artifacting
-
Ash reacted to a post in a topic: Massive lag with the whole Suite
-
Aeromachinator reacted to a post in a topic: Massive lag with the whole Suite
-
Aeromachinator reacted to a post in a topic: Massive lag with the whole Suite
-
Aeromachinator reacted to a post in a topic: Massive lag with the whole Suite
-
I've just had my morning coffee and now I'm looking back at my instance of the Designer beta. 1790 is still as snappy as ever, and I think Serif has done a solid job at improving the latency issue from what I'm experiencing. There remains a small bit of latency when I jump between object selections, but it's not program-breaking and I can see myself using this build for my actual work if it were released as 2.1 today. Thanks for this!
-
Aeromachinator reacted to a post in a topic: Massive lag with the whole Suite
-
Aeromachinator reacted to a post in a topic: Massive lag with the whole Suite
-
Aeromachinator changed their profile photo
-
Aeromachinator reacted to a post in a topic: Massive lag with the whole Suite
-
nitro912gr reacted to a post in a topic: Massive lag with the whole Suite
-
AdamW reacted to a post in a topic: Massive lag with the whole Suite
-
thegary reacted to a post in a topic: Massive lag with the whole Suite
-
debraspicher reacted to a post in a topic: Massive lag with the whole Suite
-
Okay, so I'm running an instance of the 1790 build with OpenCL disabled on my Windows computer right now, and I have to say that so far it's a remarkable improvement over the lagging I got in 1781—probably at least as fast as version 1 or close to it. Granted, it's only been running for a few hours, but I'll let this instance run overnight and see if I find anything different the next day.
-
Aeromachinator reacted to a post in a topic: 2.1 bug fix list
-
Aeromachinator reacted to a post in a topic: Massive lag with the whole Suite
-
Aeromachinator reacted to a post in a topic: Massive lag with the whole Suite
-
nitro912gr reacted to a post in a topic: Massive lag with the whole Suite
-
mediumcheese reacted to a post in a topic: Affinity Designer V2 crashes when zooming in and out frequently
-
thegary reacted to a post in a topic: Affinity Designer V2 crashes when zooming in and out frequently
-
Calvert reacted to a post in a topic: Affinity Designer V2 crashes when zooming in and out frequently
-
I think it's also within our right to ask Serif why they haven't pushed critical bug fixes in smaller patches similar to 2.0.3 and 2.0.4. Given their failure to address program-breaking issues in a timely manner and the inherent risks of the beta version, I've stopped working with Designer 2 almost completely. It really is sad to see...
-
thegary reacted to a post in a topic: V2 Designer 2.0.4 Very slow between choosing objects. All of them.
-
Well, as someone with an AMD CPU and an NVIDIA dGPU, I was able to capture some of the lagging behavior on my screen. It affects my ability to jump between selections of certain objects, just as it has for users with AMD dGPUs. This is on the 1781 build of the 2.1 beta: Latency.mp4
- 41 replies
-
- windows 10
- msi installer
-
(and 2 more)
Tagged with:
-
Gotcha. I had thought you were using the latest beta build (1769), because I've been running an instance of it on my computer for a few days without any slowdowns, so I was curious to know. Please do keep us updated!
- 164 replies
-
- affinity designer
- v2
-
(and 3 more)
Tagged with:
-
That's good to hear. DId anything change between this time and the previous slowdowns?
- 164 replies
-
- affinity designer
- v2
-
(and 3 more)
Tagged with:
-
That's terrible! But at least it narrows things down for us a bit. Since this bug still persists on machines with current generation specs, it's safe to guess that it has more to do with how well Version 2 of the suite is ported to Windows, which is... quite poorly, from my experience.
- 164 replies
-
- affinity designer
- v2
-
(and 3 more)
Tagged with:
-
It's truly sad. Like other people in this thread I've gone back to using Designer 1 for my design work—it is a bit of an inconvenience as the shape builder doesn't exist in that version (and boy, was it fun to use), but I'd pick an old but reliable hammer over a new but spotty toolbox anytime. Also, I am curious to know what processor you're using @Balakov and whether you think this Find() bug has anything to do with it, especially as I've been crawling the forums lately and several Serif mods implied that this is an issue with AMD CPU-based devices running this software. Then again, we're also seeing people on Intel Core processors experiencing this slowdown, so I can't be entirely sure about that yet. https://forum.affinity.serif.com/index.php?/topic/184265-affinity-designer-2-beta-performance-lag-so-bad-its-almost-unusable/&do=findComment&comment=1071617
- 164 replies
-
- affinity designer
- v2
-
(and 3 more)
Tagged with:
-
Part of me has been wondering if this is related to how .NET is integrated into the Windows version of this program and could very well be something on Microsoft's side—hence the problem's presence in both version 1 and version 2. But I don't know how well that adds up since it seems to be more pronounced in version 2. Now as for the radio silence from Serif on this issue, I don't know why that's the case. Is there something we haven't yet elaborated on?
- 164 replies
-
- affinity designer
- v2
-
(and 3 more)
Tagged with:
-
Having the same issues here. I find that what @Balakov observed in his use of Designer is particularly important—the spike in latency after some time is concerning on its own, but the fact that it often fails to exit properly after clicking the close button is an even bigger cause for concern. I wonder if Serif have done anything towards patching this in beta builds—have they logged this issue or addressed it in their commits at this time? My specs Windows 11 Pro AMD Ryzen 7 5800X 64 GB DDR4 RAM NVIDIA GeForce RTX 3070
- 164 replies
-
- affinity designer
- v2
-
(and 3 more)
Tagged with:
-
I noticed a bug in version 2.0.0 of Affinity Designer. Some warp groups in the Bend - Vertical configuration may leave a trail when you drag them around. Reproducing this bug—which may or may not occur—is simple. One needs to simply type in text and click Layer > Warp Group > Bend - Vertical to distort the letters, and then drag the warp group around. I have attached the .afdesign file if anyone wants to take a look or confirm this is also going on in their end. Bart.afdesign
-
While we are on this topic, I read in a AECMagazine article by Martyn Day that at least one customer is beta testing Affinity 2.0: https://aecmag.com/technology/serif-affinity-for-aec-firms/ For those who don't wish to click the link: “Version 2 of the suite is due out in 2022 and promises to bring a slew of new capabilities. One customer who is beta testing V2 told me [Day] it will also make the switch from Adobe ‘even easier’, acknowledging some ‘growing pains’ in the initial transition.” Is Serif in a position to confirm or deny any of these rumors at this time?
-
I lurked the forums a bit more and realized that the reason might be that a particular shape was corrupting the entire file—I was able to delete it and recreate it without causing Affinity to crash, so I would like to consider the issue closed. Still, though, I have included the .DMP files for developer analysis.
-
Hi there—I am reporting a stack overflow exception (0xC00000FD) that happened while I was working on a document this morning. I was working on a particular vector since last night, and in between that time I put my computer to sleep and woke it back up, resuming where I had left off in Affinity Designer without terminating the process. Some time later, I tried to move a vector and the program suddenly shut down for no apparent reason. After reproducing the crash at least once, I took the dump files of both crashes to DebugDiag to create a stack trace—I have attached all of them in this post. Because it's happening with one particular file, I will assume that it has been corrupted somehow—time to start my work all over again... Here are my specifications if you need them: Windows 10 Pro (19044.1889) AMD Ryzen 7 5800X 64 GB DDR4 RAM NVIDIA GeForce RTX 3070 (driver version 512.15) 17af89f1-d0d8-45e1-a9b8-a552661d3daf.dmp 703f0e7d-c139-4636-acba-45f79ddabfdb.dmp MultipleDumps_CrashHangAnalysis.mht