Many thanks Also take note if it hang on the yellow/colored bottom screen in which case its homemenu hax problem.Yes, I also tried with 0.
No problem, I will boot 25 times into rxTools using 0 and 25 times using 2, then I'll report the stats.
Many thanks Also take note if it hang on the yellow/colored bottom screen in which case its homemenu hax problem.Yes, I also tried with 0.
No problem, I will boot 25 times into rxTools using 0 and 25 times using 2, then I'll report the stats.
Yes, I know about that debug stuff, but thanks for reminding me, I shouldMany thanks Also take note if it hang on the yellow/colored bottom screen in which case its homemenu hax problem.
Hi, just uploaded a new version :
1.0: add boot menu entry from the file manager (X) (.3dsx only)
1.0: remove boot menu entry from boot menu (X)
1.0: add a few more help/information to the bottom screen
I just tried it, and in fact, both ftbrony and 3DSlink now work for me. There's still the problem / annoyance that for both, I need multiple tries (start app, close app, start app, ...) to succeed. Both apps (ftbrony and 3DSlink) need the wifi connection present right from the start. One way to solve this would be to wait until the wifi connection is established before actually starting the app. Such a feature would require a timeout, of course, because if no wifi network if present we'd otherwise wait till kingdom come.Hi, just uploaded a new version :
1.0: add boot menu entry from the file manager (X) (.3dsx only)
1.0: remove boot menu entry from boot menu (X)
1.0: add a few more help/information to the bottom screen
I just tried it, and in fact, both ftbrony and 3DSlink now work for me. There's still the problem / annoyance that for both, I need multiple tries (start app, close app, start app, ...) to succeed. Both apps (ftbrony and 3DSlink) need the wifi connection present right from the start. One way to solve this would be to wait until the wifi connection is established before actually starting the app. Such a feature would require a timeout, of course, because if no wifi network if present we'd otherwise wait till kingdom come.
Custom background\foreground colors maybe?
@cpasjuste
Testing results on n3ds for
autobootfix = 0 :
boots 41 times out of 50
and
autobootfix = 2 :
boots 50 times out of 50
You could also auto-detect whether it's an n3DS or an o3DS CBM is running on (check menuhax source for how to).Thanks ! So i'm keeping the autobootfix option !
Yeah, I know, I'm quoting myself. But I found a "solution" and it seems to work even though I'm not sure if it's supposed to...So would it be possible to set "Power off" as the default option ?
if I just fire netload up right away, without waiting, I get: "Err: SOC_buffer", then "Err: netloader_activate". If I wait for a bit (or impatiently try it multiple times), it will eventually work. Still, I'd prefer if the waiting was done automatically .Normally as soon as wifi is up, it's not disabled until a reboot. But you're right it could be problem if we try to autostart an app that need wifi yes. This is something i could easly add (option wait for wifi with a timeout), i'll try to add that soon.
But for the "netload 3dsx" option, it should not be a problem as, like as said, wifi is already enabled for netload to work, so i don't understand this situation.
Yes, its only needed when booting some payloads (bin) directly.Is it correct that CBM doesn't need the offset line for PastaCFW.3dsx ? Because it's missing in the sample boot.cfg