py-lepton - Project Hosting on Google Code

Earlier this year Nov 04, 2009 issue 5 (_glColorPointer not found (Mac OS 10.5.4, MacBookPro, GeForc...) commented on by oresmus - > what version of OpenGL is claimed to be supported? OpenGL: Version: 1.5.10 Last Modified: 11/25/08 7:19 AM Get Info String: OpenGL 1.5.10.7.0 Location: /System/Library/Frameworks/OpenGL.framework Private: No > BTW: Where did you hear about mechazoid? Some combination of reading pyglet-users (IIRC someone pointed to your code as good pyglet example code), google search (perhaps for "texture splatting"), or google code search (for uses of various pyglet functions). > what version of OpenGL is claimed to be supported? OpenGL: Version: 1.5.10 Last Modified: 11/25/08 7:19 AM Get Info String: OpenGL 1.5.10.7.0 Location: /System/Library/Frameworks/OpenGL.framework Private: No > BTW: Where did you hear about mechazoid? Some combination of reading pyglet-users (IIRC someone pointed to your code as good pyglet example code), google search (perhaps for "texture splatting"), or google code search (for uses of various pyglet functions). Nov 04, 2009 issue 4 (copy&paste error in lepton/emittermodule.c (?)) changed by casey.duncan - Good catch, I'll add a unit test and apply your patch for the next beta. Thanks! Status: Started Owner: casey.duncan Labels: Priority-High −Priority-Medium Good catch, I'll add a unit test and apply your patch for the next beta. Thanks! Status: Started Owner: casey.duncan Labels: Priority-High −Priority-Medium Nov 04, 2009 issue 5 (_glColorPointer not found (Mac OS 10.5.4, MacBookPro, GeForc...) commented on by casey.duncan - This seems to imply that the installed driver does not support OpenGL 1.1, which seems very odd. I only have a MacBook with an ATI and one with a GeForce 9400M to test and I don't have this issue. If you go into the system profiler, under Software > Frameworks, what version of OpenGL is claimed to be supported? The software basically assumes 1.4 or better, though the billboard renderer should work with 1.1 or better. BTW: Where did you hear about mechazoid? It's basically an aborted project, but there might be some nuggets in there worth stealing 8^) This seems to imply that the installed driver does not support OpenGL 1.1, which seems very odd. I only have a MacBook with an ATI and one with a GeForce 9400M to test and I don't have this issue. If you go into the system profiler, under Software > Frameworks, what version of OpenGL is claimed to be supported? The software basically assumes 1.4 or better, though the billboard renderer should work with 1.1 or better. BTW: Where did you hear about mechazoid? It's basically an aborted project, but there might be some nuggets in there worth stealing 8^) Nov 02, 2009 issue 5 (_glColorPointer not found (Mac OS 10.5.4, MacBookPro, GeForc...) reported by oresmus - What steps will reproduce the problem? 1. Download and install lepton-1.0b2.tar.gz into python 2.6.2 (build log available in attached file; build appeared to be successful but I ran no other tests) 2. svn update caseman-read-only, cd mech, python run_game.py 3. I got this traceback: Traceback (most recent call last): File "run_game.py", line 10, in <module> from mechazoid import main File "/Applications/pyglet/web-examples/caseman-read-only/mech/mechazoid/main.py", line 1, in <module> import game File "/Applications/pyglet/web-examples/caseman-read-only/mech/mechazoid/game.py", line 4, in <module> import building File "/Applications/pyglet/web-examples/caseman-read-only/mech/mechazoid/building.py", line 3, in <module> import lepton.renderer ImportError: dlopen(/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/lepton/renderer.so, 2): Symbol not found: _glColorPointer Referenced from: /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/lepton/renderer.so Expected in: dynamic lookup Exit 1 What version of the product are you using? On what operating system? lepton-1.0b2 Mac OS 10.5.4 MacBookPro (Intel Core Duo) GeForce 8600M GT python 2.6.2 What steps will reproduce the problem? 1. Download and install lepton-1.0b2.tar.gz into python 2.6.2 (build log available in attached file; build appeared to be successful but I ran no other tests) 2. svn update caseman-read-only, cd mech, python run_game.py 3. I got this traceback: Traceback (most recent call last): File "run_game.py", line 10, in <module> from mechazoid import main File "/Applications/pyglet/web-examples/caseman-read-only/mech/mechazoid/main.py", line 1, in <module> import game File "/Applications/pyglet/web-examples/caseman-read-only/mech/mechazoid/game.py", line 4, in <module> import building File "/Applications/pyglet/web-examples/caseman-read-only/mech/mechazoid/building.py", line 3, in <module> import lepton.renderer ImportError: dlopen(/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/lepton/renderer.so, 2): Symbol not found: _glColorPointer Referenced from: /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/lepton/renderer.so Expected in: dynamic lookup Exit 1 What version of the product are you using? On what operating system? lepton-1.0b2 Mac OS 10.5.4 MacBookPro (Intel Core Duo) GeForce 8600M GT python 2.6.2 Oct 07, 2009 issue 4 (copy&paste error in lepton/emittermodule.c (?)) reported by eruquen - What steps will reproduce the problem? cat lepton/emittermodule.c \| grep -C 1 '"deviation"' What is the expected output? What do you see instead? expected: [...] return (PyObject )ParticleRefObject_New(NULL, &self->ptemplate); } else if (!strcmp(name, "deviation")) { return (PyObject )ParticleRefObject_New(NULL, &self->pdeviation); -- return (PyObject )ParticleRefObject_New(NULL, &self->ptemplate); } else if (!strcmp(name, "deviation")) { return (PyObject )ParticleRefObject_New(NULL, &self->pdeviation); instead: [...] return (PyObject )ParticleRefObject_New(NULL, &self->ptemplate); } else if (!strcmp(name, "deviation")) { return (PyObject )ParticleRefObject_New(NULL, &self->ptemplate); -- return (PyObject )ParticleRefObject_New(NULL, &self->ptemplate); } else if (!strcmp(name, "deviation")) { return (PyObject )ParticleRefObject_New(NULL, &self->ptemplate); What version of the product are you using? On what operating system? latest svn checkout (rev 242) Please provide any additional information below. patch attached to this report I hope I'm not fixing a non-bug here :D What steps will reproduce the problem? cat lepton/emittermodule.c \| grep -C 1 '"deviation"' What is the expected output? What do you see instead? expected: [...] return (PyObject )ParticleRefObject_New(NULL, &self->ptemplate); } else if (!strcmp(name, "deviation")) { return (PyObject )ParticleRefObject_New(NULL, &self->pdeviation); -- return (PyObject )ParticleRefObject_New(NULL, &self->ptemplate); } else if (!strcmp(name, "deviation")) { return (PyObject )ParticleRefObject_New(NULL, &self->pdeviation); instead: [...] return (PyObject )ParticleRefObject_New(NULL, &self->ptemplate); } else if (!strcmp(name, "deviation")) { return (PyObject )ParticleRefObject_New(NULL, &self->ptemplate); -- return (PyObject )ParticleRefObject_New(NULL, &self->ptemplate); } else if (!strcmp(name, "deviation")) { return (PyObject )ParticleRefObject_New(NULL, &self->ptemplate); What version of the product are you using? On what operating system? latest svn checkout (rev 242) Please provide any additional information below. patch attached to this report I hope I'm not fixing a non-bug here :D Sep 01, 2009 Texturizer (Lepton texturizer objects) Wiki page edited by casey.duncan - Revision r242 Clarify and fix code error for create_point_texture() Revision r242 Clarify and fix code error for create_point_texture() Sep 01, 2009 Texturizer (Lepton texturizer objects) Wiki page edited by casey.duncan - Revision r241 Document create_point_texture() Revision r241 Document create_point_texture() Aug 31, 2009 Texturizer (Lepton texturizer objects) Wiki page edited by casey.duncan - Revision r239 Add links to examples Revision r239 Add links to examples Aug 31, 2009 r238 (Fix docstring typoo ) committed by casey.duncan - Fix docstring typoo Fix docstring typoo Aug 31, 2009 Texturizer (Lepton texturizer objects) Wiki page edited by casey.duncan - Revision r237 fix typoos, layout, long lines Revision r237 fix typoos, layout, long lines Aug 31, 2009 r236 (Fix texturizer docstring lies ) committed by casey.duncan - Fix texturizer docstring lies Fix texturizer docstring lies Aug 31, 2009 4 Wiki pages changed by casey.duncan - Revision r235 Add texturizer docs Added Texturizer Edited Overview, ParticleRenderer">ParticleRenderer, TableOfContents">TableOfContents Revision r235 Add texturizer docs Added Texturizer Edited Overview, ParticleRenderer">ParticleRenderer, TableOfContents">TableOfContents Aug 19, 2009 issue 3 (successful built on Debian, GL error on eee pc) commented on by chemis...@gmx.de - Hi Casey, thanks a lot for your quick answer and your help. Here is the output of gdb: $ gdb python GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i486-linux-gnu"... (no debugging symbols found) (gdb) run -m examples.fire Starting program: /usr/bin/python -m examples.fire (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [New Thread 0xb7e768d0 (LWP 5413)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) ---Type <return> to continue, or q <return> to quit--- (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) do_wait: drmWaitVBlank returned -1, IRQs don't seem to be working correctly. Try adjusting the vblank_mode configuration parameter. Traceback (most recent call last): File "/usr/lib/python2.5/runpy.py", line 95, in run_module filename, loader, alter_sys) File "/usr/lib/python2.5/runpy.py", line 52, in _run_module_code mod_name, mod_fname, mod_loader) File "/usr/lib/python2.5/runpy.py", line 32, in _run_code exec code in run_globals File "/media/SD/progs/lepton/examples/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 "/media/SD/progs/lepton/examples/fire.py", line 74, in on_draw default_system.draw() File "/home/apl/progs/lepton/lepton/system.py", line 94, in draw group.draw() RuntimeError: GL error 1280 Program exited with code 0377. (gdb) q Concerning the <GL> folder: I re-downloaded the tarball and indeed the folder is uppercase in it. I now remember that I downloaded the tarball the first time with a Windows computer and unpacked it with Total Commander to a fat32 usb stick. The error here definitely occurred on my side. Thanks again for your help. Axel Hi Casey, thanks a lot for your quick answer and your help. Here is the output of gdb: $ gdb python GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i486-linux-gnu"... (no debugging symbols found) (gdb) run -m examples.fire Starting program: /usr/bin/python -m examples.fire (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [New Thread 0xb7e768d0 (LWP 5413)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) ---Type <return> to continue, or q <return> to quit--- (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) do_wait: drmWaitVBlank returned -1, IRQs don't seem to be working correctly. Try adjusting the vblank_mode configuration parameter. Traceback (most recent call last): File "/usr/lib/python2.5/runpy.py", line 95, in run_module filename, loader, alter_sys) File "/usr/lib/python2.5/runpy.py", line 52, in _run_module_code mod_name, mod_fname, mod_loader) File "/usr/lib/python2.5/runpy.py", line 32, in _run_code exec code in run_globals File "/media/SD/progs/lepton/examples/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 "/media/SD/progs/lepton/examples/fire.py", line 74, in on_draw default_system.draw() File "/home/apl/progs/lepton/lepton/system.py", line 94, in draw group.draw() RuntimeError: GL error 1280 Program exited with code 0377. (gdb) q Concerning the <GL> folder: I re-downloaded the tarball and indeed the folder is uppercase in it. I now remember that I downloaded the tarball the first time with a Windows computer and unpacked it with Total Commander to a fat32 usb stick. The error here definitely occurred on my side. Thanks again for your help. Axel Aug 19, 2009 issue 3 (successful built on Debian, GL error on eee pc) changed by casey.duncan - Status: Accepted Owner: casey.duncan Status: Accepted Owner: casey.duncan Aug 19, 2009 issue 3 (successful built on Debian, GL error on eee pc) commented on by casey.duncan - That's strange about the directory name, when I unpack the tarball or zip file, glew/include/GL is there as expected. Can you tell me the exact sequence of commands you used to reproduce this? Any chance there was something funky about the filesystem you were using (i.e., samba, or other fs with different case rules)? As for the error, 1280 is an invalid enum error, which means the example is trying to use an OpenGL feature that is not supported on that hardware. Netbooks typically have very lightweight (literally and figuratively) graphics cards. I have a hunch that it does not support GL_POINT_SPRITE, which is used when texturing points. This feature requires OpenGL 1.5 which is probably not supported on your hardware. The flyby example does not use points. Ideally the point renderer would fall back to using textured quads when point sprites are not available. I will definitely consider doing that. To learn for sure if this is the problem you could use gdb to get a backtrace like so: % gdb python (gdb) run -m lepton.examples.fire (gdb) c ...Should see error here... (gdb) bt Then paste the backtrace here. I'm not sure what the origin of the drmWaitVBlank warning is, probably something emitted when pyglet initializes the OpenGL context. This probably means that vsync isn't functional, which might introduce flicker or tearing artifacts. But shouldn't otherwise hurt anything. Thanks for trying lepton, and thanks for the report! That's strange about the directory name, when I unpack the tarball or zip file, glew/include/GL is there as expected. Can you tell me the exact sequence of commands you used to reproduce this? Any chance there was something funky about the filesystem you were using (i.e., samba, or other fs with different case rules)? As for the error, 1280 is an invalid enum error, which means the example is trying to use an OpenGL feature that is not supported on that hardware. Netbooks typically have very lightweight (literally and figuratively) graphics cards. I have a hunch that it does not support GL_POINT_SPRITE, which is used when texturing points. This feature requires OpenGL 1.5 which is probably not supported on your hardware. The flyby example does not use points. Ideally the point renderer would fall back to using textured quads when point sprites are not available. I will definitely consider doing that. To learn for sure if this is the problem you could use gdb to get a backtrace like so: % gdb python (gdb) run -m lepton.examples.fire (gdb) c ...Should see error here... (gdb) bt Then paste the backtrace here. I'm not sure what the origin of the drmWaitVBlank warning is, probably something emitted when pyglet initializes the OpenGL context. This probably means that vsync isn't functional, which might introduce flicker or tearing artifacts. But shouldn't otherwise hurt anything. Thanks for trying lepton, and thanks for the report! Aug 19, 2009 issue 3 (successful built on Debian, GL error on eee pc) reported by chemis...@gmx.de - 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 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 Jul 24, 2009 lepton-1.0b2.win32-py2.6.exe (Lepton 1.0 beta 2 Windows Binary) file uploaded by casey.duncan - Labels: Featured Type-Installer OpSys-Windows Labels: Featured Type-Installer OpSys-Windows Jul 18, 2009 r234 (Now in beta ) committed by casey.duncan - Now in beta Now in beta Jul 18, 2009 r233 (- Fix setup.py to install image textures for examples - bump...) committed by casey.duncan - - Fix setup.py to install image textures for examples - bump version for 1.0b2 release and update change log - Fix setup.py to install image textures for examples - bump version for 1.0b2 release and update change log Jun 26, 2009 r232 (Make examples a subpackage of lepton so that they may be run...) committed by casey.duncan - Make examples a subpackage of lepton so that they may be run using python -m after install Make examples a subpackage of lepton so that they may be run using python -m after install Jun 26, 2009 r231 (Sync pkg wording with the google code site ) committed by casey.duncan - Sync pkg wording with the google code site Sync pkg wording with the google code site Jun 26, 2009 r230 (Add pkg dep info for debian/ubuntu ) committed by casey.duncan - Add pkg dep info for debian/ubuntu Add pkg dep info for debian/ubuntu Jun 26, 2009 lepton-1.0b1.tar.gz (Lepton 1.0 beta 1 release) file uploaded by casey.duncan - Labels: Featured Type-Source OpSys-All Labels: Featured Type-Source OpSys-All Jun 26, 2009 r229 (Bump version to 1.0b1 for release ) committed by casey.duncan - Bump version to 1.0b1 for release Bump version to 1.0b1 for release Jun 26, 2009 r228 (Slight timing adjustment to test ) committed by casey.duncan - Slight timing adjustment to test Slight timing adjustment to test Jun 26, 2009 r227 (Remove dead code ) committed by casey.duncan - Remove dead code Remove dead code Jun 04, 2009 Overview (Lepton -- Architecture Overview) Wiki page edited by ac1201 May 09, 2009 r225 (Try to fix test failure caused by different rounding on wind...) committed by casey.duncan - Try to fix test failure caused by different rounding on windows Try to fix test failure caused by different rounding on windows Apr 30, 2009 r224 (Fix bug in previous texturizer refactor ) committed by casey.duncan - Fix bug in previous texturizer refactor Fix bug in previous texturizer refactor Apr 29, 2009 r223 (- Substitute Py_ssize_t for int in an attempt to quell some ...) committed by casey.duncan - - Substitute Py_ssize_t for int in an attempt to quell some compiler warning on windows - Simplify inner loop code in texturizer - Substitute Py_ssize_t for int in an attempt to quell some compiler warning on windows - Simplify inner loop code in texturizer Apr 28, 2009 r222 (Define fminf for platforms that lack it ) committed by casey.duncan - Define fminf for platforms that lack it Define fminf for platforms that lack it Apr 28, 2009 r221 (Use distutils to #define GLEW_STATIC for every compiled file...) committed by casey.duncan - Use distutils to #define GLEW_STATIC for every compiled file Use distutils to #define GLEW_STATIC for every compiled file Apr 28, 2009 r220 (Fix docstring lies and minor code cleanup, no functional cha...) committed by casey.duncan - Fix docstring lies and minor code cleanup, no functional change Fix docstring lies and minor code cleanup, no functional change Apr 25, 2009 r219 (Run the fire example ahead to avoid odd colored startup ) committed by casey.duncan - Run the fire example ahead to avoid odd colored startup Run the fire example ahead to avoid odd colored startup Apr 25, 2009 r218 (Add GLEW to hopefully enable some post-GL 1.1 features on, e...) committed by casey.duncan - Add GLEW to hopefully enable some post-GL 1.1 features on, er... certain platforms cough windows cough Add GLEW to hopefully enable some post-GL 1.1 features on, er... certain platforms cough windows cough Apr 23, 2009 r217 (Update changelog, bump version for 0.10a release ) committed by casey.duncan - Update changelog, bump version for 0.10a release Update changelog, bump version for 0.10a release Apr 23, 2009 r216 (Add domain.generate() test example ) committed by casey.duncan - Add domain.generate() test example Add domain.generate() test example Apr 23, 2009 r215 (Add logo animation frames ) committed by casey.duncan - Add logo animation frames Add logo animation frames Apr 23, 2009 r214 (- Add class method to create flipbook texturizers from a seq...) committed by casey.duncan - - Add class method to create flipbook texturizers from a sequence of pyglet images - Add lepton logo example to show off flipbooks - Fix sprite texturizer class method to allow aspect adjust args - Add class method to create flipbook texturizers from a sequence of pyglet images - Add lepton logo example to show off flipbooks - Fix sprite texturizer class method to allow aspect adjust args Apr 21, 2009 r213 (ParticleGroup.new() now accepts keyword args to specify part...) committed by casey.duncan - ParticleGroup.new() now accepts keyword args to specify particle attributes ParticleGroup.new() now accepts keyword args to specify particle attributes Apr 21, 2009 r212 (Add to doc string ) committed by casey.duncan - Add to doc string Add to doc string Apr 21, 2009 r211 (Implement FlipBookTexturizer ) committed by casey.duncan - Implement FlipBookTexturizer Implement FlipBookTexturizer Apr 11, 2009 r210 (Fix import ) committed by casey.duncan - Fix import Fix import Apr 09, 2009 r209 (- Add aspect adjustment flags to sprite texturizer to match ...) committed by casey.duncan - - Add aspect adjustment flags to sprite texturizer to match aspect ratio of particle quad to texture coords automagically. - Add letters example to show off - Add aspect adjustment flags to sprite texturizer to match aspect ratio of particle quad to texture coords automagically. - Add letters example to show off Apr 08, 2009 r208 (- Fix dealloc crash-bug in sprite texturizer - Enable GC for...) committed by casey.duncan - - Fix dealloc crash-bug in sprite texturizer - Enable GC for texturizers since they have an instance dict - Other minor cleanup - Fix dealloc crash-bug in sprite texturizer - Enable GC for texturizers since they have an instance dict - Other minor cleanup Apr 07, 2009 r207 (From flame back to fire ) committed by casey.duncan - From flame back to fire From flame back to fire Apr 07, 2009 r206 (- Add texturizer support to PointRenderer using point sprite...) committed by casey.duncan - - Add texturizer support to PointRenderer using point sprites - Add create_point_texture() function for programmatically creating particle textures - Rework smoke and fire (now flame) to use point sprites - Refactor other examples to use points - Add texturizer support to PointRenderer using point sprites - Add create_point_texture() function for programmatically creating particle textures - Rework smoke and fire (now flame) to use point sprites - Refactor other examples to use points Apr 05, 2009 RoadMap (Features and changes that are planned for future versions) Wiki page edited by casey.duncan Apr 05, 2009 r204 (- Make sure texturizers clean up after themselves properly -...) committed by casey.duncan - - Make sure texturizers clean up after themselves properly - Use the texturizer object pointer as a random seed for weighted coordinate selection instead of the group, since a texturizer may in fact be used for multiple groups and the coords are cached. Otherwise the coord sequence will randomly change as the coords are regenerated with multiple groups - Make sure texturizers clean up after themselves properly - Use the texturizer object pointer as a random seed for weighted coordinate selection instead of the group, since a texturizer may in fact be used for multiple groups and the coords are cached. Otherwise the coord sequence will randomly change as the coords are regenerated with multiple groups Apr 04, 2009 r203 (- Implement SpriteTexturer - Rearchitect things a bit, the t...) committed by casey.duncan - - Implement SpriteTexturer - Rearchitect things a bit, the texturizers now have a more active role in managing the coord array, which should be useful for VBOs, also allows for more aggressive caching. - Texture coordinates are now cached - Implement SpriteTexturizerFromImages factory for convenience to create a multi-texture texturizer directly from pyglet images - Use SpriteTexturizer et al to simplify examples - Implement SpriteTexturer - Rearchitect things a bit, the texturizers now have a more active role in managing the coord array, which should be useful for VBOs, also allows for more aggressive caching. - Texture coordinates are now cached - Implement SpriteTexturizerFromImages factory for convenience to create a multi-texture texturizer directly from pyglet images - Use SpriteTexturizer et al to simplify examples

issue 3 (successful built on Debian, GL error on eee pc) commented on by chemis...@gmx.de - Hi Casey, thanks a lot for your quick answer and your help. Here is the output of gdb: $ gdb python GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i486-linux-gnu"... (no debugging symbols found) (gdb) run -m examples.fire Starting program: /usr/bin/python -m examples.fire (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [New Thread 0xb7e768d0 (LWP 5413)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) ---Type <return> to continue, or q <return> to quit--- (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) do_wait: drmWaitVBlank returned -1, IRQs don't seem to be working correctly. Try adjusting the vblank_mode configuration parameter. Traceback (most recent call last): File "/usr/lib/python2.5/runpy.py", line 95, in run_module filename, loader, alter_sys) File "/usr/lib/python2.5/runpy.py", line 52, in _run_module_code mod_name, mod_fname, mod_loader) File "/usr/lib/python2.5/runpy.py", line 32, in _run_code exec code in run_globals File "/media/SD/progs/lepton/examples/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 "/media/SD/progs/lepton/examples/fire.py", line 74, in on_draw default_system.draw() File "/home/apl/progs/lepton/lepton/system.py", line 94, in draw group.draw() RuntimeError: GL error 1280 Program exited with code 0377. (gdb) q Concerning the <GL> folder: I re-downloaded the tarball and indeed the folder is uppercase in it. I now remember that I downloaded the tarball the first time with a Windows computer and unpacked it with Total Commander to a fat32 usb stick. The error here definitely occurred on my side. Thanks again for your help. Axel

Hi Casey, thanks a lot for your quick answer and your help. Here is the output of gdb: $ gdb python GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i486-linux-gnu"... (no debugging symbols found) (gdb) run -m examples.fire Starting program: /usr/bin/python -m examples.fire (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [New Thread 0xb7e768d0 (LWP 5413)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) ---Type <return> to continue, or q <return> to quit--- (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) do_wait: drmWaitVBlank returned -1, IRQs don't seem to be working correctly. Try adjusting the vblank_mode configuration parameter. Traceback (most recent call last): File "/usr/lib/python2.5/runpy.py", line 95, in run_module filename, loader, alter_sys) File "/usr/lib/python2.5/runpy.py", line 52, in _run_module_code mod_name, mod_fname, mod_loader) File "/usr/lib/python2.5/runpy.py", line 32, in _run_code exec code in run_globals File "/media/SD/progs/lepton/examples/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 "/media/SD/progs/lepton/examples/fire.py", line 74, in on_draw default_system.draw() File "/home/apl/progs/lepton/lepton/system.py", line 94, in draw group.draw() RuntimeError: GL error 1280 Program exited with code 0377. (gdb) q Concerning the <GL> folder: I re-downloaded the tarball and indeed the folder is uppercase in it. I now remember that I downloaded the tarball the first time with a Windows computer and unpacked it with Total Commander to a fat32 usb stick. The error here definitely occurred on my side. Thanks again for your help. Axel

Earlier this year