rdb
Note the CI failures: ``` /home/runner/work/panda3d/panda3d/panda/src/movies/flacAudioCursor.cxx:68:13: error: no matching function for call to 'drflac_open' _drflac = drflac_open(&cb_read_proc, &cb_seek_proc, (void *)stream, NULL); ^~~~~~~~~~~ /home/runner/work/panda3d/panda3d/panda/src/movies/dr_flac.h:8944:20: note: candidate function not viable: no known...
Hi @pap-stavros, are you still planning to fix the build errors or should this be passed to someone else?
The problem is that ShowBase writes variables to the global scope, which are then used in various places in direct. For example, when you create a GUI item, the parent...
That depends on which features of Panda you need. This is a sample program that shows the minimal set of code needed to get a scene graph rendered without use...
You should pass in a host window to makeOutput or you will get separate graphics contexts.
Let's keep this open; I would at the very least consider it a bug that Panda is not displaying an appropriate error message.
As for why it's still an issue even though you're loading it twice: Panda caches the shaders, so you get the same shader object the second time you load it.
Normally, Panda should do that automatically - that's why this should be investigated as a bug. The Shader object could be the same but the underlying ShaderContext object should be...
This was a bug in Panda, sharing shaders was supposed to work. Fixed on master branch.
Thanks for the patch! I've applied it.