With Resolution set to Max, my resolution at boot is really low.
How can I find out what are supported resolutions for Open Core on my monitor and graphics card?
A reliable way is to run the debug mode, then extra the recorded resolutions in the log. Which looks like this
[automerge]1586411740[/automerge]
h9826790 I have installed your lastest OC with boot icons one, so that if I need to add a wallpaper to boot screen, just make a wallpaper e.g. my LG is 5120x2160px wallpaper in Png format and put in icon folder is ok?
Correct, and the files should be named as
background4k.png
, if you want to play safe, you can duplicate that file, and name it
background.png
AFAIK, Ndk 0.1.8 now will check the vertical resolutions, for 2160P monitor, it should load the 4K wallpaper.
[automerge]1586412059[/automerge]
Very strange with my EFI video card. If I boot automatically it only recognizes HFS+ drives and Windows defined in Entries:
View attachment 904589
If I reset NVRAM first and only first boot it recognizes APFS drives as well:
View attachment 904590
Every subsequent reboot, only WIN Entries and HFS+ drives/paths are recognized. I even tried to specify APFS loader in Entries. It appears there, but does not load. The only way to boot an APFS with the EFI card alongside the original card is when I hold option at boot and hit enter to OC bootloader. But automatically it only works the first time after NVRAM reset.
On my first boot with OC 0.5.7 (official release) + Ndk 0.1.8 (official release), the Windows option is missing.
I then disable Ndk for trouble shooting. All entries shows up in the native OC boot picker.
Then I re-enable Ndk, everything works flawless since then.
I am not sure if my issue is related to yours. I haven't done any reset. All I did is just change the picker mode from
External
to
Builtin
+ reboot, then the problem fixed by itself.
Since it only happened on one boot, and that's the very first boot. Therefore, I really don't know if that's OC's bug, or Ndk's bug, or my SSD wan't recognised on that particular boot, etc.
Anyway, is this also happen in 0.5.7? or only pops up after you update to 0.5.8 beta?