Author Topic: Latest Build! [CLOSED]  (Read 106596 times)

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: Latest Build!
« Reply #330 on: January 04, 2013, 11:12:51 AM »
The problem may be here, in AppData.java:

Code: [Select]
        if( DOWNLOAD_TO_SDCARD )
        {
            storageDir = Environment.getExternalStorageDirectory().getAbsolutePath();
            dataDir = storageDir + "/Android/data/" + packageName;
            // for me, dataDir = /storage/emulated/0/Android/data/paulscode.android.mupen64plusae
        }
        else
        {
            storageDir = context.getFilesDir().getAbsolutePath();
            dataDir = storageDir;
            // for me, dataDir = /data/data/paulscode.android.mupen64plusae/files
        }

Right now DOWNLOAD_TO_SDCARD is hard-coded to true.  I'm wondering if we should be using

Code: [Select]
storageDir = Environment.getExternalStorageDirectory().getAbsolutePath();
dataDir = context.getFilesDir().getAbsolutePath();

And possibly storing the values internally using File objects rather than Strings.
« Last Edit: January 04, 2013, 11:17:06 AM by littleguy »
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline RogerSmith

  • byte
  • *
  • Posts: 25
    • View Profile
Re: Latest Build!
« Reply #331 on: January 04, 2013, 11:38:21 AM »
Well last night I stayed up transferring the ROM folder to internal, mnt/SD and mnt/SD/external1 and mupen did the same thing in all 3 locations. But I won't get home till after 3pm, so I'll try to help figure this out and help you guys best i can.


Offline jonjon

  • byte
  • *
  • Posts: 31
    • View Profile
Re: Latest Build!
« Reply #332 on: January 04, 2013, 08:46:16 PM »
Has any one noticed that if you choose a custom save directory that mupen creates a /sdcard/GameSaves directory upon application launch regardless of your choice? Not sure if it counts as a bug but it coaxed me into using the default gamesaves folder...

Latest build is working great for me apart from some occasional lag waiting for the cheats list to load after pressing start (being able to disable seeing the cheats list might be nice idea).

The ROM 'restart' option is really helpful. The in-game 'reset game' option seems a little redundant now though - is there a difference between choosing 'reset game' over 'main menu' seeing that you're going to press 'restart' in the main menu either way?

Ocarina of time often freezes on the gles plugin after 30-60 mins of playing. If I slot load at that point the game works but it's too choppy to be playable - at least it means that the auto save need not be corrupted since it autosaves at the slot load point ok(obviously progress is still lost though).

Not being able to see the meters and hearts with rice plugin makes me put up with the occasional crash on gles.. Is there anyway to debug this crashing issue? Do others have the same problem with oot?

Cheers

Jon

/nexus 7

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3494
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Latest Build!
« Reply #333 on: January 04, 2013, 11:34:26 PM »
For the freezing, does it make any difference if you turn off frame skipping?
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 jonjon

  • byte
  • *
  • Posts: 31
    • View Profile
Re: Latest Build!
« Reply #334 on: January 05, 2013, 12:00:00 AM »
Frame skipping is usually off... Could that be the problem?

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3494
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Latest Build!
« Reply #335 on: January 05, 2013, 01:03:07 AM »
Not off no... usually freezing problems happen when it's on.  Note that gles2n64 and gles2rice have separate frame skipping settings, incase you didn't notice that already.
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 jonjon

  • byte
  • *
  • Posts: 31
    • View Profile
Re: Latest Build!
« Reply #336 on: January 05, 2013, 03:43:19 PM »
Yes, I have frame skip off on both plugins... I even went back to double check.

Is there anything I can do to further debug the problem? The last time it happened I could feel it coming as there was some slow down just before - next time I will try to save just before and see whether reloading the game fresh at afterwards leads to a freeze or not.

But beyond that, is there anything more I can do?

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3494
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Latest Build!
« Reply #337 on: January 05, 2013, 05:05:48 PM »
It's a unique problem, doesn't really affect other devices as far as I know.  Is the problem new in one of the latest builds, or has it always had the problem on your device?  Short of tinkering with all the settings, I don't really have any good suggestions off hand.
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 SilentHunter382

  • byte
  • *
  • Posts: 11
    • View Profile
Re: Latest Build!
« Reply #338 on: January 06, 2013, 05:56:51 AM »

In the latest snapshot, the Settings-->Input menu should look like this:
 - Touchscreen
 - Touchpad      <---- shows up ONLY for Xperia PLAY users
 - Controller
 - Octagonal joystick limits
 - Mappable volume keys
 - Player 2
 - Player 3
 - Player 4

If you don't see the Touchpad menu on the Xperia PLAY, please let me know.

Sorry for a late update.

Perfect I can see the menu and the control work now. Fantastic job.  :D
Current Phone: Sony Ericsson: Xperia Play

Offline Sowden

  • byte
  • *
  • Posts: 14
    • View Profile
Re: Latest Build!
« Reply #339 on: January 06, 2013, 09:18:50 PM »
Hey guys.  I wanted to post another video with more problems I'm having with the IME.

http://youtu.be/wcJa4BExfNI

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: Latest Build!
« Reply #340 on: January 06, 2013, 09:39:48 PM »
Love your videos 8)  Laughed a few times.

Anyhow, thanks for going to such lengths, it looks like we're headed in the right direction.  I tested with USB/BT Joystick Center IME and a logitech controller and didn't experience the same problems, so I'm scratching my head.  Fortunately Paul has the same N64 controller adapter and that should speed up the debug.

The next snapshot will include a diagnostics utility in the Advanced menu that will display raw gamepad signals, and that may also help with debugging.
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: 3494
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Latest Build!
« Reply #341 on: January 06, 2013, 09:51:44 PM »
I should be able to help test the adapters soon.  Melinda and I spent most of today filling out paperwork for the mortgage on the new house, and once we are signed and move in, I'll be able to get my stuff out of storage (including my USB OTG adapter, so I can connect some controllers to my phone).  I may be able to test sooner if my OUYA devkit arrives before then  ;D
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 Brock

  • byte
  • *
  • Posts: 27
    • View Profile
Re: Latest Build!
« Reply #342 on: January 06, 2013, 11:41:37 PM »
Hey Paul, glad to see that the project is up and going again. :-)
I've been playing around with everything and testing Paper Mario (My Favorite Game) and I would like to report to you what I've found so far.
gles2n64 :
Depth Test decreases the frequency of the flashing background by about 30-40%. It's still pretty bad in most areas.
Graphics are more consistant compaired to rice.

gles2rice:
Very playable with auto frameskip. Very slow in 1.9.2.
Fast Texture Loading solves solid background issues.
Framelimiter helps keep frame rate around 30, without it framerate is 20-60.

All above applies to both of my devices.

I will do more testing and report back, will test as builds are released.

Device: Samsung Galaxy S2
CPU: 1.5 GHz Dual Core  Snapdragon S3
RAM: 1GB
Resolution: 800 x 480
Rom: 4.1.2 Jelly Bean Stock

Device: Mach Speed Trio Stealth G2
CPU: 1.5 GHz Dual Core ARM Cortex-A9
RAM: 1GB DDR3
Resolution: 800x480
Rom: 4.0.4 ICS Stock

Device: Mach Speed Trio
CPU: 1.2 GHz Boxchip A13
RAM: 512MB DDR3
Resolution: 480x272
Rom: 4.0.4 ICS Stock

Offline archangeles

  • byte
  • *
  • Posts: 11
    • View Profile
Re: Latest Build!
« Reply #343 on: January 07, 2013, 12:26:15 AM »
This new build doesn't load hi res textures, the game goes back to the menu to restart or resume

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3494
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Latest Build! [CLOSED]
« Reply #344 on: January 07, 2013, 09:54:16 PM »
This thread is now closed
Version 2.0 Release Candidates are being stress-tested in this thread.  Please help with the testing!
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