Author Topic: Beta Testing Has Begun!  (Read 959234 times)

Offline maciek9971

  • bit
  • Posts: 8
    • View Profile
Re: Beta Testing Has Begun!
« Reply #75 on: January 02, 2012, 07:30:49 PM »
I wish that someday I will play on my Xperia X10 Mini pro games like Mario 64 or Zelda in at least 30 FPS.
Today Zelda Ocarina of Time is running for me like 2-7 FPS, and Mario 5-20 FPS in game.

Offline firstpoke

  • byte
  • *
  • Posts: 27
    • View Profile
Re: Beta Testing Has Begun!
« Reply #76 on: January 03, 2012, 07:46:01 AM »
I found the problem (small typo).  Sorry about that, it should work fine now:

Analog Keys Test

Thanks paul! its working fine now. Analog Control is very funny ;D  (I've tested it with my N64 -> USB Adapter and a real N64 controller)

KeyListener: only KeyCodes like KeyCode.KEYCODE_BUTTON_1 ... 16  are not working, because these codes are to high for SDL. But its not really a problem, because I can change the keys in my USB Joystick Center to lower keys like A-Z.

greetings
poke
« Last Edit: January 03, 2012, 07:48:49 AM by firstpoke »

Offline firstpoke

  • byte
  • *
  • Posts: 27
    • View Profile
Re: Beta Testing Has Begun!
« Reply #77 on: January 03, 2012, 07:54:57 AM »
Ah, now it would be fine... if I could play a 2 Player game :)

But this needs a 2nd Joystick config in the KeyListener site.

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Beta Testing Has Begun!
« Reply #78 on: January 03, 2012, 01:58:09 PM »
I'll be adding support for the remaining 3 joysticks in the near future.
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: Beta Testing Has Begun!
« Reply #79 on: January 03, 2012, 04:59:11 PM »
I accidentally posted the wrong source code version yesterday.  If you are building from source, please re-download it (the links are the same, in the original post of this thread).
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: Beta Testing Has Begun!
« Reply #80 on: January 03, 2012, 05:59:44 PM »
KeyListener: only KeyCodes like KeyCode.KEYCODE_BUTTON_1 ... 16  are not working, because these codes are to high for SDL. But its not really a problem, because I can change the keys in my USB Joystick Center to lower keys like A-Z.

Got my first low rating for this..  (sigh)  Sure would be nice if I could respond to rating comments..
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: Beta Testing Has Begun!
« Reply #81 on: January 03, 2012, 08:39:25 PM »
Hey Paul, I'm working on getting you that logcat right now, but I had a quick question about the current build. Did you add any performance tweaks to the the current build? I am getting way better performance in Super Mario 64, I'm thinking maybe the frame skip is working better because I'm getting the same frame rate but Mario seems to to be moving much better in 1.3. I'm using the same settings as well. Just wondering.

Thanks Paul!
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 Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Beta Testing Has Begun!
« Reply #82 on: January 03, 2012, 08:45:42 PM »
I don't notice any performance difference on my phone, but I suppose it could be due to the TLB setting which I changed to fix the Zelda crash bug.  I haven't added any real optimizations to the code with this update (the next update will).
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: Beta Testing Has Begun!
« Reply #83 on: January 03, 2012, 08:55:02 PM »
I don't notice any performance difference on my phone, but I suppose it could be due to the TLB setting which I changed to fix the Zelda crash bug.  I haven't added any real optimizations to the code with this update (the next update will).

Thanks Paul for the response, I'll be looking forward to the next update.  :)
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 firstpoke

  • byte
  • *
  • Posts: 27
    • View Profile
Re: Beta Testing Has Begun!
« Reply #84 on: January 03, 2012, 10:43:25 PM »
Got my first low rating for this..  (sigh)  Sure would be nice if I could respond to rating comments..

Yes, thats normal... I got many stupid 1-star ratings for my apps, without a reply from the user. They can get help from me... but they doesnt and rate it with 1 star  8)

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Beta Testing Has Begun!
« Reply #85 on: January 05, 2012, 04:58:03 PM »
I'm going to start with the "800 lb. gorilla in the room" as they say.. removing the SDL library.  Mupen64Plus only requires a very small piece of SDL, so it is a waste of resources to include the entire thing with this project.  Instead, I will create a tiny faux SDL library with only the functions that are used by Mupen64Plus (keyboard, audio, and joystick).  These functions will directly interface with Android/ Java through JNI.  The main thing this will do is chop the memory footprint way down (which should have a positive effect on games like Banjo Tooie).  Secondarily, it will make the code easier to navigate and profile for future optimizations.  And finally, by having a faux library in place, I will not have to touch the original Mupen64Plus code (making patches back to the original project much easier).  I'll keep everyone posted on the progress.

Since this is likely to take some time to complete, and I'll want to test it thoroughly on a number of devices before I call it an "official" update, I've decided to do it as a separate branch for now, which will allow me to continue adding other smaller bug-fixes and whatnot to the main branch until it is ready to be incorporated.  Sounds like a smart idea, anyway (we'll see how it turns out, haha)
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 firstpoke

  • byte
  • *
  • Posts: 27
    • View Profile
Re: Beta Testing Has Begun!
« Reply #86 on: January 06, 2012, 12:32:54 AM »
Sounds good :)

I did the same with Frodo C64 USB and Mame4Droid USB

Offline firstpoke

  • byte
  • *
  • Posts: 27
    • View Profile
Re: Beta Testing Has Begun!
« Reply #87 on: January 06, 2012, 12:13:25 PM »
About the GUI... is this the finale state?

Maybe I can make a seperate GUI Activity for Mupen64Plus like the horizontally scrollbar in my apps.
« Last Edit: January 06, 2012, 12:15:44 PM by firstpoke »

Offline FuzzieBoy

  • bit
  • Posts: 6
    • View Profile
Re: Beta Testing Has Begun!
« Reply #88 on: January 06, 2012, 03:43:19 PM »
Loving this emu so far, but one slight problem, I'm getting huge lag spikes on Mario Kart 64 on my Xperia play, making the game unplayable :/ I have yet to try a different rom (I get all my roms from one site that I've used for ages with no problems, unfortunately, they only have 1 rom per game, so if it is a bad dump, I have to search elsewhere).
If this is something that needs fixing (as in, rom is fine) I would love it to be fixed, being able to play Mario Kart 64 anywhere would be AMAZING!

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Beta Testing Has Begun!
« Reply #89 on: January 06, 2012, 04:51:42 PM »
About the GUI... is this the finale state?

Maybe I can make a seperate GUI Activity for Mupen64Plus like the horizontally scrollbar in my apps.

If you'd like to make a separate front-end, have a go at it.  I'll be happy to hook it up to the emulator, or you can make your own a separate branch or front-end to sell separately if you prefer, I certainly am not trying to corner the Android Market with the only working N64 emulator (N64 Arcade doesn't count, since it is a poorly-done ripoff of an early version of N64oid and doesn't even work on most phones, haha).  My only concern is if we try to get too graphics-intensive it might end up being incompatible or cause too much memory overhead and break things on some phones (we can definitely put it through trials first though to make sure it will do fine).  It might be good to just keep it simple graphics-wise, and instead focus on user-friendly and intuitive.  Anyone else have suggestions?
« Last Edit: January 06, 2012, 05:16:02 PM 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