BCT.ini is needed if you launch fusee-primary.Documentation on Atmosphere is extremely sparse, apparently, so i'll ask here since hekate is my go-to bootloader.
How do i go about using Hekate + Atmosphere? Do i start it via secondary payload, or do i chainload the primary or what? Do i need the BCT.ini if i load via Hekate? Can i use any of the Hekate patches together with Atmo?
Would a proper boot entry look like this?
[Atmosphere]
payload=fusee-primary.bin
If you launch atmosphere from kips/exo you need to create an .ini boot entry for hekate to launch
logopath key is only for boot entries. If you want to change bootlogo for all boot entries, you put it at bootloader/bootlogo.bmpAny idea why custom bootlogo Not work with my setup?
A use the Atmosphere "bootlogo.bmp" and put it on the root of my sd card...
In /bootloader/hekate.ipl ini i add/change under Config:
customlogo=1
logopath=/bootlogo.bmp
... But on every start/Restart the hekate boot Logo pops up?
If you want only for a specific entry, you put it the logopath key at its entry. Also the first slash is not needed (logopath=bootlogo.bmp)
(Also the customlogo=1 is needed at the config entry)