Python collision callback #35460

New Issue

Angus Hollands · 2013-05-22T00:43:46+02:00

Angus Hollands commented

2013-05-22 00:43:46 +02:00

%%%This patch adds support for a collision callback.
Currently it only informs you of the object you collide with.
This patch leverages the existing collision callbacks for the Touch sensors.

In order to add more information one would need to expand the touch system.%%%

%%%This patch adds support for a collision callback. Currently it only informs you of the object you collide with. This patch leverages the existing collision callbacks for the Touch sensors. In order to add more information one would need to expand the touch system.%%%

Angus Hollands commented

2013-05-22 00:43:46 +02:00

Changed status to: 'Open'

Angus Hollands commented

2013-06-07 01:15:47 +02:00

%%%Added demo file and newer, fixed release (to support properly sensor objects)%%%

Mitchell Stokes commented

2013-06-11 04:39:48 +02:00

%%%First off, you've got some whitespace/clean/style changes in your patch; those should really be in a separate patch (e.g., the .style changes to CcdPhysicsEnvironment.cpp). Also, should we be able to register more than on callback like we can with KX_Scene.pre_draw and post_draw? Lastly, isn't the KX_TouchEventManager mostly just used for logic bricks? I seem to remember a different place where I added in calling the callback when I played around with this...%%%

Angus Hollands commented

2013-06-11 21:22:16 +02:00

%%%Added new file that removes CcdPhysicsEnvironment.cpp from patch.
Added list-style callbacks
Using touch manager. This is because the collision behaviour rules that the user is used to are implemented on top of bullet using callbacks defined in TouchManager. Without using touch manager, you'd be writing the same code, and a lot of work would be required to ensure that the two systems remain exclusive to one another.
The reason you didn't use it before was that you used directly the Bullet update, however, in the event of sensor objects, they only involve themselves in collisions if they have registered sensors, so we have to extend that to treat callbacks as "sensors"%%%

%%%Added new file that removes CcdPhysicsEnvironment.cpp from patch. Added list-style callbacks Using touch manager. This is because the collision behaviour rules that the user is used to are implemented on top of bullet using callbacks defined in TouchManager. Without using touch manager, you'd be writing the same code, and a lot of work would be required to ensure that the two systems remain exclusive to one another. The reason you didn't use it before was that you used directly the Bullet update, however, in the event of sensor objects, they only involve themselves in collisions if they have registered sensors, so we have to extend that to treat callbacks as "sensors"%%%

Mitchell Stokes commented

2013-06-18 06:28:03 +02:00

%%%Are we always guaranteed to have a touch manager, even if we don't have logic bricks that use them? I haven't dug into the managers too much...%%%

Mitchell Stokes commented

2013-06-21 00:29:46 +02:00

%%%Assigning this to Benoit for final review/okay.%%%

Angus Hollands commented

2013-06-29 14:09:39 +02:00

%%%Added fix for unusual physics usage%%%

Angus Hollands commented

2013-09-03 16:22:23 +02:00

%%%Added support for the contact points from Bullet. These are also provided to the sensors now. Had to add a struct container to support forward declaring a vector type.%%%

Thomas Szepe commented

2013-10-27 10:11:00 +01:00

%%%This patch is since r60132 14.09.2013 (r60208) in the trunk.
I think this patch can be closed.

%%%

%%%This patch is since r60132 14.09.2013 (r60208) in the trunk. I think this patch can be closed. %%%

Angus Hollands commented

2013-10-31 18:30:41 +01:00

%%%Added new file with support for contact point information. This is available from the sensor as well as the callbacks.%%%

Angus Hollands commented

2013-10-31 23:10:48 +01:00

%%%Fixed refcount error.%%%

Angus Hollands commented

2014-04-27 22:58:18 +02:00

Modified previous patches to avoid random containers and use correct dt.
This now is a final patch.

However, it doesn't seem sensible that the Impulse values change with substep changes, I can't produce reliable information. Best to avoid this for now.

Modified previous patches to avoid random containers and use correct dt. This now is a final patch. However, it doesn't seem sensible that the Impulse values change with substep changes, I can't produce reliable information. Best to avoid this for now.

Mitchell Stokes commented

2014-04-28 00:26:25 +02:00

If the patch is "final," maybe it would be best to put it through Differential?

Benoit Bolsee was unassigned by Angus Hollands

2015-06-19 21:17:46 +02:00

Angus Hollands self-assigned this 2015-06-19 21:17:46 +02:00

Angus Hollands commented

2015-06-19 21:18:06 +02:00

Changed status from 'Open' to: 'Resolved'

Angus Hollands closed this issue

2015-06-19 21:18:06 +02:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Python collision callback #35460