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

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Version 2.0 Release Candidates
« Reply #90 on: January 13, 2013, 12:27:36 AM »
Posted Release Candidate 5.  The main reason I posted another build so quickly, is because I built the OUYA components into this one and I want to make sure that doesn't break the app for anyone (hoping not to need a separate branch in the repository for the OUYA port).  There shouldn't be any effect except to be a slightly larger APK file.  Littleguy fixed up the cheats menu in this build as well, so be sure to test that part out too.
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 chery2k

  • bit
  • Posts: 8
    • View Profile
Re: Version 2.0 Release Candidates
« Reply #91 on: January 13, 2013, 01:52:56 AM »
Hi I have the xperia play and I have a problem with the touchpads (enabled). The issues is when either the left or right side of the touchpad is programmed to take control of the c-button (yellow buttons) it would become unstable. ( Mupen64 was emulating the c-button perfectly after the 5 mins after that it went kaput). Meaning If I were to play Starfox with the c-buttons on either side of the touchpad it would force my ship to use boost or use the brakes repeatedly and it keeps on going. (I no longer have control of the c-buttons on the touchpad it wont allow me to do anything else). But for some reason when I was using the opposite touchpad to move the joystick it is very accurate and responsive to move my ship around. (No hiccups). Note* I used both of the touchpads on the test above.

I noticed during my testing if I just use c-button touchpad (no joystick this time) the same situation happens above even with a fresh install of mupen64.
« Last Edit: January 13, 2013, 02:01:02 AM by chery2k »

Offline zack

  • Developer
  • byte
  • *****
  • Posts: 36
    • View Profile
    • InfuseDreams
Re: Version 2.0 Release Candidates
« Reply #92 on: January 13, 2013, 09:45:57 AM »
Just pushed in some Makefile CFlags optimisations.
From testing it seems to have resulted in a small speed improvement.
« Last Edit: January 13, 2013, 09:48:17 AM by zack »

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: Version 2.0 Release Candidates
« Reply #93 on: January 13, 2013, 01:36:28 PM »
Hi I have the xperia play and I have a problem with the touchpads (enabled). The issues is when either the left or right side of the touchpad is programmed to take control of the c-button (yellow buttons) it would become unstable. ( Mupen64 was emulating the c-button perfectly after the 5 mins after that it went kaput). Meaning If I were to play Starfox with the c-buttons on either side of the touchpad it would force my ship to use boost or use the brakes repeatedly and it keeps on going. (I no longer have control of the c-buttons on the touchpad it wont allow me to do anything else). But for some reason when I was using the opposite touchpad to move the joystick it is very accurate and responsive to move my ship around. (No hiccups). Note* I used both of the touchpads on the test above.

I noticed during my testing if I just use c-button touchpad (no joystick this time) the same situation happens above even with a fresh install of mupen64.

I can't seem to replicate this behavior on my stock Verizon Xperia PLAY.  Just to clarify, you tried both layouts for the touchpad?  So when the c-buttons were on the left pad they were unusable, and when the c-buttons were on the right pad they were also unusable?  Or is it your right pad that is messed up, whether it's the c-buttons or the analog stick mapped to the right pad?

Not sure what you mean in your second paragraph.
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline chery2k

  • bit
  • Posts: 8
    • View Profile
Re: Version 2.0 Release Candidates
« Reply #94 on: January 13, 2013, 09:15:54 PM »
Correct. I am using stock 2.3.4 R800i gingerbread firmware. Yes I tried both layouts for the touchpads. When the c-buttons were setup either left or right touchpads they become unusable after 5 minutes. The emulator correctly emulated the c-buttons before that 5 minute time period. Idk know if this maybe an issue but I am using a Sandisk class 6 sd card there might be a lag or response time between the xperia play and the sd card in terms of communication. Which might explain my sudden slow up or boost in Starfox.

The touchpad that was emulating the n64 joystick is working 100% either side it was emulated on the touchpad.
« Last Edit: January 14, 2013, 12:48:22 AM by chery2k »

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: Version 2.0 Release Candidates
« Reply #95 on: January 13, 2013, 09:20:15 PM »
Ok, thanks, now I understand what you're saying.  I wonder if it's a Starfox issue or if it's a Mupen issue.  Do you get the same problem when you run a different game?
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline chery2k

  • bit
  • Posts: 8
    • View Profile
Re: Version 2.0 Release Candidates
« Reply #96 on: January 14, 2013, 12:57:59 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.

Offline maalox

  • byte
  • *
  • Posts: 17
    • View Profile
Re: Version 2.0 Release Candidates
« Reply #97 on: January 14, 2013, 05:09:15 AM »
So my Sixaxis Controllers are not behaving well anymore. In the previous test builds, they were both mapable and usable, but now there's a problem on Release Candidate 5 (not sure when the problem first started):

I have 2 controllers connected via the Sixaxis Controller app.
If I enable only player 1's controller in Mupen, then that controller works just fine. However, the second controller still works as a duplicate of the first controller (i.e. both controllers control player 1).

If I enable player 1 AND player 2's controllers in MuPen, I am able to use either controller to map buttons in the settings page. Also note that the controllers are recognized differently in the multiplayer mapping page under the Play menu (one of them is identified as "Device 11 (Gamepad 0)", and the other is identified as "Device 12 (Gamepad 1)". HOWEVER, neither controller works while playing a game. This is true whether I map none, one, or both controllers in the Multiplayer mapping page prior to starting the game.

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: Version 2.0 Release Candidates
« Reply #98 on: January 14, 2013, 05:41:54 AM »
So my Sixaxis Controllers are not behaving well anymore. In the previous test builds, they were both mapable and usable, but now there's a problem on Release Candidate 5 (not sure when the problem first started):
...
HOWEVER, neither controller works while playing a game. This is true whether I map none, one, or both controllers in the Multiplayer mapping page prior to starting the game.

This one sounds just like what I observed a few posts back.

Argh.  I'm implementing the option to allow multiple players to share a single keyboard/controller (issue 24, an easy fix) and suddenly realized multiplayer isn't working properly.  Doing a git-bisect right now to fix it.

Edit: Nevermind.  Another case of needed-to-clean-before-build.

Paul - Is it possible that RC5 wasn't cleaned fully before it was built?  All these controller issues are bewildering me after weeks of stability.

Edit: Just installed the binary from the link above.  Indeed it appears to be a build issue with RC5 since I observe the same issue others have reported.  When I clean build the same commit from source, the problem disappears.
« Last Edit: January 14, 2013, 07:52:41 AM by littleguy »
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 #99 on: January 14, 2013, 05:44:13 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.
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 #100 on: January 14, 2013, 05:49:27 AM »
However, the second controller still works as a duplicate of the first controller (i.e. both controllers control player 1).

If I enable player 1 AND player 2's controllers in MuPen, I am able to use either controller to map buttons in the settings page.
These behaviors are both by design.  In single player mode, controller differentiation is turned off so that you don't need to go through the hassle of assigning gamepads to players in the Play menu.  In the button mapping screen, controller differentiation is turned off for the same reason.  I know that's a little different that what you might find on a PC game, but the Android SDK has a few quirks that we're trying our best to work around.
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 #101 on: January 14, 2013, 08:04:32 AM »
Indeed it appears to be a build issue with RC5 since I observe the same issue others have reported.  When I clean build the same commit from source, the problem disappears.

Wow, sorry..  I thought I had done a clean build, but I will post another clean build (after doing an ant clean, ndk-build clean, and deleting the libs, obj, gen, and bin folders just to be sure).  Unfortunately I have to stay at work late today to work on a project that's due by the end of the week, so I probably won't be able to post it until later, unless I can find some free time today at some point to build it.
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 #102 on: January 14, 2013, 08:07:20 AM »
I reset to RC5 commit and did a clean from android and when I built I got the same problem.  Something more to it than a vanilla clean.  I manually deleted gen/R and am trying it now.

Edit. That didn't do it.  Looking into some other things now.  If the next couple things I try don't fix it, I'll look at the compiler settings that got changed a few RCs ago.  Maybe something got lost.
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 #103 on: January 14, 2013, 08:35:45 AM »
Ok Paul, here's what you need to do for the next release to get input back on track.

1. Hard reset to RC 2.a.0 (stash/commit local changes first if necessary)
2. Clean the project and manually delete gen/../R.java just to be safe
3. Build and run
4. Hard reset back to the latest commit (or 2.a.5), clean project, and manually delete R.java again
5. Build and run

That fixes the problem for me, so it's probably something to do with the .cproject changes I made right after RC0.  I'll take a fine tooth comb to that and push a fix today.

In the meantime might be wise to post a notice or something on the first post.
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 #104 on: January 14, 2013, 08:45:46 AM »
Thanks for tracking that down.  Sorry to sound like a newb, but do you happen to know the command-line git commands to do the stash/commit, hard reset, hard reset, then get my changes back from step 1?  I remember you are using a GUI, so you might not know off hand.  I'll probably have to do a little googling to make sure I don't mess something up.  I really should research a good git GUI for Linux.  I tried one from the Ubuntu software repository (called something like git gui I think), but couldn't do much with it except push pull and commit, which are easy from the command line anyway.
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