ill make sure to report any if i encounter them. thank you :3You could try his build, maybe it will work better, but im still within cleaning up the code, so there could be bugs ^^
ill make sure to report any if i encounter them. thank you :3You could try his build, maybe it will work better, but im still within cleaning up the code, so there could be bugs ^^
Can't work on me , this my config file :Here is a first b9s 1.2 compatible dev build.
This dev-release only include a firm, since the .bin build is not yet running.
The next targes will be more code cleanup and getting the a9lh payload running again on a9lh.
I will also try to get the gateway payload running directly, but Gateway should maybe release a updated payload, since it should not be that hard for them.
[BOOTCTR9]
key_delay = 1000
boot_splash = 0
enableAutosoftboot = 1
enableArm9CompanionBoot = 1
;Section to allow a9lh net companion payload auto booting
[COMPANION]
path = /a9nc.bin
delay = 100
offset = 0
payload = -1
;luma with BootAnimation and enabled Pathfix
[DEFAULT]
path = /luma/boot.firm
delay = 1000
splash = 4
splash_image = /anim
screenBrightness = 0x30
What excactly is the problem?Can't work on me , this my config file :
I can boot to Luma but it doesn't launch my anim file , see my config file if it's right...What excactly is the problem?
If Luma shows the unsupported path error, you could try this build:
https://gbatemp.net/threads/release-the-bootctr9-release-thread.435347/page-4#post-7444044
Is "/anim" the file or a folder?I can boot to Luma but it doesn't launch my anim file , see my config file if it's right...
[BOOTCTR9]
key_delay = 1000
boot_splash = 0
enableAutosoftboot = 1
enableArm9CompanionBoot = 1
;Section to allow a9lh net companion payload auto booting
[COMPANION]
path = /a9nc.bin
delay = 100
offset = 0
payload = -1
;luma with BootAnimation and enabled Pathfix
[DEFAULT]
path = /luma/boot.firm
delay = 1000
splash = 4
splash_image = /anim
screenBrightness = 0x30
It's a folder and inside there is "anime" and a "config" fileIs "/anim" the file or a folder?
You need to point directly to the animation file.
depends on your entrypoint, if you are using Arm9loaderhax, most of the time the github release would be the best, if you are using bootstrap9 use the release for yout bootstrap9 version on here in the thread, and if you have problems with luma saying the path is unsupported use the build from hereayyyyyyyyy questions tho what version would n average consumer download
Yes, thats right, but you should also rename the config file to [animationname].cfg for an text config, or [aniomationname].cfb for a binary configuration.It's a folder and inside there is "anime" and a "config" file
So, it will be ""/anim/anim" ?
First "anim" is a folder and a second is a file...
Great, it work now thanksYes, thats right, but you should also rename the config file to [animationname].cfg for an text config, or [aniomationname].cfb for a binary configuration.
Is Gateway working on luma 8.1?
Just look for the bootanim9 animation thread. Bootctr9 uses the same format so the animations in that that should work (except the bottom screen)Yeah, I would love a zip or rar with the way I have to set it up to make it work, since I seem a bit confused after all this info, but totally thankful for that awesome response.
Yeah, I would love a zip or rar with the way I have to set it up to make it work, since I seem a bit confused after all this info, but totally thankful for that awesome response.
I just updated the repository, so the current bootloader branch should work with boot9strap.Awesome release. Works great with Gateway. Surprisingly, it also gets Puma working too. You still need to point path.txt to a .bin copy to get reboot patches to work right, but, it works. Nice job. Now, if you could just figure out what Salt's hangup is, we'd have every A9LH payload working in B9S (well, I haven't tried converting Uncart or AGBSave9, but there's really no point). I know, Salt is currently dead because the author bricked his device. I'd offer to take it over, having a hard modded device and all, but I'm no coder. The closest I get are my non-keymapping AHK scripts for pseudo direct movement in non-import PC APRGs.
Just one question. If, say, I wanted to build a second copy that uses a different .ini file, what options would I use in firmtool? The example commands don't seem to work at all. In case you're wondering why, I'm using mini BootCTR9 configs to fix CFWs that aren't working in other chain loaders (again). CBM9 can patch it in memory, of course, so I've already got that working with separate .ini files that directly launch GW and Puma. But I'm anticipating having this issue with other chain loaders. I know, I should probably just be like "you're using BootCTR9, because it just works" but my AIO packs have always been about providing choices (which is why I was hoping someone had coded an updated A9LH installer for B9S, looks like no such luck).
P.S. It's good to see that some developers actually care whether their .bin build works or not (maybe if said A9LH installer existed, more devs would check them).
I just updated the repository, so the current bootloader branch should work with boot9strap.
Also the full boot9strap release should come in the near future, include an arm9loaderhax version.
Oh wait, nvm about my last postI just updated the repository, so the current bootloader branch should work with boot9strap.
Also the full boot9strap release should come in the near future, include an arm9loaderhax version.