DC9V
Members-
Posts
28 -
Joined
-
Last visited
Everything posted by DC9V
-
1000Hz is the standard polling rate on modern devices and it shouldn't cause any issues.
- 11 replies
-
Affinity Designer 2 for macOS - (2.0.4)
DC9V replied to Patrick Connor's topic in News and Information
Thanks for patching! Keep it up! 🙂 -
Very slow with delay
DC9V replied to suntrop's topic in Feedback for the Affinity V2 Suite of Products
I agree, and I'm probably not gonna buy any future upgrade either. Although version 2.0.3 already came with a lot of bug fixes, I think version 2.0.0 should never have been released in such a rudimentary state. Most of us simply don't have the know-how to estimate whether or not a certain issue will be fixed within future updates. And we certainly didn't want to replace beta-testers. I know that there's always a reason for all kinds of things, but I want to be clear that this is simply not acceptable from a customer's perspective. Buyers should be able to expect that an upgraded version does not perform worse than its predecessor. -
When are we going to see an official update that is not a beta?
-
Affinity Designer V2 getting really slow and laggy after some time
DC9V replied to SKT7's topic in V2 Bugs found on Windows
On my Apple Mac Studio M1 Max, Beta v2.0.3 seems to perform much better than v2.0.0.- 164 replies
-
- affinity designer
- v2
-
(and 3 more)
Tagged with:
-
Hello, a general advice to avoid data corruption: Avoid Cloud Sync if possible. Before every update, create a backup of your project files manually. When Affinity is installed on a secondary drive, make sure that the application is whitelisted in Windows Defender's 'Data Execution Prevention'. Reactivate your DRAM's XMP after every BIOS-update. Also double-check that the sticks are installed in the correct dimm slots. (See motherboard manual.)
-
Great news! I've found a simple solution for this issue. Open System Settings Click: Accessibility -> Display Set Pointer Size to Normal Click Reset Pointer Colours (fill colour: black ; outline colour: white ; 100% opacity) See video: 0:00-0:50 Demonstrating the lag issue in Affinity Designer V2.0.0 0:50-1:46 Solution: Resetting Mouse Pointer in System Settings @EmT 1779059691_SolutionforlaginV2.mov
- 11 replies
-
Very slow with delay
DC9V replied to suntrop's topic in Feedback for the Affinity V2 Suite of Products
[Edited] I think our systems should be capable. GPUs like @kamelus's 3070 Ti are used for much heavier workloads like 3D rendering. @suntrop's GPU on the other hand has only 2GB of video memory, though. I think the issue could be a memory leak. It occurs when a program incorrectly manages memory allocations. Today I noticed that my sound device driver had almost 50% CPU usage while Affinity designer was opened, and it continued to have at least 37% CPU usage after I've closed all other applications including but not limited to Affinity Designer 2.0. ( 'ApogeeGlue' is part of my sound driver. See CPU usage bottom right corner. ) . -
Very slow with delay
DC9V replied to suntrop's topic in Feedback for the Affinity V2 Suite of Products
Hello Pyanepsion, See one of my previous posts for all the details: -
Very slow with delay
DC9V replied to suntrop's topic in Feedback for the Affinity V2 Suite of Products
I can confirm that moving objects is extremely slow. It has been reported to the devs. Other actions being slow or non-responsive is probably caused by the same fundamental issue. What I've noticed is that the CPU performance doesn't seem to be spread properly among all available cores. -
Power duplicate dont work properly with move object
DC9V replied to bajqo's topic in V2 Bugs found on macOS
Yea, I was a bit off-topic. However, in case it turns out that the moving-objects-lag is not limited to M1 chips, you might also be able to benefit from a potential patch on your 2019 MacBook Pro... I just thought it was worth mentioning. -
Thank you, Happy patching!
- 11 replies
-
Power duplicate dont work properly with move object
DC9V replied to bajqo's topic in V2 Bugs found on macOS
All of my mice, as well as some other overclocked input devices, have a polling rate of 1000Hz, using at least 3200dpi. However, I noticed that resizing an object in Affinity Designer doesn't cause the issue. It only seems to happen when press-holding left-click in order to either select, or move (several) objects. This can also happen when moving files on the desktop. I assume that it's an issue with vertical sync. -
Hi! I'm a musician. I use Affinity Designer in order to transcribe music. I'm used to drawing notes with pen and paper, and I dislike modern notation software which usually requires key commands. I don't need those cheap midi sounds when I can imagine music in my head in a much better way. All I need to achieve my goals is a guitar or a piano, an empty sheet, and a pen. Furthermore, I like playing competitive video games and I'm obsessed with keeping the input latency as low as possible.
-
Hi @Dan C, No need to apologize! When using Affinity Designer, I think I've encountered a performance drop (before the upgrade) when reBAR was enabled, especially when creating vector-based arrows. However, I could simply turn reBAR off in the BIOS whenever I have the impression that it's causing issues. When playing demanding video games at 4K, it increases the frame rate by just a few FPS, if at all. I actually doubt that Affinity Designer or any other app would drastically benefit from it. What seems more important to me would be the implementation of a fixed physics tick rate, a proper way of consistent frame pacing, and decoupling the physics from vertical sync by capping the app's frame rate at a multiple of the physics tick rate, e.g. 240 or 288 FPS. There could be a toggle in the settings to choose between 120FPS (60 or 120Hz), and 288 FPS (144Hz). TL;DR, reBAR is rather unimportant. Please take a look at input variance and frame pacing. Consider disabling V-syng, by manually capping the frame rate instead. Also please check compatibility with input devices that provide a polling rate of 1000Hz or more. Cheers
-
Power duplicate dont work properly with move object
DC9V replied to bajqo's topic in V2 Bugs found on macOS
Your objects also seem to lag when moving them. Similar to what I have encountered. -
Hm, that's weird. I'm gonna contact Apple support.
- 11 replies
-
Hello, I'd like report a performance issue. Affinity Designer Version: 2.0.0 System: Apple Mac Studio, M1 Max, 24c GPU, 32GB memory, 1TB SSD macOS: Ventura 13.0 Display: LG 27GN950, Displayport 1.4, Adaptive Sync enabled, 144Hz, 4K Mouse: Logitech G502X, Polling Rate: 1000Hz, DPI: 800 - 8000 (Edit: usually I'm using 3600 - 3800 DPI) Settings: Hardware acceleration: Metal compute acceleration (Apple M1 Max) ; Display: Metal (Edit: The issue also seems to occur with OpenGL) Issue: Selecting and moving objects appears laggy. I also noticed it when moving folders or files on my Desktop, so it could also be related to macOS Ventura. Video: https://youtu.be/kzrrg5mBT30 Repeat: Open any project and move any objects. Greetings, DC9V Affinity 2.0.0 ~☺~ M1 Max.mp4
- 11 replies
-
Hello! I'm coming from an e-sports background, where minimalizing input lag is important in order to minimize the chance of random input delays due to the possible misbalance between the physics engine and the framerate. That being said, I'm used to play video games at 240 FPS or more, with a physical monitor latency of 5ms or less, while making use of Adaptive Sync technologies like G-sync. V-sync in comparison is very bad as it nearly doubles the frametime, whereas Adaptive Sync only adds 1 or 2ms of latency. Now I'd also like to reduce the latency when using a Wacom tablet in Affinity Designer. I've experienced a bit by using a software called HIDUSBF, in order to overclock the polling rate of my Wacom tablet. Although I understand that Wacom tablets work differently than mice or game pads, I feel like it still does improves the responsiveness and the detail of a quickly drawn line. My questions and thoughts are as follows: 1) Is Affinity Designer going through dwm.exe, in other words, is V-sync always active? 2) Does Affinity Designer have a fixed physics tick rate for pipelining input? 2) What happens if I enable G-sync for windowed mode in the GPU driver settings? 3) When I create a custom profile for Affinity Designer in the "Manage 3D settings" section of the driver, will it actually have any impact? Cheers!