Alpha Testing Underway!

[tgwaste]

Working very well so far although I still wish it didn't use the archaic app-data directory or at least let us specify where the program files live.   Well done though.  I really like the Simple GUI.
 

[Prophecy]

I'm pretty sure most of us are experiencing low frame rates since we are running arm v6. The best thing we could have to ease the issue a tiny bit is probably an option for frame skips. I use up to around +10-20 frame skips for my playstation emulator and it works much better. Dunno if that was already suggested though o.O

[Paul]

Hello Paul,

In latest Test App when i have to open rom, emulator is always closing before running a game. I have Xperia x10 mini pro and i dont know what should i do. Help

Sorry for my bad english. 

That's the same device Matts has, right?  I'll fix this next and try to post an update tonight.

thank you very much, the emulator works. you really did a good job, but i have got a question. the fps is very low (around 9-12), and the video + audio is laggy. is there a way to change that?

Which ROM, and what is your device?  The emulator will improve over time with optimizations, but don't expect it to happen overnight.

The best thing we could have to ease the issue a tiny bit is probably an option for frame skips.

Yep, that's one of the things that's high on my priority list.

Working very well so far although I still wish it didn't use the archaic app-data directory

This will be changed in the official build before I list it on the market (this version was just a quick update to stop the flood of emails asking why the emulator was crashing).

I am running your emulator on the original Droid. The emulator is working fine, but I was wondering if there was a way to boost the frame rate on this. Was this device meant to run the emulator smoothly? Please let me know your thoughts.

The original Droid is only 600MHz, so it will probably be a while before the emulator runs smoothly on it.  Optimizations are going to be my secondary focus in the Beta testing phase after bug-fixes.

[tgwaste]

I also get low 9-12 framerates whem playing.  im playing zelda oot on a htc thunderbolt.

[Paul]

@Paul - This particular thread is the Testing/discussion thread correct? Might i suggest making separate threads for Bug reports, tesing, etc. and then another one for QandA / Support as well as maybe a sickie for people who are new to the project and need to learn the basics, to avoid every new person asking the same questions and so on.

The Beta testing phase will also see changes to the forum boards.  Mupen64Plus-AE will be given its own category with boards for announcements, support, game compatibility, bug reports, and general discussion.  This particular thread will be in the announcements board, renamed "Alpha Testing History", and be locked.  A new thread called "Beta Test [ver #] Released!" will be created, and the .APK ad source-code will be available there.  A new thread will be created for each major update.

[Paul]

I also get low 9-12 framerates whem playing.  im playing zelda oot on a htc thunderbolt.

Yes, the higher-end games like the Zelda games (and don't get me started on Conkers) run slow for everyone, even us lucky ARM7a + Neon folks.  You can improve the speed by overclocking, but ultimately the solution will be lots of optimizations over time.

[tgwaste]

Cant wait to see the speeds on the Galaxy Nexus

[formiga]

The emulator on my ARMV6 device runs Mario64 near full speed(25-30fps)! Really thanks for this emulator!

[Paul]

I didn't have much time for programming this evening, but I managed to finish the plug-in configuration stuff.  This should fix Mats' and maciek9971's crash problem (if not, could one of you please post a logcat after the crash happens?)

It was necessary to also implement part of the "remember" code, but it is not complete yet.  I wouldn't be surprised if the config files get corrupt when doing various things, since it's only halfway implemented.  If that happens (menu or emulator crashes, virtual gamepad looks weird, etc), just refresh the app-data folder to fix it.

Also, for those who have small screens, please refresh your app-data folder and let me know how the larger font looks when the FPS indicator is on.

Test APK

[Epic_bubble]

I think it would probably be a good idea to continue testing the current builds with an unzipped mario 64 rom. That way you can be sure the crashes are not being caused by the roms.

[sergioc]

Thank you very much.....in xperia x10 mini pro it runs now, the only problem is the key mapping, it doesnt recognize the keys in the input settings and the virtual pad is too big but im not sure about what app-data folder i have to replace by to fix that, with the old app-data folder i just see the stick and the mario rom into the app runs about 13 fps without overclocking , thks again!! cant wait too see the final version

[Mats]

here is the logoutput Paul, it works ! but ven i disable the audio plugin it crash and is it possible to add frameskips so it wont lag so much ?

[neo3]

Also, for those who have small screens, please refresh your app-data folder and let me know how the larger font looks when the FPS indicator is on.

If you want, I think can decrease a little.

[Epic_bubble]

I have an idea for the emulator for the way the touch screen controls are displayed.
I dont know if this is possible in android but heres me idea:

Get users screen size
If screen size > x then use mupen64-ae analog //whatever size

So if the users screen if larger or smaller then a certain size the first time mupen is launched it will set the appropriate control size for that user.

Only make it do this on the first launch after installing or else it will override the users current settings.

Its hard to explain what I mean but im sure you understand.

[xperia64]

I think it would probably be a good idea to continue testing the current builds with an unzipped mario 64 rom. That way you can be sure the crashes are not being caused by the roms.

theres always the tiny mupen64plus.v64 rom thats included