Kode / Krom

Other
97 stars 23 forks source link

GLSL compiler error on Linux #64

Closed zicklag closed 6 years ago

zicklag commented 6 years ago

I am using Krom on Ubuntu 16.04 and get the following errors running any Armory example. There is a built example that you can test here.

GLSL compiler error: 0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, 3.00 ES, 3.10 ES, and 3.20 ES

GLSL compiler error: 0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, 3.00 ES, 3.10 ES, and 3.20 ES

GLSL linker error: error: linking with uncompiled shadererror: linking with uncompiled shader

The output from glxinfo | grep OpenGL:

OpenGL vendor string: X.Org
OpenGL renderer string: AMD MULLINS (DRM 2.50.0 / 4.13.0-32-lowlatency, LLVM 5.0.0)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.2.8
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 17.2.8
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 17.2.8
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
OpenGL ES profile extensions:

As far as I understand it, the line, OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.2.8, means that my system should work with OpenGL up to version 4.5, but the error message is saying that GLSL 3.30 is not supported.

I found a similar issue on Stack Overflow that makes it sound like this might have something to do with Krom not requesting a Core Profile, but I don't really know much about this so I wouldn't know.

If this is too specific as it has to do with Armory games, you can close the issue. I have an open issue on the Armory project, armory3d/armory#500, but I think the issue might actually be Krom. Any help at all is appreciated. :slightly_smiling_face:

Bugsbane commented 6 years ago

I'm getting this, too, with every file I've tried including the default blender cube, playground and the Armory benchmark. My card is pretty old. I've tried changing the Render Path to medium.

screenshot_20180506_064258

Specs: Kubuntu Linux 18.04 GeForce GTX 560 with Nvidia recommended proprietary driver (version 390 ) AMD64 processor

GLX version info:

server glx version string: 1.4 client glx version string: 1.4 GLX version: 1.4 Max core profile version: 4.3 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.1 OpenGL core profile version string: 4.3 (Core Profile) Mesa 18.0.0-rc5 OpenGL core profile shading language version string: 4.30 OpenGL version string: 3.0 Mesa 18.0.0-rc5 OpenGL shading language version string: 1.30 OpenGL ES profile version string: OpenGL ES 3.1 Mesa 18.0.0-rc5 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10

zicklag commented 6 years ago

In response to my original issue @luboslenco created a patch for armory that provides a temporary work around to use older shader versions ( see the comment ). It's a "Legacy Shaders" checkbox on the addon settings page. I'm not sure how many different things could break graphically by using it though.

If your issue is similar to mine, it will also probably work fine in the browser ( though the browser is going to run slower than Krom ) if that is any help.

luboslenco commented 6 years ago

With "Legacy Shaders" option enabled the voxel ao/gi stuff will not work but apart from that it should do. And also investigating the "Krom not requesting a Core Profile" now.:)

luboslenco commented 6 years ago

Krom/Kore should request core-profile now (also included in the latest armory builds).

zicklag commented 6 years ago

That's AWESOME! I can't wait to try it. :tada:

---- On Sun, 10 Jun 2018 08:26:47 -0500 Lubos Lenco <notifications@github.com> wrote ----

Krom/Kore should request core-profile now (also included in the latest armory builds).

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

zicklag commented 6 years ago

IT WORKED!! Thank you for the fix. I just can't believe how amazing Armory is. Now I can use it to its full potential. Thanks a lot!