Homebrew Discussion Can we please relax with the Boot logos?

  • Thread starter Thread starter pman152
  • Start date Start date
  • Views Views 17,457
  • Replies Replies 111
  • Likes Likes 3
I’ve tested everything I claimed in my previous post. So uh

Well, you are right that boot images themselves, do not "add time", but these bits of code do:

Sept-Secondary
/* Wait a while. */
mdelay(1500);

fusee-primary
/* Wait a while. */
mdelay(1000);

fusee-secondary
void splash_screen_wait_delay(void) {
/* Ensure the splash screen is displayed for at least three seconds. */
udelay_absolute(g_splash_start_time, 3000000);

This is also implies added wait in boot_main:
/* Display splash screen for two seconds. */
boot::ShowSplashScreen();

You say nothing of significance in regards to these bits. So uh, are we supposed to just take your word for it?

I looked at the code, I got no idea how long it takes the Switch todo whatever it does BEFORE showing the screen. So it still looks to me it's doing stuff in the background while the logo is being shown. Yes I have indeed read the source code now. Since Zach has been here forever and helped the community a lot. I do take his word for it as well. If people still wish, just remove or edit the timer and see if it makes any difference.
 
The total time taken is because you are chainloading fusee-primary which takes eons to load. Try just loading CFW with only Hekate. You can specify fusee-secondary as an fss0 in a hekate ini and it skips all of the fusee waiting nonsense.
 
Last edited by noahc3,
  • Like
Reactions: tabzer
Your right, boot time is much, much faster with no-delay, auto-boot hekate.
For your convenience also replace Reboot_Payload.bin with hekate_5.0.bin
 
I looked at the code, I got no idea how long it takes the Switch todo whatever it does BEFORE showing the screen. So it still looks to me it's doing stuff in the background while the logo is being shown. Yes I have indeed read the source code now. Since Zach has been here forever and helped the community a lot. I do take his word for it as well. If people still wish, just remove or edit the timer and see if it makes any difference.

More BS. Thanks for nothing. I know Zach is helpful and better at technicalities than you. That's why I asked him and not you.
 
Last edited by tabzer, , Reason: "a" word
More BS. Thanks for nothing. I know Zach is helpful and better at technicalities than you. That's why I asked him and not you.
You seem very upset, for a really trivial issue. Thankfully I can read code, however both write it :p
 
  • Like
Reactions: Dichotomy754
Well, you are right that boot images themselves, do not "add time", but these bits of code do:

Sept-Secondary
/* Wait a while. */
mdelay(1500);

fusee-primary
/* Wait a while. */
mdelay(1000);

fusee-secondary
void splash_screen_wait_delay(void) {
/* Ensure the splash screen is displayed for at least three seconds. */
udelay_absolute(g_splash_start_time, 3000000);

This is also implies added wait in boot_main:
/* Display splash screen for two seconds. */
boot::ShowSplashScreen();

You say nothing of significance in regards to these bits. So uh, are we supposed to just take your word for it?
I played around with the ones in fusee-primary and fusee-secondary that you mentioned. Fusee-primary appeared to be a bit faster, and fusee-secondary didn't change at all. The boot one is there to match Nintendo's behavior so I didn't mess with it, and I can't mess with the sept one.
 
Progress being made
Ask and you shall receive.

Atmosphere 0.9.3 changelog:

Thanks to hexkyz, fusee's boot sequence has been greatly optimized.
  • Memory training is now managed by a separate binary (fusee-mtc, loaded by fusee-primary before fusee-secondary).
  • Unnecessarily long splash screen display times were reduced.
  • The end result is that Atmosphere now boots significantly faster. :)
  • Note: This means fusee-primary must be updated for Atmosphere to boot successfully.
 
  • Like
Reactions: Bedel
I attempted to remove all boot logos from atmosphere some time ago. Got them all off except sept's but dropped the whole thing while trying to compile.
I never got 20s of boot logos though, not even combined.
It would be nice if I can insert the original logos in too.
 
it would be great if we can encapsulate all the boot logos with a small boot animation.
do you know when you start a game, on the bottom right corner you have a small logo animation..
I mean something like that.
All the applications theoretically run in background... like sept... fusee primary...
 
Last edited by toxic9,
it would be great if we can encapsulate all the boot logos with a small boot animation.
do you know when you start a game, on the bottom right corner you have a small logo animation..
I mean something like that.
All the applications theoretically run in background... like sept... fusee primary...
As far as I can remember, they are diferent programs with their own logos and wait times. That could be done if one same program executed those and all the waits, but not the way it's right now.
 
As far as I can remember, they are diferent programs with their own logos and wait times. That could be done if one same program executed those and all the waits, but not the way it's right now.

That's what I meant.
A single payload that executes all other payloads on the background showing a single boot animation over all.
 
  • Like
Reactions: Bedel
A single payload that executes all other payloads on the background showing a single boot animation over all.

I'm not sure if that's technically possible, but I know that SciresM wouldn't want to take the sept one out as he still seems to think TX would use it if he did.
 
I'm not sure if that's technically possible, but I know that SciresM wouldn't want to take the sept one out as he still seems to think TX would use it if he did.

TX might use sept right now. like on my idea, they can run sept in background and you only see SX bootlogo.
I would like to see anything similar in atmosphere. clean all that bootlogo sequence. one for all.
and if possible, an animation instead of a static image.
 
Last edited by toxic9,
If it's a product you are NOT paying for, you do NOT have a right to complain.

WRONG, just because something is free or open source doesn't mean you don't have the right to complain. This is some dumb ass logic.

Also since its open source, its good to critique it so that it improves.
 
  • Like
Reactions: Xiphiidae

Site & Scene News

Popular threads in this forum