-
Notifications
You must be signed in to change notification settings - Fork 37
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
Exception: bad color resource mapped #41
Comments
Huh, interesting. Thanks for reporting. I'll try to repro (I'll have access to an Ubuntu system later this week and cannot reproduce the issue on my Mac). The error message points to some issue with cuda/gl interop. You could try to deactivate direct rendering here as a workaround? (note that if you're using some sort of remote rendering and PBO-interop isn't available, the viewer currently doesn't detect that and then just fails.) |
So I haven't yet tried deactivating direct rendering, but I did just disable CUDA and it seemed to fix the issue. |
Yeah, that makes sense. The error message above is from the constructor of When I tried on Ubuntu yesterday, the viewer actually froze on startup (the other CUDA examples didn't), which is even stranger than what you're describing. Although I believe the issues are related. I unfortunately only have limited access to a PC with Linux atm, but I'm at it and will post here when the issue is fixed. |
@szellmann Thanks for the update! No rush on the patch, the rest of the library works just fine. |
I try running the viewer program, using the path tracing algorithm, and an exception is thrown:
I made a very simple model in Blender to reproduce this with.
simple model.zip
I'm using GCC 9 and Nvidia's compiler, on Ubuntu and in release mode.
The text was updated successfully, but these errors were encountered: