-
Notifications
You must be signed in to change notification settings - Fork 327
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
(Bug): check why OpenGL rendering is disabled in NatronRenderer #779
Comments
This was spotted while using |
I might be a little bit late but I think I've found the root cause of this. The following snippet is the culprit Lines 419 to 427 in e6fd459
Currently we have three settings for enabling OpenGL rendering, namely Natron/Engine/GPUContextPool.cpp Lines 102 to 109 in dbd7fb0
In case we are doing a background rendering the function is going to return a null OpenGL context pointer ( With what was mentioned above I've tried with making So to provide a fix for this I have two ideas in mind. One is to set |
Thank you for taking a closer look! What I understand is that Natron does what is expected, based on the enableOpenGLRendering setting:
If you set the setting to eEnableOpenGLEnabled in the GUI, is background rendering using OpenGL? |
When I set So the issue originates from my expectation to have OpenGL enabled when I run |
I think we should replace this PR by:
Hardware-accelerated OpenGL rendering is disabled by default when running in background because different hardware may render differently, and the hardware may not implement floating-point rendering, thus the output quality may be degraded. For these reasons, users should be extra careful when enabling OpenGL rendering for high-quality renders, and this shouldn't be the default. |
The command-line option (for the message) is |
Noticed, will open another PR.
I think that a flag alias |
Feel free to make that change too |
@YakoYakoYokuYoku reported here that OpenGL rendering seems to be disabled when using NatronRenderer, even when a display is available and detected.
I'd like to get an answer to this before testing and merging #765
(looking for a volunteer to work on this)
The text was updated successfully, but these errors were encountered: