It really sounds like something wrong with how the d-pad is doing debouncing on some consoles. Dirt or corrosion on the contacts could possibly cause it, though admittedly I don't know how the 3DS does debouncing.
Could it be possible to add the input delay as a configurable option in it then?Arguably the way I'm handling input doesn't help the problem, though.
Could it be possible to add the input delay as a configurable option in it then?
I'd help those with the issue and those that don't need it could leave it off as default?
Are you going to have it behave like Luma?I mean, I could, but that seems like a compatibility hack to me.
I'd rather fix the actual behavior of the menu.
Are you going to have it behave like Luma?
I mean, I could, but that seems like a compatibility hack to me.
I'd rather fix the actual behavior of the menu.
@chaoskagami One question about the screen garbage. The main issue is with A9LH itself?
the post got deleted from reddit???
I find that screen garbage only happen when using arm9loaderhax_si.bin. Otherwise running just normal arm9loaderhax.bin seems to work just fine for me with LumaNAND (still not the official name)Some of it is indeed my fault - but the initial garbage on boot is not. AuroraWright's branch doesn't clear the screen before turning on the backlight (as arm9loaderhax_si.bin) This is relevant when booting initially, and hitting reboot in the menu. Chainloader is entirely my fault, however.
My bet is that beefhash removed it (since he knows I would prefer to post myself.) I'll have to check with him on that, though.
huh. I'm not particularly bothered by the chainloading garbage. Only the reboot/power on . For the time being, I changed to /arm9loaderhax.bin so it's not annoying anymore. lelSome of it is indeed my fault - but the initial garbage on boot is not. AuroraWright's branch doesn't clear the screen before turning on the backlight (as arm9loaderhax_si.bin) This is relevant when booting initially, and hitting reboot in the menu. Chainloader is entirely my fault, however.
I find that screen garbage only happen when using arm9loaderhax_si.bin. Otherwise running just normal arm9loaderhax.bin seems to work just fine for me with LumaNAND (still not the official name)
Of course I would have called this out as a bug, but this issue seems to exist all A9LH CFW's. So I can tell it's not just your's that is having this issue and it's an A9LH issue.
It also happens with ShadowNAND, when booting into "screen-int" versions of the CFW. Which is why I didn't report this issue here in the first place.Blame AuroraWright's payload for everything aside from the chainloader menu. Not really my fault, sadly. :|
It actually acts a lot more like ctrbootmanager, expect a lot easier.Quick question, when you boot menu similar to lumas chainloading it is the first to boot, correct? Just asking because I want to be prone to bricks. Also have been rocking Skeith for the day and it has been awesome. Great job man!
I figured that out just wondering if it can save from bricks.It actually acts a lot more like ctrbootmanager, expect a lot easier.
You just put your files into the "Boot" folder and the apps will appear in the chainload menu, nothing more needs to be done. From there you just launch them through the corbenik boot menu.
There's no chance of bricking using the payload chain. What you use with it is where you can run into issues, but that's not a Corbenik issue.I figured that out just wondering if it can save from bricks.
(Cute new avatar)
No not I ment is it like lumas payload er that serves it under as people say "brick protection" like is it possible to still boot into that menu and into Hourglass9 if I brick?There's no chance of bricking using the payload chain. What you use with it is where you can run into issues, but that's not a Corbenik issue.