Same problem here, after a clean install of my Mac with Sonoma and the latest Scrivener (3.3.6 Build 16305). Simple documents with only text, but extremely laggy scrolling, especially when changing scrolling direction (ie I’m scrolling down and want to scroll back up, but there’s a delay between the two movements). Not an issue in other applications such as safari etc. I’m using zoom 125%, but the problem persists when I switch to Zoom 100%.
you have some of these web pages in your References?
Same lagging problem with two-finger magic trackpad scrolling on a 16" Macbook Pro M1 Max running Sonoma 14.3.1. Scrivener 3.3.6 (16304)
Mm, I didn’t think it would happen to me too. Unfortunately, I’ve been having the same experience for a few days now. But it also affects apps other than Scrivener. Which could mean that it’s not a Scrivener problem. So far the only way to fix the problem is to restart an app (not Scrivener). But I don’t understand where the connection is supposed to be.
Thanks for noting your solve (and for posting this issue), because I tried everything you did except for installing the prior version of Scrivener.
I’ve got a little extra info about this problem, at least as I’m experiencing it. It seems to be related to the scroll animation as implemented in Scrivener in conjunction with Sonoma. Note that I’m using two-finger scrolling on a MacBook Pro.
When I maintain contact with two-fingers on the trackpad, I can scroll up and down normally in Scrivener, and the application responds normally and immediately. I can even wiggle the scroll up and down, and everything responds fine. If I scroll by swiping two fingers up or down the trackpad, I get a scroll animation, which is also normal.
So far, so good.
The problem comes in when you try to scroll while a scroll animation is still in effect. Scroll animations in Scrivener on Sonoma at present apparently cannot be interrupted by new scroll input. Normally, if you “toss a page” up or down with a scroll swipe, that animation stops as soon as a new scroll input is received. But in the current version of Scrivener on Sonoma, you can’t increase, stop, or reverse a scroll animation once it’s in motion. The animation plays out completely, and then the next scroll input received triggers a new animation which plays out completely, and so on.
And that’s the problem.
New scroll input no longer causes scroll animation to exit. Instead, scroll input is being stored in an array and retrieved in queue order with each scroll animation playing out fully. Which makes navigating really annoying.
Anyway, hopefully Literature and Late with correct this with an update soon. Cheers!
4 Likes
Oh, this doesn’t appear to affect fullscreen Composition Mode. FYI.
Thank you for testing this and noting what you’ve found, punkrot. Those details are helpful.
Hi all,
Has there been any updates on this? I just updated my MacOS after being a version behind for a long time and I’m running into this issue.
I usually have 3-4 large projects open and tab between them for research, and this bug is driving me insane. It’s making Scriviner unusable as I’m working with texts up to 12k words per file and it’s impossible to scroll through them.
I’m trying to eliminate possible causes. It doesn’t happen consistently. Opening and closing projects, resizing the window to at least 50% the size of the screen, then back up to 100%, all reset the scrolling bug. It always returns VERY quickly however.
Really hope there’s some solution for this because I’m incredibly regretting updating my laptop now.
I’m on latest MacOS 14.4.1 and Scriviner is on version 3.3.6. I’m on a 2021 M1 Max MacBook Pro.
What we’re seeing most often is what you’ve experienced yourself. Namely, these lagging issues are made worse by really long, single documents and zooming the text or by collecting lots of documents into a Scrivenings sessions and zooming the text.
From our testing, the lagging is due to issues with how the text engine redraws the text when those combinations are in play. It’s also causing some odd reports when adding text to a longer document. Particularly if that document uses Page View.
The text engine in question is one provided by Apple in macOS Sonoma for third-party developers. It’s also the generic one Apple use in Numbers, Mail, and TextEdit. (They have a proprietary text engine for Pages.)
Since the macOS provides the text engine, Apple will need to make some fixes to those tools in Sonoma. (I suspect they’ll not bother since they seem to prefer shiny new macOS versions to fixing existing tools…)
Since Scrivener is an outliner-based writing tool, it tends to work better on any version of the operating system when the documents are smaller. If those large documents in your projects can be divided into smaller groups, that could improve the behavior.
To put this another way, Scrivener can stitch together lots of smaller texts during compile, so the only thing forcing long chapters or documents is the user’s comfort level.
I tend to divide my work by larger sections, scenes, or chapters, but that’s because it’s how I think of structuring my manuscript. It’s a habit I’m still trying to unlearn.
I’ve seen plenty of users note that they’ll create a new document whenever they need to scroll, so they avoid these kinds of issues. I haven’t quite reached that point yet, but I’m trying.
3 Likes
Thank you for your elaborate answer, I appreciate it!
But that’s really disappointing to hear. Breaking up these long documents isn’t really an option for me, as it completely breaks my work flow. It’s super frustrating Apple keeps introducing small bugs like this and never fixing them.
Do you perhaps know of a support ticket/forum post someone has made where we can echo these sentiments? The more people report it in a single place, the more likely they might ever look at it, I suppose…
Either way thank you. I guess I’ll just live with it for now
1 Like
I’m very curious why/how your workflow is so fixed you can’t use smaller Scrivener files.
Scrivener is designed specifically for smaller files to compose/edit long form (big) projects. It has lots of features and tools to facilitate that design philosophy. The list of those methods and tools is long, e.g. easy to Menu: Document->Split, Menu: View → Scrivenings view in which to make it “appear” one is working in a long file, etc.
As long as you are using Scrivener and not a traditional word processor product, I recommend you consider a small tweak in how you work to exploit Scrivener’s power. You can do that now instead of “waiting for godot” … I mean “waiting for Apple”.
2 Likes
If you don’t really need Sonoma, you can downgrade to Ventura. The internet is full of helpful articles on this.
1 Like
It is perhaps telling that Wikipedia usually has a little paragraph on what each OS release brings to the table, in their macOS summary page, and macOS 14.0 has this to say:
macOS Sonoma was announced during the WWDC keynote speech on June 5, 2023. It was released on September 26, 2023.
“Please clap.”
4 Likes
I see the same problem, the three most relevant points being:
- Lag definitely appears to happen only when a current scroll command fails to be interrupted by a subsequent command. (No lag unless a scroll command is already in progress.)
- The problem does not occur in composition mode.
- The problem started with the installation of Sonoma.
1 Like
Exact same problem here.
2023 MacBook Pro 16 in, 16GB M2 chip
Sonoma 14.4.1
Scrivener 3.3.6
Using laptop trackpad
I’ve been experiencing exactly what punkrot described above for the last week or so – uncontrollable scrolling that plays out in its entirety, even when I tell it to stop or signal it to switch directions. This is in the regular single document mode, in all documents that require scrolling – doesn’t matter if it’s 1800 words or 5500. Doesn’t matter if it’s zoomed to 125%, or set at 100%.
Issue only occurs in Scrivener 3.3.6, no other programs.
Being in Scrivener for 8-16 hours every day and needing to consistently scroll to reference scene notes, the issue is…well, the word ‘maddening’ comes to mind.
Breaking up scenes into individual 500 word documents was not a practical solution for me, so after finding this thread, like Frank above, I downgraded to Scrivener 3.3.1 and the scrolling is now functioning properly.
I’m sure it created other issues, as someone noted, but I shall deal with those when I encounter them. For now, I just want to be able to scroll like normal. Haha. Hopefully it’s only a temporary solution, and a future update will make 3.3.6 usable for me again.
1 Like
Same problem here and it’s been bugging me for a few weeks. I’m using 2021 M1 MacbookPro with 16GB, Sonoma 14.4.1 with Scrivener 3.3.6. Looking forward to a patch for this issue.
Interestingly though, I did a mac update last night and this morning. Now the mac still says its Sonoma 14.4.1 as same verison of Scrivener however now the lag is gone. Weird.
Joining this thread in desperation . . . MacBook Pro; Sonoma 14.5; Scrivener 3.3.6. I’ve had the same problem for a few months, have upgraded everything, have restarted, etc. I’m reluctant to reset preferences unless someone tells me that that actually WORKS. (Can anyone confirm or refute?) Nor do I want to reinstall an earlier version of Sonoma. I have large projects but short documents, but all that seems irrelevant—that is, if I open a completely new project and write a couple of test documents, I experience exactly the same scrolling behavior. Since there are several of us in this boat, could someone knowledgable (i.e. an L & L genius) set out the steps we need to take to remedy this bug?
1 Like
As discussed in the thread, it appears to be an Apple issue, unfortunately.
1 Like