Author Topic: Zelda Majora's Mask Test  (Read 37980 times)

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Zelda Majora's Mask Test
« on: October 03, 2012, 09:03:29 AM »
THIS TOPIC IS CLOSED.  THE ORIGINAL TOPIC WAS ABOUT A PROBLEM THAT HAS SINCE BEEN FIXED.


Gillou68310 recently posted a solution for the Zelda Majora's Mask freeze at the first portal.  Since the fix was to regress the dynarec back to an earlier version, I'd like to get a bunch of people to test this build with a lot of different games to figure out what is different.  In particular, I'm looking for information on speed differences and differences in crashes, graphics problems, and other bugs.

Zelda MM Fix

For accuracy, please compare the above fixed version to latest build of the main branch (exactly the same, just with the newer dynarec that has the MM freeze bug):

Master Branch


I gave them different package names from each other, so they can both be installed at the same time without interfering with each other (to make comparisons easy).  The Majora's Mask fixed build has "ZeldaMM" at the end of the app title, so you can tell the two apart.  Note that these builds have the current load-state problem, so you won't be able to save-/ load-state or auto-save/ resume.  When that problem is fixed, I'll post the updated APKs here so testing will be easier.
« Last Edit: April 10, 2013, 07:18:04 AM by Paul »
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Zelda Majora's Mask Test
« Reply #1 on: October 03, 2012, 01:58:00 PM »
The Majora's Mask fixed build has "ZeldaMM" at the end of the app title, so you can tell the two apart.

I just realized that the "ZeldaMM" is getting cut off in the apps list.  If you have both of them installed, then if they are listed alphabetically, the Zelda Majora's Mask fixed build will be the second one.

You can also tell the apps apart when you run them, by looking at the title bar and action bar, which will have "ZeldaMM" in it for the MM fixed build.:



Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline xperia64

  • Moderator
  • double
  • *****
  • Posts: 591
    • View Profile
    • My Apps
Re: Zelda Majora's Mask Test
« Reply #2 on: October 03, 2012, 04:07:13 PM »

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Zelda Majora's Mask Test
« Reply #3 on: October 03, 2012, 04:12:12 PM »
Thanks, I had a feeling that was going to happen.  This is due to the changes by littleguy for joystick support (specifically "implements View.OnGenericMotionListener").  This limits the app to Honeycomb or higher.  I'll see about fixing that, sorry.
« Last Edit: October 03, 2012, 08:04:08 PM by Paul »
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Zelda Majora's Mask Test
« Reply #4 on: October 03, 2012, 05:38:42 PM »
Fixed.  The links in the original post are still the same.

There are still a couple of things in there that will probably crash on pre-Honeycomb devices (the "Credits" dialog, cheats description dialog, etc), but the apps should now be testable.  Sorry for not catching that earlier (don't have my Droid X with me to test on at the moment, just my Galaxy Nexus)
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Zelda Majora's Mask Test
« Reply #5 on: October 03, 2012, 08:02:30 PM »
I'll kick the testing off by posting the results of a recent test.

I decided to look at Banjo Tooie, because this is a game that has never worked on my Galaxy Nexus, and because I was just chatting with xperia64 about it.  I know that the problem is somewhere in the dynarec.  I also know that it runs differently between different devices and even between different builds of the emulator.  I figured this would make it a good candidate for testing.  I know these results will differ from other devices (xperia64 reported completely different results when he tested on his device).

I found that 10 out of 10 tries to run Banjo Tooie on the Master Branch crashed immediately after loading the ROM into memory.  7 out of 10 tries on the Zelda Majora's Mask fixed build also crashed in the same place.  3 out of 10 tries crashed after picking Game 1 (immediately after the puzzle-piece transition).  This is an interesting slight improvement, but the game is still unplayable on my phone.

My next test will be with Paper Mario, which had a similar problem to Majora's Mask where the game would freeze with the emulator core still running and functional.
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Zelda Majora's Mask Test
« Reply #6 on: October 03, 2012, 08:12:24 PM »
Paper Mario freeze when Luigi brings in the mail is still present.  This freeze only happens for gles2rice, so that is something that distinguishes it from the Majora's Mask freeze.  Next, I'm going to see if the freeze during the first battle is also still present.
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Zelda Majora's Mask Test
« Reply #7 on: October 03, 2012, 08:51:04 PM »
The freeze during the first battle (or any battle for that matter) is also still present.  These freezes, like the one where Luigi brings in the mail, are specific to gles2rice, and do not affect gles2n64.  This definitively shows that the Paper Mario freezes, despite appearing to have a similar behavior to the Majora's Mask freeze, are not actually related.

Next up is Rayman 2, which also has a game freeze while the core continues running.
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Zelda Majora's Mask Test
« Reply #8 on: October 03, 2012, 08:56:04 PM »
The Rayman 2 freeze is also still present in the Majora's Mask fixed build.   :'(

Just goes to show there is still a LOT of work left to do on this emulator.
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Zelda Majora's Mask Test
« Reply #9 on: October 03, 2012, 08:57:14 PM »
The Donkey Kong 64 crash is also still present.

The Blast Corpse crash is still there.

Excite Bike 64 still freezes.
« Last Edit: October 03, 2012, 09:21:07 PM by Paul »
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline Evil King Stan

  • byte
  • *
  • Posts: 33
    • View Profile
Re: Zelda Majora's Mask Test
« Reply #10 on: October 03, 2012, 09:06:02 PM »
But would Donkey Kong 64 actually be a problem with the dynarec? I know it also crashes on n64oid, and I believe the same problem persists with the PC version. http://code.google.com/p/mupen64plus/issues/detail?id=273 It's probably a problem with the core of the emulator.

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Zelda Majora's Mask Test
« Reply #11 on: October 03, 2012, 09:20:40 PM »
Yes, you are correct.  I'm just trying out all of the crashes and freezes to find anything that might behave differently.
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline Evil King Stan

  • byte
  • *
  • Posts: 33
    • View Profile
Re: Zelda Majora's Mask Test
« Reply #12 on: October 03, 2012, 09:39:01 PM »
I see what you mean. Also, has anybody tested to check if the Bomber's notebook works in Majora's Mask? In n64oid, even though you could get past the forest portal, when you become a member of the Bombers and get the notebook it can't be opened. What I mean is it just shows a black screen. You can still hear the cursor move over things in the notebook, selecting things etc. you just can't see anything. I'm hoping that it's just a problem with Yongzh's video plugin. I would normally test myself, but my phone is MIA at the moment.

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Zelda Majora's Mask Test
« Reply #13 on: October 03, 2012, 09:41:40 PM »
I do need to do some more extensive tests with games that I know already work, to find things that broke by the change.  In fact, the only differences I've found so far are that Majora's Mask doesn't freeze any more, and Banjo Tooie behaves differently.  There is definitely a lot more testing to be done to figure out how much is really changed by using the older dynarec.

One thing I'm really interested in are speed differences on lower-end devices.  I haven't noticed any speed differences on my Galaxy Nexus, but I know that slower devices are more sensitive to change.

I'll try out the bombers notebook when I have some time to play (if somebody else doesn't get to it first).  I tend to give up looking for all those dumb kids hiding around the town, haha.  Sounds like a frameskip issue.. may require gles2rice with skip frame disabled, but I'll see.
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline Evil King Stan

  • byte
  • *
  • Posts: 33
    • View Profile
Re: Zelda Majora's Mask Test
« Reply #14 on: October 03, 2012, 09:52:31 PM »
Thanks, I appreciate it, and when I get my phone back, which should be tomorrow or Friday, I'll do my part for testing games I own. Although I think that for the twelve hours this new APK has been up, you've done quite a bit of testing with it. Also, is it possible to somehow combine the dynarecs, or have both of them in the app? Then use some extra lines of code so that the emulator can recognize certain games as being better suited for the older dynarec, so that one would be loaded instead. That way it would kind of be a "best of both worlds" type of deal. I'm not entirely sure if it's at all possible. I'm still extremely amateur with programming, and emulation is just beyond me. I just figured it would be worth it to ask.