All Projects Gameplay + OpenGL Software Renderer zdoom.org (Site)

View Issue Details

Jump to NotesIssue History
IDProjectCategoryView StatusDate SubmittedLast Update
0000172Gameplay + OpenGL[All Projects] Bugpublic2017-02-03 23:242017-02-04 17:57
ReporterT-10a 
Assigned To 
PrioritylowSeverityminorReproducibilityalways
Status closedResolutionnot fixable 
PlatformLinuxOSArch LinuxOS Version
Summary0000172: OpenGL effects such as Bloom, Lens Distortion, and Tonemap do not work on Linux
DescriptionThe following OpenGL visual effects under Preferences do not seem to work under Linux systems:
- Multisample
- Tonemap Mode
- Bloom Effect
- Lens Distortion
- Ambient Occlusion Quality
- FXAA Quality

Other settings that do not seem to work are related to the above.
Steps To ReproduceStart GZDoom with any IWAD. (I used Doom for testing)

If these effects are enabled already, turn them off for comparison.

Start up a game (Due to the visible lights right off the bat, E1M1 in Doom is what I used to test the flares)

Pause the game, and go into Display Options > OpenGL Options > Preferences.

Turn on any of the effects listed above in the description, and compare the background to when the effects were off.
Additional InformationInterestingly, the above effects work when I run the Windows version of GZDoom in Wine.

This bug also affects QZDoom.

In earlier versions of GZDoom (i.e. 2.3.0), these effects worked.

I tried using both the AUR versions (gzdoom and gzdoom-git) and manually compiled versions from Github. They both had the above problems.
TagsBloom, Effects, FXAA, Lighting, Visual

Relationships

Activities

T-10a

T-10a

2017-02-03 23:24

reporter  

GZDoomError.png (407,042 bytes)
T-10a

T-10a

2017-02-03 23:26

reporter   ~0000344

Last edited: 2017-02-03 23:27

View 2 revisions

 I do not know if this bug affects other Linux distributions. If anyone else can replicate this bug on other distros (Fedora, Ubuntu/Debian, OpenSUSE, Gentoo, etc.), please confirm here as well.
_mental_

_mental_

2017-02-04 01:50

developer   ~0000345

All these settings require render buffers to be supported and enabled.
What's the version of OpenGL reported during startup? What's the value of gl_renderbuffers CVAR?

You said that earlier versions work right now but the latest does not. I suspect it may be related to this line.
If you are building from sources: replace it with if (false) or just comment these lines.
T-10a

T-10a

2017-02-04 02:05

reporter   ~0000346

gl_renderbuffers is true. However, I did check my system and apparently it is on OpenGL 3.0, the version noted in the source. I'll try alternate drivers which might provide a newer OpenGL version, and try again.
_mental_

_mental_

2017-02-04 02:35

developer   ~0000347

Did everything work fine before this check was introduced in 2.3.1? I mean there were no visual glitches like missing sprites or geometry.
If so, apparently some adjustments to it are needed.
Please post startup lines beginning with GL_..., GL_VENDOR and GL_RENDERER in particular.
T-10a

T-10a

2017-02-04 02:55

reporter   ~0000350

Last edited: 2017-02-04 02:55

View 2 revisions

 ok, here it is:

GL_VENDOR: X.Org
GL_RENDERER: Gallium 0.4 on AMD HAWAII (DRM 3.8.0 / 4.9.6-1-ARCH, LLVM 3.9.1)
GL_VERSION: 3.0 Mesa 13.0.4 (Compatibility profile)
GL_SHADING_LANGUAGE_VERSION: 1.30
T-10a

T-10a

2017-02-04 04:38

reporter   ~0000352

Last edited: 2017-02-04 04:39

View 2 revisions

 I compiled again with the changes you suggested. Unfortunately, it did not fix the issue.

Here's what i did:


.. 
    if ((gl_version >= 3.3f || CheckExtension("GL_ARB_sampler_objects")) && !Args->CheckParm("-nosampler"))
    
{
        gl.flags |= RFL_SAMPLER_OBJECTS;
    }
    
    // The minimum requirement for the modern render path are GL 3.0 + uniform buffers. Also exclude 
the Linux Mesa driver at GL 3.0 because it errors out on shader compilation.
/*
    if (gl_version < 3.0f || (gl_version < 3.1f && (!CheckExtension("GL_ARB_uniform_buffer_object") 
|| strstr(gl.vendorstring, "X.Org") != nullptr)))
    {
        gl.legacyMode = true;
        gl.lightmethod = LM_LEGACY;
        gl.buffermethod = BM_LEGACY;
        gl.glslversion = 0;
        gl.flags |= RFL_NO_CLIP_PLANES;
    }
    else
    */
..


Graf Zahl

Graf Zahl

2017-02-04 06:39

administrator   ~0000353

The Mesa driver does not handle these features in a sufficient manner and has been intentionally bumped down into legacy support.

I'm sorry but if a hardware vendor does not provide a proper driver and forces to use something this broken there's not much I can do about it.
T-10a

T-10a

2017-02-04 17:55

reporter   ~0000378

Last edited: 2017-02-04 17:57

View 2 revisions

 I have found a fix for this, however it is user-side and may cause issues (as noted in the source code):

running GZDoom with an environment variable MESA_GL_VERSION_OVERRIDE="3.1FC" fixes it.

source: http://mesa3d.org/envvars.html

This is for those who are having a similar issue and are looking for a fix.

Issue History

Date Modified Username Field Change
2017-02-03 23:24 T-10a New Issue
2017-02-03 23:24 T-10a File Added: GZDoomError.png
2017-02-03 23:24 T-10a Tag Attached: Bloom
2017-02-03 23:24 T-10a Tag Attached: Effects
2017-02-03 23:24 T-10a Tag Attached: FXAA
2017-02-03 23:24 T-10a Tag Attached: Lighting
2017-02-03 23:24 T-10a Tag Attached: Visual
2017-02-03 23:26 T-10a Note Added: 0000344
2017-02-03 23:27 T-10a Note Edited: 0000344 View Revisions
2017-02-04 01:50 _mental_ Note Added: 0000345
2017-02-04 02:05 T-10a Note Added: 0000346
2017-02-04 02:35 _mental_ Note Added: 0000347
2017-02-04 02:55 T-10a Note Added: 0000350
2017-02-04 02:55 T-10a Note Edited: 0000350 View Revisions
2017-02-04 04:38 T-10a Note Added: 0000352
2017-02-04 04:39 T-10a Note Edited: 0000352 View Revisions
2017-02-04 06:39 Graf Zahl Note Added: 0000353
2017-02-04 06:39 Graf Zahl Status new => closed
2017-02-04 06:39 Graf Zahl Resolution open => not fixable
2017-02-04 17:55 T-10a Note Added: 0000378
2017-02-04 17:57 T-10a Note Edited: 0000378 View Revisions