EggToaster
commented
3 weeks ago The part that says "injects Clover properties" are completely right, and not all configurators are equal. We count OCAT as configurators and that has broke some config in past, so no I just saw a person who changed their SMBIOS to be compatible with Sonoma, but it did not work for some reason, probably because of OCC. The biggest part is, why configurators? ProperTree always works. Another big part is, everybody has different experience. You can't say it's good because it :worksonmymachine:.
SeverusSnape799
Guide: OpenCore Install Guide
Pages with the issue:
First, please understand I am not saying there is anything intentional occurring here. I am using the exact definition of the word and do not intend for any additional connotation to be attached. The definition of misinformation is simply information that is false or inaccurate, but not deliberately so. When done deliberately, it is no longer misinformation, but rather disinformation.
Some further context to give my experiences a bit more weight:
I have been hackintoshing since the Clover days, many years now. Over the years, I have made a few modest contributions to the hackintosh community which include:
xcpm_ipikernel flagSSDT-CPU-WRAP.dslfix, which eventually lead to others creating the far more compact and efficientSSDT-CPUR.dslfix.My intent is not to brag and like I said, these contributions are modest and generally quite niche. My intent is to demonstrate that I have been active in the community for many years and am capable enough to solve previously unsolved problems then share that with the community.
I have been using OpenCore since version ~0.6, and I regularly update it upon every new release for over 2 years now.
During those two years, I have been using Mackie's OpenCore Configurator exclusively to manage my config.plist files.
In those two years:
The following false assertions in this guide are as follows:
The claims about OpenCore Configurator have not been true for at least 2 years which makes their continued inclusion in the guide a form of misinformation. Even if these claims were at one point true, this is no different from any other software project in early stages of development. Singling out this tool by perpetuating myths about bugs that were fixed long ago is unfair to the developer and a disservice to the target audience of the guide by turning them away from what is now an excellent tool.
A tool that is far safer than any sort of semi-manual editing using tools like Plistbuddy, as it removes the possibility of human error, incorporates as much as it can directly from OpenCore itself (documentation, configuration settings, validation of those settings etc.). It warns the user if their plist is meant for a different version of OpenCore than they have installed. It has built-in update support so using an outdated version is not really a risk.
It is even in-line with Dortania's own goals. Dortania wants people to actually learn what is going on rather than just doing things by copying them from somewhere else without understanding what any of it does or means. OpenCore Configurator facilitates learning and understanding by making it easy to mouse over each and every setting and read all about what it is, what it does, and if/when it might be needed. No more blind toggling of mystery settings. Not even this guide provides a complete description of every setting, only a handful that are usually the minimum needed, but not all systems are so easy.
Frankly, what would be the most beneficial to users of this guide, in my opinion, would be not only to remove the false statements, but accurately mention Open Core Configurator has long since corrected past issues with corruption etc, and recommend it as an easier and safer alternative to manual editing using Plistbuddy. An alternative that incorporates OpenCore's own config validation, finding any configuration problems as they're made. This does not mean to say it should be officially supported, I agree it should not be. The guide should remain as generic as possible and not rely on custom tools, but all of the guide's instructions are easily and intuitively done in OpenCore Configurator, so suggesting it as a viable but unsupported alternative is still worthwhile.
However, at the very minimum, the false statements should be removed from the guide. I feel like this is a case of some bugs in the past propagating like old wives' tales or myths as many bits of information seem to do in the hackintosh community, an effect that this guide was, amongst other things, meant to combat. How often do you see people putting ancient boot flags in their config.plist because of what amounts to digital superstition? And how is this any different?
I would encourage the authors to download Open Core Configurator and (with an open mind free of preconceptions) reevaluate it for themselves, as it really has become a very mature, safe, and reliable tool no matter how bumpy its development have been at the beginning.