Polyscope OpenGL Error! Type: Invalid enum
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.2k
- Forks
- 242
- Avg merge
- 11m
- Merged PRs (30d)
- 1
Description
[polyscope] Backend: openGL3_glfw -- Loaded openGL version: 3.3 (Core Profile) Mesa 20.0.8
[polyscope] Polyscope OpenGL Error! Type: Invalid enum
GLError() after shader compilation! Program text:
// tag ${ GLSL_VERSION }$
// from rule: GLSL_VERSION
#version 330 core
in vec3 a_position;
out vec2 tCoord;
void main()
{
tCoord = (a_position.xy+vec2(1.0,1.0))/2.0;
gl_Position = vec4(a_position,1.);
}
Traceback (most recent call last):
File "/userhome/37/gdwei/geolearning/IGR/code/reconstruction/playground.py", line 8, in
ps.init()
File "/userhome/37/gdwei/anaconda3/envs/neuralpull/lib/python3.9/site-packages/polyscope/core.py", line 12, in init
psb.init(backend)
RuntimeError: OpenGl error occurred. Text: Invalid enum
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure from the reported ps.init() entry point using OpenGL 3.3 Core Profile and Mesa 20.0.8. Read the shader compilation path around the reported vertex shader and GLError; the issue is done when initialization no longer raises the Invalid enum error in this environment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100