Author Topic: 3.0 Alpha Testing  (Read 325835 times)

Offline rafar

  • int
  • **
  • Posts: 67
    • View Profile
Re: 3.0 Alpha Testing
« Reply #420 on: January 16, 2015, 09:05:55 AM »
I run the scan again after of change the Languaje to english (I had spanish) and it found all the roms... and then I re scan after of change to Spanish if that was the problem and it found all the roms again... I dont know how it happened but  at the first time I installed the new build I did like 3 or 4 scans and always found 7 or 8 (always the same roms).
Here if the logcat if you still want to see it: 

Code: [Select]
--------- beginning of /dev/log/system
[ 01-16 15:58:51.392 32345:32345 I/ViewRootImpl ]
ViewRoot's Touch Event : Touch Down

[ 01-16 15:58:51.472 32345:32345 I/ViewRootImpl ]
ViewRoot's Touch Event : Touch UP

[ 01-16 15:58:54.082 32345:32345 I/ViewRootImpl ]
ViewRoot's Touch Event : Touch Down

[ 01-16 15:58:54.142 32345:32345 I/ViewRootImpl ]
ViewRoot's Touch Event : Touch UP

[ 01-16 15:58:55.472 32345:32345 I/ViewRootImpl ]
ViewRoot's Touch Event : Touch Down

[ 01-16 15:58:55.512 32345:32345 I/ViewRootImpl ]
ViewRoot's Touch Event : Touch UP

[ 01-16 15:58:57.752 32345:32345 I/ViewRootImpl ]
ViewRoot's Touch Event : Touch Down

[ 01-16 15:58:57.862 32345:32345 I/ViewRootImpl ]
ViewRoot's Touch Event : Touch UP

[ 01-16 15:58:59.352 32345:32345 I/ViewRootImpl ]
ViewRoot's Touch Event : Touch Down

[ 01-16 15:58:59.802 32345:32345 I/ViewRootImpl ]
ViewRoot's Touch Event : Touch UP

[ 01-16 15:59:02.872 32345:32345 I/ViewRootImpl ]
ViewRoot's Touch Event : Touch Down

[ 01-16 15:59:07.322 32345:32345 I/ViewRootImpl ]
ViewRoot's Touch Event : Touch UP

[ 01-16 15:59:09.872 32345:32345 I/ViewRootImpl ]
ViewRoot's Touch Event : Touch Down

[ 01-16 15:59:09.942 32345:32345 I/ViewRootImpl ]
ViewRoot's Touch Event : Touch UP

--------- beginning of /dev/log/main
[ 01-16 15:59:17.512 32345:32345 I/Xposed   ]
org.mupen64plusae.v3.alpha OFF

[ 01-16 15:59:17.642 32345:32345 I/ActivityManager ]
Timeline: Activity_idle id: android.os.BinderProxy@431f7588 time:79777663

[ 01-16 15:59:18.892 32345:32345 I/ViewRootImpl ]
ViewRoot's Touch Event : Touch Down

[ 01-16 15:59:18.972 32345:32345 I/ViewRootImpl ]
ViewRoot's Touch Event : Touch UP

[ 01-16 15:59:20.362 32345:32345 I/ViewRootImpl ]
ViewRoot's Touch Event : Touch Down

[ 01-16 15:59:20.422 32345:32345 I/ViewRootImpl ]
ViewRoot's Touch Event : Touch UP

[ 01-16 15:59:22.912 32345:32345 I/ViewRootImpl ]
ViewRoot's Touch Event : Touch Down

[ 01-16 15:59:22.992 32345:32345 I/ViewRootImpl ]
ViewRoot's Touch Event : Touch UP

« Last Edit: January 16, 2015, 09:10:11 AM by littleguy »

Offline Sowden

  • byte
  • *
  • Posts: 14
    • View Profile
Re: 3.0 Alpha Testing
« Reply #421 on: January 16, 2015, 02:39:33 PM »
Hey guys.  I just tried playing Mario Golf on the latest build (the one thats auto built) and I have noticed some huge problems from the last google play version.  I have uploaded photos from my list in order and they were all played on the "Fast"est.  They go as followed:

Glide64: Displays everything for the most part, but it is way laggy.  Its unplayable because I can't make an accurate club swing
http://troyh.us/FTPshare/pieproductions/Screenshot_2015-01-17-04-12-13.png
Gin64: Landscape graphics are all messed up, can't see where I'm hitting the ball at.  Will say though that this is the smoothest plugin out of them all, somewhat playable
http://troyh.us/FTPshare/pieproductions/Screenshot_2015-01-17-04-14-20.png
Rice: Landscapes are a little messed up, but I can make it out for the most part.  The screen is black until I slightly move my joy stick.  Not so much lag, most playable out of all of them
http://troyh.us/FTPshare/pieproductions/Screenshot_2015-01-17-04-17-59.png

I don't know if this has been mentioned, but this sticks out at me.  Thanks, later.

Offline rafar

  • int
  • **
  • Posts: 67
    • View Profile
Re: 3.0 Alpha Testing
« Reply #422 on: January 16, 2015, 03:05:37 PM »
Perfect dark and Pokemon Stadium 2 with last build are  very laggy now (glide64 fast).  But as I said few days ago, several games improved greatly their performance (conker, banjo tooie, donkey kong 64, pokemon stadium for example)
« Last Edit: January 16, 2015, 04:00:31 PM by rafar »

Offline d3n3

  • byte
  • *
  • Posts: 15
    • View Profile
Re: 3.0 Alpha Testing
« Reply #423 on: January 16, 2015, 04:23:44 PM »
Hi All,

I noticed in the 3.0 version there is not an option to load a custom controller profile?  I created the InputProfiles folder and nothing is picked up there...

I saw there was a new Profile folder and created a .cfg but it's not being picked up by the program.  I'm using an amazon fire controller which requires the config.

Thanks

Edit: Just renamed my custom file to controller.cfg and it works now :D
« Last Edit: January 16, 2015, 04:26:16 PM by d3n3 »

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: 3.0 Alpha Testing
« Reply #424 on: January 16, 2015, 04:24:42 PM »
@rafar Can you narrow down between which alpha versions or auto-builds the lagginess started and/or performance improved?  I haven't touched the core in awhile.
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: 3.0 Alpha Testing
« Reply #425 on: January 16, 2015, 04:32:36 PM »
Hi All,

I noticed in the 3.0 version there is not an option to load a custom controller profile?  I created the InputProfiles folder and nothing is picked up there...

I saw there was a new Profile folder and created a .cfg but it's not being picked up by the program.  I'm using an amazon fire controller which requires the config.

Thanks

The new version uses a somewhat different system for controller profiles.  Rather than using a unique file for each controller profile, all the controller profiles are placed in a single file, located at mupen64plusae-v3-alpha/Profiles/controller.cfg.  Normally you wouldn't need to manually edit it, but since that controller has unique issues, you can workaround them by editing the file:

Code: [Select]
[Amazon Fire Controller]
map=0:-31,1:-32,2:-33,3:-34,4:108,5:-47,6:99,7:96,8:-23,9:-24,10:-29,11:-30,12:103,13:102,16:-1,17:-2,18:-3,19:-4
sensitivity=100
deadzone=0

If you want to edit the mappings via the UI (e.g. for the Start button) go to Settings -> Controller profiles... in the main screen of the V3 app.  Then tap the name of the controller you wish to modify/copy/delete/etc.
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline d3n3

  • byte
  • *
  • Posts: 15
    • View Profile
Re: 3.0 Alpha Testing
« Reply #426 on: January 16, 2015, 04:53:52 PM »
Quote

The new version uses a somewhat different system for controller profiles.  Rather than using a unique file for each controller profile, all the controller profiles are placed in a single file, located at mupen64plusae-v3-alpha/Profiles/controller.cfg.  Normally you wouldn't need to manually edit it, but since that controller has unique issues, you can workaround them by editing the file:

Code: [Select]
[Amazon Fire Controller]
map=0:-31,1:-32,2:-33,3:-34,4:108,5:-47,6:99,7:96,8:-23,9:-24,10:-29,11:-30,12:103,13:102,16:-1,17:-2,18:-3,19:-4
sensitivity=100
deadzone=0

If you want to edit the mappings via the UI (e.g. for the Start button) go to Settings -> Controller profiles... in the main screen of the V3 app.  Then tap the name of the controller you wish to modify/copy/delete/etc.

Works perfectly. Thank you.

Offline rafar

  • int
  • **
  • Posts: 67
    • View Profile
Re: 3.0 Alpha Testing
« Reply #427 on: January 16, 2015, 05:21:50 PM »
@rafar Can you narrow down between which alpha versions or auto-builds the lagginess started and/or performance improved?  I haven't touched the core in awhile.

Sure, tomorrow I will edit this post with more details   ;D

Edit: it is probably I said be my fault, because I am having problem with several builds, I will make a clean install for be sure.
« Last Edit: January 17, 2015, 11:11:48 AM by rafar »

Offline retroben

  • float
  • ****
  • Posts: 432
    • View Profile
Re: 3.0 Alpha Testing
« Reply #428 on: January 17, 2015, 12:47:17 PM »
Donkey Kong 64 has a major warping issue on x86 Intel devices.
I can instantly warp out of bounds by touching a certain part of the left wall near Cranky's Lab,and also in DK's Cabin at the boombox table when jumping at it.
Please don't make me go through the 20+ different builds worth of testing because of this.

Needed mention:This does not happen in Gillou's version,which must mean something crucial is missing from the Alpha builds.

Offline rafar

  • int
  • **
  • Posts: 67
    • View Profile
Re: 3.0 Alpha Testing
« Reply #429 on: January 17, 2015, 01:15:52 PM »
@retroben    the issue looks like the post #328?

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: 3.0 Alpha Testing
« Reply #430 on: January 17, 2015, 03:44:47 PM »
I have said it many times and I will say it again.  Gilles is working on pushing his dynarec fixes upstream.  He's already got a bunch of them upstream, and they are in the latest alphas.  He still has a few more to go.  From what I understand, he is not fully comfortable with the remaining fixes and wants to find a "better" solution before they get pushed upstream.  In other words, he's concerned that the remaining fixes are just a "band-aid" and might create as many new bugs as they fix.  So he is wisely cautious.

Once his fixes are merged upstream, I will pull them immediately into the alphas.  I have no control over when they will be merged upstream, but you can be sure I will make them available here as soon as humanly possible.

@Gilles - Feel free to make a branch off of master if you want folks to test your remaining fixes.  They will be built automatically every hour and posted here.  You can discuss them here or on a separate thread -- whatever you like.  I would recommend changing the Android manifest so that users can install it side-by-side with the alphas.  (The easiest way to do it is in the context menu in Eclipse, when you right-click on the project.)
« Last Edit: January 17, 2015, 03:48:49 PM by littleguy »
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: 3.0 Alpha Testing
« Reply #431 on: January 17, 2015, 03:58:31 PM »
Please don't make me go through the 20+ different builds worth of testing because of this.

You can do whatever you wish.  The more effort you feel like putting in, the less the devs have to do.

Speaking of which, I kind of feel all alone again on this project.  If any devs want to join in and tackle some major issues, that would be fantastic.
 - Fix the crash on exit that xperia64 has described, almost certainly related to ae-bridge
 - New gallery screen
 - Multiple, timestamped auto-saves (in case the last auto-save is corrupt)
 - Selection screen for unmatched/unknown ROMs (e.g. prompt for closest match or define new meta-data)
 - Hi-res texture UI for friendliness
 - General front-end polishing
 - Polygon offset wizard or something (need to know GL)

I know that the java code has become a behemoth, but I'll be happy to explain anything and everything as best I can if any dev has any questions.  I will write formal documentation if necessary.

Right now I'm polishing the ROM search process to incorporate @retroben's good suggestions.  I'm also working on a few things I left dangling upstream.  If no one tackles the crash on exit, that will be my next priority.
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline xperia64

  • Moderator
  • double
  • *****
  • Posts: 591
    • View Profile
    • My Apps
Re: 3.0 Alpha Testing
« Reply #432 on: January 17, 2015, 04:03:18 PM »
I do want to redo CheatActivity with an ActionBar. Are we using appcompat_v7 yet? If so, I'll try to work on it soon.

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: 3.0 Alpha Testing
« Reply #433 on: January 17, 2015, 07:21:10 PM »
I'll add it if it's not there already.
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: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: 3.0 Alpha Testing
« Reply #434 on: January 17, 2015, 08:17:15 PM »
Speaking of which, I kind of feel all alone again on this project.

Sorry about that, lately I seem to only have an hour or two here and there to spend on programming.  I have a little time tomorrow, though.  I'll try and get something useful committed.
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