-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
Nothing happens when manimgl is run! #1391
Comments
You need to pass some flag(s) for it to work. |
same issue here ! OS System: Ubuntu 20.04.1 (5.8.0.43-generic) I have tried the following command line:
the terminal will wait command return after hit enter, and htop showing CPU single thread almost 100 % usage. |
Arguments and flags make no difference, the script should show some error or the help menu when nothing is specified. Works as expected with the ManimCommunity fork. See @gnap114039's comment above. I can see similar CPU usage too. I'm surprised there are no more reports of this issue, I had the same issue on the master branch even before 1.0.0 was merged/released. |
Got the same problem, manimgl installed using OS: Ubuntu 20.0.1 |
Quick answer, try running the command below in same virtual environment. python -m pip install manimpango --force --no-binary :all: see if that fixes. Could be related to #1387 |
Have the same problem, was wondering if it has somethinig to do with OpenGL verson and GPU driver. |
Same issue |
I'm not sure about this |
I switched to "Manim Community" repo and it worked like a charm, guess thats the one thatI |
Downgrade moderngl to 5.5.* |
@MLee-Sci Can you make an issue in moderngl repo if this fixes? |
Do not downgrade moderngl. This can cause more issues. Downgrading to 5.5.x is not really advicable because it will use statically linked libGL. If it doesn't work with latest moderngl or glcontext it would be nice to figure out why. 😄 |
EDIT : This is a manimpango issue Please follow instructions here : #1391 (comment) |
This solves the problem, closing this issue. |
The issue itself it not really fixed. It's a band-aid to some other unknown issue. The |
We get stuck here when pyglet calls
|
Again, is manimpango the problem? Could you try commenting it out? |
@naveen521kk .. so we might have an xy problem here. |
@einarf Now try, compiling it from source? |
Yep. This solves the problem. I'm guessing this is relateed to other segfault issues, but here there was memory currption causing a random issue. The random issue was pyglet hanging on |
The real solution is to compile manimpango from source. Do not downgrade moderngl 😄 moderngl should be squeeky clean and doesn't really do much on initial import. The action mainly happens on context creation. On import it mainly registers types. I'm guessing a downgrade only changes the memory profile slighty so this random corruption doesn't cause any issues. |
I have asked them to do so long back see #1391 (comment) I had to have the wheels for Linux simply for readthedocs builds on documentation, which will break if there are no wheels, I have asked users to not install wheels on Linux, but nobody sees to read or it is so hidden... Meanwhile, let me try if static linking helps here. Again, I would need someone to test or I would simply consider it as fixed :) |
@naveen521kk Poke me any time for testing I should have followed your advice about compiling it, but I got cought up in the debugger 😄 |
I plan to remove those wheels in the next release see ManimCommunity/ManimPango#27 |
My solution: Then, install the newest |
Thanks EVERYBODY!!!!!!!! I ! use ! your ! methods ! and ! SUCCEED!!!!! OHHHHHH!!!!!!!! PERFECT !!!!!!!!! |
Describe the error
No output on the console or no GUI shows up when
manimgl
is run from the command line (installed bypip install manimgl
). I observe the same issue when running from this repository and installing usingpip install -e .
as well.Code and Error
Environment
OS System: Ubuntu 20.04.1 (5.8.0.38-generic)
OpenGL version: 4.6.0 NVIDIA 450.102.04
manim version: 1.0.0 (
pip install manimgl
)python version: Tried both 3.6 and 3.8
The text was updated successfully, but these errors were encountered: