Jump to content

Customized OpenCore with additional features


n.d.k
1,348 posts in this topic

Recommended Posts

1 minute ago, Ellybz said:

Compile the Debug version of OC and make sure in your config/Misc/Debug your target is 67.

Log file will be in your EFI upon reboot.

 

Thanks :)

 

I can keep BOOTX64 release? 

Link to comment
Share on other sites

Do you think ii would be a good idea to have a future release with a circle around the icon ( Instead of a square ). Changing the background color does not allow to get rid of that black inner-filing between the square and Icon..Picture below.

pic.png

3 minutes ago, Matgen84 said:

 

Thanks :)

 

I can keep BOOTX64 release? 

Sure why not.  I usually change everything and save each EFI in a different Drive ( USB backup ). So I can access both at any given time.

  • Like 1
Link to comment
Share on other sites

49 minutes ago, Ellybz said:

Compile the Debug version of OC and make sure in your config/Misc/Debug your target is 67.

Log file will be in your EFI upon reboot.

 

You can find debug boot log for my Z390 Aorus Master in attachment.

Note: I test NDK-OC from USB pendrive.

 

opencore-2020-02-04-075153.txt

Edited by Matgen84
Link to comment
Share on other sites

3 hours ago, Matgen84 said:

 

Thanks :)

 

I make a try by re-compiling NDK-OC:

 

  • Big icons ----> SOLVED
  • Low Resolution ---> NOT SOLVED (Icons + Text under icons)
  • distortion of icons: oval instead of round

 

I can't send you a screenshot because there isn't daylight (the flash cancels the colors). 

 

In attachment my config.plist if I've made a mistake!

config.plist

I just want to add that I have the same problem and in my case the LCD resolution in bootpicker is fine, but boootpicker's graphics is scaled so it looks like low resolution.

If we can disable this scaling, i think it will be ok.

Edited by darthsian
  • Like 1
Link to comment
Share on other sites

5 hours ago, Matgen84 said:

 

You can find debug boot log for my Z390 Aorus Master in attachment.

Note: I test NDK-OC from USB pendrive.

 

opencore-2020-02-04-075153.txt

 

this is not good "2:245 00:051 OCABC: No slide values are usable! Falling back to 0 with 0x173F2000 bytes!"

 

btw: last time I ran into trouble not loading OC cos BOOTx64 was from an older version. It doesn't cost anything to copy this file always

 

  • Like 1
Link to comment
Share on other sites

7 minutes ago, texem said:

 

this is not good "2:245 00:051 OCABC: No slide values are usable! Falling back to 0 with 0x173F2000 bytes!"

 

btw: last time I ran into trouble not loading OC cos BOOTx64 was from an older version. It doesn't cost anything to copy this file always

 

 

Maybe because I use debug OC version with BOOTX64 release? What do you think!

Link to comment
Share on other sites

4 minutes ago, texem said:

 

always copy OpenCore.efi, FWRuntimeServices.efi and BOOTX64 from your latest compilation

 

 

I know that.

 

@n.d.k asks to me to use debug file for test GUI Picker, not working fine on my Z390 Aorus Master, Bro

Link to comment
Share on other sites

7 hours ago, Ellybz said:

Do you think ii would be a good idea to have a future release with a circle around the icon ( Instead of a square ). Changing the background color does not allow to get rid of that black inner-filing between the square and Icon..Picture below.

pic.png

Sure why not.  I usually change everything and save each EFI in a different Drive ( USB backup ). So I can access both at any given time.

 

Usually, Icons are designed for certain theme, if you look at the Clover Theme package, they usually have a background and selection images attached to their designed icons, so it looks right on the screen.  For now, only black color look good all icons, that may changed in the future if I am gonna make it's compatible with Clover's themes.

 

It's still looking good with square black box though...:)

Edited by n.d.k
  • Like 1
Link to comment
Share on other sites

1 hour ago, n.d.k said:

 

Usually, Icons are designed for certain theme, if you look at the Clover Theme package, they usually have a background and selection images attached to their designed icons, so it looks right on the screen.  For now, only black color look good all icons, that may changed in the future if I am gonna make it's compatible with Clover's themes.

 

It's still looking good with square black box though...:)

Using a box to select an icon is not as nice as using a small Arrow under the icon to select the icon!

If OC uses clover's theme, it will look like clover!

  • Like 2
Link to comment
Share on other sites

1 hour ago, btwise said:

Using a box to select an icon is not as nice as using a small Arrow under the icon to select the icon!

If OC uses clover's theme, it will look like clover!

 

What!, a good looking theme is a good looking theme regardless if it was designed for Clover or not, I will not discriminate whether it's Clover or OC, Of course, any Clover logo badges will not be used. If it wasn't for Clover, this OC UI would be impossible, some of the Clover's UI code or refit's was used by for this OC UI's project. 

Link to comment
Share on other sites

25 minutes ago, n.d.k said:

New commit should take care of your low resolution, since we are switching to GUI, I forgot that I need to set resolution screen to Max before loading the GUI boot picker.

 

Thanks :) Now your GUI Picker works in UEFI mode: no more low resolution. The icons are a bit pixelated on the outline. the shape smoothing is missing.

I have to check them.

 

 

1.jpg

Link to comment
Share on other sites

5 minutes ago, Ellybz said:

Being able to upload your your own background would be Aaaaamazing :P 

Screen Shot 2020-02-04 at 10.21.50 AM.png

 

It's easily doable but, it will create a delay effect when loading the background image, especially if it's high resolutions screen. I tried, it's kinda annoying effect.

  • Like 2
Link to comment
Share on other sites

39 minutes ago, mathew2019 said:

Does any one able to use Apple Hot Keys? if so how?

 

I never tried to see if it work, but for CMD+OPT+P+R, CMD+R, they need to be pressed and hold before the boot picker show up, for all other apple hotkeys you need to fist select the entry then press the hotkeys combination instead of Enter key or Index key.

Edited by n.d.k
Link to comment
Share on other sites

NDK,

 

I downloaded latest commit and compiled. When running debug version, boot halted with ASSERT error. I've not seen this error before (in fact, I've never seen any errors appear before in this project). Included are some earlier resolution comments as FYI. For this compile, I'd not edited any files and only used your stock icons.

 

I see you added OcClearScreenArea to function PrintOcVersion in OcSimpleBootMenu.c with this latest commit. PrintOcVersion calls AsciiStrCopyToUnicode (from OcAsciiLib.c) and maybe this led to the ASSERT error since OcClearScreenArea is an 'else' statement and String might = NULL. (Trying to be helpful, but I probably don't know what I'm talking about.)

 

Spoiler

08:514 00:001 OCB: Performing OcShowSimpleBootMenu... 0 - 7 entries found
08:516 00:001 OCB: BootNext has not been found
08:518 00:001 OCB: BootOrder is unavailable - Not Found
08:519 00:001 OCB: Initial default is 0, fallback
08:521 00:001 OCSBM: FileSystem Found!
08:522 00:001 OCC: Requesting 480x113 (max: 0) console mode, curr 3, max 4
08:524 00:001 OCC: Mode 0 - 80x25
08:525 00:001 OCC: Mode 1 - 128x40
08:527 00:001 OCC: Mode 2 - 100x31
08:529 00:002 OCC: Mode 3 - 480x113
08:530 00:001 OCC: Current console mode matches desired mode 3, forcing update
08:532 00:001 OCC: Setting mode 3 (prev 3) with 480x113 console mode
09:125 00:592 OCC: Changed console mode to 3
09:126 00:001 OCSBM: Resetting console mode to 480x113 - Success
09:708 00:581 OCC: Requested resolution is 0x0@0 (max: 1) from Max
09:709 00:001 OCC: Requesting 0x0@0 (max: 1) resolution, curr 0, total 8
09:711 00:001 OCC: Mode 0 - 3840x2160:1
09:712 00:001 OCC: Mode 1 - 640x480:1
09:714 00:001 OCC: Mode 2 - 800x600:1
09:715 00:001 OCC: Mode 3 - 1024x768:1
09:717 00:001 OCC: Mode 4 - 1280x1024:1
09:718 00:001 OCC: Mode 5 - 1400x1050:1
09:720 00:001 OCC: Mode 6 - 1600x1200:1
09:721 00:001 OCC: Mode 7 - 1280x960:1
09:723 00:001 OCC: Current mode matches desired mode 0
09:725 00:001 OCC: Changed resolution to 0x0@0 (max: 1) from Max - Success
09:726 00:001 OCUI: Initialize Graphic Screen...Success
09:728 00:001 OCUI: Initialize HiiFont...Success
09:729 00:001 OCC: Configuring behaviour 2
09:731 00:001 OCUI: Set ConsoleControlGraphic...Success
09:732 00:001 OCUI: Got system fontsize - w:8xh:19
10:895 01:162 OCUI: Clearing Graphic Screen Area...Success
10:896 00:001 ASSERT [OpenCore] /Users/~/OpenCorePkg-master/edk2/OcSupportPkg/Library/OcStringLib/OcAsciiLib.c(74): AsciiString != ((void *) 0)

 

Edited by iGPU
  • Thanks 1
Link to comment
Share on other sites

1 hour ago, iGPU said:

NDK,

 

I downloaded latest commit and compiled. When running debug version, boot halted with ASSERT error. I've not seen this error before (in fact, I've never seen any errors appear before in this project). Included are some earlier resolution comments as FYI. For this compile, I'd not edited any files and only used your stock icons.

 

I see you added OcClearScreenArea to function PrintOcVersion in OcSimpleBootMenu.c with this latest commit. PrintOcVersion calls AsciiStrCopyToUnicode (from OcAsciiLib.c) and maybe this led to the ASSERT error since OcClearScreenArea is an 'else' statement and String might = NULL. (Trying to be helpful, but I probably don't know what I'm talking about.)

 

  Reveal hidden contents

08:514 00:001 OCB: Performing OcShowSimpleBootMenu... 0 - 7 entries found
08:516 00:001 OCB: BootNext has not been found
08:518 00:001 OCB: BootOrder is unavailable - Not Found
08:519 00:001 OCB: Initial default is 0, fallback
08:521 00:001 OCSBM: FileSystem Found!
08:522 00:001 OCC: Requesting 480x113 (max: 0) console mode, curr 3, max 4
08:524 00:001 OCC: Mode 0 - 80x25
08:525 00:001 OCC: Mode 1 - 128x40
08:527 00:001 OCC: Mode 2 - 100x31
08:529 00:002 OCC: Mode 3 - 480x113
08:530 00:001 OCC: Current console mode matches desired mode 3, forcing update
08:532 00:001 OCC: Setting mode 3 (prev 3) with 480x113 console mode
09:125 00:592 OCC: Changed console mode to 3
09:126 00:001 OCSBM: Resetting console mode to 480x113 - Success
09:708 00:581 OCC: Requested resolution is 0x0@0 (max: 1) from Max
09:709 00:001 OCC: Requesting 0x0@0 (max: 1) resolution, curr 0, total 8
09:711 00:001 OCC: Mode 0 - 3840x2160:1
09:712 00:001 OCC: Mode 1 - 640x480:1
09:714 00:001 OCC: Mode 2 - 800x600:1
09:715 00:001 OCC: Mode 3 - 1024x768:1
09:717 00:001 OCC: Mode 4 - 1280x1024:1
09:718 00:001 OCC: Mode 5 - 1400x1050:1
09:720 00:001 OCC: Mode 6 - 1600x1200:1
09:721 00:001 OCC: Mode 7 - 1280x960:1
09:723 00:001 OCC: Current mode matches desired mode 0
09:725 00:001 OCC: Changed resolution to 0x0@0 (max: 1) from Max - Success
09:726 00:001 OCUI: Initialize Graphic Screen...Success
09:728 00:001 OCUI: Initialize HiiFont...Success
09:729 00:001 OCC: Configuring behaviour 2
09:731 00:001 OCUI: Set ConsoleControlGraphic...Success
09:732 00:001 OCUI: Got system fontsize - w:8xh:19
10:895 01:162 OCUI: Clearing Graphic Screen Area...Success
10:896 00:001 ASSERT [OpenCore] /Users/~/OpenCorePkg-master/edk2/OcSupportPkg/Library/OcStringLib/OcAsciiLib.c(74): AsciiString != ((void *) 0)

 

 

Good catch, Thanks, ya it would create assert error if Oc Version wasn't allowed to show, it's fixed now.

Edited by n.d.k
  • Like 2
Link to comment
Share on other sites

2 hours ago, n.d.k said:

 

Good catch, Thanks, ya it would create assert error if Oc Version wasn't allowed to show, it's fixed now.

how to disable PrintOCVersion?Your updated code will display REL-2020-2 in the lower right corner by default!Just press the space bar when the display is very good effect

Link to comment
Share on other sites

×
×
  • Create New...