Version 2.0 Release Candidates

[gdark100]

I will wait rc6... Why don't use a expand menu to show cheats?  Like a button show/hide cheats on play menu

[littleguy]

Already done.  Will be in RC6

[Paul]

I think I'll shoot for publishing tomorrow evening.  That will give RC6 (which I'll post this evening) a day to be tested, and if anything else serious surfaces I can push it back a while longer.  I'm not in any rush to publish, just like to have a plan for things.

[littleguy]

Cool.  There are a few missing translations at the moment, maybe we say no more changes to the source strings now, unless there's anything you wish to change/add/cleanup.

[littleguy]

There's one last option I can think to add, and that would be an override to enable/disable input unbiasing and normalizing.  Maybe turn those off by default, and tell Xbox users to enable it.

Edit: come to think of it, maybe we just leave things as they are on that topic.

[Paul]

Looks pretty good to me when I did a quick look-through earlier.  Only things I noticed were "Main Menu" and "Depth test", but those are minor points.

[littleguy]

Oops, you're right.  Any ideas what to call depth test?  Currently, checked means normal, unchecked means it does some rescaling and offset in the depth coordinate.

[littleguy]

Have you refreshed the translations yet? If not I'll do it real fast.

[Paul]

Thanks, I pulled from 00380eb2a5 when I build Release Candidate 6.  Hopefully that's everything.

[littleguy]

Yup.  I'm done for the night.  Didn't fix the Main Menu or Depth Test strings though.

[Paul]

No problem.  Thanks for all the help today.  I'm going to play around with the OUYA now.

[littleguy]

Cool.  Check out your OUYA thread, I posted a bunch of stuff that should hopefully help you sort out what's going on.

[xavouine]

Just tried RC6 on my TF300 (JB 4.1) and it is super smooth.
The only issue I've come up with is that you can't use the "share controller" with the on-screen input. In turn-based games for example, it would be nice to be able to both use the controls on-screen for those who don't have an external controller. ( Like I thought I was part of until I remembered my keyboard) .
I'm not a pro at programming but I was wondering if it was perhaps possible to integrate a "switch controller" in the in-game mini-menu.

[chery2k]

Update: Just as I feared it seems the tests I did above my perception has changed. I remapped the c-buttons (all 4) to my xperia play physicals buttons: triangle, square, x, and circle. I get the same result above on starfox never ending braking and sudden acceleration. I guess Mupen has problems emulating the c-buttons alone proving my touchpad problem is farce.

There's still a possibility that the problem is with Starfox itself.  Do you observe the same problem when you play a different ROM, say Mario 64?  Just trying to rule out other explanations.

I just got back from playing Mario 64 (latest mupen64 candidate) the c-buttons is played out perfectly on my xperia play (played the whole level without hiccups) Ok heres another game with c:button trouble it is also on Star Wars Episode 1 Pod Racer (No control over cbutton behavior). My pod racer always stays tilted during a race from start to finish. The pod racer can't center itself.

[chery2k]

Any chance to port the cbutton code from Mupen64 Version 1.9 (6 May 2012) towards the latest candidate? Something changed on the source code for the c:buttons not to be emulated perfectly on the touchpad or gamepad.  For some reason when I use that version I posted above I have no problems or limitations with the c:buttons being used on the touchpad or hard keys.