Author Topic: Zelda OOT with Galaxy S3  (Read 3553 times)

Offline aphadyn

  • bit
  • Posts: 3
    • View Profile
Zelda OOT with Galaxy S3
« on: September 02, 2012, 04:58:00 PM »
Hello Board!

I tried Muppen64, latest version with my favorite Game Zelda!
It works well with libgles2rice... is it possible to deactivate the stretch mode? Link looks sooo fat. With the other plugin it is possible, but with this plugin I have so many GFX bugs... so I don't want to use this.

HELP!

:-) Thx a lot

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Zelda OOT with Galaxy S3
« Reply #1 on: September 02, 2012, 05:26:48 PM »
This option will be in the next update.  No way to do it in the current version though, sorry.
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 aphadyn

  • bit
  • Posts: 3
    • View Profile
Re: Zelda OOT with Galaxy S3
« Reply #2 on: September 02, 2012, 10:39:39 PM »
sounds great!

will it probably release in days, weeks or months?

Offline aphadyn

  • bit
  • Posts: 3
    • View Profile
Re: Zelda OOT with Galaxy S3
« Reply #3 on: September 02, 2012, 11:24:15 PM »
I tried the other plugin (gles2n64) again and found some advantages. In the game Zelda I can see my arrow on the map and the first beating heart is shown (with gles2rice both parts are completely missing on the screen). The big minus of gles2n64 is the flickering street/way on the ground. I tested all options but found no way to fix it.

Is this bug/problem known?

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Zelda OOT with Galaxy S3
« Reply #4 on: September 03, 2012, 06:57:14 AM »
Yes, this is a known problem.  Unlike some, it only affects some devices and not others (My Droid X, for example, had the problem but my Nexus doesn't).  The solution will likely have to tie into the hardware profiler, but I have to find the cause first.

As for the time frame for the next update, that is still up in the air.  I have to get a job first before I'll have time for programming.
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