[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

[kwalter]

I'm glad!

That's because your settings are different. To test Unigine Valley (or Heaven) I use a Custom preset with every possible setting maxed out. That includes Vsync ON, Antialiasing ON (x8), Maximum resolution (that you got right, it's 2160x1440) and Ultra Quality.

Mine settings:

View attachment 419504

Your settings:

View attachment 419505

Try again with different settings,

Cheers!

Yes, that's more like the comparison I expected
Cheers

 

[BarryNance]

Casey and everyone else -- thanks for the clear, comprehensive guide and the tons of helpful information on what works and what doesn't. You've made building my new "Macintosh" fairly simple and easy. My hat's off to you.

 

[Psyvire]

I purchased it as soon as it was announced. It will be delivered on Friday. Stay tuned.

I'm very interested in hearing the result of this, good luck! I have an i9 9900K, I've ordered a Z390 DESIGNARE, and have a similar 8GB RX 580, so if your tests prove fruitful I will also order a 5K UltraFine

Are you dual booting with Windows? I am interested to know how/if Windows handles it!

 

[Pete141]

guys,

Any idea how to fix Preview? Can't open any photos . Tried to follow the Framebuffer guide but its not as clear as Casey's. I'm kind of stuck...

 

[CaseySJ]

guys,

Any idea how to fix Preview? Can't open any photos . Tried to follow the Framebuffer guide but its not as clear as Casey's. I'm kind of stuck...

Preview, Quick Look, H.264, HEVC, etc. can depend on the combination of (a) SMBIOS name, and (b) IGPU status. For example:

• If using iMac19,1 or MacMini8,1 we should ideally set IGPU to headless platform ID 0x3E980003 with Mojave 10.14.6 and omit "device-id". Latest versions of Mojave support the 9th Gen iGPU natively so there's no need to spoof the device-id.
  • In BIOS, IGPU should be enabled.

Please let us know:

• Which version of macOS you're running.
• What "AAPL,ig-platform-id" you currently have.
• What SMBIOS name you're current using.

All of this information is embedded in the IOReg file which you can generate by downloading and running IORegistryExplorer and selecting File --> Save As... You may upload that file.

 

[nifranza]

Preview, Quick Look, H.264, HEVC, etc. can depend on the combination of (a) SMBIOS name, and (b) IGPU status. For example:

• If using iMac19,1 or MacMini8,1 we should ideally set IGPU to headless platform ID 0x3E980003with Mojave 10.14.6 and omit "device-id". Latest versions of Mojave support the 9th Gen iGPU natively so there's no need to spoof the device-id.
  • In BIOS, IGPU should be enabled.

Please let us know:

• Which version of macOS you're running.
• What "AAPL,ig-platform-id" you currently have.
• What SMBIOS name you're current using.

All of this information is embedded in the IOReg file which you can generate by downloading and running IORegistryExplorer and selecting File --> Save As... You may upload that file.

Hey @CaseySJ, hope you're having a good day! Just being curious: Why is it necessary to avoid device-id when implementing iGPU in headless mode?

I just ask because I noticed mine is [not-avoided] (if that's a word..) and I have not been having any noticeable issues. I guess I must have skipped the part where you said that. Sorry!

 

[CaseySJ]

Hey @CaseySJ, hope you're having a good day! Just being curious: Why is it necessary to avoid device-id when implementing iGPU in headless mode?

I just ask because I noticed mine is [not-avoided] (if that's a word..) and I have not been having any noticeable issues. I guess I must have skipped the part where you said that. Sorry!

View attachment 419604
View attachment 419605

In this case there’s no issue because the real device ID is the same as what you’ve entered. In general, though, it’s better to let macOS detect and inject the appropriate properties. The less we “interfere” with macOS, the better!

 

[nifranza]

In this case there’s no issue because the real device ID is the same as what you’ve entered. In general, though, it’s better to let macOS detect and inject the appropriate properties. The less we “interfere” with macOS, the better!

Haha! I love that vanilla spirit!

Cheers!

 

[suteapod]

It is Asus. This is new. Need to introduce EmuVariableUefi-64? My GPU worked fine in the previous state of your presentation. It is likely that something changed in the SSDT and drivers64UEFI folder is causing the problem. Or Config-prist?

I removed EmuVariableUefi-64 and replaced Config-prist with the one I created. Also, I added SSDT-Z390-VEGA64.aml just in case. As a result, sleep and wake problems have been fixed. Thank you. However, I can not yet determine if the random freeze problem I initially feared has been fixed.

 

[Pi3rre]

Can anyone tell me if my graphic card is installed in PCI Slot 1 or PCI Slot 2 ?