On Nov 30, 11:53 pm, Richard Jones <[email protected]> wrote:
> On Wed, Dec 1, 2010 at 10:26 AM, Jonathan Hartley <[email protected]> wrote:
> > From your tone I infer I should beware of intermittent and
> > unrepeatable problems.
>
> Tone was intended to be helpful ;-) Any bugs introduced in a
> transition would typically be quite repeatable and obvious. Now,
> switching from pyglet to C-based calls via cython, there's a source of
> real crashing bugs and other oddities :-)  [oh, how I haven't missed
> you, Bus Error]
>
> > Cythoning is going well, in half-hour snatches over breakfast and
> > lunch! Doubled my frame rate with the low-hanging fruit (type tags in
> > my inner render loop.) Now I'm doing judicious bits of my matrix
> > class, which should leave me with 100% 'white' source lines in my
> > inner render loop ('white' as in the colored output of "cython -a".)
> > Published results soon.
>
> Awesome. Indeed I've also found that the cython'ing mostly helps when
> applied to intensive Python calculation code, rather than just
> cython'ing some random calls into OpenGL. My core "render a bunch of
> landscape segments" code is cython'ed because it operates on actual C
> structures so I've not actually compared how it performs to a vanilla
> Python loop.
>
>  A little judicious use can go a long way :-)
>
>       Richard


Hey. Thanks very much once again.

I think I am being pretty judicious - I've just done the twenty lines
in my innermost loop around 'glDrawElements', and now I'm just  doing
a small portion of my 'matrix' class, the data members of which are
being passed to glMultMatrix inside that same loop. It should only
take a couple of hours, I'm just a crap coder with poor time
management, is all.

It sounds like I should be using my matrices to set uniforms (and
modify shaders accordingly), instead of calling glMultMatrix, I'm
hopeful that change will be relatively straightforward too.

Also, thank-you very much Tristam, your suggestion definitely goes
onto my list - Sounds like I should do that sooner rather than later,
and (possibly) resume Cythoning, etc, when the code is more stable.
I'll take a look at that then.

Wish I had a three week vacation to bury myself in this.

-- 
You received this message because you are subscribed to the Google Groups 
"pyglet-users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/pyglet-users?hl=en.

Reply via email to