pyode-user — PyODE User Discussions

[Pyode-user] collide2 ?

[Fred B. <fl...@ys...>]

I just wanted to check:
    At the moment, in PyODE, there is no (quick for spaces with many 
objects) way to do check for collisions between objects in two different 
spaces (like the collide2 function available in the C API of ODE) right?

I was going to put static world things in one space, and dynamic things 
in another space and do collide2 between them, putting them in one space 
seems to waste so much time doing collision between static things that 
it is faster to just use nested for loops to check the various pairings...

(static, moving)
(stopped, moving)
(moving, moving)

(where stopped are those that have body.enabled set to false)

Re: [Pyode-user] build problems with gcc 4.0.2?

[Hart's A. <bha...@ya...>]

your right, the problem is with pyrex, not pyode.
-brett

--- Chris Bainbridge <chr...@gm...> wrote:

> On 26/01/06, Hart's Antler <bha...@ya...> wrote:
> > this is strange, i've gotten it to work on ubuntu in the past, but i just got the latest gcc,
> so
> > maybe it is too new... here is the errors:
> 
> Is your pyrex compatible with gcc-4? The basic 0.9.3 isn't. See
> http://codespeak.net/lxml/installation.html section "Building lxml
> with gcc 4.0" for a patch.
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Re: [Pyode-user] build problems with gcc 4.0.2?

[Chris B. <chr...@gm...>]

On 26/01/06, Hart's Antler <bha...@ya...> wrote:
> this is strange, i've gotten it to work on ubuntu in the past, but i just=
 got the latest gcc, so
> maybe it is too new... here is the errors:

Is your pyrex compatible with gcc-4? The basic 0.9.3 isn't. See
http://codespeak.net/lxml/installation.html section "Building lxml
with gcc 4.0" for a patch.

[Pyode-user] build problems with gcc 4.0.2?

[Hart's A. <bha...@ya...>]

this is strange, i've gotten it to work on ubuntu in the past, but i just got the latest gcc, so
maybe it is too new... here is the errors:

Reading ODE configuration "../ode/config/user-settings"...
ode_trimesh.c is up to date
ode_notrimesh.c is up to date
Installing without trimesh support.
running build
running build_py
creating build
creating build/lib.linux-i686-2.4
creating build/lib.linux-i686-2.4/xode
copying xode/parser.py -> build/lib.linux-i686-2.4/xode
copying xode/geom.py -> build/lib.linux-i686-2.4/xode
copying xode/joint.py -> build/lib.linux-i686-2.4/xode
copying xode/node.py -> build/lib.linux-i686-2.4/xode
copying xode/__init__.py -> build/lib.linux-i686-2.4/xode
copying xode/body.py -> build/lib.linux-i686-2.4/xode
copying xode/transform.py -> build/lib.linux-i686-2.4/xode
copying xode/errors.py -> build/lib.linux-i686-2.4/xode
running build_ext
building 'ode' extension
creating build/temp.linux-i686-2.4
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -fPIC -I../ode/include
-I/usr/local/include/python2.4 -c ode_notrimesh.c -o build/temp.linux-i686-2.4/ode_notrimesh.o
In file included from ../ode/include/ode/common.h:27,
                 from ../ode/include/ode/ode.h:30,
                 from ode_notrimesh.c:10:
../ode/include/ode/error.h:49: warning: function declaration isn’t a prototype
../ode/include/ode/error.h:50: warning: function declaration isn’t a prototype
../ode/include/ode/error.h:51: warning: function declaration isn’t a prototype
In file included from ../ode/include/ode/ode.h:33,
                 from ode_notrimesh.c:10:
../ode/include/ode/memory.h:46: warning: function declaration isn’t a prototype
../ode/include/ode/memory.h:47: warning: function declaration isn’t a prototype
../ode/include/ode/memory.h:48: warning: function declaration isn’t a prototype
In file included from ../ode/include/ode/ode.h:36,
                 from ode_notrimesh.c:10:
../ode/include/ode/timer.h:50: warning: function declaration isn’t a prototype
../ode/include/ode/timer.h:64: warning: function declaration isn’t a prototype
../ode/include/ode/timer.h:69: warning: function declaration isn’t a prototype
In file included from ../ode/include/ode/ode.h:39,
                 from ode_notrimesh.c:10:
../ode/include/ode/misc.h:37: warning: function declaration isn’t a prototype
../ode/include/ode/misc.h:42: warning: function declaration isn’t a prototype
../ode/include/ode/misc.h:45: warning: function declaration isn’t a prototype
../ode/include/ode/misc.h:54: warning: function declaration isn’t a prototype
In file included from ../ode/include/ode/ode.h:40,
                 from ode_notrimesh.c:10:
../ode/include/ode/objects.h:36: warning: function declaration isn’t a prototype
In file included from ../ode/include/ode/collision.h:137,
                 from ../ode/include/ode/ode.h:43,
                 from ode_notrimesh.c:10:
../ode/include/ode/collision_trimesh.h:51: warning: function declaration isn’t a prototype
In file included from ../ode/include/ode/ode.h:43,
                 from ode_notrimesh.c:10:
../ode/include/ode/collision.h:159: warning: function declaration isn’t a prototype
ode_notrimesh.c: In function ‘__pyx_f_3ode_4Mass___new__’:
ode_notrimesh.c:387: warning: label ‘__pyx_L1’ defined but not used
ode_notrimesh.c: In function ‘__pyx_f_3ode_4Mass_setZero’:
ode_notrimesh.c:408: warning: label ‘__pyx_L1’ defined but not used
ode_notrimesh.c: In function ‘__pyx_f_3ode_5World___new__’:
ode_notrimesh.c:2197: warning: label ‘__pyx_L1’ defined but not used
ode_notrimesh.c: In function ‘__pyx_f_3ode_5World___dealloc__’:
ode_notrimesh.c:2221: warning: label ‘__pyx_L1’ defined but not used
ode_notrimesh.c: In function ‘__pyx_f_3ode_4Body___dealloc__’:
ode_notrimesh.c:3036: warning: label ‘__pyx_L1’ defined but not used
ode_notrimesh.c: In function ‘__pyx_f_3ode_4Body_getMass’:
ode_notrimesh.c:3776: error: invalid lvalue in assignment
ode_notrimesh.c:3784: error: invalid lvalue in assignment
ode_notrimesh.c: In function ‘__pyx_f_3ode_4Body_enable’:
ode_notrimesh.c:4851: warning: label ‘__pyx_L1’ defined but not used
ode_notrimesh.c: In function ‘__pyx_f_3ode_4Body_disable’:
ode_notrimesh.c:4872: warning: label ‘__pyx_L1’ defined but not used
ode_notrimesh.c: In function ‘__pyx_f_3ode_10JointGroup___new__’:
ode_notrimesh.c:5139: warning: label ‘__pyx_L1’ defined but not used
ode_notrimesh.c: In function ‘__pyx_f_3ode_10JointGroup___dealloc__’:
ode_notrimesh.c:5188: warning: label ‘__pyx_L1’ defined but not used
ode_notrimesh.c: In function ‘__pyx_f_3ode_10JointGroup_empty’:
ode_notrimesh.c:5234: warning: label ‘__pyx_L3’ defined but not used
ode_notrimesh.c:5216: warning: label ‘__pyx_L2’ defined but not used
ode_notrimesh.c: In function ‘__pyx_f_3ode_5Joint__destroyed’:
ode_notrimesh.c:5583: warning: label ‘__pyx_L1’ defined but not used
ode_notrimesh.c: In function ‘__pyx_f_3ode_9BallJoint___new__’:
ode_notrimesh.c:5973: error: invalid lvalue in assignment
ode_notrimesh.c:5988: error: invalid lvalue in assignment
ode_notrimesh.c: In function ‘__pyx_f_3ode_9BallJoint_setParam’:
ode_notrimesh.c:6220: warning: label ‘__pyx_L1’ defined but not used
ode_notrimesh.c: In function ‘__pyx_f_3ode_10HingeJoint___new__’:
ode_notrimesh.c:6272: error: invalid lvalue in assignment
ode_notrimesh.c:6287: error: invalid lvalue in assignment
ode_notrimesh.c: In function ‘__pyx_f_3ode_11SliderJoint___new__’:
ode_notrimesh.c:6747: error: invalid lvalue in assignment
ode_notrimesh.c:6762: error: invalid lvalue in assignment
ode_notrimesh.c: In function ‘__pyx_f_3ode_14UniversalJoint___new__’:
ode_notrimesh.c:7084: error: invalid lvalue in assignment
ode_notrimesh.c:7099: error: invalid lvalue in assignment
ode_notrimesh.c: In function ‘__pyx_f_3ode_11Hinge2Joint___new__’:
ode_notrimesh.c:7601: error: invalid lvalue in assignment
ode_notrimesh.c:7616: error: invalid lvalue in assignment
ode_notrimesh.c: In function ‘__pyx_f_3ode_10FixedJoint___new__’:
ode_notrimesh.c:8196: error: invalid lvalue in assignment
ode_notrimesh.c:8211: error: invalid lvalue in assignment
ode_notrimesh.c: In function ‘__pyx_f_3ode_10FixedJoint_setFixed’:
ode_notrimesh.c:8303: warning: label ‘__pyx_L1’ defined but not used
ode_notrimesh.c: In function ‘__pyx_f_3ode_12ContactJoint___new__’:
ode_notrimesh.c:8326: error: invalid lvalue in assignment
ode_notrimesh.c:8342: error: invalid lvalue in assignment
ode_notrimesh.c: In function ‘__pyx_f_3ode_6AMotor___new__’:
ode_notrimesh.c:8439: error: invalid lvalue in assignment
ode_notrimesh.c:8454: error: invalid lvalue in assignment
ode_notrimesh.c: In function ‘__pyx_f_3ode_6AMotor_setNumAxes’:
ode_notrimesh.c:8599: warning: label ‘__pyx_L1’ defined but not used
ode_notrimesh.c: In function ‘__pyx_f_3ode_10GeomObject___dealloc__’:
ode_notrimesh.c:9043: warning: label ‘__pyx_L1’ defined but not used
ode_notrimesh.c: In function ‘__pyx_f_3ode_10GeomObject_getSpace’:
ode_notrimesh.c:9791: warning: label ‘__pyx_L1’ defined but not used
ode_notrimesh.c: In function ‘__pyx_f_3ode_10GeomObject_enable’:
ode_notrimesh.c:9946: warning: label ‘__pyx_L1’ defined but not used
ode_notrimesh.c: In function ‘__pyx_f_3ode_10GeomObject_disable’:
ode_notrimesh.c:9967: warning: label ‘__pyx_L1’ defined but not used
ode_notrimesh.c: In function ‘__pyx_f_3ode_14_SpaceIterator___iter__’:
ode_notrimesh.c:10052: warning: label ‘__pyx_L1’ defined but not used
ode_notrimesh.c: In function ‘__pyx_f_3ode_9SpaceBase___new__’:
ode_notrimesh.c:10170: warning: label ‘__pyx_L1’ defined but not used
ode_notrimesh.c: In function ‘__pyx_f_3ode_9SpaceBase___dealloc__’:
ode_notrimesh.c:10246: warning: label ‘__pyx_L1’ defined but not used
ode_notrimesh.c: In function ‘__pyx_f_3ode_11SimpleSpace___new__’:
ode_notrimesh.c:10682: error: invalid lvalue in assignment
ode_notrimesh.c:10696: error: invalid lvalue in assignment
ode_notrimesh.c: In function ‘__pyx_f_3ode_11SimpleSpace___init__’:
ode_notrimesh.c:10748: warning: label ‘__pyx_L1’ defined but not used
ode_notrimesh.c: In function ‘__pyx_f_3ode_9HashSpace___new__’:
ode_notrimesh.c:10771: error: invalid lvalue in assignment
ode_notrimesh.c:10785: error: invalid lvalue in assignment
ode_notrimesh.c: In function ‘__pyx_f_3ode_9HashSpace___init__’:
ode_notrimesh.c:10837: warning: label ‘__pyx_L1’ defined but not used
ode_notrimesh.c: In function ‘__pyx_f_3ode_13QuadTreeSpace___new__’:
ode_notrimesh.c:10969: error: invalid lvalue in assignment
ode_notrimesh.c:10983: error: invalid lvalue in assignment
ode_notrimesh.c: In function ‘__pyx_f_3ode_13QuadTreeSpace___init__’:
ode_notrimesh.c:11093: warning: label ‘__pyx_L1’ defined but not used
ode_notrimesh.c: In function ‘__pyx_f_3ode_10GeomSphere___new__’:
ode_notrimesh.c:11195: error: invalid lvalue in assignment
ode_notrimesh.c:11209: error: invalid lvalue in assignment
ode_notrimesh.c: In function ‘__pyx_f_3ode_10GeomSphere___init__’:
ode_notrimesh.c:11268: warning: label ‘__pyx_L1’ defined but not used
ode_notrimesh.c: In function ‘__pyx_f_3ode_7GeomBox___new__’:
ode_notrimesh.c:11455: error: invalid lvalue in assignment
ode_notrimesh.c:11469: error: invalid lvalue in assignment
ode_notrimesh.c: In function ‘__pyx_f_3ode_7GeomBox___init__’:
ode_notrimesh.c:11542: warning: label ‘__pyx_L1’ defined but not used
ode_notrimesh.c: In function ‘__pyx_f_3ode_9GeomPlane___new__’:
ode_notrimesh.c:11768: error: invalid lvalue in assignment
ode_notrimesh.c:11782: error: invalid lvalue in assignment
ode_notrimesh.c: In function ‘__pyx_f_3ode_9GeomPlane___init__’:
ode_notrimesh.c:11855: warning: label ‘__pyx_L1’ defined but not used
ode_notrimesh.c: In function ‘__pyx_f_3ode_13GeomCCylinder___new__’:
ode_notrimesh.c:12066: error: invalid lvalue in assignment
ode_notrimesh.c:12080: error: invalid lvalue in assignment
ode_notrimesh.c: In function ‘__pyx_f_3ode_13GeomCCylinder___init__’:
ode_notrimesh.c:12144: warning: label ‘__pyx_L1’ defined but not used
ode_notrimesh.c: In function ‘__pyx_f_3ode_7GeomRay___new__’:
ode_notrimesh.c:12346: error: invalid lvalue in assignment
ode_notrimesh.c:12360: error: invalid lvalue in assignment
ode_notrimesh.c: In function ‘__pyx_f_3ode_7GeomRay___init__’:
ode_notrimesh.c:12419: warning: label ‘__pyx_L1’ defined but not used
ode_notrimesh.c: In function ‘__pyx_f_3ode_13GeomTransform___new__’:
ode_notrimesh.c:12650: error: invalid lvalue in assignment
ode_notrimesh.c:12664: error: invalid lvalue in assignment
ode_notrimesh.c: In function ‘__pyx_f_3ode_13GeomTransform_getGeom’:
ode_notrimesh.c:12916: warning: label ‘__pyx_L1’ defined but not used
ode_notrimesh.c: In function ‘__pyx_f_3ode_collide’:
ode_notrimesh.c:13091: error: invalid lvalue in assignment
ode_notrimesh.c:13138: error: invalid lvalue in assignment
ode_notrimesh.c:13157: warning: label ‘__pyx_L3’ defined but not used
ode_notrimesh.c:13128: warning: label ‘__pyx_L2’ defined but not used
ode_notrimesh.c: In function ‘__pyx_f_3ode_CloseODE’:
ode_notrimesh.c:13268: warning: label ‘__pyx_L1’ defined but not used
ode_notrimesh.c: In function ‘__pyx_tp_new_3ode_Mass’:
ode_notrimesh.c:13406: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_dealloc_3ode_Mass’:
ode_notrimesh.c:13414: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_traverse_3ode_Mass’:
ode_notrimesh.c:13420: warning: unused variable ‘p’
ode_notrimesh.c:13419: warning: unused variable ‘e’
ode_notrimesh.c: In function ‘__pyx_tp_clear_3ode_Mass’:
ode_notrimesh.c:13425: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_new_3ode_Contact’:
ode_notrimesh.c:13578: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_dealloc_3ode_Contact’:
ode_notrimesh.c:13586: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_traverse_3ode_Contact’:
ode_notrimesh.c:13592: warning: unused variable ‘p’
ode_notrimesh.c:13591: warning: unused variable ‘e’
ode_notrimesh.c: In function ‘__pyx_tp_clear_3ode_Contact’:
ode_notrimesh.c:13597: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_new_3ode_World’:
ode_notrimesh.c:13749: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_dealloc_3ode_World’:
ode_notrimesh.c:13757: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_traverse_3ode_World’:
ode_notrimesh.c:13772: warning: unused variable ‘p’
ode_notrimesh.c:13771: warning: unused variable ‘e’
ode_notrimesh.c: In function ‘__pyx_tp_clear_3ode_World’:
ode_notrimesh.c:13777: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_new_3ode_BallJoint’:
ode_notrimesh.c:14522: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_dealloc_3ode_BallJoint’:
ode_notrimesh.c:14530: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_traverse_3ode_BallJoint’:
ode_notrimesh.c:14536: warning: unused variable ‘p’
ode_notrimesh.c:14535: warning: unused variable ‘e’
ode_notrimesh.c: In function ‘__pyx_tp_clear_3ode_BallJoint’:
ode_notrimesh.c:14542: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_new_3ode_HingeJoint’:
ode_notrimesh.c:14674: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_dealloc_3ode_HingeJoint’:
ode_notrimesh.c:14682: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_traverse_3ode_HingeJoint’:
ode_notrimesh.c:14688: warning: unused variable ‘p’
ode_notrimesh.c:14687: warning: unused variable ‘e’
ode_notrimesh.c: In function ‘__pyx_tp_clear_3ode_HingeJoint’:
ode_notrimesh.c:14694: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_new_3ode_SliderJoint’:
ode_notrimesh.c:14831: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_dealloc_3ode_SliderJoint’:
ode_notrimesh.c:14839: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_traverse_3ode_SliderJoint’:
ode_notrimesh.c:14845: warning: unused variable ‘p’
ode_notrimesh.c:14844: warning: unused variable ‘e’
ode_notrimesh.c: In function ‘__pyx_tp_clear_3ode_SliderJoint’:
ode_notrimesh.c:14851: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_new_3ode_UniversalJoint’:
ode_notrimesh.c:14985: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_dealloc_3ode_UniversalJoint’:
ode_notrimesh.c:14993: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_traverse_3ode_UniversalJoint’:
ode_notrimesh.c:14999: warning: unused variable ‘p’
ode_notrimesh.c:14998: warning: unused variable ‘e’
ode_notrimesh.c: In function ‘__pyx_tp_clear_3ode_UniversalJoint’:
ode_notrimesh.c:15005: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_new_3ode_Hinge2Joint’:
ode_notrimesh.c:15142: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_dealloc_3ode_Hinge2Joint’:
ode_notrimesh.c:15150: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_traverse_3ode_Hinge2Joint’:
ode_notrimesh.c:15156: warning: unused variable ‘p’
ode_notrimesh.c:15155: warning: unused variable ‘e’
ode_notrimesh.c: In function ‘__pyx_tp_clear_3ode_Hinge2Joint’:
ode_notrimesh.c:15162: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_new_3ode_FixedJoint’:
ode_notrimesh.c:15302: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_dealloc_3ode_FixedJoint’:
ode_notrimesh.c:15310: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_traverse_3ode_FixedJoint’:
ode_notrimesh.c:15316: warning: unused variable ‘p’
ode_notrimesh.c:15315: warning: unused variable ‘e’
ode_notrimesh.c: In function ‘__pyx_tp_clear_3ode_FixedJoint’:
ode_notrimesh.c:15322: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_new_3ode_ContactJoint’:
ode_notrimesh.c:15450: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_dealloc_3ode_ContactJoint’:
ode_notrimesh.c:15458: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_traverse_3ode_ContactJoint’:
ode_notrimesh.c:15464: warning: unused variable ‘p’
ode_notrimesh.c:15463: warning: unused variable ‘e’
ode_notrimesh.c: In function ‘__pyx_tp_clear_3ode_ContactJoint’:
ode_notrimesh.c:15470: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_new_3ode_AMotor’:
ode_notrimesh.c:15597: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_dealloc_3ode_AMotor’:
ode_notrimesh.c:15605: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_traverse_3ode_AMotor’:
ode_notrimesh.c:15611: warning: unused variable ‘p’
ode_notrimesh.c:15610: warning: unused variable ‘e’
ode_notrimesh.c: In function ‘__pyx_tp_clear_3ode_AMotor’:
ode_notrimesh.c:15617: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_new_3ode_SpaceBase’:
ode_notrimesh.c:15968: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_dealloc_3ode_SpaceBase’:
ode_notrimesh.c:15976: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_traverse_3ode_SpaceBase’:
ode_notrimesh.c:15991: warning: unused variable ‘p’
ode_notrimesh.c:15990: warning: unused variable ‘e’
ode_notrimesh.c: In function ‘__pyx_tp_clear_3ode_SpaceBase’:
ode_notrimesh.c:15997: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_new_3ode_SimpleSpace’:
ode_notrimesh.c:16131: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_dealloc_3ode_SimpleSpace’:
ode_notrimesh.c:16139: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_traverse_3ode_SimpleSpace’:
ode_notrimesh.c:16145: warning: unused variable ‘p’
ode_notrimesh.c:16144: warning: unused variable ‘e’
ode_notrimesh.c: In function ‘__pyx_tp_clear_3ode_SimpleSpace’:
ode_notrimesh.c:16151: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_new_3ode_HashSpace’:
ode_notrimesh.c:16278: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_dealloc_3ode_HashSpace’:
ode_notrimesh.c:16286: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_traverse_3ode_HashSpace’:
ode_notrimesh.c:16292: warning: unused variable ‘p’
ode_notrimesh.c:16291: warning: unused variable ‘e’
ode_notrimesh.c: In function ‘__pyx_tp_clear_3ode_HashSpace’:
ode_notrimesh.c:16298: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_new_3ode_QuadTreeSpace’:
ode_notrimesh.c:16427: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_dealloc_3ode_QuadTreeSpace’:
ode_notrimesh.c:16435: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_traverse_3ode_QuadTreeSpace’:
ode_notrimesh.c:16441: warning: unused variable ‘p’
ode_notrimesh.c:16440: warning: unused variable ‘e’
ode_notrimesh.c: In function ‘__pyx_tp_clear_3ode_QuadTreeSpace’:
ode_notrimesh.c:16447: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_new_3ode_GeomSphere’:
ode_notrimesh.c:16574: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_dealloc_3ode_GeomSphere’:
ode_notrimesh.c:16582: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_traverse_3ode_GeomSphere’:
ode_notrimesh.c:16588: warning: unused variable ‘p’
ode_notrimesh.c:16587: warning: unused variable ‘e’
ode_notrimesh.c: In function ‘__pyx_tp_clear_3ode_GeomSphere’:
ode_notrimesh.c:16594: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_new_3ode_GeomBox’:
ode_notrimesh.c:16726: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_dealloc_3ode_GeomBox’:
ode_notrimesh.c:16734: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_traverse_3ode_GeomBox’:
ode_notrimesh.c:16740: warning: unused variable ‘p’
ode_notrimesh.c:16739: warning: unused variable ‘e’
ode_notrimesh.c: In function ‘__pyx_tp_clear_3ode_GeomBox’:
ode_notrimesh.c:16746: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_new_3ode_GeomPlane’:
ode_notrimesh.c:16878: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_dealloc_3ode_GeomPlane’:
ode_notrimesh.c:16886: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_traverse_3ode_GeomPlane’:
ode_notrimesh.c:16892: warning: unused variable ‘p’
ode_notrimesh.c:16891: warning: unused variable ‘e’
ode_notrimesh.c: In function ‘__pyx_tp_clear_3ode_GeomPlane’:
ode_notrimesh.c:16898: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_new_3ode_GeomCCylinder’:
ode_notrimesh.c:17029: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_dealloc_3ode_GeomCCylinder’:
ode_notrimesh.c:17037: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_traverse_3ode_GeomCCylinder’:
ode_notrimesh.c:17043: warning: unused variable ‘p’
ode_notrimesh.c:17042: warning: unused variable ‘e’
ode_notrimesh.c: In function ‘__pyx_tp_clear_3ode_GeomCCylinder’:
ode_notrimesh.c:17049: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_new_3ode_GeomRay’:
ode_notrimesh.c:17181: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_dealloc_3ode_GeomRay’:
ode_notrimesh.c:17189: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_traverse_3ode_GeomRay’:
ode_notrimesh.c:17195: warning: unused variable ‘p’
ode_notrimesh.c:17194: warning: unused variable ‘e’
ode_notrimesh.c: In function ‘__pyx_tp_clear_3ode_GeomRay’:
ode_notrimesh.c:17201: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_new_3ode_TriMeshData’:
ode_notrimesh.c:17493: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_dealloc_3ode_TriMeshData’:
ode_notrimesh.c:17498: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_traverse_3ode_TriMeshData’:
ode_notrimesh.c:17504: warning: unused variable ‘p’
ode_notrimesh.c:17503: warning: unused variable ‘e’
ode_notrimesh.c: In function ‘__pyx_tp_clear_3ode_TriMeshData’:
ode_notrimesh.c:17509: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_new_3ode_GeomTriMesh’:
ode_notrimesh.c:17635: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_dealloc_3ode_GeomTriMesh’:
ode_notrimesh.c:17640: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__pyx_tp_traverse_3ode_GeomTriMesh’:
ode_notrimesh.c:17646: warning: unused variable ‘p’
ode_notrimesh.c:17645: warning: unused variable ‘e’
ode_notrimesh.c: In function ‘__pyx_tp_clear_3ode_GeomTriMesh’:
ode_notrimesh.c:17652: warning: unused variable ‘p’
ode_notrimesh.c: In function ‘__Pyx_GetStarArgs’:
ode_notrimesh.c:18542: warning: suggest explicit braces to avoid ambiguous ‘else’
ode_notrimesh.c:18544: warning: suggest explicit braces to avoid ambiguous ‘else’
ode_notrimesh.c: In function ‘__Pyx_EndUnpack’:
ode_notrimesh.c:18693: warning: suggest parentheses around assignment used as truth value
error: command 'gcc' failed with exit status 1


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Re: [Pyode-user] subclassing ode

[Chris B. <chr...@gm...>]

On 23/01/06, Ricardo Kirkner <ric...@gm...> wrote:
> Hi:
>
> I want to create a subclass of ode.Body. I have written a class

> I get the error:
>
> TypeError: function takes exactly 1 argument (0 given)

PyODE uses Pyrex to wrap the C ODE library in python classes.

From http://www.cosc.canterbury.ac.nz/~greg/python/Pyrex/version/Doc/specia=
l_methods.html

"Keep in mind that any arguments passed to the constructor will be
passed to the __new__ method as well as the __init__ method. If you
anticipate subclassing your extension type in Python, you may find it
useful to give the __new__ method * and ** arguments so that it can
accept and ignore extra arguments. Otherwise, any Python subclass
which has an __init__ with a different signature will have to override
__new__ as well as __init__, which the writer of a Python class
wouldn't expect to have to do."

You can find the ode.Body wrapper in the pyode source at src/body.pyx

[Pyode-user] subclassing ode

[Ricardo K. <ric...@gm...>]

Hi:

I want to create a subclass of ode.Body. I have written a class

class myBody(ode.Body):
    def __init__(self):
        self.world =3D ode.World()
        ode.Body.__init__(self, self.world)

...

The strange part is that when I execute the line

mb =3D myBody()

I get the error:

TypeError: function takes exactly 1 argument (0 given)

It appears as it tries to run the ode.Body.__init__ method before
calling the myBody.__init__ method. I have made some variations that
just confirm this thought.

Can anyone please tell me why this is happening, and how I can get around t=
his?

Regards,

Ricardo Kirkner

Re: [Pyode-user] Re: ropes, in ODE.

[Matthias B. <ba...@ir...>]

Simon Wittber wrote:
>> Does it really look like a rope? A hinge can freely rotate around its
>> axis, so I'd expect such a "rope" rather to look like a chain. Did you
>> do any special stuff to get it more "rope-like"?
> 
> Well, it does look more like a chain than a rope. I not really
> satisfied with the results yet.

You could try adding some friction to the hinges. This can be done by 
activating the motors. Set the target velocity to 0 and the maximum 
force to a relatively low value (higher values = more friction). I could 
imagine that this already improves the look of the rope.

- Matthias -

Re: [Pyode-user] setQuaternion on Geometry Objects

[Matthias B. <ba...@ir...>]

Simon Wittber wrote:
> void dGeomSetQuaternion (dGeomID, const dQuaternion);
> 
> is missing from pyode (Ie I cannot set a geometry's rotation using a
> quaternion).
> 
> Is there a reason for this (should I not be using it for any reason?)
> or it simply not implemented yet?

The latter, it simply was not implemented yet. I've just added the 
get/set methods and committed them into the cvs repository.

- Matthias -

Re: [Pyode-user] Re: ropes, in ODE.

[Matthias B. <ba...@ir...>]

Simon Wittber wrote:
>>> I want to simulate a rope in ODE.
>> I've made the simulation much better, by reducing the world.step time
>> to 0.01, and iterating it 10 times. It's killed my performance though.
> 
> Problem solved. I added more mass to the rope segments, and the
> simulation stabilised.

Does it really look like a rope? A hinge can freely rotate around its 
axis, so I'd expect such a "rope" rather to look like a chain. Did you 
do any special stuff to get it more "rope-like"?

- Matthias -

[Pyode-user] setQuaternion on Geometry Objects

[Simon W. <sim...@gm...>]

It appears that:

void dGeomSetQuaternion (dGeomID, const dQuaternion);

is missing from pyode (Ie I cannot set a geometry's rotation using a
quaternion).

Is there a reason for this (should I not be using it for any reason?)
or it simply not implemented yet?

[Pyode-user] Re: ropes, in ODE.

[Simon W. <sim...@gm...>]

On 1/17/06, Simon Wittber <sim...@gm...> wrote:
> On 1/17/06, Simon Wittber <sim...@gm...> wrote:
> > I want to simulate a rope in ODE.
>
> I've made the simulation much better, by reducing the world.step time
> to 0.01, and iterating it 10 times. It's killed my performance though.
>

Problem solved. I added more mass to the rope segments, and the
simulation stabilised.

[Pyode-user] Re: ropes, in ODE.

[Simon W. <sim...@gm...>]

On 1/17/06, Simon Wittber <sim...@gm...> wrote:
> I want to simulate a rope in ODE.

I've made the simulation much better, by reducing the world.step time
to 0.01, and iterating it 10 times. It's killed my performance though.

[Pyode-user] ropes, in ODE.

[Simon W. <sim...@gm...>]

I want to simulate a rope in ODE.

I am using a hinge joint, to constrain the rope to the z axis.

I attach one end of the rope to the environement, and the other end to
a body. In between the environment and body are 10-15  bodies, which
make up segments of the rope. These are all joined using HingeJoints.

The simulation seems to work for a few seconds, but after that, the
rope goes nuts. It seems that the joints stretch apart then bounce
back, causing the rope to go a little epileptic.

Any ideas on how to do a better rope simulation? I am new to ODE, so I
may have missed something.


-Sw.

Re: [Pyode-user] Sandwich plane

[Thomas P. <tho...@fr...>]

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<blockquote cite="mid...@mc..." type="cite">
  <blockquote type="cite">
    <pre wrap="">I'm attempting to use PyODE for a 2D platform game.

The below code is not doing what I expect.

        self.space = space = ode.Space()
        self.back = ode.GeomPlane(space, (0,0,1), 1)
        self.front = ode.GeomPlane(space, (0,0,-1),-1)

What I want to do is sandwich my world between two vertical infinite
planes. Am I going about this the right way?
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Hi Simon,

I beleive it's possible to use ODE as a 2d engine just by keeping all
your z values at zero. Check out tutorial2.py in the examples that come
with PyODE. That is, make everything in your world have no thickness and
no z values at all.

Best,

Chris.

  </pre>
</blockquote>
Hello,<br>
<br>
A patch for a Plane2D joint is available on the Ode mailing list
archive. With a little hack on PyOde, maybe this new joint type could
be available for Python.<br>
<br>
Here is a link to this patch:<br>
<br>
<a class="moz-txt-link-freetext" href="http://q12.org/pipermail/ode/2003-November/010325.html">http://q12.org/pipermail/ode/2003-November/010325.html</a><br>
<br>
Thomas<br>
</body>
</html>

Re: [Pyode-user] Sandwich plane

[Matthias B. <ba...@ir...>]

Simon Wittber wrote:
>>Of course, the best solution would be to switch to a true 2D simulator
>>as this one could be much more efficient than a full 3D simulator
>>projected back to 2D.
> 
> Thanks for the feedback. I agree, however, I cannot find a 2D
> simulator. Do you know of any such thing?

No, sorry.

> Before I started using ODE, I started coding a 2D simulator using
> Numeric. However, my knowledge of physics is not enough to finish the
> job.

Well, as long as ODE does the job without being the bottleneck in your 
game there's probably no need to write a new simulator anyway.

By the way, don't forget to post a message when you've finished the 
game... ;)

- Matthias -

Re: [Pyode-user] Sandwich plane

[Chris M. <ch...@mc...>]

On Sat, Jan 07, 2006 at 11:02:12PM +0800, Simon Wittber wrote:
> I'm attempting to use PyODE for a 2D platform game.
> 
> The below code is not doing what I expect.
> 
>         self.space = space = ode.Space()
>         self.back = ode.GeomPlane(space, (0,0,1), 1)
>         self.front = ode.GeomPlane(space, (0,0,-1),-1)
> 
> What I want to do is sandwich my world between two vertical infinite
> planes. Am I going about this the right way?

Hi Simon,

I beleive it's possible to use ODE as a 2d engine just by keeping all
your z values at zero. Check out tutorial2.py in the examples that come
with PyODE. That is, make everything in your world have no thickness and
no z values at all.

Best,

Chris.

-------------------
ch...@mc...
http://mccormick.cx

Re: [Pyode-user] Sandwich plane

[Simon W. <sim...@gm...>]

On 1/9/06, Matthias Baas <ba...@ir...> wrote:
> Apart from that, I'm not sure if your technique is a good idea at all. I
> wouldn't be surprised if the simulation does weird things sooner or
> later because ODE smashes the objects from one plane to the other and
> accumulates high velocities in your undesired third dimension.
> You may probably want to set the Z values of all positions and
> velocities to zero after each simulation step (in which case the above
> planes might even be superfluous).

Hmm I might try this.

> Of course, the best solution would be to switch to a true 2D simulator
> as this one could be much more efficient than a full 3D simulator
> projected back to 2D.

Thanks for the feedback. I agree, however, I cannot find a 2D
simulator. Do you know of any such thing?

Before I started using ODE, I started coding a 2D simulator using
Numeric. However, my knowledge of physics is not enough to finish the
job.

-Sw.

Re: [Pyode-user] Sandwich plane

[Matthias B. <ba...@ir...>]

Simon Wittber wrote:
> I'm attempting to use PyODE for a 2D platform game.
> 
> The below code is not doing what I expect.
> 
>         self.space = space = ode.Space()
>         self.back = ode.GeomPlane(space, (0,0,1), 1)
>         self.front = ode.GeomPlane(space, (0,0,-1),-1)

I believe the distance of the second plane should be +1 (as you have 
already inverted the normal), otherwise both planes coincide and the 
simulation most certainly goes haywire.

Apart from that, I'm not sure if your technique is a good idea at all. I 
wouldn't be surprised if the simulation does weird things sooner or 
later because ODE smashes the objects from one plane to the other and 
accumulates high velocities in your undesired third dimension.
You may probably want to set the Z values of all positions and 
velocities to zero after each simulation step (in which case the above 
planes might even be superfluous).

Of course, the best solution would be to switch to a true 2D simulator 
as this one could be much more efficient than a full 3D simulator 
projected back to 2D.

- Matthias -

[Pyode-user] Sandwich plane

[Simon W. <sim...@gm...>]

I'm attempting to use PyODE for a 2D platform game.

The below code is not doing what I expect.

        self.space =3D space =3D ode.Space()
        self.back =3D ode.GeomPlane(space, (0,0,1), 1)
        self.front =3D ode.GeomPlane(space, (0,0,-1),-1)

What I want to do is sandwich my world between two vertical infinite
planes. Am I going about this the right way?


-Sw.

Re: [Pyode-user] Debian packaging available for PyODE

[Timothy S. <tim...@gm...>]

Hi Josh,

Great work on your Debian packages. I have updated setup.py to search
for ODE installations in common locations like /usr or /usr/local. You
can also specify the location of user-settings directly if the script
doesn't find it automatically. As far as I can tell, it will work on
Debian without any modifications. It also works on Gentoo without any
modification.

--
Timothy

[Pyode-user] xode doesn't recognize some elements (3dsmax)

[Krystian S. <sam...@gm...>]

Hi there
i'm using octopus in 3dsmax as a plugin for exporting xode
definitions. it seems that xode (which comes from pyode package)
doesn't recognize some elements. i'm getting exceptions like this:
xode.errors.ChildError: <transform> is not a valid child of <joint>
...
i would like to export physical bodies connected with joints from 3ds
max, could someone help?
best regards
krychu

Re: [Pyode-user] Debian packaging available for PyODE

[Josh T. <jo...@ps...>]

Jean de Largentaye wrote:
> That's great Josh! I meant to do it a while ago, but never completely
> got around to doing it (/me slaps /me).
> I stumbled across a problem when I started looking into it: the Debian
> ODE package has trimeshes disabled because OPCODE has some problems on
> certain arches. I thus had to rebuild the debian ODE package for
> myself and have PyODE build off that... What have you done about this?
> Have you disabled trimeshes in your package? If yes, would it be
> vaguely possible to provide a libode package with OPCODE and trimeshes
> enabled, along with the appropriate PyODE package? Yeah I know,
> "give'em the hand and they'll want the whole arm" ;)

I haven't used trimeshes at all, so I haven't tried working with OPCODE.
 I just let PyODE build without trimesh support to match the system ODE
configuration.

I don't think it would be a good idea for Debian's ODE package to have
OPCODE enabled unless it could be enabled on all architectures, which is
not currently possible due to non-portable pointer usage.  The ideal
solution would clearly be for someone to fix OPCODE for 64-bit
architectures; given the relatively short length of the patch given in
bug 297924 <http://bugs.debian.org/297924>, which changes the ints to
longs rather than intptr_t's as suggested, it would probably not be too
difficult for someone to change the patch to use intptr_t and ptrdiff_t.
  However, I don't have a 64-bit machine available to build and test
such a fix, nor do I have sufficient knowledge about the trimesh support
to properly test the fix.  I'd also prefer not to maintain a separate
non-portable set of packages for ODE.

So the best way to resolve this problem is most likely to find an
appropriate fix for Debian's ODE packages in order to enable OPCODE and
trimeshes in the official package.  Once that happens, I'd be happy to
rebuild the PyODE packages against the trimesh-enabled ODE.  In the
meantime, my packages should build just fine against an ODE with or
without trimesh support, so if you have ODE packages with trimesh
support enabled, you can just grab my source package and build it to get
binary PyODE packages with trimesh support.

> It'd also be really nice to have this package included in Debian...
> have you looked into that possibility?

I'm planning to look for a sponsor who could upload the packages to
Debian.  I wanted to get some feedback from PyODE developers on the
package first, though.

- Josh Triplett

Re: [Pyode-user] Debian packaging available for PyODE

[Jean de L. <jla...@gm...>]

That's great Josh! I meant to do it a while ago, but never completely
got around to doing it (/me slaps /me).
I stumbled across a problem when I started looking into it: the Debian
ODE package has trimeshes disabled because OPCODE has some problems on
certain arches. I thus had to rebuild the debian ODE package for
myself and have PyODE build off that... What have you done about this?
Have you disabled trimeshes in your package? If yes, would it be
vaguely possible to provide a libode package with OPCODE and trimeshes
enabled, along with the appropriate PyODE package? Yeah I know,
"give'em the hand and they'll want the whole arm" ;)
It'd also be really nice to have this package included in Debian...
have you looked into that possibility?

Thanks a lot for your work!
John

On 12/2/05, Josh Triplett <jo...@ps...> wrote:
> [Please CC me on replies, as I'm not subscribed to the list.]
>
> Hello,
>
> I've created Debian packages for PyODE 1.1.0; you can find them at
> <http://psas.pdx.edu/~josh/pyode>.  (Not apt-gettable, as that isn't a
> permanent repository.)  These packages are built against latest Debian
> unstable, and include packages for both python 2.3 and 2.4.
>
> In order to build with GCC 4.0, I remove the pre-generated pyrex output
> files and force setup.py to rebuild them, as Debian's pyrex packages
> include a patch to fix the generated code so GCC 4.0 can compile it.
> You might want to generate the release tarballs with a similarly patched
> pyrex, to fix this issue for other users.  It would also be helpful to
> have an option for setup.py to always rebuild the output files.
>
> I also had to patch the paths in setup.py, since looking in "../ode" for
> ODE source will not work.  On Debian at least, the include files are in
> /usr/include, the libraries are in /usr/lib, and the user-settings file
> is available at /usr/include/ode/config/user-settings, so I changed
> ODE_BASE to "/usr", and changed the file location to
> os.path.join(ODE_BASE, "include", "ode", "config", "user-settings").  It
> would be helpful if the default ODE_BASE was "/usr" on non-Windows
> systems, since those systems would usually want to use a system-wide
> ODE.  I don't know whether the user-settings path will work on all
> systems; in particular, the path will differ if grabbing it out of an
> ODE source directory.  Some possible solutions for that would be to move
> the path to the user-settings file into the system-specific section (if
> it is the same on all non-Windows systems) or trying several different
> paths (ODE_BASE/include/ode/config/user-settings,
> ODE_BASE/config/user-settings, etc) and using the first working path.
>
> Thank you for PyODE.  I hope you find these packages useful.
>
> - Josh Triplett
>
>
>

[Pyode-user] Debian packaging available for PyODE

[Josh T. <jo...@ps...>]

[Please CC me on replies, as I'm not subscribed to the list.]

Hello,

I've created Debian packages for PyODE 1.1.0; you can find them at
<http://psas.pdx.edu/~josh/pyode>.  (Not apt-gettable, as that isn't a
permanent repository.)  These packages are built against latest Debian
unstable, and include packages for both python 2.3 and 2.4.

In order to build with GCC 4.0, I remove the pre-generated pyrex output
files and force setup.py to rebuild them, as Debian's pyrex packages
include a patch to fix the generated code so GCC 4.0 can compile it.
You might want to generate the release tarballs with a similarly patched
pyrex, to fix this issue for other users.  It would also be helpful to
have an option for setup.py to always rebuild the output files.

I also had to patch the paths in setup.py, since looking in "../ode" for
ODE source will not work.  On Debian at least, the include files are in
/usr/include, the libraries are in /usr/lib, and the user-settings file
is available at /usr/include/ode/config/user-settings, so I changed
ODE_BASE to "/usr", and changed the file location to
os.path.join(ODE_BASE, "include", "ode", "config", "user-settings").  It
would be helpful if the default ODE_BASE was "/usr" on non-Windows
systems, since those systems would usually want to use a system-wide
ODE.  I don't know whether the user-settings path will work on all
systems; in particular, the path will differ if grabbing it out of an
ODE source directory.  Some possible solutions for that would be to move
the path to the user-settings file into the system-specific section (if
it is the same on all non-Windows systems) or trying several different
paths (ODE_BASE/include/ode/config/user-settings,
ODE_BASE/config/user-settings, etc) and using the first working path.

Thank you for PyODE.  I hope you find these packages useful.

- Josh Triplett

Re: [Pyode-user] Collision detection and coordinates

[Matthias B. <ba...@ir...>]

Matthias Treitler wrote:
> I am very sorry that i am posting again my test program, but i have a little 
> problem which i am dialing with the whole day!
> I was inspired from tutorial2 and tutorial3 and i added in tutorial2 a block 
> which should be connected to the 
> ode.environment and with collision detection! But there is a little problem 
> with the coordinates and i don't know why!

I suppose you are referring to the collisions being somewhat away from 
the black rectangle. Your simulation is fine, the problem is just that 
you're drawing the rectangle at the wrong position. The origin of the 
GeomBox is at the *center* of the box, but your visualization has the 
origin at the corner. You have to shift the positions and draw like this:

   pygame.draw.rect(srf, (0,0,0), (coord(x-l/2,y+h/2),(l * (WIDTH / 6), 
h * (HEIGHT / 4))), 0)

- Matthias -