this post was submitted on 13 Dec 2024
5 points (85.7% liked)
Emulation
3569 readers
9 users here now
Community to talk about emulation & roms.
RULES:
1.) No bigotry
LINKS:
-
Emulation Wiki - Your source for everything emulation :)
-
[WIP] Emulation Links Wiki - My personal wiki for emulation links, please help contribute!
-
r/Roms Megathread - Megathread of Roms
-
RetroArch - RetroArch is the popular front-end to libretro which is a simple API that allows for the creation of games and emulators.
founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Well, on android you have two sections of settings unfortunately.
The cog in the bottom right, and also the core options menu that you need to load a rom and hit the menu shortcut, probably L+R+start+select together on your controller, or the space invader symbol on the touchscreen overlay.
You can then go to core options > screen > touch mode which should be auto.
If youre finding things aren't as they should be, reset the app to fresh install settings using the inbuilt function or the android app (clear cache and data feature) under your app management and see if that solves the issue.
It may be a carry over from upgrading from such an old version, so a fresh start may serve you better.
I have cleared the cache and data from the app manager, re-updated everything in the online updater section and I have checked to make sure that the touch mode setting was set to auto but it's still not working. I will continue checking every section unless you have something I can try.
Nothing right now I'm afraid. I will grab my 8bitdo later and test with an android tablet, see if I can recreate and figure out the issue. Expect a response in the next 6-8 hours, I'm afraid I gotta sleep, sorry.
Ok, I've looked into it a bit more and I found this issue on github. It seems the issue has been present since at least 1.17 stable and while it has been fixed in nightly, the issue still exists in the latest stable version because it seems like it was fixed about 5 days after the stable version was released.
I have downloaded the nightly version and I am able to use both a controller and the touchscreen together. I haven't tested the DSi emulation yet though, I'll have to do that later because I'm about to go to bed.
Nice, guess there's a fix in the pipeline. Glad you found a solution. Lmk if it works, have a good one
I have tried it more and I can't really tell if setting the console mode to DSi actually causes the games to perform better. The only game that I know of that has noticeable performance issues on real hardware is Grand Theft Auto Chinatown Wars but I can't really test it because the emulator lags during situations where the game would lag on real hardware. The only thing I have to go off of right now, is that the emulator seems to lag slightly more when the console mode is set to DSi but that could just be caused by differences in firmware.
Interesting. I've noticed a performance boost in pkmn HG/SS & B&W2 from my own testing, and I ran a homebrew game called WolveSlayer, which definitely improved too.
I'm not sure about HG/SS or WolveSlayer but all four of the gen 5 Pokemon games are DSi enhanced so they get a performance boost even without a modded DSi. I'd try other games but if the emulator is lagging on everything I have then I don't know if I'd be able to. I know other emulators, like DraStic, actually run significantly better, even on older devices, but I don't know if they automatically use the DSi's clock speed or at least have the option to.
I decided to try something. Seeing that just playing the games isn't really that good of a way to test it, I thought I could try running some homebrew that could either test the cpu or just tell me info about it. So far the closest I've gotten is to use DSLinux and run
cat /proc/cpuinfoto get some info about the CPU. The only problem with this is that, the only thing I have to go of is the "bogomips" which is not a very good way to measure CPU speed. But for what it's worth, while it doesn't work in every emulator, I've noticed that some emulators are showing about 16 bogomips and others are showing about 33.While bogomips is not a very accurate way to measure CPU speed, I think it would still be helpful in this particular situation. I can't test DSLinux on my DS because either my flash card or my DS itself aren't working properly, but I think it's probably safe to assume that the ones showing 33 bogomips are probably running at DSi clock speeds. I want to test it on more emulators but it's getting late for me, so I'll have to do that tomorrow.