I don't really know about the 3DS stuff, but it sounds like a general case of "DSTwo acts up and isn't recognised until powerdown/powerup or is recognised only 33.3repeating% of the time on a 3DS". There were some threads about those issues in /NDS/Flashcarts/Supercard.I found a strange issue. When I install TEMPGBA, after I exit out to the main 3DS XL menu, I can no longer get back into the dstwo card without physically ejecting the card and putting it back in.
If I remove the TEMPGBA folder and plugins everything works normally.
I don't really know about the 3DS stuff, but it sounds like a general case of "DSTwo acts up and isn't recognised until powerdown/powerup or is recognised only 33.3repeating% of the time on a 3DS". There were some threads about those issues in /NDS/Flashcarts/Supercard.
Looks more and more like a general "3DS and DSTwo" issue. Please search for "3DS" in /NDS/Flashcarts/Supercard to see whether you can find a workaround for the issue or get your DSTwo exchanged.So I did some further testing, just to see exactly what the issue is. It looks like the ROM i was trying to play was causing it. After switching to another ROM (same game) the issue went away. A bit strange but I guess that's all it was.
Edit: After skinning the issue came back. I don't know....
thanks for your reply nebuleon,but what must i do to complete my report ?Your report is incomplete. Please see post #451.
That actually doesn't complete the report, now that I look at post #682, but yes, the exact commit (d373639) was what I was looking for. Thanks.thanks for your reply nebuleon,but what must i do to complete my report ?
from your post it say it,s recommended to post the pic of error form lower touch screen.
version beta 13 (first time i try beta 14 and now i try beta 13 to find if it can work,but the same error happen when first time select a game)
Commit d373639
I really have to complement this project, Castlevania Aria of Sorrow was already playable before on NDSGBA, but now it plays remarkably well, full speed and almost smooth.
Metroid Zero Mission played very well as well, kudos you guys you really took Team Supercard's source code above and beyond.
Although I really commend this project, I don't imagine myself playing with TempGBA very often with the state of my DSi, the d-pad and shoulder buttons sadly are not as responsive as they once were, and the project still has a way to go.careful with zero mission and the other one. I have random audio cracking and freezing from time to time. save often.
however the emulator is light years better than what I expected it to become. so ty devs.
I agree with this, if only because its CPU is such a powerhouse - but do keep in mind that, until/unless someone picks my changes, the GCW Zero version will be essentially gpSP 0.9 by Exophase with a more efficient scaler. That means that the Golden Suns, Mario Golf and Tennis, Doom II and Duke Nukem Advance might not run so well, Golden Sun 2 will crash in battles at random and have odd-sounding audio that overlaps itself, Tales of Phantasia might or might not get past its title screen, Mario Kart might wharrgarbl, and a few odds and ends like translation gates.Although I really commend this project, I don't imagine myself playing with TempGBA very often with the state of my DSi, the d-pad and shoulder buttons sadly are not as responsive as they once were, and the project still has a way to go.
I will sooner be using a GCW Zero for GBA emulation, that should handle it superbly.
I agree with this, if only because its CPU is such a powerhouse - but do keep in mind that, until/unless someone picks my changes, the GCW Zero version will be essentially gpSP 0.9 by Exophase with a more efficient scaler. That means that the Golden Suns, Mario Golf and Tennis, Doom II and Duke Nukem Advance might not run so well, Golden Sun 2 will crash in battles at random and have odd-sounding audio that overlaps itself, Tales of Phantasia might or might not get past its title screen, Mario Kart might wharrgarbl, and a few odds and ends like translation gates.
Oh!
You touch the Touch Screen. And in the menu itself, you can assign a hotkey to the action of bringing up the menu. See /Tools/Global hotkeys.../Return to menu. By default, none is assigned, but you can assign, say, the X key.
-> Post #397One thing I was going to ask after playing with the emulator a bit more now, the CPU speed seems settable per game but, how about a default global option for CPU speed? I just figured that while the emulator is still in beta, it might be good to give it more power for keeping the frame rate up.
That actually doesn't complete the report, now that I look at post #682, but yes, the exact commit (d373639) was what I was looking for. Thanks.
None of us can actually reproduce a Guru Meditation crash that happens when "loading any game (#682)", clearly. Aeter just used beta 13 & 14 to test Fire Emblem games, and if there was really a Guru Meditation screen when loading "any game", then he would have failed. I would also fail to test any game before I shipped a version.
Can you be very specific about which games are "any" - i.e. which ones did you test? What size is your version of TempGBA.plg in /_dstwoplug on your card? What options did you use to reformat your card? Does "Loading..." appear before loading a game crashes the emulator? Does the first frame of the game appear before the crash?
I have no idea what happened there. The limit for the file browser is 512, which is more than 103. However, I don't know how the emulator reacts to 103 folders as opposed to 103 files.thanks for your help looks like i solved it even i don,t know if it is limitation of this emulator or bug
what i do is delete all my 103 folder game in tempgba / games and left pokemon diamond and pearl
after that when i press load game list it work and play pokemon diamond flawless (well just try for a few minute)
so i have few question
is this emulation have a limit how many game it can load ?
or is it because there is some game that make error screen appear when i try to load game list to play ?
thx for your help,this emulator is fabolous and terrific.
really love to play gba in my dsi xl
Not that many games need the extra CPU cycles, and it's better for power consumption if most games run with a reduced CPU frequency - you can raise the CPU frequency yourself if you see it not run well. I had a post explaining why I left the default at 360 MHz, but I can't find it anymore.
Basically, classified by emulation difficulty, there are the "easy" games, which need only 240 MHz to run at 60 FPS; the "medium" games, which need about 360 MHz and crackle once in a blue moon; and the "hard" games, for which 396 MHz isn't even enough. I left the default at 360 MHz because there are more easy and medium games than hard.