Is there an emulator through Smilebasic that supports GBA games?Nope, otherwise it would be on the front page. Also, the GBA requires WAY too much speed to even run at a playable framerate. There's an ARM processor in there, and its games require more speed than SmileBASIC can handle. The GBA has all sorts of tricks (stuff like Mode 7 effects) that run at 15 FPS max on SmileBASIC. Remember: the programs currently featured at the top of the Submissions page are squeezing every ounce of power out of SmileBASIC, and then some. There's no magical strategy that will make stuff like GBA emulation (or heck, even NES emulation) possible. The only option for playing GBA games on your 3DS (aside from being an ambassador) is hacks. Please hack responsibly. All hacks have a chance of bricking your 3DS if they are preformed incorrectly.
Also, the GBA requires WAY too much speed to even run at a playable framerate. There's an ARM processor in there, and its games require more speed than SmileBASIC can handle. The GBA has all sorts of tricks (stuff like Mode 7 effects) that run at 15 FPS max on SmileBASIC.YES I've been playing with mode 7 on SB and it doesn't get any better than 15 FPS unless you have trash graphics.
Unplayable. I released it unfinished because I doubt I’ll work on it againwahooHow fast it it?
Unplayable. I released it unfinished because I doubt I’ll work on it againIs it about as fast as it was when you released the Tetris video? It seems like you implemented at least basic OBJ, BG, and window support, as well as (I'm assuming) all opcodes? Finally, was it the speed that discouraged you from putting more work into it? Having at least a working emulator is still pretty good.
Is it about as fast as it was when you released the Tetris video? It seems like you implemented at least basic OBJ, BG, and window support, as well as (I'm assuming) all opcodes? Finally, was it the speed that discouraged you from putting more work into it? Having at least a working emulator is still pretty good.Yes. I think I have added all the opcodes. Sprites, windows, background are working, except transparency was never implemented.
At least give a key...Is it about as fast as it was when you released the Tetris video? It seems like you implemented at least basic OBJ, BG, and window support, as well as (I'm assuming) all opcodes? Finally, was it the speed that discouraged you from putting more work into it? Having at least a working emulator is still pretty good.Yes. I think I have added all the opcodes. Sprites, windows, background are working, except transparency was never implemented.
At least give a key...You will need CFW to get ROMs into smileBASIC so it is not much more work. Not including a key helps detract people from having a program they cannot use.
Why do you think you're quitting though?For the same reason most people stop: lose of motivation. Additionally, the program is quite poorly written and hard to read, which makes debugging painful.
Cool. I had not tried Donkey Kong, but I am glad it started.It's alive! (took me several minutes to even reach this screen)
One question how do you import the roms. (using CFW)Assuming you already have CFW, you can insert your SD card into a computer and put ROMs on there. Or you can use something like FTPDB and FileZilla to transfer your files remotely via FTP. Once you have your ROMs on the SD card, you can use this (https://github.com/Trinitro21/lpp-3ds/releases) tool to import them into SmileBASIC.
So I'm testing Tetris on N3DS XL and it seems to have gotten... slower? I timed it, and it took 2 minutes and 7 seconds for a Tetrimino to move one tile downwards. But in your second test video here: https://www.youtube.com/watch?v=OxC5WGD00Io ...they move a whole lot faster. Only 3-4 seconds to move. What happened?In the video, I’m holding down. Why the hell would you time that? Now that you mention it, I think that the d-pad buttons do not correctly match the direction you press… I’ll have to fix that
Ok I have successfully imported the emulator. But the Roms are still annoying. It's asking me if it's |Col int or real| after that it asks dimensions and after that the size (or something like that) Question is what should I select? (sry if sound stupid af)I'm pretty sure you should pick int and 1 dimension.
Why the hell would you time that?Why not? It's to get a good idea of how fast the emulator is compared to real time and earlier builds. You told me it was unplayably slow, but I had to find out just how unplayably slow it actually was. Even while holding down, it seems like the emulator runs at half the speed as it did before, at least in this specific example.
