It's just a case of testing for a touch down event, then looping until a touch up event occurs. During the loop, you check the position of the touch. If it enters one of the hit zones, you count that as an entry in the combination. Once the touch up event occurs and the loop is broken, you check if the zones were entered in the order expected.That's easy? Wow I don't expect that
The logic and touch handling is easy. But as I said I don't know if the touch screen works in a A9LH payload.
I'm interested to know where you got this info, since I seem to remember the opposite.
This thread has been sleeping for a little too long I feel!
I do hope my favourite 3DS homebrew is at least able to get a 1.0 release with all those little tweaks and polishes.
One of those tweaks that popped up in my mind was moving the CTRNAND payload path to 1:/arm9loaderhax.bin instead of 1:/3dsafe/emergency.bin, for the sake of consistency with AW's a9lh and Luma. At first I was getting confused why I was getting those weird crashes when trying to run DS titles.
I do hope my favourite 3DS homebrew is at least able to get a 1.0 release with all those little tweaks and polishes.
One of those tweaks that popped up in my mind was moving the CTRNAND payload path to 1:/arm9loaderhax.bin instead of 1:/3dsafe/emergency.bin, for the sake of consistency with AW's a9lh and Luma. At first I was getting confused why I was getting those weird crashes when trying to run DS titles.
Also another suggestion is if you can be allowed to edit in multiple wallpapers on the top screen if there are more than one of the file that changes the top screen is detected in the sd. Would it be possible to make it so that it will shuffle the wallpapers on the top screen?
Last edited by Ichigo1000,
I have to ask you again since you didn't really answer last time, are you trying to boot from CTRNAND or SD?
Are you using some sort of boot manager, a custom luma path, any custom titles (home menu, etc.)
Does the svcBreak occur when just booting normally, or when firmlaunching (DS/DSi/GBA/high RAM games)?
Was Luma working before or did you recently switch to Luma or 3dsafe?
It's difficult to troubleshoot without many details. I know for a fact that Luma 6.5 is working on my console with 3dsafe so I'm just trying to diagnose where the difference between your system and my system is.
On the past I installed custom GBA_firm I think.
This occurt when my 3DS boot.
I had 3DSafe yesterday, but I uninstall it because I thought that Luma 6.5 don't work with it (because it had the error «svcBreak»). So I uninstalled 3DSafe and install the arm9loaderhax version of Plailect guide and Luma made the same error.
This occurt when my 3DS boot.
I had 3DSafe yesterday, but I uninstall it because I thought that Luma 6.5 don't work with it (because it had the error «svcBreak»). So I uninstalled 3DSafe and install the arm9loaderhax version of Plailect guide and Luma made the same error.
Seems like a problem with Luma, then. The custom AGB_FIRM thing should only become a problem when trying to load a GBA game.
Similar threads
-
-
-
-
-
-
-
-
@
Xdqwerty:
@Psionic Roshambo, i also watch my hero academia and rewatching dragón ball starting from the og series -
-
-
-
-
-
@
BakerMan:
I- AURORA BOREALIS? AT THIS TIME OF YEAR, AT THIS TIME OF DAY, IN THIS PART IF THE COUNTRY, LOCALIZED ENTIRELY WITHIN YOUR KITCHEN?+1 -
@
BakerMan:
jokes aside, anyone else who saw the northern lights tonight, what did you think, i thought they were beautiful for a while, before it went to a vague pink+1
maybe later they'll pick up again -
-
-
-
-
-
-
-
-
-
