On Tue, 19 Feb 2008, simpsus_science wrote:
> I code a little project (https://launchpad.net/pytower) together with
> some cool guys.
Haha. I've just committed a similar thing to pyglet SVN (contrib/spryte/dtd)
that I've been hacking on my EEE laptop :)
Currently I have peeps solving the board and getting to their exit. I have
tower placement with constraints and towers shoot at and destroy peeps. I've
only got one type of tower though.
> I experience some strange behavior, which I even stranger as it does
> only occur on my machine, not on theirs:
>
> Almost everytime a font is rendered on the screen, the app craches
> with a "Floating point exception".
> We render text like
> "%d blabla", var1/var2
> where var1 is a parameter and var2 the given framelimit (for example).
> If I predict the number and place it directly inside the string, the
> app crashes too.
If you render the text in a stand-alone program do you still see the same
effect?
> Is there any way I can narrow this problem down?
A simple program that just exhibits the behaviour you're seeing would be good.
> What information could be useful in investigating this?
The output of glxinfo please :)
Richard
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
