Dolphin, the GameCube and Wii emulator - Forums

Damn,I was a little late.
I have it running,but analog input is broken when going ingame.
The menus can be navigated,but you just can't move around,a crappy reason to make it unplayable.

The settings along with the Game ID of the US region one in case you are in a different region,then you'd need to get and compare MD5 to gametdb.

GHQE7D.ini

[Core]
FastDiscSpeed = True

Also,whaaaat!!! Analog works now,as tried in a later debug build but pre-dating the main 9090 build,so I can use cheats.
Maybe the OTA update mysteriously fixed it.
Terribly sorry I can't think of the exact version linked that I am using,but it was the second JitARM64 performance build posted by none other than degasus.

(05-03-2016, 02:53 AM)degasus Wrote: [ -> ]There is an easy way to deal with this issue: Buy the nvidia shield android tv. No other device (maybe the pixel c) is known to work fine. But the bad point is, that why should you buy it if you can just use a common computer. Most users asking for an android port want to play it on their mobiles. It's even worse, because of the thermal bugdet on mobiles, it won't run well with good drivers.

By next year the CPU of flagships will probably be on par or better than the one in the shield tv, but that's ignoring the thermal constraints. Maybe I'm optimistic but if the driver issues weren't there then I think next year or the year after it would be playable.

You know, I'm really looking forward to being able to play dolphin on mobile, but the funny thing is I'd probably play it in my room or living room where I could just use my PC anyway

(05-02-2016, 03:41 PM)degasus Wrote: [ -> ]The wiki also tells you why: https://wiki.dolphin-emu.org/index.php?title=The_Simpsons_Hit_%26_Run#MMU_Speed_Hack
This game requires the MMU speedhack, which is NOT supported within the jitarm64. Bad luck, the primary maintainer of the arm64 port has no time any more, and the second one, me, is not interested in doing so.

Just try to run it in the interpreter, this should work just fine.

But feel free to implement it yourself. It took me a month from starting to compile it on arm64 to being able to redesign some jit functions. Everyone can do it.

Thank you for finally giving me a proper answer! I can't use MMU because it's not supported within the jitarm64. I will try to use the interpreter, thanks.
Although I'm going to have to disagree. The wiki doesn't tell me anything useful, I'd been to it 3-4 times before posting here. It doesn't tell me where to find MMU or that it's not an option in the Android build.
I'm sure everyone can do it, but I have no idea what tools I need or how to get ahold of the source code OR what I need to compile it so I could actually test a build.

(05-03-2016, 12:00 AM)helios747 Wrote: [ -> ]Gods damn what an amazing, round about way of saying "Well I could but I don't want to / can't program so blah"

but yeah. Everything but the Android version of Dolphin is under very active development. Android? Hasn't seen attention in a couple months now.

Did you even read my post? I asked for the tools and said I'd attempt it. At least I offered to try, like a developer would be imagined to do.

Android hasn't seen attention in a couple months? Mate, have you seen the any of the recent builds?
Make exceptions consistent across all JITs/Interpreters (Fixes Pokemon Box). 3 days ago (affects Android)
Android: Also copy sys/Wii directory. 8 days ago (fixes MK Wii)
[Android] Fix android builds permanently. 4 weeks ago
Android: Update gradle version. 4 weeks ago
Not to mention all the other builds that don't have Android mentioned in the PR but there are still Android build downloads there. There are dev builds that don't include Android downloads, so obviously they aren't added just because, on some of the updates.

It's certainly being worked on. In that MKWii was just fixed, naturally I figured other game fixes like for the Simpsons could be on their way.

(05-03-2016, 02:53 AM)degasus Wrote: [ -> ]There is an easy way to deal with this issue: Buy the nvidia shield android tv. No other device (maybe the pixel c) is known to work fine. But the bad point is, that why should you buy it if you can just use a common computer. Most users asking for an android port want to play it on their mobiles. It's even worse, because of the thermal bugdet on mobiles, it won't run well with good drivers.

I've got the nSATV. The reasons I bought it, even though I have a proper desktop PC that runs everything fine, are as follows:
✧ MAJOR portability! Works anywhere there's an HDMI TV, even better with Wi-Fi
✧ More 2-player possibilities
✧ Bring-anywhere infinite entertainment with thousands of games via emulators and free TV apps or websites
✧ Controllers instead of keyboards, though keyboards are compatible
✧ 4K display possibilities

(05-03-2016, 04:10 AM)retroben Wrote: [ -> ]Damn,I was a little late.
I have it running,but analog input is broken when going ingame.
The menus can be navigated,but you just can't move around,a crappy reason to make it unplayable.

The settings along with the Game ID of the US region one in case you are in a different region,then you'd need to get and compare MD5 to gametdb.

GHQE7D.ini

[Core]
FastDiscSpeed = True

Also,whaaaat!!! Analog works now,as tried in a later debug build but pre-dating the main 9090 build,so I can use cheats.
Maybe the OTA update mysteriously fixed it.
Terribly sorry I can't think of the exact version linked that I am using,but it was the second JitARM64 performance build posted by none other than degasus.

I've heard of the non-working analog stick issue before. I have the USA copy of Simpsons Hit & Run, but what's the "GHQE7D.ini" and does "FastDiscSpeed = True" exist in Dolphin.ini? I dunno how to find the MD5# or what gametdb is.
UPDATE: I added FastDiscSpeed = True to my .ini and started it up in my recent dev build, did some waiting and it starts, analog stick works ingame too. Not sure who to thank, but definitely ben if that code did it!
My only question would be why the hell would Disc Speed matter when there is no disc?!
P.S.: @degasus... no... It ONLY works on the jitarm64 recompiler.

If you want to be pedantic about it...

Nobody's working specifically on Android. Any core fixes that happen to fix something on Android is a happy coincidence. Fine. nobody is working on making things any faster or less broken for Android.

(05-03-2016, 08:59 AM)helios747 Wrote: [ -> ]If you want to be pedantic about it...

Nobody's working specifically on Android. Any core fixes that happen to fix something on Android is a happy coincidence. Fine. nobody is working on making things any faster or less broken for Android.

Oh, I see. Good to know.
My bad, I didn't notice your "developer" rank the first time so I didn't give you enough credit for what you said. I was just shocked.

Here's hoping that within the surge of nVIDIA SHIELD emulated gaming, there becomes enough demand for somebody who has the tools, wisdom and willpower to do it.
Thread dead. GG.

Eh, don't give me more credit just because I have dev tags. Don't do that for anybody. (Unless we're talking specifically about code we've worked on, I guess)

I just know from IRC and being around awhile that nobody's focusing specifically on JIT or GLES stuff for Android anymore.

(05-03-2016, 07:39 AM)Satan Wrote: [ -> ][...] The wiki doesn't tell me anything useful, I'd been to it 3-4 times before posting here. It doesn't tell me where to find MMU or that it's not an option in the Android build.

Current wiki maintainers (I speak for myself but I think MaJoR and Kolano probably share similar thoughts) aren't bothered in covering Android related stuff on the wiki, at least not yet: like others said, there's only one device currently capable of running the Android port and even on it you'll suffer with some slowdowns on demanding games, generally (but not limited to) unimplemented features on ARM64 JIT or OpenGL ES side.

So, considering the amount of work needed to refine the wiki to accommodate Android stuff is simply not worth at the moment (after all, currently there's little to no demand, from my point of view). The furthest we got was doing some mockups of the testing template in order to accommodate Android testing reports, and that's all. Anyway, just like the source code, the wiki is also open, you're free to contribute Android stuff to it...

(05-03-2016, 01:50 PM)helios747 Wrote: [ -> ]Eh, don't give me more credit just because I have dev tags. Don't do that for anybody.

/\ THIS. Some forum members like mimimi contributed lots of code to Dolphin and despite that he's still a regular user without any special tag. Would you just disregard his posts just because of the absence of a green dev tag? That's not how it works! Even I already contributed some very small and very specific code patches to Dolphin, would you disregard whatever I might have said about Dolphin's source code just because my username is behind a "Content Creator" tag?

(05-03-2016, 07:39 AM)Satan Wrote: [ -> ]Did you even read my post? I asked for the tools and said I'd attempt it. At least I offered to try, like a developer would be imagined to do.

Have you ever tried it?

ok, some steps for dummys: There is a "Code" button here on the forum, it will point you to: https://github.com/dolphin-emu/dolphin
There is a "Building for Android" topic, you just need to scroll down: https://github.com/dolphin-emu/dolphin#building-for-android
"If you do not have an Android dev environment set up, see AndroidSetup.md.": https://github.com/dolphin-emu/dolphin/blob/master/AndroidSetup.md

I don't expect anyone to be a developer already. But there is no point if you don't have the ability for it. So the first required skill is to be able to read....

(05-03-2016, 07:39 AM)Satan Wrote: [ -> ]Android hasn't seen attention in a couple months? Mate, have you seen the any of the recent builds?
Make exceptions consistent across all JITs/Interpreters (Fixes Pokemon Box). 3 days ago (affects Android)
Android: Also copy sys/Wii directory. 8 days ago (fixes MK Wii)
[Android] Fix android builds permanently. 4 weeks ago
Android: Update gradle version. 4 weeks ago
Not to mention all the other builds that don't have Android mentioned in the PR but there are still Android build downloads there. There are dev builds that don't include Android downloads, so obviously they aren't added just because, on some of the updates.

PR 3800, like many others, isn't made with Android in mind at all but still has an effect on Android because the Android version shares the emulation core with the PC version. Saying that nothing is changing in the Android version at all isn't true, but that very little work being done specifically for the Android version is true. PR 3767 is indeed a PR that fixes something for Android, but it's the only such PR I've seen in a while. The last two PRs are one-line changes that don't actually affect anything for end-users, they're just needed for the buildbots.

Android downloads are actually available for development versions just because. The goal is to have all builds available for all platforms. Sometimes the buildbot randomly doesn't build some platforms for some versions, but that's not intentional at all. For instance, "4.0-9237 Android: Also copy sys/Wii directory" was never built for Android, even though it only affects Android! Nobody would make that choice on their own.

(05-03-2016, 07:39 AM)Satan Wrote: [ -> ]My only question would be why the hell would Disc Speed matter when there is no disc?!

Dolphin emulates your ISO as a virtual disc. The FastDiscSpeed setting affects the virtual disc drive that the virtual disc is inserted into.

(05-03-2016, 04:21 PM)Jhonn Wrote: [ -> ]Current wiki maintainers (I speak for myself but I think MaJoR and Kolano probably share similar thoughts) aren't bothered in covering Android related stuff on the wiki, at least not yet: like others said, there's only one device currently capable of running the Android port and even on it you'll suffer with some slowdowns on demanding games, generally (but not limited to) unimplemented features on ARM64 JIT or OpenGL ES side.

So, considering the amount of work needed to refine the wiki to accommodate Android stuff is simply not worth at the moment (after all, currently there's little to no demand, from my point of view). The furthest we got was doing some mockups of the testing template in order to accommodate Android testing reports, and that's all. Anyway, just like the source code, the wiki is also open, you're free to contribute Android stuff to it...

/\ THIS. Some forum members like mimimi contributed lots of code to Dolphin and despite that he's still a regular user without any special tag. Would you just disregard his posts just because of the absence of a green dev tag? That's not how it works! Even I already contributed some very small and very specific code patches to Dolphin, would you disregard whatever I might have said about Dolphin's source code just because my username is behind a "Content Creator" tag?

I see, good to know about the wiki. You can hardly say, however, that I would be wrong for giving credit to someone listed as a dev and not giving credit to somebody with no tag. That's not how it should work. Anybody contributing to the inner workings and improvement of the software should be recognized as a developer. Any other way is just unintuitive.

(05-03-2016, 07:56 PM)degasus Wrote: [ -> ]Have you ever tried it?

ok, some steps for dummys: There is a "Code" button here on the forum, it will point you to: https://github.com/dolphin-emu/dolphin
There is a "Building for Android" topic, you just need to scroll down: https://github.com/dolphin-emu/dolphin#building-for-android
"If you do not have an Android dev environment set up, see AndroidSetup.md.": https://github.com/dolphin-emu/dolphin/blob/master/AndroidSetup.md

I don't expect anyone to be a developer already. But there is no point if you don't have the ability for it. So the first required skill is to be able to read....

Thank you for the information, exactly what I was looking for.

(05-03-2016, 08:56 PM)JosJuice Wrote: [ -> ]PR 3800, like many others, isn't made with Android in mind at all but still has an effect on Android because the Android version shares the emulation core with the PC version. Saying that nothing is changing in the Android version at all isn't true, but that very little work being done specifically for the Android version is true. PR 3767 is indeed a PR that fixes something for Android, but it's the only such PR I've seen in a while. The last two PRs are one-line changes that don't actually affect anything for end-users, they're just needed for the buildbots.

Android downloads are actually available for development versions just because. The goal is to have all builds available for all platforms. Sometimes the buildbot randomly doesn't build some platforms for some versions, but that's not intentional at all. For instance, "4.0-9237 Android: Also copy sys/Wii directory" was never built for Android, even though it only affects Android! Nobody would make that choice on their own.


Dolphin emulates your ISO as a virtual disc. The FastDiscSpeed setting affects the virtual disc drive that the virtual disc is inserted into.

I see. It's very good to know that's how the buildbot works, and what the situation with Android is. I hope you can see where I saw an illusion of Android builds being worked on, without knowing any of this.
Interesting that the FastDiscSpeed setting changes how the virtual drive works, for games. That would certainly explain why Simpsons H&R wasn't working, if that's how the .iso was indeed set up.

Thanks all, for your thorough answers. Much appreciated. As well, thanks for all the work that each of you have done, Android or otherwise.