Skip to main content
R
RMcCarthy
Participant
November 18, 2021
Question

Weird glitch while panning and scrolling in InDesign

  • November 18, 2021
  • 2 replies
  • 1367 views

Hey all, I'm running into some bizarre behavior in InDesign while scrolling or panning. See here for a video (also attached). 
InDesign version 17.0 (M1 version) on a M1pro Macbook Pro.Using an external display, see here for display settings (also attached). 

I have tried reinstalling indesign, switching between CPU and GPU previews, changing monitor settings, and changing monitor connections but none have helped with the issue. 

Has anyone seen an issue similar to this or have any idea what might be causing it?

    This topic has been closed for replies.

    2 replies

    R
    RMcCarthyAuthor
    Participant
    November 23, 2021

    UPDATE: Changing the display scaling setting in MacOS seems to be a temporary workaround. I don't view this as a fix because I now have to run my monitor at less than its native resolution. 

      J
      jill853
      Participant
      November 30, 2021

      THIS!!!! I have tried every other fix in this forum, and this is the first thing to work. I scaled down from 3840x2160 to 3200x1800 and now the glitch is eradicated. Thank you for this bandaid, hero! 

        C
        corinnae5000
        Participant
        November 30, 2021

        Where can I find the scaling options? I'm experiencing the same issue and it's driving me crazy.

        Garrett_Drach
        Garrett_Drach
        Participant
        November 19, 2021

        I'm getting the same issue (see attached video).  InDesign version 17.0.  MacBookPro 2015.

        I've tried everything you have mentioned also with zero success.

        R
        RMcCarthyAuthor
        Participant
        November 19, 2021

        I talked to someone on the support chat box for about an hour after posting this. He could not come up with a solution after remoting in to my MBP. He said he was forwarding the info on to engineering and to expect an update to address it eventually. Still possible to work with the bug, but it's really annoying. 

          Terms & ConditionsAccessibility statement
          Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices