-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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/GLFW Conflict Between Taichi and PyGEL3D on macOS (Apple Silicon) #165
Comments
I find that this bug is not caused by OpenGL/GLFW conflict. I compile PyGEL3D without OpenGL/GLFW, by setting Use_GLGraphics to OFF in CMakeLists.txt. Conflict warnings disappear but bug still exists. 20241221-012147.mp4 |
I fixed it by replacing 20241221-021753.mp4Just wonder why don't use pyrender via pip but copy-paste? |
The same issue on Python 3.10 and 3.12 |
… duplicate class names on MacOS (M1) by changing "PyGEL3D == 0.1.0"
I solve this problem using the older "PyGEL3D == 0.1.0" version on MacOS M1 chip. #179 |
Thanks to the post of: I was able to get the initial getting started script working on my Macbook Pro M3 Max w/ Sonoma 14.5. I could not get it to work with my python venv's but I had success using miniconda with Python 3.10. |
Environment
Issue
When running the macOS example script with visualization enabled, there's a conflict between GLFW implementations from Taichi and PyGEL3D packages. This leads to OpenGL initialization issues and ultimately causes a framebuffer binding error.
The specific error starts with duplicate GLFW class implementations:
OpenGL.error.GLError: GLError(
err = 1282,
description = b'invalid operation',
baseOperation = glBindFramebuffer,
cArguments = (GL_DRAW_FRAMEBUFFER, 0)
)
The text was updated successfully, but these errors were encountered: