Author Topic: 3.0 Alpha Testing  (Read 288001 times)

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: 3.0 Alpha Testing
« Reply #120 on: December 10, 2014, 12:13:14 PM »
@retroben Thanks for the very clear report. :)

The regression is probably due to this:
https://github.com/mupen64plus-ae/mupen64plus-ae/commit/6f66b694aa610b2d7cf569e2fbdcc7f979cc7bd9#diff-06f7a4d6687ec9ef8bc2e5cfe714616eR470

@retroben You could try deleting that line (file located in /Android/data/org.mupen64plusae.v3.alpha) and see if the speed returns.

There are also other glide settings you can change manually:
https://groups.google.com/forum/#!topic/mupen64plus/urawGVtw2qY
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: 3.0 Alpha Testing
« Reply #121 on: December 10, 2014, 12:16:08 PM »
Here's the upstream commit.  Notice the comments at the bottom of the page.

https://github.com/mupen64plus/mupen64plus-video-glide64mk2/commit/b2a78163914a54d8ed1c1e2641cbf47f6896e250
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline retroben

  • float
  • ****
  • Posts: 432
    • View Profile
Re: 3.0 Alpha Testing
« Reply #122 on: December 10, 2014, 01:08:37 PM »
So,install Alpha 5 again and change that setting?
It does not alter the performance in Alpha 4 when "fb_read_always" is default in the user config.
« Last Edit: December 10, 2014, 01:18:57 PM by retroben »

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: 3.0 Alpha Testing
« Reply #123 on: December 10, 2014, 01:15:54 PM »
Yes, please install alpha 5 and delete that line from Glid64Mk2.ini.  Thanks.
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline retroben

  • float
  • ****
  • Posts: 432
    • View Profile
Re: 3.0 Alpha Testing
« Reply #124 on: December 10, 2014, 01:19:13 PM »
Did what you said,and I already mentioned better speeds with it off.
It is still quite a bit slower compared to Alpha 4.
The previously mentioned regression where Link's pause model is missing the torso,and with other various graphics missing and glitched.
The biggest offender is when fb_read_always is turned off in Alpha 5,the fade transitions no longer work.
Strangely,this does not happen with older Alphas having it turned off,they properly show fade transitions.

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: 3.0 Alpha Testing
« Reply #125 on: December 10, 2014, 01:34:08 PM »
@Paul - Could you please post the commit hashes next to the builds in the OP?  Thanks.
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: 3495
  • Developer
    • View Profile
    • PaulsCode.Com
Re: 3.0 Alpha Testing
« Reply #126 on: December 10, 2014, 01:37:01 PM »
Sure, I'll do that in a bit when I get a few minutes
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: 3.0 Alpha Testing
« Reply #127 on: December 10, 2014, 01:46:18 PM »
@retroben - The only configuration changes made between alpha 4 and alpha 5 were to some default settings.  You could try changing these back to their v4 values by editing mupen64plus.cfg

DefaultsAlpha 4Alpha 5
adjust_aspect10
fb_read_always01
vsync01
clock_24_hr01
wrpAnisotropic01
aspect-10

Edit: The other possible cause is the new rotation setting.
« Last Edit: December 10, 2014, 01:49:15 PM by littleguy »
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline retroben

  • float
  • ****
  • Posts: 432
    • View Profile
Re: 3.0 Alpha Testing
« Reply #128 on: December 10, 2014, 02:51:12 PM »
It could either be the Vsync slowing things dowm or the wrpAnisotropic,or both.

Edit:Can't be either since both are already disabled on my settings files.

Still saying the main cause is something that got mixed up in Glide64 after the data merge.
« Last Edit: December 10, 2014, 03:12:41 PM by retroben »

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3495
  • Developer
    • View Profile
    • PaulsCode.Com
Re: 3.0 Alpha Testing
« Reply #129 on: December 10, 2014, 06:13:34 PM »
Added links to commits for each Alpha in OP.
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: 3495
  • Developer
    • View Profile
    • PaulsCode.Com
Re: 3.0 Alpha Testing
« Reply #130 on: December 10, 2014, 07:07:41 PM »
@retroben, I built a version of Alpha 5 with the Glide64 rotation stuff removed.  Please note whether this performs any differently than Alpha5:

Alpha 5b (Glide64 no rotation comparison) 4fe367f
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: 3.0 Alpha Testing
« Reply #131 on: December 10, 2014, 07:41:05 PM »
I just git-bisected.  This is the commit that breaks it, no doubt about it.
https://github.com/mupen64plus-ae/mupen64plus-ae/commit/6f66b694aa610b2d7cf569e2fbdcc7f979cc7bd9

One thing I stupidly forgot to do was bump the asset version, so testers will have to manually "Reload App Resources" when going from Alpha4 (or earlier) to Alpha5, and vice versa.  This is located in
    Global Settings->Data->Reload App Resources

We'll need to update the asset version before posting Alpha6.
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline xperia64

  • Moderator
  • double
  • *****
  • Posts: 591
    • View Profile
    • My Apps
Re: 3.0 Alpha Testing
« Reply #132 on: December 10, 2014, 07:43:50 PM »
Yep. Yes those games have FB effects, but the nuked speed is definitely not worth it.

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3495
  • Developer
    • View Profile
    • PaulsCode.Com
Re: 3.0 Alpha Testing
« Reply #133 on: December 10, 2014, 07:48:55 PM »
I'm thinking these settings will have to work similarly to the other ini settings we were discussing (except in this case, it is organized by ROM header name instead of MD5).  Probably could do the same thing, where we maintain two files (one for defaults, and one for user overrides).  The overrides could still be stored by MD5 (so from user's perspective it is no different than the other ini settings).  Then give the plugin a small INI file upon launch for the specific game being launched.  Sounds complicated though now that I'm typing it out...
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: 3.0 Alpha Testing
« Reply #134 on: December 10, 2014, 07:51:27 PM »
First we should study the upstream code.  We may be able to override the setting in mupen64plus.cfg.  That would be much easier by far.
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version