pyglet VS moderngl

After some testing, I saw that Pyglet could detect and get values from my controller with this script from the Pyglet Github: https://github.com/pyglet/pyglet/blob/master/examples/input/controller.py

https://pyglet.org/ maybe?

Learn to be proficient in pyglet or pyglet.

Years ago I had some success with pyglet. It seems to still be actively developed! I haven't seen anything about swf files though.

Bottom of the page: https://pyglet.org/

I see to be finding a lot of (old) links saying they have issues with H264 videos from ffmpeg. similar to this: https://github.com/pyglet/pyglet/issues/279 Although most of them seem to stem back to RPi3 or even RPi2.

Pyglet

You can see how to do it here: https://github.com/moderngl/moderngl/blob/master/examples/fragment_output.py

making an executable is an absolute pain but PySide6, DearPyGui, moderngl and much more exists

Whenever I try to run examples/loading_obj_files.py from moderngl/moderngl: Modern OpenGL binding for python (github.com) , I get this error:

Not sure what rgl supports, but there's https://github.com/moderngl/moderngl - provides Pythonic wrapper around OpenGL functions.

I'm guessing minimal overhead. The README says that it is a "simplification of a subset of ModernGL with some extras that were not possible to include in ModernGL." The documentation for ModernGL (lazy-link) talks about speed only in comparison with PyOpenGL, and says that it's faster since C++ calls are "bundled together," which I assume means that ModernGL (compared to PyOpenGL) does a little more than just wrapping - for good and bad.

I would not use Pyglet, I would use ModernOpenGL. https://github.com/moderngl/moderngl It's still OpenGL but with a more pythonic interface and way less useless boilerplate. Plus you get access to modern features by default (in fact, are required, and btw modern = more than a decade old), and I believe pyglet still relies on old immediate mode opengl.

As you can see, the new version is dramatically lower than the previous one, but it is consistent with the package's tags. The downside is that this won't trigger your AUR helper to update the package, so you'll have to do it manually. You may also want to just reinstall manim as a whole to account for the new dependency version.

I am currently trying to use a compute shader to compute 2D projection of 3D points (to create a little 3D renderer in python). I am using the moderngl library, and this is my code. So my compute shader is using 2 buffers: 1 for input and 1 for output. The input is composed of 3 vec3 (to represent the 3 3D points for a triangle), and the output will be 3 2D points. The code I showed you here is for testing, which just takes the input values and put them in the output buffer. Here is my problem: