Beta Testing Has Begun!

[Paul]

if im gonna buy a new phone, some ideas i need android on it  and run mupen64plus ae in full speed

Xperia Play 

[crualfoxhound]

if im gonna buy a new phone, some ideas i need android on it  and run mupen64plus ae in full speed

Xperia Play 

Agree with paul.

But if u want a device to angle loads of different emulators at full speed.
A dualcore is needed.
My galaxy note runs n64oid,mupen64plus android edition and fpse at full speed.
Thanks to schtruck for implementing the dualcore option.

Catch ya later.

[Mats]

if im gonna buy a new phone, some ideas i need android on it  and run mupen64plus ae in full speed

Xperia Play 

thanks i think i go for a xperia play

[Epic_bubble]

if im gonna buy a new phone, some ideas i need android on it  and run mupen64plus ae in full speed

Xperia Play 

thanks i think i go for a xperia play

In the UK the xperia play has gone very cheap too. I could get it locked to o2 for just about ?150

It would be tough to find a phone with the same specs for that price point.

EDIT: typo

[Mats]

if im gonna buy a new phone, some ideas i need android on it  and run mupen64plus ae in full speed

Xperia Play 

thanks i think i go for a xperia play

In the UK the xperia play has gone very cheap too. I got get it locked to o2 for just about ?150

It would be tough to find a phone with the same specs for that price point.

yeah ! i know, in Norway is it pretty cheap too its cost about 1500 nok. its about 230,76 dollars

[Paul]

I posted an update to fix some various bugs.  The Market listing has also been updated.

Bug Fixes:
- Improved compressed-ROM reading (Game Hunter ROMs no longer require unzipping)
- Fixed problem where input from IMEs was not detected by Key Listener dialog
- Implemented work-around for missing buttons bug (enable Skins->Virtual Gamepad->Redraw All).  This bug will be fixed in a future update after implementing the virtual gamepad in GLES instead of through the Android API (which is painfully slow and buggy).
- (Xperia Play version) Fixed Xperia Play "optimized" metadata
- (Xperia Play version) Fixed missing plug-ins in "change" menus

I've also noticed that Zelda OOT has started crashing randomly (it never used to do this).  I'll need to go back through the archives to figure out when this started, to determine what I changed that created the problem.

[Rezk]

Hi Paul,

Great, great work you did with this project. I'm running it on my Xperia Play right now and Mario 64 is running smoothly with light overclocking.

I was wondering though, is it possible to get rid of the black borders up and down of the screen during playing? I turned on stretching but it only stretches horizontally, not vertically. Hope you have an answer for this.

[Paul]

Hi Paul,

Great, great work you did with this project. I'm running it on my Xperia Play right now and Mario 64 is running smoothly with light overclocking.

I was wondering though, is it possible to get rid of the black borders up and down of the screen during playing? I turned on stretching but it only stretches horizontally, not vertically. Hope you have an answer for this.

With screen stretch, is the black on the top and bottom very small (i.e. half the width of the notification bar)?  As I recall there was some reason I couldn't stretch it any more than this, but I'll take another look at this.

[Mats]

on my xperia x8 it runs very slow with frameskip on 5, in future is it possible to get full speed ??

[Paul]

Yes, it will get there eventually.  I've got a couple good ideas for optimizations to try once I work out the stability issues that some folks are having.

[Epic_bubble]

Hi Paul,

Great, great work you did with this project. I'm running it on my Xperia Play right now and Mario 64 is running smoothly with light overclocking.

I was wondering though, is it possible to get rid of the black borders up and down of the screen during playing? I turned on stretching but it only stretches horizontally, not vertically. Hope you have an answer for this.

With screen stretch, is the black on the top and bottom very small (i.e. half the width of the notification bar)?  As I recall there was some reason I couldn't stretch it any more than this, but I'll take another look at this.

Its the same on other N64 emulators, I believe it is to do with the fact that a lot of n64 games are displayed in different resolutions. Super smash brother is the most noticeable as there is a small black border around the entire edge of the screen while games like super mario 64 only have a slight black bar on the top and bottom.

One way I could think of that could be used to get around this would be by allowing two values to be specified for the x and y axis which would determine how much the games are manually stretched to.

This has been done before with the xperia plays native ps1 emulator, it gives you a 'zoom' option so there are no black bars on the screen but some of the gameplay is cut off on the edges because it is zoomed it a bit too much.

Heres a mock up of before and after manual stretching:


Also because each n64 game has a different resolution you would need to create a way to create manual config profiles so for example a user could have super smash brothers set to fill the screen but they could create a separate profile for mario otherwise their previous setting would stretch mario 64 too much.

I hope this makes sense

[firstpoke]

Hello Paul,

Did you implemented the "AnalogKey Option" for the USB Joystick Center, to move Mario with analog moves ?

I've tested your last beta today and I can not mapping keys, because your "Key Listener" PopUp can not handle IME Keys (only Hardware pressed Keys).

poke

[Paul]

I will have this implemented in the next update.  Are you sure you are using the latest version (1.2), because I thought I fixed that bug.  At least the IMEs I have on my phone seem to work (anyone else have this problem still?).  I'll have to rig up an adapter to use USB on my phone, so would you like to run the tests for me (assuming we can get the input to be detected in the first place)

[scorpio16v]

Botton mapping is somthing strange.
Mapping the sixaxis over USB, is not a problem.
Mapping it with the sixaxis app as an IME is broken. Only some keys are working.
For example, if I map the square-button to a key (0-9)(a-z), it'll recognized by the key listener.
But if I do it with the x-button, the key listener get no input.
Mapping via config file has worked in older versions. Your SDL-Scancode program has it recognized too.

add:
After a test with my SGS 2, it seems OK on this device. The problem affects only on my tegra tablet.

That must be a problem with the sixaxis program, not yours.

Another add:
This problem seems to occur, if you have enabled a touch profile on the sixaxis app.

@ poke
thank you, for adding the option for other mac adresses in your app. It's worth a million. 

[firstpoke]

Mapping it with the sixaxis app as an IME is broken.

That must be a problem with the sixaxis program, not yours.

@ poke
thank you, for adding the option for other mac adresses in your app. It's worth a million. 

I can not map keys with the USB Joystick Center, too. I really think its not a Sixaxis/USB Joystick Center problem. Tested with the last Beta 1.2 Version.

Thanks, the option for other mac addresses was wanted from many users, so I did it

@paul, ok, then I will testing the analog key function in the next version. Some hints to your GUI... it would be better, to sort your Settings GUI, because there are many options that a user never use. ROM selection, KEY Mapping, should be in an easy GUI mode at the top of the menu, so the user can use your Emu without to search his needed functions.

Maybe it would be better, if you could implement my GUI style with the horizontal Box-Scrollbars and Top-Switches (take a look at my Frodo C64 USB Emu). The users love this GUI

I'll have to rig up an adapter to use USB on my phone, so would you like to run the tests for me (assuming we can get the input to be detected in the first place)

I use an USB OTG cable also with my xoom... I can test it if you want. You can send me pre-version apk's to "poke64738 at googlemail dot com"