Issues running Mupen64plus on Android

I'm using Retroarch which includes the 'Mupen64plus' emulator. I've been able to run every N64 rom I've thrown at it, but the quality of the gameplay is not very good.. lots of video/audio stutters, and lag. The device also starts to burn my hands after about 10-15 minutes of playtime, though that might be normal. If you're in last place in F-Zero X, the gameplay is smooth as butter until coming up on a group of racers, from that point there is much lag (and heartache, lel).

I'm running Mupen on a Nexus 7 2012 (tablet) with default settings:

Audio
-Enable audio = on
-Dynamic rate control = on
-Audio Latency = 64ms (low)
-Automatically detect audio latency = on

Video
-Aspect Ratio = Auto
-VSync = on
-Auto-rotate = on
-Scale Integer = off
-Threaded video driver = on
-Forced refresh rate (hz) = 60
-Bilinear filter = on
-First pass shader = off
-On-screen fonts = on

I've turned the refresh rate down to 30, turned the 'bilinear filter' off, and turned off the 'threaded video driver', but neither of them combined seem to help gameplay.. it seems exactly the same?

N64 emulation is just very heavy for an andriod device alot more so than PSX emulation is, your machine is getting hot because it's using everything it has to offer

Try using N64oid. I used it on a Huawii y210 (seriously look it up as it's a lot less spec wise)

http://www.epforums.org/showthread.php?80762-N64oid

I used this and didn't have too much of a problem but mind I only tried out Mario64 and Mariokart which aren't exactly the most demanding games around.

Keep in mind as Zorlon said N64 can be heavy (especially for something like Goldeneye) and is far from perfect too.

Quote:

---

Originally Posted by Zorlon

N64 emulation is just very heavy for an andriod device alot more so than PSX emulation is, your machine is getting hot because it's using everything it has to offer

---

..more than the PS1? i know they came from the same generation, but dang.. compared to discs, cartridges don't strike me as being very performance heavy
:psyduck:

Quote:

---

Originally Posted by Zaladane

Try using N64oid. I used it on a Huawii y210 (seriously look it up as it's a lot less spec wise)

http://www.epforums.org/showthread.php?80762-N64oid

I used this and didn't have too much of a problem but mind I only tried out Mario64 and Mariokart which aren't exactly the most demanding games around.

Keep in mind as Zorlon said N64 can be heavy (especially for something like Goldeneye) and is far from perfect too.

---

Yes I may try a different emulator, but like keeping my gamesaves under one emulator.

I've asked the question before, but am gonna ask again to be sure---can an N64 gamesave created on one emulator be used on a different emulator? Are all N64 emus created equal when it comes to saving?

Quote:

---

Originally Posted by Double44

can an N64 gamesave created on one emulator be used on a different emulator? Are all N64 emus created equal when it comes to saving?

---

Generally speaking as long as both emulators create save files with the same file extension they will work interchangeably; this goes for most emulators for most consoles. It's usually more likely that they'll use different save state file types, so those won't be interchangeable.

One thing to watch out for is that, even if both emulators use the same file type, they might name saves differently. Some will give them the same name as the rom used, others will use different naming conventions (So say, MarioWorld.smc might make MarioWorld.sav on one, but make something like Super Mario World(U).sav on another).

Quote:

---

Originally Posted by MaslowK

Generally speaking as long as both emulators create save files with the same file extension they will work interchangeably; this goes for most emulators for most consoles. It's usually more likely that they'll use different save state file types, so those won't be interchangeable.

One thing to watch out for is that, even if both emulators use the same file type, they might name saves differently. Some will give them the same name as the rom used, others will use different naming conventions (So say, MarioWorld.smc might make MarioWorld.sav on one, but make something like Super Mario World(U).sav on another).

---

Could the MarioWorld.sav still be read using a rom titled Super Mario World.sfc, or do both have to be titled the same?

There's also the different rom extensions.. for instance, the SNES has .sfc and .smc. Could a save created by a .sfc rom be read when using a .smc rom?

Quote:

---

Originally Posted by Double44

..more than the PS1? i know they came from the same generation, but dang.. compared to discs, cartridges don't strike me as being very performance heavy
:psyduck:

---

More to do with the hardware you're trying to emulate really. But yeah it's heavy for how old it is.
As already mentioned some particular games (Goldeneye) are even more demanding on top of the hardware issue.

Quote:

---

Originally Posted by Double44

Could the MarioWorld.sav still be read using a rom titled Super Mario World.sfc, or do both have to be titled the same?

---

What I was getting at is that what the .sav needs to be named depends on the emulator. So if say the emulator you used gave your .sav a different name than the rom, you wouldn't want to rename the save if using that same emulator. If you went to use that same save on a different emulator, say one that makes .sav files with the same name as your rom, then you'd want to give it the same name as your rom.

Quote:

---

Originally Posted by Double44

There's also the different rom extensions.. for instance, the SNES has .sfc and .smc. Could a save created by a .sfc rom be read when using a .smc rom?

---

In the case of SNES roms, .smc and .sfc files are the same thing; you could even rename one to the other and it would still work. Unless the emulator uses the sfc/smc bit as part of the save files name (i've never seen SNES emulators do this though) it won't make a difference.