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

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: Latest Build!
« Reply #30 on: December 02, 2012, 11:40:28 PM »
Whatever works for you.  If you want to make the backend for it, it will only take me ten minutes to do the front.
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline SilentHunter382

  • byte
  • *
  • Posts: 11
    • View Profile
Re: Latest Build!
« Reply #31 on: December 03, 2012, 04:52:48 AM »
I am just gonna say my experience with this small release. I know some of these problems may have be repeated but its better to see that.

-Device: Xperia Play

Problems
- I can't find the option to toggle to have xperia play controls like in the last build
- When loading the game for the first time loading the emulator it crashes but runs fine after the second game. (It does this for every game I tried)
- Emulator crashes if you open and close the xperia play controls.

These are a few but I my encounter more.
Current Phone: Sony Ericsson: Xperia Play

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3496
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Latest Build!
« Reply #32 on: December 03, 2012, 05:18:44 AM »
Awesome, I'll add them to the list.

For the Xperia Play controls, if you are using an Xperia Play (I assume so), and you can't find them under Settings->Touch, could you look up what says in Settings->Advanced->Device Info in the "Hardware" section near the bottom?  There is new code that should make these settings only available to Play users, but it makes an assumption about what's in the device info, that we might need to test.  Let me know.

@littleguy, I remember having problems with the Xperia Play when the controlls are slid in or out while in-game.  Problem in that case was that this was considered an "orientation change", which resulted in the rendering context being lost.  The fix was to indicate in the manifest that we are handling the slide keyboard orientation (or something along those lines).  I'd have to look at the manifest closer to see if that is related to what's happening in this case.
« Last Edit: December 03, 2012, 05:23:17 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 SilentHunter382

  • byte
  • *
  • Posts: 11
    • View Profile
Re: Latest Build!
« Reply #33 on: December 03, 2012, 05:33:46 AM »
For the Xperia Play controls, if you are using an Xperia Play (I assume so), and you can't find them under Settings->Touch, could you look up what says in Settings->Advanced->Device Info in the "Hardware" section near the bottom?  There is new code that should make these settings only available to Play users, but it makes an assumption about what's in the device info, that we might need to test.  Let me know.

Yes I am using the Xperia Play, this is the device info.

Processor: ARMv7 Processor rev 1 (v7|)
BogoMIPS: 163.57
Features: swp half thumb fastmult vfp edsp neon vfpv3
CPU implementer: 0x51
CPU architecture: 7
CPU variant: 0x1
CPU part: 0x00f
CPU reversion: 1

Hardware: zeus
Revision: 000b
Serial: 0000000000000000
Current Phone: Sony Ericsson: Xperia Play

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3496
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Latest Build!
« Reply #34 on: December 03, 2012, 05:43:17 AM »
Hardware: zeus

Hmm.. this is what the code should be checking on to see if you have a Play (so far seems to be unique).  I'm at a loss why the settings aren't showing up for you in the touch menu :(
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 #35 on: December 03, 2012, 05:59:07 AM »
Hardware: zeus

Hmm.. this is what the code should be checking on to see if you have a Play (so far seems to be unique).  I'm at a loss why the settings aren't showing up for you in the touch menu :(

That's ok. I can edit the controls for me to customize them myself in the input menu but editing the anolog and the C controls to the 2 anolog touch pads are the hardest part.

EDIT: Another bug. It won't let me display the onscreen controls if I decide to use them ingame. This must have something to do with the emulator knowing that you have an xperia play and refuses to display them. Though this may not be a bug and I could be doing something wrong.
« Last Edit: December 03, 2012, 06:02:20 AM by SilentHunter382 »
Current Phone: Sony Ericsson: Xperia Play

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: Latest Build!
« Reply #36 on: December 03, 2012, 06:19:57 AM »
I can see why this is confusing now.  The touchpad itself is mapped in the Touch settings.  The buttons are mapped in the Input settings.  In the Input settings, don't bother trying to map the analog stick or c-pad; they're already mapped for you when you enable the touchpad.

The input mapping settings clearly need a major update, and that's on the top of my plate right now.

Paul - I'll look into the manifest and get a fix for that since I have an XPlay and can test directly.  I noticed the crash with the slider opern/close, but I assumed that was related to the Activity Stack Double Pop bug (ASDP, that's what I'm calling it) so I didn't look into it too much.
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline quho

  • bit
  • Posts: 4
    • View Profile
Re: Latest Build!
« Reply #37 on: December 03, 2012, 07:00:42 AM »
This version is the fastest so far.  Very good!  :)

There's just one very annoying bug which wasnt on the list in op. When playing ocarina of time (havent tested other games yet, but i will soon) after ~15 minutes, the touch controls get bugged badly. For example, can't aim with boomerang, can't play ocarina (wont register c/A button presses when playing it), and sometimes buttons get jammed (shield being up even if im not pressing r).

Also is it possible to do importable gles2n64 graphics plugin which would have tribuffer opt disabled? thanks.

Offline Vincentmrl

  • Cyan Team
  • long
  • *
  • Posts: 121
    • View Profile
Re: Latest Build!
« Reply #38 on: December 03, 2012, 09:31:06 AM »
Hey Paul, nice work  on the new version, but there's a problem, the key mapping interface is confusing and I can't map the back button, that's important for me because I use it as B button, also Mario is laggy but it goes at 20-25fps, better than nothing. I'm offering to do the italian translation when this is done. I suggest putting a lower resolution graphical plugin or something to lower video resoultion, so that older phones can play better with worse graphics, it's an option in a mac n64 emu called sixtyforce, it's using gles2n64 0.5.2 (wonder why the emu is slow :3) and the option's called High resolution rendering, I can enable or disable it, disabled shows the games at lower quality but they go better.
I just tried Mario 64 on the emu again and it froze to sound select after mario's head.
Device: Lg Optimus One
CPU: 600 Mhz ARMv6 (Overclocked to 748Mhz ondemand governor)
GPU: Qualcomm Adreno 200
RAM: 512 MB
Resolution: 320 x 480
Rom: Unofficial Cyanogenmod 9

Offline Tom.K

  • Green Team
  • long
  • *
  • Posts: 130
    • View Profile
Re: Latest Build!
« Reply #39 on: December 03, 2012, 02:31:36 PM »
Just to note:
Quote
- Emulator crashes if you open and close the xperia play gamepad controls.
This happens even on my hardware keyboard if I try to open or close it.

Another bug:
If I disable audio by disabling plugin in settings, after loading game it will crash.
If I choose no-sound-hle, game plays with very strange sound stuttering (it loops same pattern for whole time) and it's very slow.

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: Latest Build!
« Reply #40 on: December 03, 2012, 02:34:12 PM »
Just to note:
Quote
- Emulator crashes if you open and close the xperia play gamepad controls.
This happens even on my hardware keyboard if I try to open or close it.
Great, that's helpful.  I think we just fixed this one today, and I think the solution applies to all types of slider phones.
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline Godshinnok

  • bit
  • Posts: 7
    • View Profile
Re: Latest Build!
« Reply #41 on: December 03, 2012, 04:48:13 PM »
whenever i start a game it instantly crashes the app. i tried to change around the settings to fix this, what can i do?

im sorry if this is a known bug

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3496
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Latest Build!
« Reply #42 on: December 03, 2012, 05:38:16 PM »
Any particular game, or does Mario 64 crash too?  What is your phone model?  You should also verify your ROMs are OK by testing on an emulator for your PC if you have one.
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 Godshinnok

  • bit
  • Posts: 7
    • View Profile
Re: Latest Build!
« Reply #43 on: December 03, 2012, 06:24:51 PM »
Any particular game, or does Mario 64 crash too?  What is your phone model?  You should also verify your ROMs are OK by testing on an emulator for your PC if you have one.

 a Samsung Galaxy Q (or gravity smart in america). the roms i have like super mario 64 and ocarina of time  work perfectly fine with PJ64, Mupen64, and 1964 on my PC but when i try to play them on the app it freezes and force closes the app

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3496
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Latest Build!
« Reply #44 on: December 03, 2012, 06:27:39 PM »
Ok, thanks I'll post a debug build for you to run, so we can figure out where it's crashing.  Probably won't have time until tomorrow though (trying to finish a feature tonight before bed)
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