PaulsCode Forum

Mupen64Plus AE => Support => Topic started by: ThatRyanDude on November 04, 2013, 11:49:32 AM

Title: Gles2glide64 plugin orientation issue
Post by: ThatRyanDude on November 04, 2013, 11:49:32 AM
Hello Guys,

I'm attempting to play Majoras Mask, so far the best results are from using the gles2glide64 video plugin. However when I choose this it seems to stick into portrait orientation mode, regardless of what orientation I set it to. Does anyone know a solution to this?

Im using a Nexus 5 if that helps.

Many thanks  :)
Title: Re: Gles2glide64 plugin orientation issue
Post by: littleguy on November 04, 2013, 11:59:22 AM
Hmm, that's a new one.  Do the other video plugins show the same orientation bug, or is it just glide?

I wonder if this is a kitkat issue.  @Paul we should probably bump to SDK 19 now in the manifest.
Title: Re: Gles2glide64 plugin orientation issue
Post by: ThatRyanDude on November 04, 2013, 12:11:51 PM
It is just Glide, unfortunately with the other plugins majora's mask begins to glitch out. If I choose a landscape layout only the controller UI changes, the game remains in portrait.
Title: Re: Gles2glide64 plugin orientation issue
Post by: ThatRyanDude on November 04, 2013, 12:21:17 PM
Just tried out on the same thing on a Nexus 7 and it works fine. Probably a kit kat issue.
Title: Re: Gles2glide64 plugin orientation issue
Post by: littleguy on November 04, 2013, 06:21:23 PM
With any luck my 2012 Nexus 7 will be getting an OTA KitKat upgrade soon.  Should make it possible to track this down.
Title: Re: Gles2glide64 plugin orientation issue
Post by: littleguy on November 18, 2013, 10:50:58 AM
I just upgraded to KitKat.  Putting this high on my todo list.
Title: Re: Gles2glide64 plugin orientation issue
Post by: storm20200 on November 19, 2013, 01:48:44 PM
Hi there, I've had the issue since I got my Nexus 5 too, just wanted to confirm it isn't an isolated issue. Hope you can fix this, it'll be great fun being able to play Majora's Mask and Paper Mario better :-)
Title: Re: Gles2glide64 plugin orientation issue
Post by: littleguy on November 19, 2013, 01:53:53 PM
Would you mind testing this version?
https://dl.dropboxusercontent.com/u/3899306/Mupen/Mupen64Plus-AE-lcfixes-head.apk

This one also has Immersive Mode in the video settings if you want to give that a try ;)
Title: Re: Gles2glide64 plugin orientation issue
Post by: nighthawk on November 19, 2013, 02:26:42 PM
Hi,

I've actually had this problem too under the similar conditions. I'm currently using a Galaxy Nexus 4, running Android 4.4.

I tested your patched version above, but this doesn't seem to alleviate the issue, in fact it will do one of the 3 upon freshly restarting an emulation of Majora's Mask:

1. Phone restarts (happened once, haven't since repeated)
2. Emulator falls back to preceding menu screen
3. (Most common) Black screen but emulation is running (can hear associated sounds).

Let me know if there's something I can give you to be of more help (I don't remember if I can send you a core dump or something, haven't done too much development on android lately).
Title: Re: Gles2glide64 plugin orientation issue
Post by: littleguy on November 19, 2013, 02:27:44 PM
Try restarting (rather than resuming) the game.
Title: Re: Gles2glide64 plugin orientation issue
Post by: nighthawk on November 19, 2013, 02:33:03 PM
I actually did a restart, and the behavior I described in 2 and 3 were the result. I believe 1 was caused by a resume (which I suppose would make sense).
Title: Re: Gles2glide64 plugin orientation issue
Post by: littleguy on November 19, 2013, 02:33:41 PM
How about the other video plugins in the test build?
Title: Re: Gles2glide64 plugin orientation issue
Post by: littleguy on November 19, 2013, 02:36:51 PM
If you keep getting the "falling back to menu" behavior, please do this:

Go to Settings -> Advanced -> Enable crash reporting
Add your username so I can find the report easily
Next time the app crashes, go back to this menu and hit the Test button at the very bottom of the screen.  Then post back or shoot me a PM and I'll know to look in the crash reports.
Title: Re: Gles2glide64 plugin orientation issue
Post by: nighthawk on November 19, 2013, 02:41:22 PM
gles2rice plugin actually works about half the time. The other half, upon doing a emulation restart, it will fall back to the main menu.

gles2n64 is the most consistent, working every time except one outlying case:

Immediatly after switching from gles2rice to gles2n64, starting up the emulator (fresh restart) caused the render to display in kind of a tile mode. Restarting the emulation fixed this, but I don't know if this is related or a separate issue.

I'll send you those crash reports in a moment.
Title: Re: Gles2glide64 plugin orientation issue
Post by: nighthawk on November 19, 2013, 02:46:56 PM
I've sent 2 crash reports.

The first one occurred with gles2glide64, and the second with gles2n64. 
Title: Re: Gles2glide64 plugin orientation issue
Post by: storm20200 on November 19, 2013, 04:00:34 PM
I tried the test version too. The issue still remains the same, portrait mode is used in landscape and reverse landscape modes. Immersive mode works beautifully though, having it enabled or disabled doesn't change the orientation issue though.
Title: Re: Gles2glide64 plugin orientation issue
Post by: littleguy on November 19, 2013, 04:47:31 PM
Thanks a lot guys.

I only seem to have received one crash report from nighthawk and unfortunately didn't have the information I hoped it would.  This test was a bit of a long shot anyhow... the main thing I thought might help was changing some build configuration stuff to explicitly include KitKat SDK.

Immersive mode will be coming in one of the next releases, probably 2.5.0 in the next week or two.  Until then you can enjoy the test version posted here.
Title: Re: Gles2glide64 plugin orientation issue
Post by: littleguy on November 19, 2013, 04:51:38 PM
BTW, if you find any other app that had this problem and got it resolved recently, please let us know.  May hold the clue to the issue.  For now it looks like a graphics driver issue since I don't have this problem on my 2012 Nexus 7 running KitKat.
Title: Re: Gles2glide64 plugin orientation issue
Post by: storm20200 on November 19, 2013, 04:58:40 PM
How unfortunate, Qualcomm don't seem like the best at making graphics drivers. Is there anything else we could do to help figure this out?
Title: Re: Gles2glide64 plugin orientation issue
Post by: littleguy on November 19, 2013, 05:07:32 PM
Not sure yet because I still haven't had much time to look at this (and no way to test).  But once I do I'll post back here for help.  The best way to help right now would be to see if any other apps (a) had the problem and (b) resolved it.  Then let us know.
Title: Re: Gles2glide64 plugin orientation issue
Post by: puppy on December 14, 2013, 07:01:22 PM
Hello,

Registered to say I have the same problem on my Nexus 5 running android 4.4.2.

Just to give a slightly more accurate description of the problem, there is a difference between portrait and landscape. On landscape mode it stretches the screen to the proper size for landscape, but then the actual graphics are sideways and very stretched since the aspect ratio is reversed. Portrait mode works as it should.

Hopefully I explained that well enough, haha. If you don't understand let me know and I can take some screenshots.

Hopefully this helps in your debugging efforts.

Thanks for all your hard work.
Title: Re: Gles2glide64 plugin orientation issue
Post by: Naked_Snake on January 04, 2014, 12:09:27 PM
Hi,

Juste adding a little stone too the wall, I have the exact same issue on my Nexus 4 with Android 4.4.2. It's a shame, because playing majora mask whenever I want is a dream I had for a long time !

Thanks for your hard work, and for bringing littles dreams to reality. I hope this can get fixed some way.
Title: Re: Gles2glide64 plugin orientation issue
Post by: littleguy on January 04, 2014, 04:00:31 PM
Of course it does.  This issue will affect all users with Adreno 320 chipsets and KitKat because the Adreno drivers are broken.  If the right dev joins the team, or the rest of us get more free time, we may be able to find a workaround.  Until then, keep pestering Qualcomm to fix their drivers.
Title: Re: Gles2glide64 plugin orientation issue
Post by: Dragoth on January 06, 2014, 06:45:49 AM
Damn, it really looks like a driver problem.
According to the qualcomm support forums and the dolphin blog:


This problem is really frustrating. GLES2Glide64 is the only plugin that works best for me. Very accurate and fast.

I'm no Android specialist or coding specialist in perticular, but i took a look at some files and was trying to find where the function glBlitFramebuffer was beeing used and found this in SDL_opengl.h under jni/SDL2/include:

Code: [Select]
GLAPI void APIENTRY glBlitFramebuffer (GLint srcX0, GLint srcY0, GLint srcX1, GLint srcY1, GLint dstX0, GLint dstY0, GLint dstX1, GLint dstY1, GLbitfield mask, GLenum filter);
Now my relative "primitive" idea was to swap GLint srcX0 with GLint srcY0 to bend the image back to landscape (negate the 90░ error). This would just be a quick hack to identify the problem. If it works we would only need to identify devices with an adreno 320 and apply that hack to fix qualcomms damn bug in the driver.

Am i going into the right direction? If not, where could i look?
I'd be interested in fixing this... but would probably need alot of time.
Title: Re: Gles2glide64 plugin orientation issue
Post by: littleguy on January 06, 2014, 07:11:09 AM
Thanks for digging into that.  Are you a developer?  If so then by all means give it a shot.  You can just submit a pull request on github or post a patch on the forum.  I don't have an Adreno 320 device but could probably put up a few test builds later this week if no one else has jumped on it by then.  xperia64 might be a good person to try it since he's familiar with all the code and has a 2013 nexus 7.
Title: Re: Gles2glide64 plugin orientation issue
Post by: littleguy on January 06, 2014, 07:25:48 AM
Wait, no that won't solve the issue.  I should have read more carefully.  SDL_opengl.h isn't compiled into the app.  Plus it's just a declaration so changing the variable names wouldn't do anything anyhow.  But I'll take a look in the rest of the code, I think I heard that mentioned before about the blitting being buggy.
Title: Re: Gles2glide64 plugin orientation issue
Post by: Dragoth on January 06, 2014, 08:47:04 AM
Thanks for digging into that.  Are you a developer?  If so then by all means give it a shot.  You can just submit a pull request on github or post a patch on the forum.  I don't have an Adreno 320 device but could probably put up a few test builds later this week if no one else has jumped on it by then.  xperia64 might be a good person to try it since he's familiar with all the code and has a 2013 nexus 7.

No, i'm no Android developer. I'm currently developing/developed a compiler at work that translates robot-code. I also programmed a small Android app a couple of years ago in college... but it's been a while.

I have no idea about OpenGL and the sorts but am very interested and currently going through some OpenGL ES 2.0 tutorials.
I'll try to make a pull request later this week.

If you need additional testers, i'll gladly help since my Nexus 4 also has an Adreno 320 GPU.

Quote
Wait, no that won't solve the issue.  I should have read more carefully.  SDL_opengl.h isn't compiled into the app.  Plus it's just a declaration so changing the variable names wouldn't do anything anyhow.  But I'll take a look in the rest of the code, I think I heard that mentioned before about the blitting being buggy.

Damn it... i was hoping that changing the declaration/switching the variables would do the trick. It would have been way to easy... should have known :P

I'll keep reading through the code. If there is anything i can help with, give me a shout.
Title: Re: Gles2glide64 plugin orientation issue
Post by: Dragoth on January 10, 2014, 04:29:53 AM
Small update about the orientation issue on devices with an Adreno 320 using the gles2glide64 plugin (gles2n64 & gles2rice work fine):

This is how the current problem looks like:

Native resolution - no scaling - Landscape

(http://s1.directupload.net/images/140110/smuvkfgf.png) (http://www.directupload.net)

Native resolution - no scaling - Reverse Landscape

(http://s14.directupload.net/images/140110/f2dve4tx.png) (http://www.directupload.net)

Native resolution - no scaling - Portrait

http://s14.directupload.net/images/140110/mdcrbxjp.png (http://s14.directupload.net/images/140110/mdcrbxjp.png)

Native resolution - no scaling - Reverse Portrait

http://s14.directupload.net/images/140110/hznhgtal.png (http://s14.directupload.net/images/140110/hznhgtal.png)



The interesting part about this bug is that portrait mode renders correctly. As soon as you switch to landscape, the rendered image rotates 90░. A dolphin developer said that the cause for this was that if you glBlitFramebuffer to a hardware buffer the output of the buffer gets rotated by 90░ (which is a bug in the qualcomm drivers for the adreno 320).

Here you can see a similar/same problem with Dolphin for Android on an Adreno 320 device:

(http://media.bestofmicro.com/8/5/403349/gallery/Screenshot_2013-06-06-06-48-56_w_500.png)

If you compare the two pictures between mupen64plus-ae and dolphin, you can see that the image gets cut in mupen and in dolphin the image that is missing gets drawn again and causes an overlaped image. So i'm not sure if we are experiencing the same problem in mupen. I couldn't find any function in the mupen64plus-ae repository that uses glBlitframebuffer either. Maybe the output of the buffer always gets rotated by 90░ when copying to a backbuffer?

Since i'm a huge noob when it comes to developing for android and working with openGL i just tried to throw things at the code in hoping that i somehow magically find a solution for this bug that qualcomm so kindly put into their drivers...

My idea was to find specific code that renders the screen with x/y or width/height variables and tried to switch said variables to bend back the image to landscape.

Sadly, my noobish approach didn't bring any results. All i could accomplish was switching the variables width & height (stretch scale) in /persistent/UserPrefs and got the image to stretch in the right direction and not make it look so squashed anymore (while in landscape). But the rotation was still there:

Default stretch

(http://s14.directupload.net/images/140110/66yolo4y.png) (http://www.directupload.net)

Switch width & height while in stretch mode in /persistent/UserPrefs

(http://s1.directupload.net/images/140110/xzxuikhw.png) (http://www.directupload.net)


I'm back here now asking for some advice.

Could anyone point me into the right direction? Where and how could i look to find the problem? I lack the knowledge of how exactly mupen64plus-ae puts its pieces of code together.
Which part of the code has the job of rendering? We compile the plugins into an .so file. We also have SDL2 which seems to provide access to graphics hardware via OpenGL.. But it also gets compiled into an .so file. Which part of the code executes these .so files?

It would be awesome if somebody could help me out. I really want to get this working... or help the real developers in some way to get it working.

edit: sorry for the 403 error. I thought that dropbox could link pics... it can't :(
Title: Re: Gles2glide64 plugin orientation issue
Post by: littleguy on January 10, 2014, 07:16:34 AM
I can't seem to access the screenshot links (getting a 403 error).

Since we're not really fixing our own bug, but rather finding a workaround to someone else's, then in theory there may be more than one solution.  Or none at all.  The first place I'd look would be the gles2glide64 plugin itself.  The location of the source is
   - jni/gles2glide64/src/Glitch64
   - jni/gles2glide64/src/Glide64
You can ignore everything inside GlideHQ since that is not currently compiled into the app.

SDL2 is used mainly for OpenGL initialization, and is used by all three plugins.  I don't think any of its run-time rendering functions are being used anywhere.  You could maybe see if there are any SDL2 functions that glide uses that rice and gln64 do not, and see if a workaround could be inserted there.  But SDL2 isn't the first place I'd look for the solution.

Likewise, the java code only contains a bit of OpenGL initialization stuff (src/paulscode/android/mupen64plusae/jni/NativeSDL.java), so there's very little opportunity there to insert a workaround.

I'd start with the native code in Glitch64, then Glide64.  I think part of the solution will involve just doing a lot of googling to identify other apps with the same issue, and to see if anyone has found a workaround.  And although we don't use much SDL2 functionality, it may still be worthwhile to check their repository (http://hg.libsdl.org/SDL) to see if they've had to deal with the issue.  Might not solve our problem directly, but could give us some more hints.  We're using the 2.0.0-release version of SDL2.
Title: Re: Gles2glide64 plugin orientation issue
Post by: Dragoth on January 10, 2014, 08:36:17 AM
I can't seem to access the screenshot links (getting a 403 error).

Since we're not really fixing our own bug, but rather finding a workaround to someone else's, then in theory there may be more than one solution.  Or none at all.  The first place I'd look would be the gles2glide64 plugin itself.  The location of the source is
   - jni/gles2glide64/src/Glitch64
   - jni/gles2glide64/src/Glide64
You can ignore everything inside GlideHQ since that is not currently compiled into the app.

SDL2 is used mainly for OpenGL initialization, and is used by all three plugins.  I don't think any of its run-time rendering functions are being used anywhere.  You could maybe see if there are any SDL2 functions that glide uses that rice and gln64 do not, and see if a workaround could be inserted there.  But SDL2 isn't the first place I'd look for the solution.

Likewise, the java code only contains a bit of OpenGL initialization stuff (src/paulscode/android/mupen64plusae/jni/NativeSDL.java), so there's very little opportunity there to insert a workaround.

I'd start with the native code in Glitch64, then Glide64.  I think part of the solution will involve just doing a lot of googling to identify other apps with the same issue, and to see if anyone has found a workaround.  And although we don't use much SDL2 functionality, it may still be worthwhile to check their repository (http://hg.libsdl.org/SDL) to see if they've had to deal with the issue.  Might not solve our problem directly, but could give us some more hints.  We're using the 2.0.0-release version of SDL2.

Thanks for the info! I'll try my luck with the native code of Glitch64/Glide64.  :)
Title: Re: Gles2glide64 plugin orientation issue
Post by: neopoya on January 12, 2014, 01:16:50 PM
I have a Nexus 5 and i am really looking forward for a fix on this. Sadly i have no idea about developing/android/open GL or emulation  :(

I really hope you guys manage to fix this somehow and i wish you the best luck on it. I really love your work and i wish there was a way i could help you with this matter, the only thing i can do is say THANK YOU for everything and throwing my support with this comment  ;)
Title: Re: Gles2glide64 plugin orientation issue
Post by: Mikhail on January 12, 2014, 02:20:59 PM
I think it might already be fixed, Qualcomm have updated to the v66 driver now, a few Samsung devices have it already and the Asus PadFone X just showed up with it on GFXbench reading the forum their was supposed be an update on the 18 dec that has been delayed for us Nexus users, it'll more than likely showup in the next ota update.
Title: Re: Gles2glide64 plugin orientation issue
Post by: Dragoth on January 13, 2014, 01:27:23 AM
I think it might already be fixed, Qualcomm have updated to the v66 driver now, a few Samsung devices have it already and the Asus PadFone X just showed up with it on GFXbench reading the forum their was supposed be an update on the 18 dec that has been delayed for us Nexus users, it'll more than likely showup in the next ota update.

That's some awesome news! I'll spam F5 on XDA hoping on a new ROM Version. Thanks :)
In the meantime i'll keep looking through the code...  :-\
Title: Re: Gles2glide64 plugin orientation issue
Post by: Dragoth on January 15, 2014, 01:50:36 AM
I pretty much give up at this point. I've tried everything to my knowledge. I barely know about framebuffers, glscissor and the sorts with opengl... but not enough to fix this problem. I have absolutely no clue, how to rotate the framebuffer. I'm not even sure where excatly the problem arises. It could be when copying to the hardware buffer or when reading from it. I couldn't find out. Logically, changing the viewport or glscissor dimensions does nothing to the video output when the problem exists in the framebuffer...

I somehow managed to manipulate the framebuffer by switching width/height variables in the glitch64 source, but thats it.

(http://i.imgur.com/Agy7IeU.png?1)

I need to first read up on OpenGL and understand more about framebuffers and how to rotate them (if even possible).

I just hope that the coming update from Qualcomm will fix this issue (and that it doesn't take too long to arrive as an OTA update).  :(

edit: I also have not found another app with this problem but the dolphin emulator. And they seem to have fixed it with some help from the Freedreno developer http://bloggingthemonkey.blogspot.co.uk/2012/04/fighting-back-against-binary-blobs.html (http://bloggingthemonkey.blogspot.co.uk/2012/04/fighting-back-against-binary-blobs.html). I'm not sure if it worked. I didn't contact any of the developers.
Title: Re: Gles2glide64 plugin orientation issue
Post by: Mikhail on January 15, 2014, 03:09:46 AM
Check the code commit here from 6 weeks ago, then the 336947580d6644de82cd692675175feb8a77ca7b - diff https://android.googlesource.com/platform/hardware/qcom/display/

http://www.youtube.com/watch?v=v9BJZLquL-4
irc when you booted Android 4.3 in landscape it produced a bug on bootup where it'd flicker black before correcting it's orientaion for the lock screen, the bug didn't happen in portrait.
This probably explains why they simplified the boot animation also for 4.4 to mask the X placement being in the wrong spot.
Title: Re: Gles2glide64 plugin orientation issue
Post by: littleguy on January 15, 2014, 07:19:12 AM
Interesting, thanks guys for sharing.  Here's a shortcut to the diff Mikhail mentioned:
https://android.googlesource.com/platform/hardware/qcom/display/+/1a1d427bb6df85a38b874bf5c7689e7147f848fe%5E1..1a1d427bb6df85a38b874bf5c7689e7147f848fe/
Title: Re: Gles2glide64 plugin orientation issue
Post by: littleguy on February 03, 2014, 07:52:27 PM
For anyone who has the 90-degree screen rotation in glide, would you mind testing the version below?  It's a bit of a long shot, but one of the upstream devs made some changes to some of the blitting code, and blitting is the only thing I've heard as possibly associated with the issue.

https://dl.dropboxusercontent.com/u/3899306/Mupen/mupen64plus-ae-299a9c4.apk
Title: Re: Gles2glide64 plugin orientation issue
Post by: Dragoth on February 04, 2014, 05:06:35 AM
For anyone who has the 90-degree screen rotation in glide, would you mind testing the version below?  It's a bit of a long shot, but one of the upstream devs made some changes to some of the blitting code, and blitting is the only thing I've heard as possibly associated with the issue.

https://dl.dropboxusercontent.com/u/3899306/Mupen/mupen64plus-ae.apk

Sadly no... same issue  :'(
Title: Re: Gles2glide64 plugin orientation issue
Post by: Dragoth on February 11, 2014, 07:52:30 AM
Anyone here with a Nexus 5 that has had this orientation problem?

If yes, could you test out the new qualcomm driver? (Flash .zip through recovery [TWRP/Clockwork])

Download:
http://d-h.st/f47


More Info: https://developer.qualcomm.com/mobile-development/maximize-hardware/mobile-gaming-graphics-adreno/mobile-gaming-graphics-optimization-tools


I just tried it with my Nexus 4 (Adreno 320). But it didn't fix the problem. The driver is most likely not compatible with the Adreno 320 since it's made for the Adreno 330.

The driver didn't break anything, but make a Backup beforehand, just in case.

Title: Re: Gles2glide64 plugin orientation issue
Post by: puppy on February 11, 2014, 10:31:28 PM
Anyone here with a Nexus 5 that has had this orientation problem?

If yes, could you test out the new qualcomm driver? (Flash .zip through recovery [TWRP/Clockwork])

Download:
http://d-h.st/f47


More Info: https://developer.qualcomm.com/mobile-development/maximize-hardware/mobile-gaming-graphics-adreno/mobile-gaming-graphics-optimization-tools


I just tried it with my Nexus 4 (Adreno 320). But it didn't fix the problem. The driver is most likely not compatible with the Adreno 320 since it's made for the Adreno 330.

The driver didn't break anything, but make a Backup beforehand, just in case.

Just flashed my Nexus 5 with the new driver linked in your post, still has the same issue, sadly.
Title: Re: Gles2glide64 plugin orientation issue
Post by: Dragoth on February 12, 2014, 01:09:56 AM
Just flashed my Nexus 5 with the new driver linked in your post, still has the same issue, sadly.

(http://nooooooooooooooo.com/vader.jpg)

That means, we can't really hope that qualcomm will fix this issue. Maybe with an official OTA update... which could take months because there are no signs of an update. Damn, this makes me sad  :'(

Thank you for trying it out!

Here is the thread from the person who made the flashable zip: http://forum.xda-developers.com/showthread.php?t=2629123 (http://forum.xda-developers.com/showthread.php?t=2629123)
Credits to Aiko0923.

I guess i'll revert to Android 4.3 now...
Title: Re: Gles2glide64 plugin orientation issue
Post by: Mikhail on February 16, 2014, 03:30:32 PM
4.4.2 r2 KVT49L is out now for Nexus 7 2013 deb / lte verizon
https://dl.google.com/dl/android/aosp/qcom-deb-kvt49l-a9b89301.tgz
possibly contains a newer Adreno320 driver.
Title: Re: Gles2glide64 plugin orientation issue
Post by: littleguy on February 16, 2014, 06:07:00 PM
Also, could someone test to see if either of these fixes the rotation bug?

 - In Android, go to Settings -> Developer options and check "Force GPU rendering (Force use of GPU for 2d drawing)"

 - While in game with the rotated screen, press the recent apps key (or long-click home) on your device, then return to the game.
Title: Re: Gles2glide64 plugin orientation issue
Post by: Grantious on February 16, 2014, 08:55:10 PM
Unfortunately both of those fixes don't work :/
Title: Re: Gles2glide64 plugin orientation issue
Post by: Mikhail on February 28, 2014, 09:09:46 PM
It received another update on the 28th, Nexus 7 2013 Adreno 320 driver included in this release also
https://developer.qualcomm.com/mobile-development/maximize-hardware/mobile-gaming-graphics-adreno/mobile-gaming-graphics-optimization-tools
Title: Re: Gles2glide64 plugin orientation issue
Post by: xperia64 on March 01, 2014, 10:15:40 AM
Not too optimistic about this one either, looks like its mostly Adreno Profiler updates rather than anything useful (although it does mention UBO's which may affect dolphin).
Title: Re: Gles2glide64 plugin orientation issue
Post by: maalox on March 01, 2014, 10:17:38 AM
I haven't read the whole thread so this may be a useless suggestion, but there is a tool called Display Orientator for android that may help override the behavior as a workaround.

https://play.google.com/store/apps/details?id=rubberbigpepper.Orientator&hl=en
Title: Re: Gles2glide64 plugin orientation issue
Post by: robopilot99 on March 12, 2014, 04:16:09 PM
Hello fellow users I am also experiencing this issue and I want to help get it fixed. I just flashed the drivers milkhail found and they don't work sadly. I have a second generation Nexus 7 and I have TWRP installed. Sadly i'm not a programer but I'll be happy to test any potential fixes you find.
Title: Re: Gles2glide64 plugin orientation issue
Post by: xperia64 on March 25, 2014, 05:53:03 PM
Supposedly recent builds of dolphin fixed the display orientation bug on the v66 driver on an Adreno 305:
https://forums.dolphin-emu.org/Thread-opengl-es-3-guide?pid=316681#pid316681
Mario Sunshine actually looks pretty nice.
Title: Re: Gles2glide64 plugin orientation issue
Post by: Grantious on April 22, 2014, 08:29:07 AM
Has there been any progress? not to be a nag haha, its okay with oot because other plugins work at acceptable speed and stablity but with majora its slow or crashy or sideways :/
Title: Re: Gles2glide64 plugin orientation issue
Post by: puppy on April 23, 2014, 02:05:09 PM
Also curious about this as Conker's Bad Fur Day only runs on Gles2Glide
Title: Re: Gles2glide64 plugin orientation issue
Post by: dermeister1337 on May 01, 2014, 02:41:52 PM
@puppy that's exactly what I'm running into as well.
Conker's Bad Fur Day on Nexus 5 seems to be unplayable with Mupen64plus, since only Glide gives the needed performance...
Edit: I just flashed the zip from http://forum.xda-developers.com/google-nexus-5/general/updated-driver-binaries-qualcomm-adreno-t2629123
and it worked perfectly fine!
Finally I am able to play Conker :-)
Title: Re: Gles2glide64 plugin orientation issue
Post by: tigershark160 on May 01, 2014, 10:53:49 PM
@puppy that's exactly what I'm running into as well.
Conker's Bad Fur Day on Nexus 5 seems to be unplayable with Mupen64plus, since only Glide gives the needed performance...
Edit: I just flashed the zip from http://forum.xda-developers.com/google-nexus-5/general/updated-driver-binaries-qualcomm-adreno-t2629123
and it worked perfectly fine!
Finally I am able to play Conker :-)
That's great! I'm not experienced at that kind of advanced work, but it seems like that could at least hold the key to fixing the problem for those of us who would rather not flash those drivers. Great find.
Title: Re: Gles2glide64 plugin orientation issue
Post by: LuisAngel323 on May 02, 2014, 12:29:16 AM
Guys 2 times 15 hrs game play for Majora's Mask and it deleted my file on the Galaxy Note 3! I'm so mad cus I didn't spend more then a day just for nothing! My phone just turns of and back on and my save slots are erased. I go to my memory Sd... and the slopes are still there... but I play the game and no saved files! Fix this please paul! It's so Un fair...
Title: Re: Gles2glide64 plugin orientation issue
Post by: robopilot99 on May 02, 2014, 07:24:41 PM
Do you know if there are any new drivers for the nexus 7 2013?
Edit:
Flashed the above one (for nexus 5) and it works! Time to finish Majora's mask!
Title: Re: Gles2glide64 plugin orientation issue
Post by: Mikhail on May 03, 2014, 03:36:13 PM
https://developer.qualcomm.com/mobile-development/maximize-hardware/mobile-gaming-graphics-adreno/tools-and-resources
Title: Re: Gles2glide64 plugin orientation issue
Post by: tigershark160 on May 10, 2014, 05:45:20 PM
Will this be fixed without us having to flash drivers? I'm not comfortable doing that and weirdly enough, I've had trouble finding a plain English step by step guide for doing it. Also, i'm not prepared to lose any files on my phone.
Title: Re: Gles2glide64 plugin orientation issue
Post by: artorias on May 12, 2014, 03:52:33 AM
While Qualcomm staff tries to fix their bug, I have modified some custom virtual pad profile I downloaded here to play Majora's Mask on portrait, uploaded by a user named Tripod. (default action)

It's not the ideal way, but at least the Nexus 5 has enough resolution to fit the N64 resolution several times, even in portrait.


This is the original layout by Tripod
http://db.tt/7gbiQorE (http://db.tt/7gbiQorE)

As I only changed the button positions, I post the pad.ini

Code: [Select]
[INFO]
name=Default Action Portrait for MM
version=0.1
about=Portrait for MM
author=Tripod, Modified

[MASK_COLOR]
CUp=57546
CRight=16737116
CDown=8692181
CLeft=5925663
A=32582
B=4934475
L=16757760
R=7020361
Z=4368108
Start=11820381

[FPS]
info=fps
x=50
y=100
numx=27
numy=50
rate=15
font=Mupen64Plus-AE-White

[ANALOG]
info=Analog hat
x=30
y=75
min=1
max=55
buff=55

[BUTTON1]
info=CUp - CRight - CDown - CLeft
x=80
y=70

[BUTTON2]
info=A - B
x=85
y=90

[BUTTON3]
info=L
x=0
y=50

[BUTTON4]
info=R
x=0
y=60

[BUTTON5]
info=Z
x=65
y=100

[BUTTON6]
info=Start
x=40
y=90


This is how it looks

(http://s4.postimg.org/6yib1951p/Screenshot_2014_05_12_10_37_57.jpg)

Also I have a question, In case Qualcomm released a final version of the drivers with the issue solved, ┐How would it reach users with un-rooted devices? With the next Android update, I suppose?
Title: Re: Gles2glide64 plugin orientation issue
Post by: littleguy on May 12, 2014, 08:28:06 AM
Thanks artorias.

I would think that the various device manufacturers would need to release an OTA update for non-rooted users to get the fixed drivers.  Unfortunately such an update would probably vary from model to model and carrier to carrier, so it's by no means a guarantee.

It is very unlikely that mupen64plus ae will ever implement a workaround for Qualcomm's bug.  None of the usual developers here knows what causes the bug, let alone how to make a workaround for it.  The only way we could fix it is if some new developer jumped in who knew how to fix the problem, or some knowledgeable user pointed us to more technical information about the cause of the bug so we could fix it.  Right now development on the project is almost nil, so this really isn't at the forefront of anyone's mind unfortunately.
Title: Re: Gles2glide64 plugin orientation issue
Post by: artorias on May 12, 2014, 01:17:28 PM
Thanks for the info, littleguy!, and for the great job in Mupen!

Let's hope for a Qualcomm update or a reboost in the MupenAE project.
Title: Re: Gles2glide64 plugin orientation issue
Post by: scorpio16v on May 12, 2014, 11:33:22 PM
Is this bug still there in the actual N5 fw ?
As I understand, the same rotation bug was fixed in Dolphin emulator with Qualcomm driver v.66.
At least, on my Xperia Z1c, the bug in Dolphin and MP64+ was fixed with the fw update and driver v.66. So other Qualcomm based devices with newer updates should have the fix now.
Title: Re: Gles2glide64 plugin orientation issue
Post by: artorias on May 13, 2014, 02:57:00 PM
Yes, in my Nexus 5 with 4.4.2 still is the bug
┐How did you update to that driver? did you flash it in a rooted device, or did it come with some OTA update?
Title: Re: Gles2glide64 plugin orientation issue
Post by: scorpio16v on May 13, 2014, 03:10:44 PM
The driver was updated in the latest stock firmware some weeks ago.
I thought the N5 has the v66 driver too, because the lg g2 has it.
Title: Re: Gles2glide64 plugin orientation issue
Post by: artorias on May 14, 2014, 07:06:44 AM
I emailed Qualcomm support, and after a few questions, the guy told me it must be fixed in the next update fot the Nexus 5, as the bug was identified and fixed some months ago, and some devices such as Nexus 4 have already received the fix
Title: Re: Gles2glide64 plugin orientation issue
Post by: tigershark160 on May 14, 2014, 11:03:30 PM
That's really great news... Any idea of when perhaps that could happen? Or about every how often do those updates happen?
Title: Re: Gles2glide64 plugin orientation issue
Post by: asturias3636 on May 17, 2014, 02:08:56 PM
This error will be fixed in drivers following android 4.4.3 OTA? Supposedly coming out on May 23
Title: Re: Gles2glide64 plugin orientation issue
Post by: Snowball on May 20, 2014, 04:11:06 AM
Hi there,

my first post here. :)

I have a Nexus 5 + SuperN64 emulator + Majora's Mask (best game ever IMHO)

Leaving plugin as default I got of flickering problems in the town (I'm still at the begin of the game).
I heard that this problems is fixed changing the plugin to "gles2glide64" but as soon as I change it, I'm getting the orientation issue too.

My post here just to ask: have they fixed this issue yet?
Thanks!
Title: Re: Gles2glide64 plugin orientation issue
Post by: tigershark160 on May 21, 2014, 10:19:22 AM
So it looks like the update has been delayed.


http://www.android.gs/android-4-4-3-kitkat-update-for-google-nexus-4-nexus-5-nexus-7-and-nexus-10-might-be-delayed-again/

http://m.ibtimes.com/android-443-kitkat-update-reportedly-delayed-developer-expects-rooting-problems-1586672

That sucks.
Title: Re: Gles2glide64 plugin orientation issue
Post by: artorias on May 25, 2014, 04:00:42 PM
It's a matter of days/weeks that the OTA with the fix comes.
But if you really want to play Majora's now, you can try N64oid, it runs fine in that emulator, although the dev stopped working in it in 2012 and it has much fewer options and customization than Mupen64.

IMPORTANT: In newer Android versions, the game wont start when you load it, you have to enter the menu, then return to the game, and it will start.

N64oid can't be found on Google Play, you can still purchase it on SlideME. It was witdrawn for Google Play for using open source code to make a paid app.



N64oid was a nice emulator, and it was better than Mupen64 a couple of years ago, as it had the advantage of being closed source and a paid app, but as soon as N64oid stopped updatting, Mupen64 took over and got better in most aspects.
Title: Re: Gles2glide64 plugin orientation issue
Post by: retroben on May 25, 2014, 09:25:53 PM
I don't get the orientation issue on Fire TV when using Glide.
Maybe it is because of an app I got that forces it to be landscape for apps like 1mobile market.

One thing that N64oid has Mupen64Plus AE and the faster SuperN64 4.0 (no longer in play store) beat on is instant access to cheats for enabling and disabling them without needing to exit the game.
I have Mupen64Plus AE Free and the also free SuperN64 on my Fire TV,and they can run quite well at 1080P and with HQ4X enhancement.
Just wished that Banjo-Tooie would run crashless and in unga cave,and that DK64 had working collisions.

Paul,could you please add in the option to access cheats in-game?
Maybe even to the further extreme,you can be the first on android to make it possible to edit cheats in real-time!

I also hope you can find the same kind of speed increases that the SuperN64 and CoolN64 devs got.
CoolN64 fails to run correctly for me though,just returns to the menu after trying to load a game.
Maybe there is a conflict with the multiple emulators based on mupen being installed on the same device?
Title: Re: Gles2glide64 plugin orientation issue
Post by: littleguy on May 25, 2014, 09:35:01 PM
SuperN64 is written by a douchebag.  I wouldn't use that emulator even if you think it's faster.  They just took the mupen64plus ae source code and slapped ads on it, and failed to release the source code.  As far as I can tell it's just the source code from an older version of mupen64plus ae.  If it truly is faster, that would indicate either a regression in code (possible) or you aren't using the same settings in both apps (more likely).

If you want a real alternative to mupen64plus ae, try retroarch.  Their devs are really hard working, release all the source code as soon as it's written, and never ask for a penny in return.  They're also talented devs and have fixed a lot of bugs, so you might get better results with some games.
Title: Re: Gles2glide64 plugin orientation issue
Post by: retroben on May 25, 2014, 10:50:13 PM
The Fire TV uses a sucky Qualcomm Adreno processor that can't run most of the cool apps because of major compatibility/stability issues.
Most of the problem is likely caused by being on a custom Android ROM.
What proves that Qualcomm initially sucks is that somebody had to make their own custom driver for it just to make it function better (freedreno).
Read about all the trouble that the Dolphin Emulator for Android has with Qualcomm chips and you'll get my point.

I already tried the stable version of retroarch and it sucks for N64 because it is much slower than all other renditions of mupen and lacks analog input mapping for keyboard users,as does Reicast.

The later unofficial RetroArch builds are virtually unusable to me because the inputs failed to work at all.
They should fix it where the normal controls work on the in-game settings GUI instead of forcing the gamepad inputs.
They also lack specific control mappings for each system like the C buttons for N64.
Title: Re: Gles2glide64 plugin orientation issue
Post by: artorias on June 02, 2014, 06:08:13 PM
The new OTA with the 4.4.3 update is finally out!
It will arrive gradually to the devices in the following days.
According to Qualcomm staff this will fix the bug, I will confirm this as soon as the OTA arrives to my NEXUS 5, but that should be it.
Title: Re: Gles2glide64 plugin orientation issue
Post by: Mikhail on June 03, 2014, 03:16:52 AM
No change with 4.4.3 it still uses the v53 driver for whatever reason :-(
the only thing I have noticed is the screen contrast is higher now making the screen slightly darker.
Title: Re: Gles2glide64 plugin orientation issue
Post by: asturias3636 on June 03, 2014, 09:49:36 AM
have not corrected the flaw in android 4.4.3?? :(
Title: Re: Gles2glide64 plugin orientation issue
Post by: Mikhail on June 03, 2014, 10:47:21 AM
Nope not on Nexus 7 flo on ktu84l dunno about Nexus 5, there's mention of ktu84m on aosp already though.
The odd thing is this doesn't effect retroarch with the glide plugin, I guess it renders the window differently or uses open gl es 2.0 instead.
Title: Re: Gles2glide64 plugin orientation issue
Post by: tigershark160 on June 03, 2014, 02:10:35 PM
Oh man that's ridiculous. I'm still holding out hope that it will be fixed for nexus 5 as that's what I have. Retroarch for android has no control input and getting it to run is extremely esoteric and I don't understand it, or else I'd just use that.
Title: Re: Gles2glide64 plugin orientation issue
Post by: xperia64 on June 04, 2014, 06:47:30 PM
Can someone try these drivers and report back? http://forum.xda-developers.com/showpost.php?p=53042116&postcount=80

Includes Nexus 4, 5, and 7 (2013).
Title: Re: Gles2glide64 plugin orientation issue
Post by: artorias on June 05, 2014, 05:57:51 PM
I updated my Nexus 5 to 4.4.3 and the bug is still there, this is ridiculous, FFS, why didn't Google include the updated drivers.???
Title: Re: Gles2glide64 plugin orientation issue
Post by: Grantious on July 27, 2014, 03:19:28 AM
I finally gave up waiting :P and decided to figure stuff out haha
if you game follow the instructions on that vid to update your adreno drivers!! worked thank f@$k
I'm assuming that eventually new drivers will be included in newer firmware updates but until then!
https://www.youtube.com/watch?v=ONhQCkCaOlw
No adverse effects as of yet so yay.
Title: Re: Gles2glide64 plugin orientation issue
Post by: artorias on November 10, 2014, 03:14:07 PM
Not strictly on topic, but now I switched to a Xperia Z3 compact, the plugin works fine in this device, but I noticed that in the video options it has "no more than 5 frames" in the frameskip options as default. I supossed it was automatic and it would not skip frames if it wasn't needed, but as I noticed poor performance, I tried to lower it to 2 frames, and Holy fuck, it runs perfect at 100% speed.

Edit:
So, thank you all devs! finally I can play MM at 100% speed on android, You really made me happy   :)
Title: Re: Gles2glide64 plugin orientation issue
Post by: tigershark160 on November 20, 2014, 11:05:48 PM
Android 5 fixes orientation problem with glide, but it seems to have framerate issues not previously present. Good sign though
Title: Re: Gles2glide64 plugin orientation issue
Post by: littleguy on December 17, 2014, 08:25:29 AM
Resurrecting an old thread...

Does anyone here still have the glide rotation issue (i.e. still running Adreno 320 and KitKat)?  If so, please go to the Alpha testing thread.  We can probably fix the issue now, but first I need to see if there are any testers available.
Title: Re: Gles2glide64 plugin orientation issue
Post by: MoopenGirl on December 26, 2014, 12:05:41 AM
Nexus 7 32GB 2013 (WiFi) still has this problem on Mupen64Plus AE 2.4.4 running on stock Android 4.4.4, but the issue seems to be fixed in the Mupen64Plus AE 3.0 Alpha 10. I'll make a reply in the 3.0 testing thread for it with more information if you're still looking for testers.