Bit depth of your bmp should be 32, i couldn't make it to work too at first when i tried to make my own icons, was saving them as 24 bit depth bmp and nyx didn't see them... As for the logo path, if im not mistaken it's for the boot logo.I cant get the custom icons to show in the launch menu, it keeps using the default ones.
Here is my hekate_ipl.ini inside the bootloader folder.
Code:[config] autoboot=0 autoboot_list=0 bootwait=3 verification=1 backlight=100 autohosoff=0 autonogc=1 [Atmosphere] fss0=atmosphere/fusee-secondary.bin kip1patch=nosigchk atmosphere=1 logopath=bootloader/res/atmosphere.bmp icon=bootloader/res/atmosphere.bmp [Stock] fss0=atmosphere/fusee-secondary.bin stock=1 icon=bootloader/res/atmosphere.bmp [Atmosphere-emuMMC] payload=bootloader/payloads/fusee-primary.bin icon=bootloader/res/atmosphere-emc.bmp
all assets and files are inside the correct folder. So why wont hekate find them?
Also what is the difference between Icon and logo path?
I thank you, in the end I did as you saidNot sure with the new method.
But with the "first gen" of emunand settings you could change
emummc_nintendo_path = EmuNAND<-- to whatever you want!
Bit depth of your bmp should be 32, i couldn't make it to work too at first when i tried to make my own icons, was saving them as 24 bit depth bmp and nyx didn't see them... As for the logo path, if im not mistaken it's for the boot logo.
Can anyone upload the Atmosphere logo in bmp 32 bit? Paint doesn't support bmp 32bit...
I believe so.would it be possible to use sxos launcher to create a hidden partition in the sd?
I assume theres no fuses risk involved when using emummc right?
Is there a reason I may not want to use the Nyx GUI? Is everything done while in Hekate prior to detectable/bannable activity? I still have AutoRCM from way back and have been using stock firmware (except to manually update firmware from 5.1.0 to 7~something, then to 8.0.1). In other words, if I was still okay (not banned) for having AutoRCM, having booted Atmosphere twice for manual updates, and using stock firmware until now, is there anything about the new Hekate that will flag my system and add to the ban potential?
The core of hekate is largely the same, it added support for new atmos and emuemmc stuff, nyx is a module, you can remove it from the sys dir and use the old text interface if you wanted to. There isn't any risk of hekate getting you banned, same with autorcm.
[CFW]
fss0=atmosphere/fusee-secondary.bin
kip1patch=nosigchk
atmosphere=1
logopath=bootloader/bootlogo.bmp
{ }
[Stock]
fss0=atmosphere/fusee-secondary.bin
stock=1
{ }
Thank you for the reply. With the addition of emuMMC support, do I need to add a line to disable it (if I read correctly, it's enabled by default).
I'm not looking to change my Hekate setup at all... I just want the added support for 8.1.0 so I can safely update.
Here are the relevant lines of my current config:
Code:[CFW] fss0=atmosphere/fusee-secondary.bin kip1patch=nosigchk atmosphere=1 logopath=bootloader/bootlogo.bmp { } [Stock] fss0=atmosphere/fusee-secondary.bin stock=1 { }
Do I need to add/change anything? I'm just looking to boot Atmosphere to update without burning fuses, then continue using stock firmware as I have been.
same I want it tooI cant find this background.bmp in the github repo, can someone share it?