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

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Version 2.0 Release Candidates
« Reply #60 on: January 11, 2013, 06:38:38 AM »
Unfortunately I don't have an Xperia Play for testing on so might take me a while to figure out.  Littleguy will probably have better luck tracking this one down if he is experiencing the problem 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 littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: Version 2.0 Release Candidates
« Reply #61 on: January 11, 2013, 06:45:22 AM »
I'll start looking into it.  Not sure how much progress I can make since it involves the core and isn't something easy like an npe.
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline zack

  • Developer
  • byte
  • *****
  • Posts: 36
    • View Profile
    • InfuseDreams
Re: Version 2.0 Release Candidates
« Reply #62 on: January 11, 2013, 06:46:01 AM »
The good news is that it works on my Samsung Galaxy S2 now. So I can test my rice changes at last :)


PS: I think we should consider moving the "Z" button from the top left corner to next to the B/A buttons.
Have any of you tried to play goldeneye? It's impossible with the "Z" button in that top left corner :p
« Last Edit: January 11, 2013, 06:48:03 AM by zack »

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Version 2.0 Release Candidates
« Reply #63 on: January 11, 2013, 07:43:48 AM »
I'll start looking into it.  Not sure how much progress I can make since it involves the core and isn't something easy like an npe.
Seemed like an issue with JNI, though I didn't see the full log cat before the acra report.  Another possibility is it could be a similar problem as the rsp-hle bug, needing to build in arm mode instead of thumb.  Should be able to put in some logging to check if the file libxperia-touchpad.so exists, and what error message is in the Exception thrown of you call System.load on it.

--EDIT--
This is assuming your problem is the same one as zack posted.  The following from zack's crash is what gives me the impression it is probably a JNI issue:

Code: [Select]
E/AndroidRuntime( 4986): FATAL EXCEPTION: main
E/AndroidRuntime( 4986): java.lang.RuntimeException: Unable to start activity ComponentInfo{paulscode.android.mupen64plusae/paulscode.android.mupen64plusae.GameActivityXperiaPlay}: java.lang.IllegalArgumentException: Unable to load native library: /data/data/paulscode.android.mupen64plusae/lib/libxperia-touchpad.so
E/AndroidRuntime( 4986):        at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1659)
E/AndroidRuntime( 4986):        at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1675)
E/AndroidRuntime( 4986):        at android.app.ActivityThread.access$1500(ActivityThread.java:121)
E/AndroidRuntime( 4986):        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:943)
E/AndroidRuntime( 4986):        at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 4986):        at android.os.Looper.loop(Looper.java:130)
E/AndroidRuntime( 4986):        at android.app.ActivityThread.main(ActivityThread.java:3701)
E/AndroidRuntime( 4986):        at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 4986):        at java.lang.reflect.Method.invoke(Method.java:507)
E/AndroidRuntime( 4986):        at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:866)
E/AndroidRuntime( 4986):        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:624)
E/AndroidRuntime( 4986):        at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 4986): Caused by: java.lang.IllegalArgumentException: Unable to load native library: /data/data/paulscode.android.mupen64plusae/lib/libxperia-touchpad.so
E/AndroidRuntime( 4986):        at android.app.NativeActivity.onCreate(NativeActivity.java:199)
E/AndroidRuntime( 4986):        at paulscode.android.mupen64plusae.GameActivityXperiaPlay.onCreate(GameActivityXperiaPlay.java:61)
E/AndroidRuntime( 4986):        at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)
E/AndroidRuntime( 4986):        at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1623)
E/AndroidRuntime( 4986):        ... 11 more
--END EDIT--

PS: I think we should consider moving the "Z" button from the top left corner to next to the B/A buttons.
Have any of you tried to play goldeneye? It's impossible with the "Z" button in that top left corner :p

That's more an application for a custom gamepad layout than for the default.  Most games would be difficult if z required lifting the right thumb (fast jump in Mario 64, for example).  Top-right corner most closely matches the N64 controller on multi-touch devices, because you can trigger z with the side of your left index finger while using analog with your left thumb and A/ B with your right thumb, and R with the side of your right index finger.  Same fingers as used on the controller (albeit a bit more awkward)
« Last Edit: January 11, 2013, 08:08:20 AM by Paul »
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 gdark100

  • Green Team
  • byte
  • *
  • Posts: 48
    • View Profile
Re: Version 2.0 Release Candidates
« Reply #64 on: January 11, 2013, 08:33:55 AM »
paul, i tried with glesn64 plugin, disabled and enabled depth test, no changes. The path still flickering , sometimes it just disappear. The fps count is strange, when i play the game seems fullspeed, but counter show 17 fps  :o Only in cutscenes the sound is choppy, during gameplay is ok.

Tested with Super Mario 64. With depth test off, the shadow flicker a lot, disappear some times, show cut. With depth test on, don't flicker anymore, but shadow still cut and disappear some times.

Here some nice pics:
Spoiler: show

Depth test on

Depth test off

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 #65 on: January 11, 2013, 09:46:00 AM »
With depth test on, don't flicker anymore, but shadow still cut and disappear some times.

Paul - I can add a preference for manually selecting the polygon-offset profile in the Video menu.  Might solve some of these problems.  The only question is what to write in the UI list.  I'll use the following for now, unless you can think of something better:

Default
OMAP
OMAP (alternate)
IMAP
Qualcomm
Tegra
Auto detect*

* Default setting on install
« Last Edit: January 11, 2013, 09:54:00 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 #66 on: January 11, 2013, 09:50:32 AM »
It's a different story this time.

http://pastebin.com/Kcp9vvas

Seems to be related to the xperia touchpad library (same thing littleguy reported) this time.

Bug fixed in the source by Sven.  Makefile-related bug, introduced just a few days ago.

Now I'm wondering if it's a similar story for all the other missing library exceptions.
« Last Edit: January 11, 2013, 09:52:08 AM 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 #67 on: January 11, 2013, 09:53:14 AM »
That seems best, from a human-readable perspective, vs. displaying the numbers.  Those names were originally just meant for me to distinguish the profiles, and don't really have a 1-to-1 relation with the devices that fit into them.  I can foresee having to explain that to folks a few times when they wonder why their random ARMv6 device fits into the Tegra category, for example, but oh well!
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 Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Version 2.0 Release Candidates
« Reply #68 on: January 11, 2013, 09:57:20 AM »
paul, i tried with glesn64 plugin, disabled and enabled depth test, no changes. The path still flickering , sometimes it just disappear.
I have a feeling this is related to Tribuffer Opt.  Could you post a screenshot? (the Tribuffer Opt bug has an easily recognizable look to 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 #69 on: January 11, 2013, 10:00:06 AM »
Might be able to add an extra popup with info on that particular menu item.

The question to me is whether you'd ever have, say, an OMAP device whose best setting was, say, Tegra.  That would be really confusing.
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline gdark100

  • Green Team
  • byte
  • *
  • Posts: 48
    • View Profile
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 Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Version 2.0 Release Candidates
« Reply #71 on: January 11, 2013, 03:49:55 PM »
Here more screenshots from zelda oot:
That's not Tribuffer Opt - definitely a polygon offset issue there.  Should be able to fix Mario and OOT for your device at once if we're lucky.
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 Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Version 2.0 Release Candidates
« Reply #72 on: January 11, 2013, 03:51:28 PM »
The question to me is whether you'd ever have, say, an OMAP device whose best setting was, say, Tegra.
That's a good point.  It might be better to just list the numbers, or maybe "Profile A", "Profile B", etc.  It is an advanced setting anyway, so don't have to make it understandable by everyone.
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 #73 on: January 11, 2013, 04:13:19 PM »
Alright.  I could just use cryptic codes to make it easy for devs and hard-core users, while still encouraging the general population to try all of them if they're having problems.

Title: Hardware profile (affects texture/shadow flicker)
Summary: [selected value]
Entries:
  Auto-detect*
  Standard
  O1
  O2
  Q
  T

Remind me again - is this specific to one of the video plugins, or does it affect them both?
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 #74 on: January 11, 2013, 04:36:02 PM »
It affects both
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