Hacking Share your custom Atmosphere (fusee-secondary) bootlogos.

[JayBae]

why is there not a normal way to replace the atmosphere logo? I replaced the hekate one easy enough... But I cannot figure out how to replace the Atmosphere one...

 

[BaamAlex]

You have to "inject" it into the package2. Pretty easy when you know how it is done

Send me your bootlogo and i (or someone else) do that for you.

 

[Hayato213]

why is there not a normal way to replace the atmosphere logo? I replaced the hekate one easy enough... But I cannot figure out how to replace the Atmosphere one...

Lmao Blame SciresM lol

Custom splash screen BMP parsing is no longer supported (as it slows down boot for 99% of users).

• To compensate for this, a script to insert a custom splash screen into a package3 binary has been added to the utilities folder of the atmosphere repository.

Another thing he changed in 1.0.0 changelog, the other thing you question about BCT.ini

 

[JayBae]

Lmao Blame SciresM lol

Custom splash screen BMP parsing is no longer supported (as it slows down boot for 99% of users).

• To compensate for this, a script to insert a custom splash screen into a package3 binary has been added to the utilities folder of the atmosphere repository.

Another thing he changed in 1.0.0 changelog, the other thing you question about BCT.ini

thamx this was helpful!

 

[Purple_Heart]

can someon

e inject this into a package 3 file? if i try it myself then it doesnt patch it. still have the stock ams boot logo

 

[BaamAlex]

Convert it correctly as a bmp for hekate.

 

[Purple_Heart]

here

 

[zamastyle]

Hijacked a nice enough background from google. Cleaned it up and tacked in some prompts. Needed something that looked decent on a switch and reminded users how to get to hekate settings because I was getting a lot of "i forgot how to..." texts

 

[wavedotwav]

made this for fun when i was updating atmosphere for the hell of it. art is by @1TZAH on twitter!

 

[laz305]

made this for fun when i was updating atmosphere for the hell of it. art is by @1TZAH on twitter!View attachment 428647

nice, do you have a matching background?

Post automatically merged: Mar 31, 2024

Lmao Blame SciresM lol

Custom splash screen BMP parsing is no longer supported (as it slows down boot for 99% of users).

• To compensate for this, a script to insert a custom splash screen into a package3 binary has been added to the utilities folder of the atmosphere repository.

Another thing he changed in 1.0.0 changelog, the other thing you question about BCT.ini

Oooooo how do we do that?

• insert a custom splash screen into a package3

 

[Frok]

Custom splash screen BMP parsing is no longer supported (as it slows down boot for 99% of users).

How to spoil something that was perfectly working.
I've not the competence to install/use/understand-what-is Python.

 

[Hayato213]

nice, do you have a matching background?

Post automatically merged: Mar 31, 2024

Oooooo how do we do that?

How to spoil something that was perfectly working.
I've not the competence to install/use/understand-what-is Python.

You guys can refer to this post.

https://github.com/Atmosphere-NX/Atmosphere/blob/master/docs/features/configurations.md

Adding a Custom Boot Splashscreen​

Atmosphère provides its own default splashscreen which is displayed at boot time. However, this can be replaced at will.

Boot splash screens must be 1280x720 resolution.
(this size will be the full screen logo shared above…not the little one…the little image is for the IPs patch version)

A script can be found inside the source tree (/utilities/insert_splash_screen.py) for inserting a custom splash screen into a release binary.

To do so, execute the following command on the script: python insert_splash_screen.py <path to your splash screen image> <path to /atmosphere/package3 on your SD card>

Like so:
python insert_splash_screen.py sodabootsplash.png package3

Need to have python3 installed and download this utility:
https://github.com/Atmosphere-NX/Atmosphere/blob/master/utilities/insert_splash_screen.py

I typically copy the image and a clean copy of package3 into the same directory as the Python utility. Once I have my new package3 I backup my original and move the new one in its place.

 

[Frok]

You guys can refer to this post.

Yes, saw it, thanks. But it seems over complicated.