Jivix

It did help performance but even with the panel removed I'm still getting weird UI refreshes, input lag, and increasingly slow performance over about an hour of use. Saving and editing the document seems to accelerate the performance decline.

I just noticed the feature in 1.9 for some reason (probably because I had to remove my settings while attempting to fix performance issues). There was also a new post made by staff regarding the issue which seemed to indicate this is an issue which has cropped up recently. Perhaps people are reporting it because the magenta frames are more visible than they had been?

Some people are making bug posts about the new Snapping Candidates feature. It's very unintuitive at first, especially due to the ways candidates are chosen. The feature describes the process of assigning candidates as "Creating a new object, or hovering over an existing object, designates it as a snapping candidate". It turns out that you can also create candidates when deselecting elements (doesn't matter how you deselect, they always become a candidate). I initially thought I was not able to assign a candidate by hovering, only selecting. It turns out this is because there is a fairly lengthy delay (which I don't see any way to configure). The hovering method can produce very unexpected results in documents with overlapping frames - sometimes it appears that the top frame is chosen, other times it is the lower frame. This is also a problem when using the selection method, because if you click the wrong element there is no way to prevent it from becoming a candidate, short of closing the document (I was hoping pressing escape to deselect would prevent this from happening), meaning you get to click 7 things to get back to the same set of candidates you had previously, plus the correct selection. This can be very tedious. As long as this is part of the candidate selection process, there really needs to be a way to back out of a selection, because I am constantly selecting and rearranging elements and it is extremely difficult to manage a "good" set of candidates. I would almost prefer a candidate toggle option on each and every element on a page. Creating a new object means that one of your previous candidates is no longer a candidate. This can be a problem when you are trying to create a layout with lots of elements and you want the same set of candidates to snap all of them to. I propose making each of these candidate selection methods optional, so users can gain more control over when and how candidates change, and preventing Escape deselection from creating a candidate from a selected element. Edit: Also I am not sure the whole snapping candidate feature should be the default option, given how confusing it has been for some users who are exposed to it for the first time and accidentally reported the feature as a bug, the other options are a lot more intuitive.

Unfortunately, closing the paragraph panel did not solve my issue (but it did provide a UI speed boost). The app still gets progressively slower the more it is used, after about an hour it gets to the point where doing anything takes multiple seconds. Saving the document and restarting the application makes the slowdown go away, and that's my temporary fix until a new version comes out.

Sorry, this isn't really relevant to this thread, but how do you add a signature to your posts? I don't see an option in the post or in my account.

Uploaded my old folder. Mine was pretty small, just 348kB.

Unfortunately that was just a temporary fix for me, it got steadily worse over about an hour of use.

Updated to 1.9, memory usage steadily rising again. Have no idea what's going on.

Fix helped me, but I can see there is still quite a lot of UI jitter going on, especially when dragging elements around. I double checked the settings and the new GPU acceleration is on. After about 5 minutes of editing it is acting very sluggish again, though not as bad as before. All of the elements on the screen are constantly flickering and refreshing as I make changes. This is really annoying. I can't even type in a text box without massive lag. Ryzen 5 3600, 32GB ram, RTX 3070

Throwing in my 2 cents: - The update notification blocks all UI interaction until it's dismissed. This could easily have been made into a Windows notification instead, and politely stayed out of the way of my work. You can't even close the application until you've dismissed the popup!!! Totally wrong. - The update process is super janky if you bought from Affinity store. How is there no check for updates option in the Windows version? This CAN'T be difficult. - I start Publisher about 10-20 times a day when I'm working, clicking that stupid popup every single time when there's an update available is unbelievably annoying. It's extremely bad user experience design to force your users to update software right after they opened your application to start getting work done. - This is the 21st century and there is no way to disable automatic update checking? We must be in a dystopian timeline. Why does every app contact the mothership each time I start it? This is easily my least favorite aspect of Affinity, because it's totally in your face about it.

Thanks for stopping by! Well, there is, but I decided to jump forward to driver 461.40 as there were claims and reports that it is more stable. So far, I haven't noticed a significant slowdown, but I also haven't used Publisher for a 6-hour stretch since. I guess the garbage collector wasn't working properly on the older driver for whatever reason. The issue persisted through system reboots so I'm only theorizing that was the case. So far, I haven't gotten the memory to rise beyond 900MB even with significant content changes in the document. Not sure if there is a place to report bad driver interactions - 461.09 was definitely a problem child for the Affinity suite.

After examining my event viewer history, I saw some errors related to graphics (nvlddmkm event id 14 error), and apparently there's some instabilities in the graphics drivers for new cards, that others are having issues with as well. It's odd that I have been using over a dozen different apps and the problem is only visible in Publisher, but that's a natural result of the complexity of computer software I guess.

Hi all, first time here. I need some support assistance. I'd love to know what's going on with my issue. I have used Publisher several times to create documents for a project I'm working (currently using v703 on Win10 20H2) , but it appears to be behaving oddly now. The only significant change I have made since I last used Publisher was replacing my graphics card (nvidia 1070 upgraded to 3070), and updated the graphics driver (461.09). I have monitored my cpu (ryzen 5 3600) and gpu load, and neither are going above 20% under any conditions, but Publisher is becoming extremely sluggish. It's possible this is unrelated as I did not use Publisher for that many projects preceding this. Publisher is taking 1800 MB of memory after having it open for 2-3 hours. Just having a simple 4 page spread with a text frame on each page (no heavy graphics - just a couple pages of text) and clicking in and out of frames can take over 5 seconds and causes the UI to update multiple times. The issue quickly re-occurs if the application is closed and reopened, whether or not the document is new or an existing document. To be extra clear, I don't have any issues with typing or editing within a single frame, but working with multiple frames gets to be unacceptably slow, by a huge margin. Sometimes it takes 1/10th of a second to click out, other times up to 3-5 seconds. And clicking into a frame has the same kind of random disparity, but is much faster (like 1/20th of a second to 1/2 a second, but still noticeable and enough to cause mis-clicks). I noticed these UI changes cause my CPU and GPU usage to spike to 10-20% during that time, and the memory usage rapidly changes multiple times as well. It also gets progressively worse the more times I click in and out of the frames. I noticed the memory usage also rapidly climbs while doing this. Just clicking in and out a few dozen times (representing about 3-5 minutes of work for me), the app is already taking over 700MB just to display one spread. But here's the weird thing, sometimes it just doesn't happen. I have no idea what's causing this behavior to start or stop, but it happens during a single session. Help! I just want to get a simple project out of the way and this is totally infuriating. I would rather not have to work not knowing if my input is causing it to get slower with every click.