Author Topic: Testers needed! (input plug-in, touchscreen controls)  (Read 12157 times)

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3495
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Testers needed! (input plug-in, touchscreen controls)
« Reply #15 on: March 06, 2013, 03:43:12 PM »
Nothing too out of the ordinary in the logcat.  Do you remember whether you had the fps indicator enabled or disabled for that test?
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 Tom.K

  • Green Team
  • long
  • *
  • Posts: 130
    • View Profile
Re: Testers needed! (input plug-in, touchscreen controls)
« Reply #16 on: March 07, 2013, 08:37:27 AM »
FPS indicator was disabled by default. Even if enabled it didn't work.

After running Numeral Crash Test #1, emulation works, but gamepad is completely gone (not drawn on screen, tapping anywhere where are controls are supposed to be are not doing anything.)

Hardware keyboard mapping still works, though.
« Last Edit: March 07, 2013, 08:39:39 AM by Tom.K »

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3495
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Testers needed! (input plug-in, touchscreen controls)
« Reply #17 on: March 07, 2013, 08:42:20 AM »
Interesting.  I'll have to look at it some more to figure out what is going on, from a synchronization perspective.  I might need to post a verbose build to figure out where the resize calculations are breaking down.  I have a feeling that it somehow calculated a scale of 0 (that would make everything invisible).
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: Testers needed! (input plug-in, touchscreen controls)
« Reply #18 on: March 08, 2013, 07:30:48 PM »
Ok, next test (this one won't fix your problem, Tom.K - I haven't had a chance to look at it yet)

The button scaling is now based on the longest side (rather than scaling up from the shortest side in portrait).  This will make the controls a consistent size in both orientations.  However, I noticed the controls in portrait were actually a tad larger on my phone, so I'm worried about overlap being a bigger problem this way (it will depend on the aspect ratio though).  I moved the L and Z buttons up 2% to make room for the D-Pad on the "Both" layout.  Let me know how it looks in portrait mode on various devices:

Touch Controls Test #4
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 WinSuk

  • byte
  • *
  • Posts: 11
    • View Profile
Re: Testers needed! (input plug-in, touchscreen controls)
« Reply #19 on: March 08, 2013, 08:32:42 PM »
Ok, next test (this one won't fix your problem, Tom.K - I haven't had a chance to look at it yet)

The button scaling is now based on the longest side (rather than scaling up from the shortest side in portrait).  This will make the controls a consistent size in both orientations.  However, I noticed the controls in portrait were actually a tad larger on my phone, so I'm worried about overlap being a bigger problem this way (it will depend on the aspect ratio though).  I moved the L and Z buttons up 2% to make room for the D-Pad on the "Both" layout.  Let me know how it looks in portrait mode on various devices:

Touch Controls Test #4

Looking good here :) (Aria)
http://dl.dropbox.com/u/1077120/mupentesting/Screenshot_2013-03-08-18-16-14.png

(I'm assuming screenshots of my other 2 devices aren't needed as their screens are pretty common and it looks fine. Let me know if you still want them)
« Last Edit: March 08, 2013, 08:34:40 PM by WinSuk »

Offline xperia64

  • Moderator
  • double
  • *****
  • Posts: 591
    • View Profile
    • My Apps
Re: Testers needed! (input plug-in, touchscreen controls)
« Reply #20 on: March 08, 2013, 08:45:41 PM »
Works perfect on my s2

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3495
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Testers needed! (input plug-in, touchscreen controls)
« Reply #21 on: March 08, 2013, 09:02:13 PM »
Hey, I just updated the test (same link above) with a change in the SDL header that could potentially have a fairly wide-reaching impact on the app (or maybe not - need to test).  If everyone has a chance, please try out a few games to see if compatibility or speed is affected in any way by this change.
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 WinSuk

  • byte
  • *
  • Posts: 11
    • View Profile
Re: Testers needed! (input plug-in, touchscreen controls)
« Reply #22 on: March 09, 2013, 07:40:30 PM »
Hey, I just updated the test (same link above) with a change in the SDL header that could potentially have a fairly wide-reaching impact on the app (or maybe not - need to test).  If everyone has a chance, please try out a few games to see if compatibility or speed is affected in any way by this change.

I don't notice anything different/better... I don't have that many games to test with though.

And I've found a bug with joystick animation enabled:
It starts out centered, but once it's moved it resets to center wrong (and in different places on each device)
https://dl.dropbox.com/u/1077120/mupentesting/Screenshot_2013-03-09-17-23-41.png
https://dl.dropbox.com/u/1077120/mupentesting/Screenshot_2013-03-09-17-24-46.png
https://dl.dropbox.com/u/1077120/mupentesting/Screenshot_2013-03-09-17-36-26.png

Offline xperia64

  • Moderator
  • double
  • *****
  • Posts: 591
    • View Profile
    • My Apps
Re: Testers needed! (input plug-in, touchscreen controls)
« Reply #23 on: March 09, 2013, 08:02:49 PM »
Changing touchscreen control size seems to be broken (at least from normal to small) And the buttons are a little bit close to my capacitive home/back/menu/search buttons at the bottom

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3495
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Testers needed! (input plug-in, touchscreen controls)
« Reply #24 on: March 09, 2013, 08:47:14 PM »
Touchscreen controls size option will be removed (size will be based on the device rather than selected).
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: Testers needed! (input plug-in, touchscreen controls)
« Reply #25 on: March 17, 2013, 02:36:07 PM »
FPS indicator was disabled by default. Even if enabled it didn't work.

After running Numeral Crash Test #1, emulation works, but gamepad is completely gone (not drawn on screen, tapping anywhere where are controls are supposed to be are not doing anything.)

Hardware keyboard mapping still works, though.

Sorry for the delay.  I finally got around to writing the verbose test.  Please uninstall the previous test before installing this one (to make sure the current resources get loaded).  Just start a game so it loads the touch map, then grab the logcat and either post it here or email it to me.

Verbose Test
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 Tom.K

  • Green Team
  • long
  • *
  • Posts: 130
    • View Profile
Re: Testers needed! (input plug-in, touchscreen controls)
« Reply #26 on: March 17, 2013, 04:42:44 PM »
Looks like I was actually wrong a bit. Gamepad touchscreen is drawn, but only on Normal and Tablet (and ridiciously shrunk): http://i.imgur.com/NvCzZHP.png
This is a screenshot of gamepad when it's on Normal in that version. Usually, buttons on Normal on my phone would fill all over my screen.

Small and Tiny layouts can't be seen on screen still. I guess that you only need to re-align them to fit as usual to QVGA.

If it helps, here is the logcat, but not sure is it useful at all, can't clean it up at the moment: http://pastebin.com/v9uFLs7a

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3495
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Testers needed! (input plug-in, touchscreen controls)
« Reply #27 on: March 17, 2013, 06:05:59 PM »
That is the intended behavior.  There won't be "tiny" and "small" layouts any more - just one size that rescales to fit the screen dimensions.  Obviously it makes it hard to play on tiny screens, but I've had as many people complain about the buttons filling up the entire screen (so can't please everyone - better to standardize and leave customization as an option).

If you need help writing a custom layout that fits your needs better, let me know.
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: Testers needed! (input plug-in, touchscreen controls)
« Reply #28 on: March 17, 2013, 06:11:20 PM »
I'm going to add a scaling factor preference (slide bar I think, like the speed selector), which will let folks scale up or down to a certain degree.  Maybe have the best of both worlds.
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: Testers needed! (input plug-in, touchscreen controls)
« Reply #29 on: March 17, 2013, 06:13:18 PM »
Yeah, I think that would be wise.  I'm afraid without something like that, people are going to be pissed for taking something away for no apparent reason.
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version