Beta Testing Has Begun!

[Meneer Jansen]

Unfortunately the two Star Wars games that are unique to this console are not playable:

• Rogue Squadron
• Shadows of the Empire

I know that all the Rogue Squadrons used quite a bit of console trickery. Level 5 was famous for pulling all kinds of techno stunts for the RS games and all the emulators, even Dolphin, have problems running them properly.

That's very unfortunate! However, 'Shadows of the Empire' is from another developer I think... I remember playing it on my PC. I don't know if it was the PC CD-ROM version or via an N64 emulator....

Anyway, do you know of a list of working games?

[Paul]

Anyway, do you know of a list of working games?

That is a more complicated question than it sounds.  In large part, it depends on your device, due to an enormous variation in speed and graphics differences.  The definition of "working" depends on who is talking (many would consider that to mean "emulated perfectly".. which no game currently is, while others would consider that to mean "doesn't crash".. which doesn't take into account graphics problems).  A better word to use might be "playable", but even that is a matter of personal opinion and experience with the game in question.  The best solution is to write out an objective list of specific behaviors for specific devices and specific versions of the emulator.  Then folks can use to make the determination themselves if something is playable or not.

Anyway, you could try the wiki and look for a device with similar specs to yours if yours isn't on there.  I'm not sure how up to date it is since the 2.0 upgrade which fixed a lot of games (and broke others), so take that into consideration when reading.  If you can contribute to the wiki, that would be very nice.

[littleguy]

Where's the wiki?

[Paul]

OP of this thread

[xperia64]

Glitch with dropdown menus: all are functional, but show %1$s instead of the actual selection

[littleguy]

Thanks, just noticed that yesterday and already fixed it.

[Meneer Jansen]

Anyway, do you know of a list of working games?

That is a more complicated question than it sounds.  In large part, it depends on your device, due to an enormous variation in speed and graphics differences.  The definition of "working" depends on who is talking (many would consider that to mean "emulated perfectly".. which no game currently is, while others would consider that to mean "doesn't crash".. which doesn't take into account graphics problems).  A better word to use might be "playable", but even that is a matter of personal opinion and experience with the game in question.  The best solution is to write out an objective list of specific behaviors for specific devices and specific versions of the emulator.  Then folks can use to make the determination themselves if something is playable or not.

Anyway, you could try the wiki and look for a device with similar specs to yours if yours isn't on there.  I'm not sure how up to date it is since the 2.0 upgrade which fixed a lot of games (and broke others), so take that into consideration when reading.  If you can contribute to the wiki, that would be very nice.

Thank you very much for your clear reply. Is this the Wiki you mean: http://en.wikipedia.org/wiki/Mupen64Plus [nofollow] ?

And are you still actively developing Mupen64+AE for a larger amount of ROM's compatibility? Ore are you only trying to make it faster....?

P.S. Thanks for porting Mupen to Android! Now I can play 'Shadowman' when I'm on the road. Its one of the games that completely blew me away at the time. Until 'Half Life 2' came! The PSX rom don't work on the 'droid emu I have (FPSE, which is very good!). Now all we have left, to play all those old time classics, is to wait for an Win 95 or XP emulator on Android (may take a few years, ha ha). This is, however, if Win8 won't become more popular than Android on mobile devices (I recon Win8 is backwards compatible w/ XP andDirectX).

[Paul]

Is this the Wiki you mean: http://en.wikipedia.org/wiki/Mupen64Plus ?

I meant the one in the OP of this thread:

Compatibility Wiki

And are you still actively developing Mupen64+AE for a larger amount of ROM's compatibility? Ore are you only trying to make it faster....?

Most of what I've done recently has been with the front-end, but I want to get back to working on the native code again.  The vast majority of game compatibility problems stem from problems either with the video plug-ins (GLES2) or with the dynarec (ARM assembly).  I've never tried to pretend I am very good with either of these -- they are in fact two of my weakest skills (especially assembly language).  This is why progress in the area of game compatibility has been slow for most of the life of the project (the biggest improvements have come when other devs have volunteered to help out).

I'm hoping to get more devs on board with some assembly or GLES2 skills to help out in this area (the OUYA and Open Pandora ports will hopefully help to increase visibility and interest in the project).  To answer your question, my focus will be mainly on improving speed once I get back to working on the native code (I want to try updating to SDL 2.0 to see if that has any improvement, and if not, removing the SDL layer all together, as Yongzh did for N64oid).

Now all we have left, to play all those old time classics, is to wait for an Win 95 or XP emulator on Android (may take a few years, ha ha). This is, however, if Win8 won't become more popular than Android on mobile devices (I recon Win8 is backwards compatible w/ XP andDirectX).

The biggest problem with Windows emulation on Android via WINE or ReactOS, or backwards compatibility for XP using Win8, is that most mobile devices use the ARM architecture instead of x86 like PCs.  Emulating x86 on ARM has a HUGE impact on performance.  An increasing number of mobile devices are starting to have x86 chips in them, so perhaps in the near future x86 will beat out ARM in the mobile market, making this a more realistic possibility.  Otherwise we'll have to wait several more device generations before XP would be usable within an x86 emulator,  I'm afraid (Win8 or otherwise).  It is possible that a future version of ARM will be capable of virtualization, which would make something like VirtualBox for Android possible (where XP could be installed as a guest system).

[Arceles]

I bought the emulator now that it is on play store and indeed I'm quite satisfied with it... this emulator just needs to use now the proper power of the RAZR i (x86) processor. It's not difficult to implement the optimization for this phone, I was betatester of the ePSXe emulator and in two days got a version that was optimized for this phone, the emulation went from 24 fps up to 230+... so please consider this option. Thanks!

[Paul]

It is using the x86 dynarec, so from that perspective the core is already optimized for your device.  Slowness compared to the PC version is likely due to the Android port of SDL and the video plug-ins which use GLES2 instead of OpenGL.

[Paul]

Published update 2.1.0.  See the changelog for the new features in this version.

[Pau]

I bought the emulator now that it is on play store and indeed I'm quite satisfied with it... this emulator just needs to use now the proper power of the RAZR i (x86) processor. It's not difficult to implement the optimization for this phone, I was betatester of the ePSXe emulator and in two days got a version that was optimized for this phone, the emulation went from 24 fps up to 230+... so please consider this option. Thanks!

Please specify "optimization" (as in: what did they do and where can I see the changes for their optimizations). Because m64p+ae can just render 10x more frames per VI. But this would decrease the user experience. So please give us enough information to check for possible optimization. "Make it fast" doesn't help at all. Or even better: Please ask Paul to pull the optimization from your git repo.

[BobCat]

beta for what?

[Jxx]

Just installed 2.1.0 on my galaxy tab 2 7.0
Works great with my nyko playpad and zelda ocarina of time

added a page to the compatibility wiki for tab 2

[Paul]

I published version 2.1.1.  The only feedback I've gotten so far is "What happened to gles2n64?"  I don't see any problems on my devices, but if anyone notices some problems introduced in this update that weren't there in 2.1.0, be sure to let me know.