Author Topic: Version 2.0 Release Candidates  (Read 51667 times)

Offline gdark100

  • Green Team
  • byte
  • *
  • Posts: 48
    • View Profile
Re: Version 2.0 Release Candidates
« Reply #120 on: January 14, 2013, 04:14:50 PM »
I will wait rc6... Why don't use a expand menu to show cheats?  Like a button show/hide cheats on play menu
Motorola Xoom 2 ME:
OMAP CPU Dual Core @ 1.2 Ghz and PowerVR SGX 540 GPU
8.2'' 1280x800 Screen
1GB Ram Dual Channel
32 GB internal storage

Galaxy SII Lite:
NovaThor U8500 CPU Dual Core @ 1.0 Ghz and Mali-400MP GPU
4.0'' 800x480 Screen
768MB Ram
8GB internal storage

Huawei U8150:
Qualcomm CPU @ 532 Mhz, no GPU
3'' 240x320 Screen
256 MB Ram

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: Version 2.0 Release Candidates
« Reply #121 on: January 14, 2013, 04:39:42 PM »
Already done.  Will be in RC6
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Version 2.0 Release Candidates
« Reply #122 on: January 14, 2013, 04:55:19 PM »
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.
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: Version 2.0 Release Candidates
« Reply #123 on: January 14, 2013, 05:08:01 PM »
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.
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: Version 2.0 Release Candidates
« Reply #124 on: January 14, 2013, 05:09:42 PM »
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.
« Last Edit: January 14, 2013, 05:12:28 PM by littleguy »
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Version 2.0 Release Candidates
« Reply #125 on: January 14, 2013, 05:13:38 PM »
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.
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: Version 2.0 Release Candidates
« Reply #126 on: January 14, 2013, 05:45:17 PM »
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.
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: Version 2.0 Release Candidates
« Reply #127 on: January 14, 2013, 06:50:50 PM »
Have you refreshed the translations yet? If not I'll do it real fast.
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Version 2.0 Release Candidates
« Reply #128 on: January 14, 2013, 07:45:03 PM »
Thanks, I pulled from 00380eb2a5 when I build Release Candidate 6.  Hopefully that's everything.
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: Version 2.0 Release Candidates
« Reply #129 on: January 14, 2013, 07:46:10 PM »
Yup.  I'm done for the night.  Didn't fix the Main Menu or Depth Test strings though.
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Version 2.0 Release Candidates
« Reply #130 on: January 14, 2013, 07:47:46 PM »
No problem.  Thanks for all the help today.  I'm going to play around with the OUYA now.
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: Version 2.0 Release Candidates
« Reply #131 on: January 14, 2013, 07:51:00 PM »
Cool.  Check out your OUYA thread, I posted a bunch of stuff that should hopefully help you sort out what's going on.
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline xavouine

  • bit
  • Posts: 2
    • View Profile
Re: Version 2.0 Release Candidates
« Reply #132 on: January 14, 2013, 09:48:29 PM »
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.
« Last Edit: January 14, 2013, 10:23:43 PM by xavouine »

Offline chery2k

  • bit
  • Posts: 8
    • View Profile
Re: Version 2.0 Release Candidates
« Reply #133 on: January 15, 2013, 12:34:51 AM »
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.
« Last Edit: January 15, 2013, 01:12:29 AM by chery2k »

Offline chery2k

  • bit
  • Posts: 8
    • View Profile
Re: Version 2.0 Release Candidates
« Reply #134 on: January 15, 2013, 01:16:20 AM »
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.
« Last Edit: January 15, 2013, 01:24:59 AM by chery2k »