yashsingh1/xdaforums huggingface dataset:
[Xperia Play Android Development] acocalypso:
ok thanks a lot i tested it with gles2n64 and rice both the same.
[Xperia Play Android Development] paulscode:
That's weird. I don't think there is anything that would limit it. It targets version1.3, and CM7 fits that. That's the only limitation besides requiring an ARM processor, which the Play does. Anyone else having this problem with CM7? I'll try putting it on my phone to see if I get the same thing. Maybe the Xperia Play Optimized metadata is causing this?
[Xperia Play Android Development] bubblegumballoon:
It that is the problem then its going to be annoying to fix. You can remove the metadata to support custom roms but will also remove that app from the xperia launcher or you leave it in and not support custom roms. :/

Not a nice decision to make...

Is there any way to change the metadata after an app is installed? If its possible you could maybe make some option in the settings to add it to the launcher.

Im pretty sure its not possible to change the metadata after installation though.
[Xperia Play Android Development] paulscode:
Yeh, I'm hoping that's not the cause. I can built a test version without the metadata to see if that fixes the error message in My Apps.

Another thought I had is that versions of CM7 (not sure if this is one of them) are designed to boot off the 2.2 kernel, even though they are 2.3. Maybe this confuses the software? Don't know much about custom ROMs myself, so I couldn't really say.

We should know for sure if CM7 is the issue once someone else with it on their Xperia Play has/ doesn't have the same problem.
[Xperia Play Android Development] antEris:
Just downloaded and installed from the market on cm7.

Edit: Just to be clear, I don't get the "not compatible with you're device"
[Xperia Play Android Development] NeoandGeo:
It is weird since I was able to initially purchase it and install it. I also got one update I believe.
[Xperia Play Android Development] paulscode:
Yeh, the only thing that changed in the settings is the Xperia Play optimized metadata, but weird it only affects your phone. When I have the time, I'll build a version without that metadata, and that should tell us for sure if it is the problem or not.
[Xperia Play Android Development] German-Guy:
I love your Emulator! Thanks for this! Mario 64 playing with Analog Controls is perfect!

How i can maxed out Framerate & Performance in Mario? Any tricks or settings?

Thanks!

Gesendet von meinem R800i mit Tapatalk
[Xperia Play Android Development] NeoandGeo:
Until this is ever sorted out, can I just install your free version over the market version and overwrite?
[Xperia Play Android Development] paulscode:
You should be able to, since it has the same signature and everything (they are the same file, unless the market does something to it after I upload it). So you weren't actually able to update it through the market at all?

---------- Post added at 11:07 PM ---------- Previous post was at 10:57 PM ----------

The Xperia Play version is pretty well optimized already. It is using the gles2n64 plug-in which is the faster of the two, it has Redraw All disabled, screen-stretch disabled, and has the virtual gamepad disabled. You could also disable "Accurate N64 stick" under Skins->Touchpad to maybe get a tiny improvement (probably won't be noticable). If there are issues with the audio skipping, you could turn off Auto Frame Skip and play with the Max Frame Skip value (the higher the number, the smoother the emulation will run, but the choppier the frame rate will look). If you are comfortable playing without the audio, you can get a performance boost by disabling the audio plug-in under Settings->Audio, and choosing the librsp-hle-nosound.so RSP plug-in under Settings->RSP->Change. You could map the "Fast Forward" function to a button under Settings->Core->Configure, and press that button in-game to run it in fast motion (cool to watch, but not practical for playing really). I'll be adding more optimizations in the coming updates, but that's about all you can do for now (besides overclocking and killing unnecessary background processes on the phone).
[Xperia Play Android Development] acocalypso:
@Paul

is it possible to put the plugins in different folders like audio_plugins and video_plugins, so it wont confuse someone new who dont know for what the plugins are.
[Xperia Play Android Development] German-Guy:
Thanks for answer Paul! Works now a little bit smoother!

Now i have OC, too and the games run very fast!

Gesendet von meinem R800i mit Tapatalk
[Xperia Play Android Development] paulscode:
I can't move them to a different folder (that's where Android installs them). However, I can do it like I do with the skins, and create a plugin list for each type, and populate the "Change" menu with just those. This is probably a smarter way to do it anyway, since I eventually want to add the option of importing new plug-ins (once other devs take an interest in the project and start writing their own branches and plug-ins). It could start to become very difficult to keep track of the plug-ins if there are lots to choose from, not to mention unrooted devices won't be able to put them in the /data/data/...[etc] folder, so plug-ins will end up spanned across multiple folders.
[Xperia Play Android Development] Zerobarat1:
Does this emulator actually run anything else other than Maria and Zelda?! I just tried Mortal Kombat trilogy and it does not run it at all, even with rice shader and it still hangs
[Xperia Play Android Development] paulscode:
Yes it does play a lot of games (although a lot more do not work), and it can depend on the phone, OS version, and which video plug-in you use as well. I haven't tested a lot of different games yet myself (more focused on stability and device-specific problems at the moment), but ones that work fine on my phone (Droid X) with the default gles2n64 video plug-in are:

Banjo Kazooie (runs as well as Mario 64)

Banjo Tooio (crashes periodically, and laggy in a few places)

Goldeneye 007 (a tad slow, similar performance to Zelda)

Scooby Doo! Classic Creep Capers

Doubutsu no Mori (untranslated Animal Forest)

I know that's not much of a list. I recall someone was putting together a list of compatible games (not sure if its up to date, and if it only includes games tested with gles2n64 or if it also has gles2rice). If it hasn't been maintained, perhaps someone else could take on a project like this and put together a comprehensive list of games and compatibility based on device model, OS version, app version, and video plug-in version for Xperia Play. At some point I will do one for the Droid X on my forum.
[Xperia Play Android Development] NeoandGeo:
I've noticed in Banjo Kazooie that sometimes the text doesn't start displaying until about 2 seconds after the characters begin talking, and sometimes the text doesn't show up at all.
[Xperia Play Android Development] paulscode:
This could be related to the polygon offset values. I'm planning to add in some advanced settings to the GUI and have folks play around with them to come up with good default values to use on first run depending on the hardware profile. This should be a good way to handle small graphics problems like this one.
[Xperia Play Android Development] acocalypso:
I thought about something like pluins/Video and plugins/Audio
[Xperia Play Android Development] Nhialor:
where do you learn all this? it amazes me! You're a genius. I'm a beginner programmer (3rd year college) and hope to one day do projects like this. Any tips on where to go?
[Xperia Play Android Development] paulscode:
I prefer to learn by trial and error. Classes are useless in my opinion compared to real experience. When I began this project, I had no idea how or if it would ever get to this point, and I have no doubt that I'll learn a whole lot more before it is done. The only reason I know anything about polygon offsets is because I ran into it while tinkering with the code to try and fix a completely different problem. I may not be the fastest developer in the world, but I can definitely be persistent.
[Xperia Play Android Development] acocalypso:
Hey Paul i downloaded your source, what kind of IDE did you use? Eclipse?
[Xperia Play Android Development] acocalypso:
hey paul,

i looked thrue your code and the only i can say is wow =)

i figured out that you can make subdirs in lib/ like the previously mentioned folders audio and video.

hope it is useful for you
[Xperia Play Android Development] paulscode:
Normally I use Eclipse, but I've been building from the command line with this project, due to the "RAM full of zeros" bug which is preventing the code from being built as a single project.
[Xperia Play Android Development] CZroe:
Is there any reason to run the regular edition on my HP TouchPad tablet instead of the Xperia Play edition that I purchased for my Xperia phone?
[Xperia Play Android Development] bubblegumballoon:
Xperia play version only works on gingerbread devices, a lot of people still dont have gingerbread thats why there are two versions.

If you tablet is using android 2.3 or newer is should work anyway, Just remember to enable to touch screen controls in the settings. (in the xperia version these are off by default).
[Xperia Play Android Development] paulscode:
I posted an update to the emulator last night (link is on my forum).
[Xperia Play Android Development] paulscode:
Anyone else having problems after the update?

Reynaldo posted that the update caused games to stop working on his Xperia Play (link to his comment). Is anyone else having problems after the update? I wish I could respond to tell him to try choosing "Refresh App Data" from the Settings menu, because it is most likely a problem of corrupt config files. I'd like to fix this problem immediately if it is affecting a lot of users.
[Xperia Play Android Development] bubblegumballoon:
I dont think he has updated the official builds yet (theres no need for the two separate versions anymore), heres the test version that worked properly on the Xperia Play: http://www.paulscode.com/source/Mupen64Plus-AE/16SEP2011/Mupen64Plus-debug-0_1_c1.apk

EDIT: the emulator will be a lot faster when its finished, it still has alot of debugging code in it for stuff like scancode toast messages and specific logcat outputs, some versions also have things like neon optimisations disabled for test purposes.
[Xperia Play Android Development] Dyelon:
Oh so it only plays Super Mario 64?

I didn't realize it was SO early in development....cool cool.

I hope his methods work when he expands the program...n64oid can definitely use some competition
[Xperia Play Android Development] bubblegumballoon:
Nope it can run lots of different roms but all us testers are using the same version of super mario 64 to make sure test results are accurate. (if we all used different roms or different region versions of super mario 64 it would be a nightmare to debug the problems)

If you go into the app data you can change the rom manually, just replace mario.n64 with whatever rom you like but remember to rename your rom to mario.n64

And yes theres still a lot to be done before its finished :)
[Xperia Play Android Development] Dyelon:
thanks! how to map the xperia buttons?

i appreciate the help
[Xperia Play Android Development] bubblegumballoon:
you can manually configure the keys using the scan codes the app gives you by going to /app-data/paulscode.android.mupen64plus/data/inputauto.cfg/

It will be easier to wait until the emulator is finished though, When a GUI is implemented I would imagine that configuring buttons will be the same as n64oid.
[Xperia Play Android Development] Dyelon:
cool...thanks!

have you played any games that play better than n64oid? (or that dont play on n64oid at all)
[Xperia Play Android Development] bubblegumballoon:
the emulator will be a lot faster when its finished, it still has alot of debugging code in it for stuff like scancode toast messages and specific logcat outputs, some versions also have things like neon optimisations disabled for test purposes.

And also I havent really tried any other games tbh, Ive just been trying to help Paul locate bugs by testing like 100 different versions of the emulator with super mario 64 haha :)
[Xperia Play Android Development] Dyelon:
haha cool! that's awesome that you're helping out...PSX emulation is strong for xperia, with near-perfect emulation for the great majority of games...

but n64 needs alot of work, and this project, with its decidedly alternate method of improvement/growth is just the shot in the arm the community needs

analog touch pad support....that is enabled now?
[Xperia Play Android Development] bubblegumballoon:
No it is not added, although the beauty of this emulator is that it is open source (unlike n64oid which is mostly closed source) this means that any developer could take this emulator and add touch pad support if they wanted. :)
[Xperia Play Android Development] dsswoosh:
Looking forward to a finished version.

Would pay for a perfect n64 emu.
[Xperia Play Android Development] bubblegumballoon:
The emulator now works properly on a lot more devices including the Xperia play!

Also its now more compatible than n64oid, heres a comparison video of banjo-tooie running on both emulators:

[YOUTUBE]SNvfzy_iYR8[/YOUTUBE]

Banjo-Tooie crashes on N64oid but Starts up fine on Mupen64plus-ae
[Xperia Play Android Development] Nhialor:
sweet, any idea when it might go stable? he's making good progress and quite fast aswell
[Xperia Play Android Development] bubblegumballoon:
Yeah progress is going very quickly atm. And it will probably be a while before there is a stable build, he is still killing some graphics bugs on other devices atm before moving onto things like the GUI. I would say once the GUI is finished then it will be near completion.
[Xperia Play Android Development] yourmajesty90:
That's more than awesome really, even it's not complete, you can see how powerful this mobile is. It's an achievement and I have to thank you for it :)
[Xperia Play Android Development] bubblegumballoon:
Dont thank me thank Paul Lamb and all the people behind the original Mupen64 source code :)
[Xperia Play Android Development] El_Colombiano:
Nevermind, he should have stated that the only game that he allows to run right now is that exact version of Mario 64.

EDIT: Haha well Starcraft 64 "boots". Completely messed up graphically, and slow but at least it boots with sound! I already like this emulator better than N64oid.
[Xperia Play Android Development] Cat_On_Droid:
Banjo tooi?yesss?
[Xperia Play Android Development] bubblegumballoon:
Its advised to only use that rom when testing because it makes debugging the emulator easier, you can use any roms you like with it though.

---------- Post added at 07:44 PM ---------- Previous post was at 07:43 PM ----------

Is that a question? xD
[Xperia Play Android Development] Cat_On_Droid:
No.stupid 234 keyboard,still restoring apps
[Xperia Play Android Development] bubblegumballoon:
Quick update

Touch controls are alot more responsive, lots of bugs and graphics issues have been fixed and xperia play touch controls are being worked on.

Edit: Xperia play controls are now on hold until the GUI is done.
[Xperia Play Android Development] jacklebott:
Works fine on my PLAY
[Xperia Play Android Development] sonicfreak360:
Works fine for my play!
[Xperia Play Android Development] foryou168:
This is a great emu that support xplay touchpad, but its still laggy on oot even cpu oc to 1.6g

Sent from my R800i
[Xperia Play Android Development] bubblegumballoon:
Are you guys using the latest version? http://www.paulscode.com/forum/index.php?topic=96.0
[Xperia Play Android Development] German-Guy:
I using the last version from market. (updated yesterday). No fc or errors...

Another question: is the rgba_8888 sinfully for Xperia play performance?

For what is the alpha & fog mode in video settings?

Thanks!

Gesendet von meinem R800i mit Tapatalk
[Xperia Play Android Development] Barguast:
Has anyone got a decent controls config for Goldeneye? I switched to Solitaire and un-inverted the Y axis thinking that might improve things, and it does - but it still needs work!
[Xperia Play Android Development] ando_uk:
goldeneyes just one of those games what needs a dedicated n64 controller IMO

finally got round to installing this last night, only gripe is the touch pad is a little over sensitive

paul gotta say though some great work on porting this n64 collection in my pocket is pretty cool :D
[Xperia Play Android Development] scorpio16v:
The rgba_8888 fix is for devices like Galaxy S2 and fixed the color banding on graphics.

Don't use it, if your device isn't affected, becaused the higher color range used more resources on processor power.

Fog mode is for fog effects on graphics. It needs some fixes to work correctly.

But it needs processor power.

Alpha test ??? Don't know :confused:
[Xperia Play Android Development] bubblegumballoon:
Disabling alpha test will give you a very small speed boost but it will remove transparency from sprites so games will have significantly more graphical glitches.
[Xperia Play Android Development] paulscode:
Yes, the Alpha Test was mainly to improve the black-textures bug on some new dual-core devices like Droid Bionic, Droid Razer, and Motorola Atrix. It can also be used as a speed hack (but it creates graphics glitches). I mainly want to hook this up to gles2rice at some point, because without alpha test it runs at the same speed as gles2n64 on my phone (and renders most games better than gles2n64 even with the extra graphics problems).
[Xperia Play Android Development] CZroe:
Thanks. Will it work on ICS?

Goldeneye has a mode that can be played with two controllers for dual analog. Perhaps there's a way to map 1st and 2nd player analog to the left and right touchpads.
[Xperia Play Android Development] Mael5trom:
I have quite enjoyed this emulator so far, and i love the fact that paul is here and takes feedback from us.

In that vein, theres 2 things im hanging out for in addition to the eventual compatibility/performance updates.

a: let me pick a default folder for roms

b: allow me to manually set the analog sensitivity for both horizontal and vertical.

i would change it in games, but some games dont let me or it doesnt seem to work.

anyways, just some things to consider, thanks again, great work.
[Xperia Play Android Development] bubblegumballoon:
It should work but I havent tested it myself on ICS.
[Xperia Play Android Development] paulscode:
The first one can be done now. Put your roms anywhere on the SD card, and you will only have to navigate to that folder once. It will remember it as the default folder when you run the app again.

The second one, I'm not sure specifically what behavior you are after. Are you talking about implementing the analog control as three nested ovals instead of circles? The sensitivity for BOTH horizontal and vertical (at the same time) can be set in the pad.ini file under [sdcard]/Android/data/paulscode.android.mupen64plus/skins/touchpads/Mupen64Plus-AE-Xperia-Play/ (or something similar, I don't have my phone with me at the moment to check). The 3 radius values are what you can tweak to change the sensitivity. You could potentially do several different ones (say low, medium, and high sensitivity). Just add them to the touchpad_list.ini file in the skins/touchpads folder. However, changing the horizontal and vertical sensitivity separately from each other would take a bit more math to implement.. (might need some help on that one)
[Xperia Play Android Development] Mael5trom:
@paul

a: i hadnt realised it had that functionality now, i ended up getting lazy and moved some of my roms to the original default directory, is this from the newest update? i swear it didnt do it last week, ive navigated my sd card seemingly hundreds of times.

b: to elaborate i ment still using the one left touchpad, but being able to set how sensitive horizontal and vertical are individually.

as an example, i was testing some fps games due to them being reportedly rather difficult on the xplay touchpads, and since your touchpads are the best ive encountered i thought it would make a good test of the pads when properly implemented.

I found that the horizontal sensitivity was fairly good, whilst vertical sensitivity was extremely high and id be looking everywhere but straight ahead with the slightest movement.

I thought just having a couple of slider bars or editable values that allow you to set sensitivity fairly easily in settings would be easy (well relatively speaking) to implement, if thats not the case, thats cool, was just an idea.

again, thanks for taking feedback, especially from the xplay minority.
[Xperia Play Android Development] benc1213:
I have so far tried out Zelda:Oot and Goldeneye and the sound lags on both of them. Is there any way to fix this?
[Xperia Play Android Development] paulscode:
Sounds like the dead zone needs to be larger. Try playing around with the "min" value. You'll probably need to change "max" by an equal amount to maintain the same sensitivity (they should generally add up to something close to 100) Allowing horizontal and vertical settings to be independent will require implementing the nested ovals like I mentioned. I'll consider tackling this at some point if it can't be corrected through tweaking the existing settings.
[Xperia Play Android Development] jacklebott:
I've played some more today, and I've found that pressing the PLAY's L Button makes the game close. When I go back into the app, it force closes as soon as I open a game. My PLAY's L Button is set the the Camera function, could that be an issue? Should be able to make it ignore the normal function of the button?
[Xperia Play Android Development] mehdi.moha:
hi friends

nice update , but still have maaaaaaaaaaany problem on " Paper Mario"

thanks :)
[Xperia Play Android Development] sonicfreak360:
Just be patient...
[Xperia Play Android Development] DeanBoro:
that is exactly why :)
[Xperia Play Android Development] paulscode:
Thanks, at least that's a good working theory for why folks have reported the app is broken. I'm pretty sure I'm telling the app to ignore the normal function of every non-home button (except volume keys unless the option to disable them is checked), so I'll have to do some googling to see how to solve this problem.
[Xperia Play Android Development] paulscode:
jacklebott, when it gets into the state of crashing every time you open a game, does rebooting the phone fix the problem, or does it continue until you restore the app data (I'm trying to figure out if the configs are being corrupted or if it is just the previous SDL thread is still running - I'm thinking the latter)
[Xperia Play Android Development] jacklebott:
Rebooting seems to fix it, until I press L again..
[Xperia Play Android Development] paulscode:
Thanks! Could you post the logcat output after the crash happens (the first time, when you press L), so I can see if there is anything useful? (If you aren't familiar with accessing the logs, I posted instructions in this thread.
[Xperia Play Android Development] jacklebott:
Here's the logcat as per instruction, though it's excessively long due to "no service" errors, etc. Also, when the emulator closes, it keeps the service's icon in the taskbar even though the app is no longer running (no option manually close it in settings either). Once I go back into the app, I can then close it properly. I hope any of this helps