Robo and pyggel/OpenGL errors after fresh install

[Michael Clark]

Greetings. Thanks to all of you in advance for all of your hard work.
I'm working on a new 3d Game, and i am pretty good at python, so i
want to dev it in Py... ok here we go:

ActivePython 2.6.1.1 (ActiveState Software Inc.) based on
Python 2.6.1 (r261:67515, Dec 5 2008, 13:58:38) [MSC v.1500 32 bit
(Intel)] on win32

PyOpenGL-3.0.1a3
pyggel-0.08-alpha4b.linux-i686.exe

errors are:
Robo:

C:\Users\llama\Desktop\Python Research\pyggel\Robocalypto>python
run_game.py
Traceback (most recent call last):
File "run_game.py", line 10, in <module>
main.main()
File "C:\Users\llama\Desktop\Python Research\pyggel\Robocalypto
\gamelib\main.py", line 14, in main
g = game.Game()
File "C:\Users\llama\Desktop\Python Research\pyggel\Robocalypto
\gamelib\game.py", line 117, in __init__
self.player = Player(self)
File "C:\Users\llama\Desktop\Python Research\pyggel\Robocalypto
\gamelib\objects.py", line 77, in __init__
self.gun = Gun(self.game, self)
File "C:\Users\llama\Desktop\Python Research\pyggel\Robocalypto
\gamelib\objects.py", line 142, in __init__
GameObject.__init__(self, game, obj=pyggel.mesh.OBJ("data/
gun.obj", colorize=[0.2, 0.2, 0.2, 1]),
File "C:\Python26\Lib\site-packages\pyggel\mesh.py", line 42, in OBJ
objs[-1].material = mtls[values[1]]
IndexError: list index out of range

I don't get it.....

And SOME of the pyggel/OpenGL tests cause:

C:\Users\llama\Desktop\Python Research\pyggel>python test_core.py
Traceback (most recent call last):
File "test_core.py", line 162, in <module>
main()
File "test_core.py", line 8, in main
pyggel.view.set_debug(False)
File "C:\Users\llama\Desktop\Python Research\pyggel\pyggel\view.py",
line 259, in set_debug
oglError.ErrorChecker.registerChecker(lambda:None)
AttributeError: '_ErrorChecker' object has no attribute
'registerChecker'

Now THIS, i understand, it's an OpenGL issue, but dont' know why it is
an issue...
I try this:

from OpenGL import error
error.ErrorChecker.registerChecker( myAlternateFunction )

and i get:
C:\Users\llama\Desktop\Python Research\pyggel>python
ActivePython 2.6.1.1 (ActiveState Software Inc.) based on
Python 2.6.1 (r261:67515, Dec 5 2008, 13:58:38) [MSC v.1500 32 bit
(Intel)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> from OpenGL import error
>>> error.ErrorChecker.registerChecker( myAlternateFunction )
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
AttributeError: '_ErrorChecker' object has no attribute
'registerChecker'
>>>


So my pyOpenGL doesn't seem to have this "registerChecker" so .....
help?... Please?
This needs to work :)

[RB[0]]

Yes, these are some known errors from the release of PYGGEL - they have both been fixed in SVN.
We've been holding off releasing a bugfix release until we get some memleak issues resolved, but hopefully soon I can get it released :)

Until then perhaps you can try the SVN and see if it works?

[Michael Clark]

Greetings again!
Thanks for your help.

I used
svn checkout http://pyggel.googlecode.com/svn/trunk/ pyggel-read-only
and then overwrote the pyggel folder in site-packages with the new
one. It definitely doesn't error in the same place, so yea! :)

However, not so good on the run part:

c:\temp\Robocalypto>python run_game.py

Traceback (most recent call last):
File "run_game.py", line 10, in <module>
main.main()

File "C:\temp\pyggel-read-only\Robocalypto\gamelib\main.py", line
15, in main
g.run()
File "C:\temp\pyggel-read-only\Robocalypto\gamelib\game.py", line
249, in run
self.main_loop()
File "C:\temp\pyggel-read-only\Robocalypto\gamelib\game.py", line
244, in main_loop
self.do_draw()
File "C:\temp\pyggel-read-only\Robocalypto\gamelib\game.py", line
234, in do_draw
self.scene.render(self.camera)
File "C:\Python26\lib\site-packages\pyggel\scene.py", line 115, in
render
mpx, mpy = pick_pos
TypeError: 'LookFromCamera' object is not iterable

c:\temp\Robocalypto>

and here are a few of the other errors i get now:
c:\temp\pyggel-read-only>python test_camera.py

Traceback (most recent call last):

File "test_camera.py", line 141, in <module>
main()
File "test_camera.py", line 138, in main
mscene.render()
File "C:\temp\pyggel-read-only\pyggel\scene.py", line 148, in render
i.render(camera)
File "C:\temp\pyggel-read-only\pyggel\particle.py", line 85, in
render
i.render(camera)
File "C:\temp\pyggel-read-only\pyggel\particle.py", line 43, in
render
self.image.render(camera)
File "C:\temp\pyggel-read-only\pyggel\image.py", line 168, in render
self.display_list.render()
AttributeError: 'NoneType' object has no attribute 'render'

c:\temp\pyggel-read-only>python test_core.py

Traceback (most recent call last):

File "test_core.py", line 163, in <module>
main()
File "test_core.py", line 20, in main
img2sub = img2.sub_image((0,0), (15, 15))
AttributeError: 'Image' object has no attribute 'sub_image'

c:\temp\pyggel-read-only>python test_gui.py

Traceback (most recent call last):

File "test_gui.py", line 87, in <module>
main()
File "test_gui.py", line 34, in main
font_underline=True)
File "C:\temp\pyggel-read-only\pyggel\gui.py", line 1017, in
__init__
self.ireg.compile()
File "C:\temp\pyggel-read-only\pyggel\font.py", line 114, in compile
i.render()
File "C:\temp\pyggel-read-only\pyggel\image.py", line 78, in render
if not self.test_on_screen():
AttributeError: 'Image' object has no attribute 'test_on_screen'

c:\temp\pyggel-read-only>python test_mesh.py

this one actually worked! :)

I am willing to help, just not sure where to start.....

oh oh
i wondered, it doesn't error while running anymore, but what was the
fix for:

from OpenGL import error
error.ErrorChecker.registerChecker( myAlternateFunction )

because it still errors for me when i run these lines, just wanted to
make sure i get the error checking before i jump in and screw it up
ehehheh


once again, thanks for any time y'all put in my direction, i sincerely
appreciate it. If i am not reading enough and asking questions too
quickly, i would be happy to read more, just not sure what to read :\

[M]

[RB[0]]

OpenGL changed it's method of overwriting the error checking, which we now use - those lines worked in older versions of PyOpenGL but won't now.

You're current errors are my fault, actually - we are write in the middle of a large code-cleanup to try and get rid of some mem leaks and such, so some examples are still using outdated code - I will get right to work removing that :)

Thanks for the error reports!

[Michael Clark]

Wow.
I'm as sorry as possible for pouring salt on your wounds. I am eager
to help if i can. I will certainly at least test when you are ready.

Thanks again for your diligence.

[M]

[RB[0]]

Pouring salt on my wounds? LOL - not a problem, isn't like that in the least :)

[Ian Mallett]

Pour bilge-water on your wounds = worse.

[RB[0]]

Ugg - well, I just cleaned up some spam on the forums, but otherwise
haven't gotten anything done with PYGGEL.
Mainly due to two things, lack of motivation, and pondering of how to
proceed.

At the moment I was rewriting a huge chunk of core features (mainly
textures and images) - but in so doing have messed up a bunch of other
things that need to be fixed now.
Just working on this will take a few weeks or a month probably, before
I even got to these bugs you pointed out, and a release to fix them.
On the other hand, if I revert back to before *these* changes and just
proceed again from there, I'll give up quite a bit of work... :S

Any thoughts?

[Robert Ramsay]

My vote is to continue rewriting the core features. And in the meantime I can work on fixing the latest tag (possibly in a branch if it requires a lot of work). But the main goal here, is to keep you motivated! So do whatever interests you the most. To make it easier for me create a bug list in Google Code and attach them to me, or just send me a list of the bugs in the current tag. I'll do the look up in the trunk for the fixes. I have plenty of time on my hands. So I'll be happy to help.

Robert (durandal/FatalFred)

[RB[0]]

That sounds like a good idea - perhaps make a different branch for bug-fixes to teh last release, and continue with this one (since it should *eventually* fix the bugs anyways, just a long ways off)

We'll see though, if you would like to implement the bugfixes exposed in the last release I would be happy to set up a trunk and help out.. :)