Jump to content

Ugly dithering of 3D borders on destop elements (after upgrading to Monterey)


jota29
 Share

9 posts in this topic

Recommended Posts

After upgrading macOS from Majove to Monterey on my HP EliteDesk 800 G1 I noticed a strange effect with the 3D borders of the control center and other elements (widgets, dock ...). It looks like some kind of (not good looking) dithering, that even worse changes when I move the mouse over the element.

image.png.e76a2288e61d3f647586e0cf8abba0b3.png

I'm wondering, if that is related to the Intel graphics driver (Intel HD Graphics 4600) and my configuration of it, or if that is a normal effect (which I cannot believe in view of Apples requirement for good looking GUIs).

Did anyone see this effect on his/her hackintosh or even know how to fix it?

Link to comment
Share on other sites

<key>Properties</key>
		<dict>
			<key>PciRoot(0x0)/Pci(0x2,0x0)</key>
			<dict>
				<key>AAPL,ig-platform-id</key>
				<data>
				BgAmCg==
				</data>
				<key>device-id</key>
				<data>
				EgQAAA==
				</data>
				<key>framebuffer-con1-enable</key>
				<data>
				AQAAAA==
				</data>
				<key>framebuffer-con1-pipe</key>
				<data>
				EgAAAA==
				</data>
				<key>framebuffer-con1-type</key>
				<data>
				AAgAAA==
				</data>
				<key>framebuffer-con2-alldata</key>
				<data>
				/wAAAAEAAABAAAAA
				</data>
				<key>framebuffer-con2-enable</key>
				<data>
				AQAAAA==
				</data>
				<key>framebuffer-cursormem</key>
				<data>
				AACQAA==
				</data>
				<key>framebuffer-memorycount</key>
				<data>
				AgAAAA==
				</data>
				<key>framebuffer-patch-enable</key>
				<data>
				AQAAAA==
				</data>
				<key>framebuffer-portcount</key>
				<data>
				AgAAAA==
				</data>
			</dict>
		</dict>

 

Link to comment
Share on other sites

Thanks a lot for the quick reply. As @Hervé stated, I use

AAPL,ig-platform-id        0300220D        DATA

because the the HP EliteDesk 800 G1 is a desktop platform.

Therefor the configuration of @HmO does not work for me. Even after changing APPL,ig-platform-id to 0300220D.

 

Here is my config.plist

config.plist

Edited by jota29
Link to comment
Share on other sites

By the way: my configuration is based on the configuration from @Donw35 in the thread Monterey, Big Sur, Catalina, Mojave, High Sierra on HP 800 G1 USDT,SFF and Tower PC's.

I had to apply some changes. In case of video configuration I made changes to support resolutions higher than 1920x1080 regarding framebuffer memory.

But: Also with the original config from @Donw35 I see the issues with 3d border dithering.

Link to comment
Share on other sites

@jota29

I can propose you to experiment with some additional properties for the IGPU

AAPL00,Dither - expected value 4 bytes zero. Set to <01 00 00 00>?

AAPL,GfxYTile - same

graphic-options - Clover set the property automatically, for example <0c 00 00 00>

 

Link to comment
Share on other sites

1 hour ago, Hervé said:

Some these patches/settings do raise questions

@Hervé, I have to admit, that many of the values in the configuration came from the configs, I just copied from the the discussion in thread  Monterey, Big Sur, Catalina, Mojave, High Sierra on HP 800 G1 USDT,SFF and Tower PC's.

The framebuffer values are the only values, I have read about in the opencore documentation and changed to get the full resolution of my monitor.

 

BUT: Thank you very much for the advice to try a minimalistic configuration.

<key>AAPL,ig-platform-id</key>
<data>AwAiDQ==</data>
<key>hda-gfx</key>
<data>b25ib2FyZC0xAA==</data>  <- OpenCore 7.6 says, this has to be type DATA, not STRING

With this configuration I get the same result, but now my feeling is much better knowing not to change things I don't really understand.

 

Unfortunately, the dithering effects also stayed.

 

I played around with different values for AAPL00,Dither  AAPL,GfxYTile and graphic-options, as @Slice recommended, but without success. Thanks @Slice!

 

Link to comment
Share on other sites

@jota29 What about "9mb cursor bytes" patch?

                <key>framebuffer-cursormem</key>
				<data>
				AACQAA==
				</data>
				<key>framebuffer-memorycount</key>
				<data>
				AgAAAA==
				</data>
				<key>framebuffer-patch-enable</key>
				<data>
				AQAAAA==
				</data>

Maybe this is help you.

Edited by HmO
Link to comment
Share on other sites

Thanks @HmO and @Hervé,

framebuffer-patch-enable    01000000    DATA

I tried that in my original configuration -> no success

 

In combination with

framebuffer-cursormem        00009000        DATA

my computer even doesn't reach the second apple boot logo. Either stalled at the first apple logo (boot-args without -v) or does a reboot at once (boot-args with -v).

 

Link to comment
Share on other sites

  • 2 months later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...