XOpenGL OpenGL3 / OpenGL4 renderer for UnrealTournament

[lowenz]

I've seen this error only if the card isn't supporting the OpenGL version fully. In other words, neither OpenGL3.3 nor OpenGL ES 3.0 are correctly supported by the drivers of this card as far I can tell.

You're probably right.
It's a pity for ES path.

[Smirftsch]

in order to make XOpenGL work on Linux ARM, I may implement a lower OpenGL ES version yet (something 1.x) , but for now my Pandaboard which I am using is instable and support is lousy. I don't have the money right now to buy another dev platform right now, but this may work out for such graphics cards like the one you mentioned as well.

[スマイル・ドラゴン]

I can't run this on open source drivers I just get this error:

Code: Select all

SDL2: Opening viewport.
Bound to XOpenGLDrv.so
SDL2: Loaded render device class.
XOpenGL:Creating new OpenGL context.
SDL2: Using OpenGL
SDL2: Creating new window with 1024x768
Glew successfully initialized.
XOpenGL: MakeCurrent
GL_VENDOR     : X.Org
GL_RENDERER   : Gallium 0.4 on AMD BARTS (DRM 2.43.0, LLVM 3.8.0)
GL_VERSION    : 3.0 Mesa 11.2.0-devel (git-85fab1f 2016-02-10 trusty-oibaf-ppa)
OpenGL 3.3 context initialized!
Log compiling xopengl/DrawSimple.vert 0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, and 3.00 ES

appError called:
Failed compiling xopengl/DrawSimple.vert
UXOpenGLRenderDevice::LoadShader

[[]KAOS[]Casey]

Looks like the driver hasn't put in tesselation yet for the barts series of gpus

https://www.x.org/wiki/RadeonFeature/#index1h2

have you tried the DRM drivers?

[lowenz]

With "ES" path the brightness handling is completely different.
Can you match it with "Core"'s one or is a pain in the ass?

[スマイル・ドラゴン]

AMD BARTS doesn't support double precision floating point and nobody at Mesa feels like adding the neccesary software emulation to make it work.

I'm on 4.4.0-22-generic so I doubt proprietary drivers are a good idea right now. Nor do I even want to use proprietary drivers when everything else from Terraria to Source Engine seems to work fine.

[Smirftsch]

I can't run this on open source drivers I just get this error:

Code: Select all

SDL2: Opening viewport.
Bound to XOpenGLDrv.so
SDL2: Loaded render device class.
XOpenGL:Creating new OpenGL context.
SDL2: Using OpenGL
SDL2: Creating new window with 1024x768
Glew successfully initialized.
XOpenGL: MakeCurrent
GL_VENDOR     : X.Org
GL_RENDERER   : Gallium 0.4 on AMD BARTS (DRM 2.43.0, LLVM 3.8.0)
GL_VERSION    : 3.0 Mesa 11.2.0-devel (git-85fab1f 2016-02-10 trusty-oibaf-ppa)
OpenGL 3.3 context initialized!
Log compiling xopengl/DrawSimple.vert 0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, and 3.00 ES

appError called:
Failed compiling xopengl/DrawSimple.vert
UXOpenGLRenderDevice::LoadShader

[スマイル・ドラゴン]

Then I wonder why I don't get GLSL 3.30 despite having OpenGL 3.3 context support.

I read online it may be due to the program not requesting a OpenGL 3.3 Core profile context, because Mesa doesn't support Compatibility context's for some reason.

I don't know how to get it to switch to ES, and glxinfo doesn't even report OpenGL ES at all.

[Smirftsch]

it's a setting in advanced options:
OpenGLVersion=Core
to
OpenGLVersion=ES

and it's definitely core profile - but as said, with my Intel card and Mesa I don't get 3.3 either.


[edit]glxinfo | grep 'version'[/edit] should show ES as well though, do you get nothing at all there about ES?

[スマイル・ドラゴン]

I get nothing about OpenGL ES in glxinfo. So why is it saying I support a GLSL version of 3.00 ES?

[Smirftsch]

need to check again though, but as far I do remember right now, is Mesa supporting it by default, so I'm more wondering why it should NOT support it - except maybe it's some additional package and not in core packages at least...

[スマイル・ドラゴン]

Even setting that variable in the ini it still crashes.

What would happen if I went and changed every shader file to ask for 1.30 GLSL? Will that just fail spectacularly? Is there a reason why it needs 3.30 because Terraria and Source Engine have shaders working just fine on 1.30...

[Smirftsch]

not spectacularly, but will fail for the moment. When I find some time I will see what all is required or is to be stripped&changed to make it work with the 1.3 version, functionality in general should be possible with this version though.

[lowenz]

Test on Intel Skylake (i3 6300) + Intel GPU (HD 530).

OpenGL ES -> strange behaviour, corrupted geometry, no menu, etc....

OpenGL Core -> perfect (!!!!), constantly 300 FPS in DM-Agony.....brilliant!

So the problem is only for Radeon GPUs (drivers).

[スマイル・ドラゴン]

Maybe if I wasn't stuck on a GPU that had no hardware support for double precision floating points I wouldn't have this problem.

Or maybe if Mesa did Compatibility Profiles, I mean yeah that would be REALLY nice.

[lowenz]

EDIT

Low FPS problem with "Core" mode still present with Win10

With "ES" mode 90 FPS vs.....250 (GeForce 750 Ti).

[REA]

Any news so far?

[Smirftsch]

not much, got little feedback recently and my time was very limited also. Still alive though

[AFreakinProblem]

Just gave the latest a try and I don't know if AMD just hates OpenGL or what, but I have not been able to get decent performance out of this. In Direct3D10 and other OpenGL renderers, I've been able to pretty much just max out every setting (parallax mapping, etc.) in the preferences window and get 200fps unless I used vsync. with XopenGL however that is far from the case, regardless of settings I'm lucky to crack 15fps default or with tweaks and with some tweaks I've gotten the game to completely lock up, display almost all black, or display everything over lit. My rig has a Radeon HD7950 3GB graphics card and a 4GHz Vishera and 8GB of RAM if you need specs. OpenGL version: 6.14.10.14008, Radeon Settings Version: 2016.0916.1515.27418, running Windows 10 here.

[Leo T_C_K]

What parallex mapping? Unreal didn't have support for that since version 0.83 (October 1996), shamefuly enough....

Unless its something new in these drivers.

[AFreakinProblem]

Gave the renderer another try and strangely I got it (mostly) playable after switching from core to es, but I still ended up taking a 100+fps hit, running it at roughly 60-100, and experiencing a pretty long precache message between bringing up and closing out of the UT desktop or taking screenshots. There's also a strange issue with how the brightness is handled. On older OpenGL renderers and Direct3D I get considerably brighter lighting in-game and typically have to just adjust it up one (Direct3D) or down one (OpenGL) to get pretty close to the same scene. Under XopenGL however, I have to put it considerably higher and I'll get basically the same scene on the map itself, but things like my HUD, weapon, characters, and pickups will still be far darker than they should be.

What parallex mapping? Unreal didn't have support for that since version 0.83 (October 1996), shamefuly enough....

Unless its something new in these drivers.

Direct3D 10 for Unreal Tournament has it, barely noticeable in-game though. You can see it when you put the camera really close to surfaces, particularly at an angle.

[Leo T_C_K]

Is there a screen or video of this?

[AFreakinProblem]

Is there a screen or video of this?

Screenshots for whatever reason get butchered with UT99's built in tool... never displays the gamma correctly. I'll see if Steam's tool does a better job.

EDIT: Doesn't seem to work with non-Steam games (I have GotY in disc form).

[Leo T_C_K]

Just try print screen or alt print screen(windowed) and paste it in an image program and save.

[AFreakinProblem]

Just try print screen or alt print screen(windowed) and paste it in an image program and save.

Have the same issue. Gamma is never accurately screencapped, and I'm on a CRT monitor so I can't just snap a pic of the screen.