Beginners Guide to using OC Auxiliary Tools App (Also known as OCAT)

[D-an-W]

It is ok to use as long as you check the 'Coverage' with Apple to insure the S/N is not in circulation as one of their own.

I was going through trying to get one to match! Good to know, thanks.

 

[RayEsko]

Why must this be so painful? I have a running system with Catalina and Clover. Should upgrade now to Monterey. Why can't I do this with MultiBeast ? I don't want to learn several days about OC and all that kext and plist stuff ...

Please, please update MultiBeast to support macOS > 11 - please

Have an i5-6400, RX 580 Graphics, nothing special...

Thanks, anyway.

 

[trs96]

I have a running system with Catalina and clover. Should upgrade now to Monterey. Why can't I do this with MultiBeast

Clover only works with Monterey because of a massive debt to OpenCore. Slice borrowed from Acidanthera's code just to be able to even boot Big Sur or newer versions. It wouldn't work otherwise. So if you want to run Monterey OC is mandatory. It's a large part of the latest Clover.

 

[Superbogey]

I've got two 4k monitors running off of my RX 5500 XT and came across this in UEFI/Output/Resolution. Do I now need to add a key in NVRAM to make this work/enable?

 

[Edhawk]

Since the release of OpenCore since 0.7.6 the UIScale key can be found in the UEFI > Output section in the Sample.plist. Default for this entry is '0'.



In older versions of OpenCore 0.7.5 and earlier, there was a NVRAM UIScale entry, as shown below from the Sample.plist from OC 0.6.9
NVRAM > Add > 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14 > UIScale > Data > <01>



If I recall correctly, ocvalidate generates an error when both UIScale keys/entries are present in the config.plist. So adding a NVRAM UIScale entry may not work.

You probably need to use the current UEFI > Output entry, change this number to '2' to see if it makes any difference.

 

[Superbogey]

Since the release of OpenCore since 0.7.6 the UIScale key can be found in the UEFI > Output section in the Sample.plist. Default for this entry is '0'.

View attachment 564651

In older versions of OpenCore 0.7.5 and earlier, there was a NVRAM UIScale entry, as shown below from the Sample.plist from OC 0.6.9
NVRAM > Add > 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14 > UIScale > Data > <01>

View attachment 564652

If I recall correctly, ocvalidate generates an error when both UIScale keys/entries are present in the config.plist. So adding a NVRAM UIScale entry may not work.

You probably need to use the current UEFI > Output entry, change this number to '2' to see if it makes any difference.

Thanks @Edhawk . The instruction I highlighted was a bit confusing. I'll try the UEFI > Output entry you suggested and see how that works.

 

[exquirentibus]

Probably a dumb question .. but .. could I use the Win64 version of OCAT running in a Virtual Machine to see what changes would be made when updating my OC EFI setup?

In other words - for an update will OCAT look at the hardware or can I just have it look at the EFI itself and change OC, kexts etc. to the updated versions?

 

[esafeddie]

In OCAT, you have the choice of updating to the latest OC version as well as all latest kext versions minus any kext you configured, altered or created to suite your machine i.e a USB ports mapped kext. Every thing else can be updated. You can update OC it self or just the kext files or both.
Hope my clumsy explanation is understandable.