Author Topic: Glide GL ES 2.0 Port (WIP) (Read 69671 times)

Kris · « **on:** March 27, 2013, 10:31:21 PM »

This is a work-in-progress version of a OpenGL ES 2.0 compatible version of the glide64mk2 plugin.

Source: https://github.com/paulscode/mupen64plus-ae/tree/Metricity/glide

~~https://bitbucket.org/Metricity/mupen64plus-ae~~

This is an early version, expect performance and graphical issues.

Java Changes:
Added option to select glide plugin.

Changes from glide64mk2:
Glitch64/combiner.cpp:
Alpha Test implemented in shader.
Custom attributes instead of unsupported built-in attributes (gl_Vertex, gl_MultiTexCoord, gl_Fog, gl_Color).

Glitch64/geometry.cpp:
Vertex arrays used instead of glBegin/glEnd.
Some calculations are done in the vertex shader so the data can be passed without being modified.

Glitch64/main.cpp:
Android context and swapbuffers.

Glitch64/textures.cpp:
Use supported texture formats.

Status
Working, perhaps with some issues:
Geometry, Textures, Shaders, Fog, Alpha Test, Framebuffer
Significant issues:
Depth buffer related glitches. (On Adreno, OK on PC)
High-res textures:
This uses boost and is not setup to compile. I have compiled it previously but never got around to testing it.
Screen Size:
You need to set Width and Height in mupen64plus.cfg [Video-General]
Performance:
Work on performance hasn't begun and I know of a few places where some easy fixes/optimizations can be made.

My thanks to the original developers and maintainers: Dave2001,Sergey 'Gonetz' Lipski,Gugaman,Hiroshi 'KoolSmoky' Morii, warhaft, ecsv

This is work in progress and I hope to fix the mentioned issues.

Looking forward to your feedback and queries.

littleguy · « **Reply #1 on:** March 27, 2013, 10:33:02 PM »

Stoked!!! Looking forward to trying it out!

littleguy · « **Reply #2 on:** March 27, 2013, 10:47:31 PM »

Funny, I just started looking at glide today, just seeing how many source files I could get to compile while flying blind. I knew a lot of the gl stuff would balk but I wasn't expecting to have such trouble with boost. Dependency hell. I eventually determined a fairly minimal subset of boost that would get the GlideHQ source to compile. But when I reopened eclipse the indexer crashed and burned. I was tinkering with the eclipse heap settings when this showed up in my inbox. Judging by your comments, did you wall off the boost dependency or something?

One of the other things I'm looking at right now is the SDL startup mechanics used by mupen-AE, to see if we can simplify it at all, or even revert somehow to the vanilla mupen mechanics. If I make any progress I'll keep you posted, would be nice to not have so many custom AE-specific changes to the upstream source.

Kris · « **Reply #3 on:** March 27, 2013, 11:09:57 PM »

Quote from: littleguy on March 27, 2013, 10:47:31 PM

Funny, I just started looking at glide today, just seeing how many source files I could get to compile while flying blind. I knew a lot of the gl stuff would balk but I wasn't expecting to have such trouble with boost. Dependency hell. I eventually determined a fairly minimal subset of boost that would get the GlideHQ source to compile. But when I reopened eclipse the indexer crashed and burned. I was tinkering with the eclipse heap settings when this showed up in my inbox. Judging by your comments, did you wall off the boost dependency or something?

I know the feeling, I had plenty of troubles with boost but did have everything compiling, it was only earlier today I looked at eliminating it to make it easier for people to test. It turned out to be really simple and I wish I knew it earlier see the changes to Glide64/TexCache.cpp and Glide64/rdp.h.

I did an draft of the post when I thought people would need to build boost which had some pointers:

Quote

I used the version at https://github.com/mcxiaoke/boost-ndk
Configured it to build with gcc4.6 by modifiying boost\tools\build\v2\user-config.jam
Then built the required modules `b2 -a --with-system --with-thread --with-filesystem toolset=gcc-android4.6 link=static runtime-link=static target-os=linux --stagedir=android --layout=system`
There is another boost for android that seems more popular by MysticTreeGames but I had problems with it.

Here is the user-config.jam

Code: [Select]

import os ;

if [ os.name ] = CYGWIN || [ os.name ] = NT
{
        androidPlatform = windows ;
}

else if [ os.name ] = LINUX
{
        androidPlatform = linux-x86 ;
}

else if [ os.name ] = MACOSX
{
        androidPlatform = darwin-x86 ;

}

modules.poke : NO_BZIP2 : 1 ; 

ANDROID_NDK = .....................;
using gcc : android4.6 :
    $(ANDROID_NDK)/toolchains/arm-linux-androideabi-4.6/prebuilt/$(androidPlatform)/bin/arm-linux-androideabi-g++ :
    <archiver>$(ANDROID_NDK)/toolchains/arm-linux-androideabi-4.6/prebuilt/$(androidPlatform)/bin/arm-linux-androideabi-ar
    <ranlib>$(ANDROID_NDK)/toolchains/arm-linux-androideabi-4.6/prebuilt/$(androidPlatform)/bin/arm-linux-androideabi-ranlib
    <compileflags>--sysroot=$(ANDROID_NDK)/platforms/android-9/arch-arm
    <compileflags>-I$(ANDROID_NDK)/sources/cxx-stl/gnu-libstdc++/4.6/include
    <compileflags>-I$(ANDROID_NDK)/sources/cxx-stl/gnu-libstdc++/4.6/libs/armeabi/include
	<compileflags>-L$(ANDROID_NDK)/sources/cxx-stl/gnu-libstdc++/4.6/libs
    <compileflags>-DNDEBUG
    <compileflags>-D__GLIBC__
    <compileflags>-DBOOST_NO_INTRINSIC_WCHAR_T
	<compileflags>-DPAGE_SIZE=2048
	<compileflags>-lgnustl_static
	<compileflags>-lsupc++
    <compileflags>-mthumb
    <compileflags>-fno-strict-aliasing
    <compileflags>-O2
        ;

Also check some of the commented out parts in the makefile for how I set it up.

I only eliminated it as it complicated the build process so it will return at some stage. I will test to see if it actually works soon.

littleguy · « **Reply #4 on:** March 27, 2013, 11:13:42 PM »

Priceless. Thanks!

Kris · « **Reply #5 on:** March 28, 2013, 12:07:35 AM »

Setting width and height in the cfg doesn't seem to work anymore it was only a temporary method anyway. I had wanted to post it a few days ago but have been sorting out the release instead of doing any of the obvious small fixes.

I had done most of my testing with other dependencies and build settings and was used to it running slower so I was unsure about the performance but now it seems better.

Paul · « **Reply #6 on:** March 28, 2013, 07:48:00 AM »

Great work, Kris! You've made some amazing progress!

littleguy · « **Reply #7 on:** March 28, 2013, 08:12:11 AM »

Cool, I just got around to actually pulling and building. It took me a while to realize that you're using git (not hg) on bitbucket... kept getting hg 404 errors.

Is there a reason you didn't branch (or fork) directly in github?

For those of you who (like me) are still working on your gitfu, you can do the following to pull Kris' work into your github-originated local repo:

Spoiler: git • show

Edit: Don't forget to reload your assets (Settings->Advanced->Reload app resources)

Kris · « **Reply #8 on:** March 28, 2013, 08:34:20 AM »

I used bitbucket because I already had an account but mainly because I was expecting to need to add hundreds of files for boost and Regal and I wanted it separate as they would have been +400mb. As these are not necessary anymore I plan to use github as you mentioned.

littleguy · « **Reply #9 on:** March 28, 2013, 08:38:28 AM »

Quote from: Kris on March 28, 2013, 08:34:20 AM

I used bitbucket because I already had an account but mainly because I was expecting to need to add hundreds of files for boost and Regal and I wanted it separate as they would have been +400mb. As these are not necessary anymore I plan to use github as you mentioned.

Ah, yes, thanks for sparing me all that data!

I made a local branch and merged the latest master without conflict.

I do get an FC however when I load a game so I'll have to check into it some more. I'll post the logcat since I'm guessing you'll be interested, but please don't take this to be a support request (I can probably track it down on my own).

Spoiler: logcat • show

Kris · « **Reply #10 on:** March 28, 2013, 09:17:34 AM »

I had it building with recent versions it's just I had a black screen so I went back. I don't know if it is the changes to SDL or GameSurface that caused me problems. Not sure about the crash did you try it without merging the later code?

littleguy · « **Reply #11 on:** March 28, 2013, 09:38:35 AM »

Yeah I was going to try that this evening. That might be all it is. As I said, don't sweat it right now.

Paul · « **Reply #12 on:** March 28, 2013, 10:18:40 AM »

BTW, are you looking only for developer feedback at this particular stage, or are you ready to start reaching out to testers yet? I've been compiling a list of emails for folks with various devices who have volunteered to test the new video plug-in (when it gets to that stage)

Kris · « **Reply #13 on:** March 28, 2013, 01:25:20 PM »

Quote from: Paul on March 28, 2013, 10:18:40 AM

BTW, are you looking only for developer feedback at this particular stage, or are you ready to start reaching out to testers yet? I've been compiling a list of emails for folks with various devices who have volunteered to test the new video plug-in (when it gets to that stage)

I was used to it running at 5fps and thought the first version would be tricky to build but as I removed the dependencies and tried a non-debug build with a 2-3x improvement we're closer than I thought. On a high end device it might be playable already.

When it is working with the latest version and the depth and screensize issues are fixed testing would be great. Until then anyone is welcome to post an early apk I just didn't want to be swamped with issues when I know there are problems affecting all or many games.

Paul · « **Reply #14 on:** March 28, 2013, 01:40:04 PM »

Ok, sure. I'll hold of on the big test for now until a few more of the big issues are worked out.

Anyone who wants a "work in progress" apk in the mean time, just PM me and I'll send you a link.

Author Topic: Glide GL ES 2.0 Port (WIP) (Read 69671 times)

Kris

Glide GL ES 2.0 Port (WIP)

littleguy

Re: Glide

littleguy

Re: Glide

Kris

Re: Glide

littleguy

Re: Glide GL ES 2.0 Port (WIP)

Kris

Re: Glide GL ES 2.0 Port (WIP)

Paul

Re: Glide GL ES 2.0 Port (WIP)

littleguy

Re: Glide GL ES 2.0 Port (WIP)

Kris

Re: Glide GL ES 2.0 Port (WIP)

littleguy

Re: Glide GL ES 2.0 Port (WIP)

Kris

Re: Glide GL ES 2.0 Port (WIP)

littleguy

Re: Glide GL ES 2.0 Port (WIP)

Paul

Re: Glide GL ES 2.0 Port (WIP)

Kris

Re: Glide GL ES 2.0 Port (WIP)

Paul

Re: Glide GL ES 2.0 Port (WIP)