- Joined
- Jul 6, 2013
- Messages
- 87
- Trophies
- 0
- Age
- 27
- Location
- Pennsylvania
- Website
- failnuke.com
- XP
- 78
- Country
Are you planing to improve 3DGB too? Or, are you already doing that?
Seems like there's a competitor for the SNES emulation : http://gbatemp.net/threads/blargsnes-snes-emulator-for-the-3ds-wip.369900/
Yeah... i know :C
I gave 3DNES a quick try with SMB, and I gotta say, good work there. No speed issues, it plays nicely. (SMB isn't the most CPU-intensive game I guess, though)
I noticed that some sprite priorities were wrong (ie powerups coming out of blocks, Mario entering pipes, etc), but that's minor. What would be nice imo would be the ability to map the 3DS A/B/X/Y to the NES A/B buttons in whatever way you like, or in a few presets that work well in the popular games.
Keep up the good work, anyway.
N64 will be a tricky one. I believe one would need a JIT to get good performance on the 3DS, but the 3DS's security system makes it impossible to implement a JIT without hacking the kernel.
Thank you for it, really , about the key map, i will work on it xD, sprite priorities really work, but i need remove it, because speed down :C
JIT = Dynamic Recompilation ? if yes, i wanna do it, maybe is the best way to work N64 good on 3DS, but the biggest problem is because we just can use one core from games :C the other core from ARM11 is to System.
I don't know much about the 3DS's internals, but wasn't the 3DS updated during the time of Super Mario 3D Land to allow that game to utilize 25% of the other core?
Really ? i didn't know about it, good information !
The CreateThread SVC call takes a bitmask that tells which CPU cores the thread can run on. One can probably just use this, unless it requires a special permission.
Now, I don't know how the '25% of the system core' would work. Does the kernel monitor CPU usage and kill your app if it goes over that number? Seems unlikely.
Well, nevermind what I said. Either it requires a special permission, or what has been said about SM3DL isn't true.
Either way, attempting to create a thread on the second core just plain crashes. Doesn't even return a 'not authorized' error code.
have you updated to 2.2
you need to be on 2.2 to run homebrew