Skip to content


My feedback

1 result found

  1. Distorted Text and Graphics in high sierra

    213 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Closed: Fixed  ·  Sumit Garg responded

    This is a macOS10.13 issue, specific for some Intel GPU cards. Apple has fixed(partially) this issue inside macOS10.13.4 released build.

    Following are the workaround for resolving this issue.
    1) Update your mac machine to latest macOS10.13.4. Here, Apple has fixed this issue to some extent. You will face very less number of rendering issues.
    2) Disable GPU preview and set display performance as typical.

    Once you have updated to macOS10.13.4 .You might still face some rendering issues. Since, Apple has not fixed this issue completely.
    Please switch off GPU rendering for these cases and report a separate post for tracking.

    An error occurred while saving the comment
    Alexander commented  · 

    Hi all, to share my experience for all of you who are struggling with this: I bought a MacBook Pro 13" 2017 in March 2018. I'm a frequent user of InDesign and obviously came across the same annoying and unworkable situation of distorted text and images, especially when zooming in or out. At that point this 'bug' was already months old and unfixed. I came across a list of GPU chips that have this problem and the GPU chip on my MacBook Pro 13" was on the list. So... I checked with one of you who changed to a 15" whether the problem remained as the 15" has a dedicated GPU. His answer was no and so I switched. Afterwards unfortunately I also returned the 15" for different reasons (it had issues unrelated to this problem). So...I am also still waiting for this to be fixed because I prefer to have a 13".

    The question is for which GPU-chips this is now resolved. Anyone?? And can it even be resolved properly you think? To me it looked like a hardware-related problem...

Feedback and Knowledge Base