Dear Casey,
having read about lepton in the Python Magazine I was very eager to try it
out myself.
At first the compilation did not run on my Debian Testing box, I always got
the error that glew.h could not be found until I realized that I had to
rename the folder <gl> provided under <glew> in the installation tarball
into <GL>, then it worked. I successfully built lepton on my terra notebook
(nvidia graphics) and on an eee pc 901. On the notebook all examples run
fine and I am completely enthusiastic about the spectacular effects. You
have really created a great and very entertaining tool, thanks a lot. I
can't wait to show it to my kids. On the eee pc however, so far only the
flyby example runs (very smoothly). When I run other examples, I get the
following traceback:
Traceback (most recent call last):
File "./fire.py", line 78, in <module>
pyglet.app.run()
File "/usr/lib/pymodules/python2.5/pyglet/app/__init__.py", line 264, in run
EventLoop().run()
File "/usr/lib/pymodules/python2.5/pyglet/app/xlib.py", line 94, in run
sleep_time = self.idle()
File "/usr/lib/pymodules/python2.5/pyglet/app/__init__.py", line 193, in idle
window.dispatch_event('on_draw')
File "/usr/lib/pymodules/python2.5/pyglet/window/__init__.py", line 1217,
in dispatch_event
EventDispatcher.dispatch_event(self, *args)
File "/usr/lib/pymodules/python2.5/pyglet/event.py", line 340, in
dispatch_event
if handler(*args):
File "./fire.py", line 74, in on_draw
default_system.draw()
File "/home/user/progs/lepton/lepton/system.py", line 94, in draw
group.draw()
RuntimeError: GL error 1280
Do you have any idea, what the cause for this could be ? Also, when I start
the examples I always get this warning:
do_wait: drmWaitVBlank returned -1, IRQs don't seem to be working correctly.
Try adjusting the vblank_mode configuration parameter.
But this does not seem to influence the execution of the scripts, since it
also occurs in the working flyby example.
Many thanks again and maybe you have an idea how I could circumvent the GL
error.
Kind regards,
Axel
Original issue reported on code.google.com by
chemis...@gmx.deon 19 Aug 2009 at 3:47