Alpha Testing Underway!

[Mats]

is some of the futures added, if it post a test

[TFreestone]

Might i suggest renaming the plugins section just to settings so really non developer users dont get confused?

if they don't even know what a plugin is...
@epic_bubble
I have dissabled the sound
i know all that
also why eould paul build in support for armv5-7 if he didn't want people with slower phones to use it?
i will overclock once villainrom is done for the galaxy ace.
Thanks for sharing though
@paul
i will any preference of game or just all of em?

[vicsiol]

Great work paul
First emulator for armv6
My galaxy 5 say thanks

[Epic_bubble]

Might i suggest renaming the plugins section just to settings so really non developer users dont get confused?

I kind of agree with this, people with a little emulator knowledge will know what a plugin is but average users might be a little confused.

[scorpio16v]

@paul
i will any preference of game or just all of em?

I belive, if you'll test zelda or other heavy titles, you'll need much time for the slomo-dia-show. 
zelda is even very slow on dual cores with rice plugin.

Funny thing is, that titles like diddi kong racing run better and faster on rice than on gles2n64 for my SGS2 and choppy and slow on tegra2  devices. 

[Mats]

this is a great emulator and my loved xperia x8 say thanks 

[Paul]

Might i suggest renaming the plugins section just to settings so really non developer users dont get confused?

I suppose that makes sense in the current basic setup.  Eventually, though, the GUI is going to be focused around the skins and plug-ins, so I reserve the right to change it back in the future when it makes more sense

is some of the futures added, if it post a test

I'll post a test soon.  Just trying to bring all the pieces together (keeping track of the views is a bit more complicated than it seems at first glance).  There are a few minor bugs that I mentioned as well that I want to address first (so the tests can focus on compatibility issues rather than fixing bugs I already know about).  They called me in to work this afternoon, so I probably won't have this finished today like I planned.

why eould paul build in support for armv5-7 if he didn't want people with slower phones to use it?

The main reason for this is because "necessity is the mother of invention", as they say.  I figure folks with slower devices will be the driving force behind optimizations and getting the emulator to run as efficiently as possible.  There's really no reason 1 GHz or higher is necessary to emulate a 93.75 MHz chip.  The general rule-of-thumb minimum requirement for emulating a CPU is at least 5X speed on the host hardware, which would translate to 470 MHz.  Clearly there is plenty of room for improvement.

i will any preference of game or just all of em?

Any that you had strange graphics problems (this is more out of curiosity than anything)  I expect gles2rice to be a lot better than gles2n64 with regards to accuracy (I'll likely make it the default video plug-in when the slow-speed problem has been improved).  Like scorpio16v said, though, it will be painfully time consuming on your device, so no worries if you don't have the time for this (I'll get around to doing more comparison tests when I move to the beta testing phase).

[TFreestone]

I know why you did i was asking bubble a rhetoricle question
I will thouroughly test rice after you finish the ui
one question though. I'm sure you know about the icontrolpad, are you planing to ad support for it? Or is there already a way that i haen't found yet?

[nscxp2005]

Hi Paul,

I was just wondering. In the official build of the GUI with it have Xperia Play Touch Pad support?

Excellent progress on the emulator.

Keep up the fantastic work.

All the best]

NSCXP2005

[scorpio16v]

The icontrolpad works fine with bluezIME.
You can map all buttons incl. the analog sticks, but you can use the sticks only for digital button press. So there is no way to walk slow with mario, for example.
As long as an emulator supports button-mapping, the iControllpad and bluezIME will work.

[TFreestone]

The icontrolpad works fine with bluezIME.
You can map all buttons incl. the analog sticks, but you can use the sticks only for digital button press. So there is no way to walk slow with mario, for example.
As long as an emulator supports button-mapping, the iControllpad and bluezIME will work.

thanks! But i was really hopeing for analogue any way you can do that paul?

[Epic_bubble]

Hi Paul,

I was just wondering. In the official build of the GUI with it have Xperia Play Touch Pad support?

Excellent progress on the emulator.

Keep up the fantastic work.

All the best]

NSCXP2005

Paul did say a while back that he wont be maintaining the xperia touchpad brach of the emulator but that he would compile a build once the GUI was done.

There are also instructions on the opening post on how to implement the controls to the newest builds yourself, If you know how to compile code then its not too hard to do.

[Paul]

I was just wondering. In the official build of the GUI with it have Xperia Play Touch Pad support?

Once I've debugged the GUI, I'll add it to the Xperia Play branch and list both on the market (and they'll both be available here too, along with the source code of course).

But i was really hopeing for analogue any way you can do that paul?

BluezIME is open-source, so yes.  Basically, I'd need to take the components of BluezIME that interpret the input, and instead of converting it into keyboard input, convert it into N64 input directly (i.e. a special input plug-in).  This is on my to-do list for some point in the future.

[nscxp2005]

Once I've debugged the GUI, I'll add it to the Xperia Play branch and list both on the market (and they'll both be available here too, along with the source code of course).

Excellent, Thank you Paul.

Much appreciated.

PS So does that mean with every new release of the emulator there will be a version with Xperia Play controls added?

[Paul]

So does that mean with every new release of the emulator there will be a version with Xperia Play controls added?

Depends on the changes.  For changes to the Java components, probably not every new update just because it is fairly tedious to maintain two of everything.  For changes to the plug-ins and core (which most updates will be focused on anyway), that is much easier (I can link both projects to the same native libraries, so both benefit from any changes).