Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

openGL error #149

Closed
huangju91 opened this issue Sep 21, 2016 · 11 comments
Closed

openGL error #149

huangju91 opened this issue Sep 21, 2016 · 11 comments

Comments

@huangju91
Copy link

Hello@stevenlovegrove , I cmaked pangolin to vs2013 and all built it successfully,but when I use it in orb-slam2 ,the following error turns out
“ OpenGL Error: XX (1280)
In:D:\orb2Depen\Pangolin\include\pangolin/gl/gl.hpp, line 189”
Though this error did not stop my running program, I still wonder why.

@stevenlovegrove
Copy link
Owner

It's possible this has been fixed in 49aa366. Otherwise, this is likely to be a warning generated from a previous OpenGL error unrelated to Pangolin.

@fsrajer
Copy link

fsrajer commented Oct 5, 2016

Hi @huangju91, I seem to be getting the same error. Did the mentioned commit fix your problem. It did not for me.
Hi @stevenlovegrove, I am using Pangolin via ElasticFusion. The error seems to be generated by this line:
https://github.com/stevenlovegrove/Pangolin/blob/master/include/pangolin/gl/gl.hpp#L176
Any ideas what could be causing this? It does not directly cause a crash but a different call to opengl later on crashes so I assume that there will be some connection.

@fsrajer
Copy link

fsrajer commented Oct 5, 2016

OK, I have fixed both, the crash and the opengl error message. My laptop was for some reason choosing integrated Intel graphics instead of NVIDIA and the code was using some functions which were not supported by the Intel graphics. So I simply opened NVIDIA control panel and set NVIDIA graphics card to be used at all times.

@stevenlovegrove
Copy link
Owner

Thanks for the update. I'll close this issue.

@M1234Thomas
Copy link

Hello,

I am getting an error as follows.

OpenGL Error: XX (1282)
In: \ElasticFusion\Pangolin-master\include\pangolin/gl/gl.hpp, line 562

I have checked the graphics card and is set to use NVIDIA to use all the times.
I can not figure out what the issue is.

@anatoly-spb
Copy link

anatoly-spb commented Mar 2, 2017

When I run ElasticFusion build with Visual Studio 2013 on Windows 7 64bit based on Pangolin (current master)), I have problem with the draw_global_surface.vert shader:

Creating live capture... failed!
DeviceOpen using default: no devices found
GLSL Shader compilation failed: H:/tmp/ef/src/ElasticFusion/Core/src/Shaders/dra
w_global_surface.vert:
ERROR: 0:21: 'location' : syntax error parse error


GLSL Program link failed: Geometry shader object: no attached vertex shader obje
ct.

OpenGL Error: XX (1280)
In: H:\tmp\ef\src\Pangolin\include\pangolin/gl/gl.hpp, line 192

What is wrong?

@Buzzroid
Copy link

Buzzroid commented Jul 8, 2017

@fsrajer Thanks for the solution. You're the guru.

@szuer2017
Copy link

Hello,

ElasticFusion could be compiled sucessfully on my Nvidia TX2 , but I am getting an error as follows:

OpenGL Error: XX (500)
In:/ElasticFusion/deps/Pangolin/include/pangolin/gl/gl.hpp, line 212

I can not figure out what the issue is.

@shoujieqiu
Copy link

Actually,I always have this error,and I can't fix it.I wonder if anybody could help to solve it?

`Framebuffer with requested attributes not available. Using available framebuffer. You may see visual artifacts.GLSL Shader compilation failed: :
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

OpenGL Error 500: GL_INVALID_ENUM: An unacceptable value is specified for an enumerated argument.
In: /usr/local/include/pangolin/gl/gl.hpp, line 205`

@shoujieqiu
Copy link

And my computer is "RTX 2070,ubuntu 16.04,glfw 3.3"

@BruceWANGDi
Copy link

@shoujieqiu Try to use this command 'MESA_GL_VERSION_OVERRIDE=3.3 ./ElasticFusion'. It may work.
I have met this issue for so long. Some said Nvidia-driver causes this issue, which the .run profile downloaded on the official website can't work. Using the command on the system terminal may be helpful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants