OK, new debs are up. They have the nvidia-cg-toolkit dependency fixed, and the p3d tools included.
They also accidentally include a fix for shadow samplers in shaders. This was a bug introduced by CMU students; I had checked in a fix before, but I forgot to pick up that fix for 1.7.1. So it’ll be properly in 1.7.2.
Was it this bug (advanced one) ?
:display:gsg:glgsg(error): GL texture creation failed for : invalid operation
:display:gsg:glgsg(error): Could not load
And this one is still crashing hard (tested on windows) :
MESA developers suggested a patch and it got rid of the SEGFAULT. Unfortunately, even with the patch the 1.7.1 Roaming-Ralph gives a black window with lots of X11 errors in the console.
My gut feeling is something broke in 1.7.1.
I am reverting back to 1.7.0. I will try to dig in more if I find time.
my game game won’t run anymore on v.1.7.1, it seems the problem is the dot operation, so, I made a test file trying to isolate the problem.
this is the test script I used:
from pandac.PandaModules import *
import direct.directbase.DirectStart
from direct.showbase.DirectObject import DirectObject
class test(DirectObject):
def __init__(self):
cp1 = VBase3(1,1,1)
cp2 = VBase3(1,1,1)
print cp1.dot(cp2)
w=test()
run()
running it by typing python main.py it prints 3.0 on console and opens the panda3d window, that’s ok.
I used packp3d to pack the application and things go wrong when running the packaged application. The application exits with errors. The key error messages are:
[cut]
print cp1.dot(cp2)
TypeError: ‘libpanda.VBase3’ object is not callable
[cut]
OK, I know what’s going on with the vector mess. It was a treacherous NDEBUG ifdef in the getattr method.
I’ll update the runtime.panda3d.org packages tomorrow. As it only occurs during the runtime, it’s not worth making a 1.7.2 right away for, but it’s important enough to have it fixed really soon.
I haven’t debugged the pdeploy issue with makensis yet, but it’s high on my priority list too, and I will get that fixed really soon, or at least implement the hacky workaround that I know will work.
drwr: do you have any thoughts on the glXMakeCurrent issue? Looking at the spec, it seems to me that we’re misusing it anyway when we’re releasing the context. I could be entirely wrong, though.
I think your proposed fix, to pass None as the Window parameter, is the right thing to do. Is there a different problem that you see in addition to this?
Your link is dead, but I think that your problem is the same as the one I’ve been hearing about from various people.
I found out I made a mistake in the way I built the 1.0.3 runtime, so I rebuilt it only a couple of hours ago and updated the download page with the updated 1.0.3 builds.
But I’m not sure if that actually fixed the problem.
Actually, I don’t think that that is the problem. I think that _context is not supposed to be NULL at that point, it is supposed to already have been initialised by glxgsg::choose_pixel_format. So something in choose_pixel_format is going wrong, or it is not being called at all for some weird reason.
Unfortunately, everything works fine on my computer, so I cannot debug it here.
I tried that on a Mac. SPACE and then ENTER works, but I get this on the console:
DirectStart: Starting the game.
Known pipe types:
osxGraphicsPipe
(all display modules loaded.)
1
:display:gsg:glgsg(error): at 4011 of panda/src/glstuff/glGraphicsStateGuardian_src.cxx : invalid operation
:display:gsg:glgsg(error): at 2907 of panda/src/glstuff/glGraphicsStateGuardian_src.cxx : invalid operation
:display:gsg:glgsg(error): at 2907 of panda/src/glstuff/glGraphicsStateGuardian_src.cxx : invalid operation
:display:gsg:glgsg(error): at 2907 of panda/src/glstuff/glGraphicsStateGuardian_src.cxx : invalid operation
:display:gsg:glgsg(error): at 2780 of panda/src/glstuff/glGraphicsStateGuardian_src.cxx : invalid operation
:display:gsg:glgsg(error): at 2907 of panda/src/glstuff/glGraphicsStateGuardian_src.cxx : invalid operation
:display:gsg:glgsg(error): at 4011 of panda/src/glstuff/glGraphicsStateGuardian_src.cxx : invalid operation
:display:gsg:glgsg(error): at 2907 of panda/src/glstuff/glGraphicsStateGuardian_src.cxx : invalid operation
:display:gsg:glgsg(error): at 2907 of panda/src/glstuff/glGraphicsStateGuardian_src.cxx : invalid operation
:display:gsg:glgsg(error): at 2907 of panda/src/glstuff/glGraphicsStateGuardian_src.cxx : invalid operation
:display:gsg:glgsg(error): at 2780 of panda/src/glstuff/glGraphicsStateGuardian_src.cxx : invalid operation
:display:gsg:glgsg(error): at 2907 of panda/src/glstuff/glGraphicsStateGuardian_src.cxx : invalid operation
:display:gsg:glgsg(error): at 4011 of panda/src/glstuff/glGraphicsStateGuardian_src.cxx : invalid operation
:display:gsg:glgsg(error): at 2907 of panda/src/glstuff/glGraphicsStateGuardian_src.cxx : invalid operation
:display:gsg:glgsg(error): at 2907 of panda/src/glstuff/glGraphicsStateGuardian_src.cxx : invalid operation
:display:gsg:glgsg(error): at 2907 of panda/src/glstuff/glGraphicsStateGuardian_src.cxx : invalid operation
:display:gsg:glgsg(error): at 2780 of panda/src/glstuff/glGraphicsStateGuardian_src.cxx : invalid operation
:display:gsg:glgsg(error): at 2907 of panda/src/glstuff/glGraphicsStateGuardian_src.cxx : invalid operation
:display:gsg:glgsg(error): at 4011 of panda/src/glstuff/glGraphicsStateGuardian_src.cxx : invalid operation
:display:gsg:glgsg(error): at 2907 of panda/src/glstuff/glGraphicsStateGuardian_src.cxx : invalid operation
:display(error): Deactivating osxGraphicsStateGuardian.
When I do ENTER x-times and then SPACE once it works, SPACE a second time and it crashes with:
9
Traceback (most recent call last):
File "dstroot/pythoncode/Developer/Panda3D/lib/direct/showbase/EventManager.py", line 61, in eventLoopTask
File "dstroot/pythoncode/Developer/Panda3D/lib/direct/showbase/EventManager.py", line 55, in doEvents
File "dstroot/pythoncode/Developer/Panda3D/lib/direct/showbase/EventManager.py", line 124, in processEvent
File "dstroot/pythoncode/Developer/Panda3D/lib/direct/showbase/Messenger.py", line 388, in send
File "dstroot/pythoncode/Developer/Panda3D/lib/direct/showbase/Messenger.py", line 473, in __dispatch
File "/Applications/Panda3D_Mare_Ceti/ynjh_no_bug.py", line 39, in destroy
self.buffer.clearRenderTextures()
AttributeError: 'NoneType' object has no attribute 'clearRenderTextures'
:task(error): Exception occurred in PythonTask eventManager
Traceback (most recent call last):
File "/Applications/Panda3D_Mare_Ceti/ynjh_no_bug.py", line 68, in <module>
run()
File "dstroot/pythoncode/Developer/Panda3D/lib/direct/showbase/ShowBase.py", line 2630, in run
File "dstroot/pythoncode/Developer/Panda3D/lib/direct/task/Task.py", line 502, in run
File "dstroot/pythoncode/Developer/Panda3D/lib/direct/task/Task.py", line 460, in step
File "dstroot/pythoncode/Developer/Panda3D/lib/direct/showbase/EventManager.py", line 61, in eventLoopTask
File "dstroot/pythoncode/Developer/Panda3D/lib/direct/showbase/EventManager.py", line 55, in doEvents
File "dstroot/pythoncode/Developer/Panda3D/lib/direct/showbase/EventManager.py", line 124, in processEvent
File "dstroot/pythoncode/Developer/Panda3D/lib/direct/showbase/Messenger.py", line 388, in send
File "dstroot/pythoncode/Developer/Panda3D/lib/direct/showbase/Messenger.py", line 473, in __dispatch
File "/Applications/Panda3D_Mare_Ceti/ynjh_no_bug.py", line 39, in destroy
self.buffer.clearRenderTextures()
AttributeError: 'NoneType' object has no attribute 'clearRenderTextures'