Dunk Fordyce wrote:
i dont think you can use the same display list for a mirrored object unless
you specifiy that the vert order for faces is also flipped when drawing a
mirrored instance.
I think you could do that by setting the culling options
before calling the display list, instead of putt
souvarine wrote:
I suggest to make a category bitfield system as in ODE. Every object
would have a 32 bit wide bitfield
Why limit it to 32? This is Python, we have
long integers...
--
Greg
___
Soya-user mailing list
Soya-user@gna.org
https://mail.gn
I think the Soya CoordSyst solid property is rather complicated to use.
I often need an object to be sometime solid and sometime non solid
depending on what I want to test. For example my character must be non
solid for the traveling camera to work, but it must be solid to allow
some others objets
On Thu, 13 Jul 2006 12:20:48 +0200
Jan Filip Tristan <[EMAIL PROTECTED]> wrote:
> Am Mittwoch, 28. Juni 2006 17:54 schrieb Jan Filip Tristan:
>
> ok, problem away, but why can't I see my mousecursor ?
Use the soya.cursor_set_visible(bool) function to hide/show the mouse cursor.
Jiba
_
While you're reworking the ODE stuff, is there any
chance of relaxing the restriction that an ode.Body
be a direct child of an ode.World?
From comments in the source, it seems that this
restriction didn't exist once, but the relevant
code is now commented out.
I'm asking because I'd like to be a
i dont think you can use the same display list for a mirrored object unless
you specifiy that the vert order for faces is also flipped when drawing a
mirrored instance. i also think you'll run into troubles with ode without two
seperate shapes.
On Friday 14 July 2006 05:23, Greg Ewing wrote: