Homebrew [SUPPORT] The BootCTR9 support thread

@RednaxelaNnamtra

I give up, after 5-6 tries I always get the same error about the config file. I only changed the default section and left everything else untouched.

;luma with BootAnimation and enabled Pathfix
[DEFAULT]
path = /luma.firm
delay = 1000
splash = 4
splash_image = /anim/0
screenBrightness = 0x30
enablePathFix = 1

I have BootCTR9 as boot.firm on the root
I renamed Luma's firm file to luma.firm and on the root
The 0 in the config is actually the animation file which has no file extension. So it's true to it's path there.

I tried placing boot_config.ini on the root since its one of the supported folders. Then I tried placing it in the boot9strap folder and still the same error comes up. Please, some direction would be nice. I can't believe I'm going through this much trouble for an animation that I used to like having.
 
@RednaxelaNnamtra

I give up, after 5-6 tries I always get the same error about the config file. I only changed the default section and left everything else untouched.

;luma with BootAnimation and enabled Pathfix
[DEFAULT]
path = /luma.firm
delay = 1000
splash = 4
splash_image = /anim/0
screenBrightness = 0x30
enablePathFix = 1

I have BootCTR9 as boot.firm on the root
I renamed Luma's firm file to luma.firm and on the root
The 0 in the config is actually the animation file which has no file extension. So it's true to it's path there.

I tried placing boot_config.ini on the root since its one of the supported folders. Then I tried placing it in the boot9strap folder and still the same error comes up. Please, some direction would be nice. I can't believe I'm going through this much trouble for an animation that I used to like having.

You can at least get your 3DS to boot if you remove everything else but:

[DEFAULT]
path = /luma.firm
delay = 1000
splash = 4
splash_image = /anim/0
screenBrightness = 0x30
enablePathFix = 1

That includes removing the ;luma with BootAnimation and enabled Pathfix line
Keep the boot_config.ini file on the root. However, I'm having trouble still anyway, my 3DS will boot up by having it set up in the same way you do with the boot_config.ini file setup as I have it there, but no boot animation will load despite an anim file in the anim/0 directory.

So I dunno what I'm missing but I can at least boot with this method, but that's not what I'm looking for, so for now I have reverted until I figure out what I might be missing.
 
You can at least get your 3DS to boot if you remove everything else but:

[DEFAULT]
path = /luma.firm
delay = 1000
splash = 4
splash_image = /anim/0
screenBrightness = 0x30
enablePathFix = 1

That includes removing the ;luma with BootAnimation and enabled Pathfix line
Keep the boot_config.ini file on the root. However, I'm having trouble still anyway, my 3DS will boot up by having it set up in the same way you do with the boot_config.ini file setup as I have it there, but no boot animation will load despite an anim file in the anim/0 directory.

So I dunno what I'm missing but I can at least boot with this method, but that's not what I'm looking for, so for now I have reverted until I figure out what I might be missing.
splash_image needs to specifically point to the anim file, not just the path. Also it only supports the top screen animation.

So it would need to be:
splash_image = /anim/0/anim

--------------------- MERGED ---------------------------

You can at least get your 3DS to boot if you remove everything else but:

[DEFAULT]
path = /luma.firm
delay = 1000
splash = 4
splash_image = /anim/0
screenBrightness = 0x30
enablePathFix = 1

That includes removing the ;luma with BootAnimation and enabled Pathfix line
Keep the boot_config.ini file on the root. However, I'm having trouble still anyway, my 3DS will boot up by having it set up in the same way you do with the boot_config.ini file setup as I have it there, but no boot animation will load despite an anim file in the anim/0 directory.

So I dunno what I'm missing but I can at least boot with this method, but that's not what I'm looking for, so for now I have reverted until I figure out what I might be missing.
Just to test I would try placing the animation file as /Animations/anim to see if that changes anything. That's my path and it works fine for me.
 
Hell yeah! that worked!! thanks for the help, can't believe I didn't catch that.
I'm actually still getting the error about the config file, do you mind sending me your full config or the config file itself? I copied the setup mentioned above, that being Animations/anim for the splash_image (And yes the anim is just a file and not a folder)
I put everything on the root, that being the ini file and luma.firm.
I also deleted the whole line that says ;luma with BootAnimation and enabled Pathfix

Here's my config for default:

[DEFAULT]
path = /luma.firm
delay = 1000
splash = 4
splash_image = /Animations/anim
screenBrightness = 0x3


I remember using CTRBootManager back in the day and even that gave me a ton of trial and error. I'm just not into coding to be fluent in this kind of stuff.
 
Last edited by MattKimura,
I'm actually still getting the error about the config file, do you mind sending me your full config or the config file itself? I copied the setup mentioned above, that being Animations/anim for the splash_image (And yes the anim is just a file and not a folder)
I put everything on the root, that being the ini file and luma.firm.
I also deleted the whole line that says ;luma with BootAnimation and enabled Pathfix

Here's my config for default:

[DEFAULT]
path = /luma.firm
delay = 1000
splash = 4
splash_image = /Animations/anim
screenBrightness = 0x3


I remember using CTRBootManager back in the day and even that gave me a ton of trial and error. I'm just not into coding to be fluent in this kind of stuff.
Is the first line in that boot_config.ini file a line of text, and if so does it have a ";" in front of it. If not try adding the semicolon. iirc the download I got didn't comment out the first line with a semicolon which would cause issues.
 
Is the first line in that boot_config.ini file a line of text, and if so does it have a ";" in front of it. If not try adding the semicolon. iirc the download I got didn't comment out the first line with a semicolon which would cause issues.
That did the trick, thanks for the support! Much appreciated
Didn't think a single line would cause issues.

The animation seemed pretty blurry compared to last I used it, and it played pretty fast. I'll need to edit the fps, but now to figure out how to do that.

Edit: It's not that blurry, it just plays really fast
 
Last edited by MattKimura,
That did the trick, thanks for the support! Much appreciated
Didn't think a single line would cause issues.

The animation seemed pretty blurry compared to last I used it, and it played pretty fast. I'll need to edit the fps, but now to figure out how to do that.

Edit: It's not that blurry, it just plays really fast

Yeah, the animation can run faster, so if you're using an animation that came in multiple FPS versions (Like I was) use a version with a higher FPS, it will be smoother and run closer to the speed that you're looking for. The animation I had been using was one that looked best at 15 or 20fps with boot9anim, but now I've moved up to the 25fps version and it looks smoother and runs at the speed I'm looking for.
 
Is the first line in that boot_config.ini file a line of text, and if so does it have a ";" in front of it. If not try adding the semicolon. iirc the download I got didn't comment out the first line with a semicolon which would cause issues.
Oh sorry, I will fix the Download , I did not test the example config for some time ^^'

And also, thanks for finding the problem :)
 
I'm having problems with the animation not playing as well. my config is:
;luma with BootAnimation and enabled Pathfix
[DEFAULT]
path = /boot9strap/luma.firm
delay = 1000
splash = 4
splash_image = /Animations/0/anim
screenBrightness = 0x3
 
Is there a way to just view the animation instead of displaying the black screen with the ascii art before the animation?
 
Is there a way to just view the animation instead of displaying the black screen with the ascii art before the animation?
I think you can just remove this from your config:

;configuration with ascii boot Image
;You have also 1 sec to press the button for the payload you want to boot
[BOOTCTR9]
key_delay = 1000
boot_splash = 3
enableAutosoftboot = 1
enableArm9CompanionBoot = 1
 
  • Like
Reactions: MattKimura
Is there a way to just view the animation instead of displaying the black screen with the ascii art before the animation?
like majickhat55 mentioned, it is configurable within the BOOTCTR region with the boot_splash option, and follows the same rules as the payload splash option, so setting it to 0 disables it.
 
Is it possible to load a bin file with the dev version for b9s if i upgraded to b9s?
I ask because i want to keep the possiblility to boot Gateway on 11.2 on my secound console but want to use newest Luma. Have only found the .bin file for the redirection to the Gateway file, haven't found a .firm version and converting it haven't worked.
 
Is it possible to load a bin file with the dev version for b9s if i upgraded to b9s?
I ask because i want to keep the possiblility to boot Gateway on 11.2 on my secound console but want to use newest Luma. Have only found the .bin file for the redirection to the Gateway file, haven't found a .firm version and converting it haven't worked.
It is possible, but you need to use another bin to load gateways.bin. Here is a Tutorial.
 
i still can't get my animation to play.
DEFAULT]
path = /boot9strap/luma.firm
delay = 1000
splash = 4
splash_image = /Animations/anim/0
screenBrightness = 0x3
 

Site & Scene News

Popular threads in this forum