Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Gillou68310

Pages: [1]
1
Support / Re: Touchscreen show/hide option?
« on: October 27, 2015, 06:02:04 AM »
Actually the profile already exist. You just have to select the (Disabled) profile.

2
General Discussion / Re: 3.0 Alpha Testing
« on: October 15, 2015, 01:21:21 AM »
@littleguy I think realtime gameshark cheat code is now possible, see here:
https://github.com/mupen64plus/mupen64plus-core/commit/44fb3c3670f59dfa0a51c6c5db1d585eb4bba5ea

3
General Discussion / Re: Backtrace on segfault in NDK code
« on: July 16, 2015, 01:38:35 AM »
@xperia64 which device are you testing on?

4
General Discussion / Re: Backtrace on segfault in NDK code
« on: July 15, 2015, 02:20:12 AM »
Using ndk-stack is the only way to get something readable from a segfault but depending on what caused the crash it may be completely unusable. ( ie: dynarec crashes )
Could you give more information on your crashes? Which game, which plugin, where it crashed, is it a random crash...?
Maybe I can help you to find the source ;)

5
General Discussion / Re: GLideN64 Android port
« on: July 06, 2015, 07:31:38 AM »
@retroben the polygon offset branch has been pushed ;)

6
General Discussion / Re: GLideN64 Android port
« on: July 06, 2015, 03:02:07 AM »
@Metalmusic the soldures guns issue is also present on PC so I recommend opening on issue here: https://github.com/gonetz/GLideN64/issues

Quote
Would a Mupen64Plus AE savestate work on PC?
@retroben yes of course!

Quote
Another thing. On my nvidia shield portable. HW lighting does not seem to be working correctly
@fzurita this is probably a driver issue with shaders because everything's fine on my device.

7
General Discussion / Re: 3.0 Alpha Testing
« on: July 06, 2015, 12:33:03 AM »
You need to fork the repo first, then push your change to the fork (master or a new branch) and finally open the pull request from there ;)

8
General Discussion / Re: GLideN64 Android port
« on: July 05, 2015, 03:25:30 PM »
Metalmusic sorry I misunderstood your issue. I also have the soldures guns. I'll take a look at it this week!

9
General Discussion / Re: GLideN64 Android port
« on: July 05, 2015, 07:18:58 AM »
Metalmusic enable frambuffer emulation. This fixed the issue for me.

10
General Discussion / Re: GLideN64 Android port
« on: July 05, 2015, 07:16:57 AM »
Quote
By second issue, do you mean third screenshot?

Yes I do.

11
General Discussion / Re: GLideN64 Android port
« on: July 05, 2015, 03:53:09 AM »
Which gles version are you using on your shield?

Zelda subscreen FB issue will be fixed as soon as this pull request will be merged:
https://github.com/mupen64plus/mupen64plus-core/pull/125

I think the second issue is caused by copyfromrdram option, try disabling it.

Also thanks for opening an issue for the x86 problem ;)

12
General Discussion / Re: GLideN64 Android port
« on: July 03, 2015, 03:46:03 PM »
Sorry retroben I doesn't have much time these days I spend some hours this week working with gonetz in order to improve the gles2 variant of gliden64. Concerning glover games please test it on PC and open an issue upstream if it fails. It will be much easier for me to track core regression  ;)

I'll create a branch for the polygon offset so you can make some experiments.

Also I'll check dk64 on PC to see if it's a gles specific issue. Could you send me a savestate?

I'm out for the weekend so I won't be able to work on the emu until monday.

13
General Discussion / Re: GLideN64 Android port
« on: July 03, 2015, 09:17:27 AM »
I just updated master with latest gliden64 fixes.

14
General Discussion / Re: GLideN64 Android port
« on: June 23, 2015, 01:40:09 PM »
I just updated master with latest gliden64 fixes.

This issue has been fixed:
https://github.com/gonetz/GLideN64/issues/586

Please test an report :)

15
General Discussion / Re: GLideN64 Android port
« on: June 22, 2015, 02:19:35 PM »
I just double checked the polygon offset issue and I don't have issues because the hardcoded value match the required value for my devices so this explains why it works for me, no need to make a screenshot ::)

A screenshot app is just fine for me BTW ;)

Pages: [1]