usePulseCollision does not work on Near and Radar sensor #35038

New Issue

Monster · 2013-04-20T12:38:37+02:00

Monster commented

2013-04-20 12:38:37 +02:00

Category: Logic

%%%usePulseCollision does not work on Near and Radar sensor.

Please find attached a test blend with near sensor.

TestCase:
Each time the near sensor triggers the controller the property "activations" will be inceased.

One sensed object is in sensor range from startup - detected at frame 0 -> property gets 1 in frame 1
Another sensed object moved into range at frame 0 - detected at frame 1

A) Without usePulseCollision the controller should not get activated -> property remains at 1
B) With usePulseCollision the controller should get activated -> property changed to 2

Both situations are tested
A) is fine
B) does not work

Remark: As there is no switch in GUI the sensor will be configured via Python controller.%%%

**Category**: Logic %%%usePulseCollision does not work on Near and Radar sensor. Please find attached a test blend with near sensor. TestCase: Each time the near sensor triggers the controller the property "activations" will be inceased. One sensed object is in sensor range from startup - detected at frame 0 -> property gets 1 in frame 1 Another sensed object moved into range at frame 0 - detected at frame 1 A) Without usePulseCollision the controller should not get activated -> property remains at 1 B) With usePulseCollision the controller should get activated -> property changed to 2 Both situations are tested A) is fine B) does not work Remark: As there is no switch in GUI the sensor will be configured via Python controller.%%%

Monster commented

2013-04-20 12:38:37 +02:00

Changed status to: 'Open'

Monster commented

2013-04-20 12:39:23 +02:00

%%%BTW. I use Blender 2.66a on Windows
The same effect is on Linux.%%%

%%%BTW. I use Blender 2.66a on Windows The same effect is on Linux.%%%

Thomas Szepe commented

2013-04-27 13:53:50 +02:00

%%%I made a fix (NearSensor_usePulseCollision.patch) for this bug.
%%%

%%%I made a fix (NearSensor_usePulseCollision.patch) for this bug. %%%

Monster commented

2013-04-30 13:57:48 +02:00

%%%very cool
Thanks%%%

%%%very cool Thanks%%%

Monster commented

2013-05-01 11:00:39 +02:00

%%%Tested with:

version 2.66 (sub 6), revision b'56420M'. b'Release'
build date: b'2013-04-30', b'21:31:38'
platform: b'Windows:32bit'

It failed the test.

Interestingly the first time I run the test it was successful. But all following test runs fail because missing activation. %%%

%%%Tested with: version 2.66 (sub 6), revision b'56420M'. b'Release' build date: b'2013-04-30', b'21:31:38' platform: b'Windows:32bit' It failed the test. Interestingly the first time I run the test it was successful. But all following test runs fail because missing activation. %%%

Monster commented

2013-05-01 11:37:07 +02:00

%%%I forgot: tested with:

version 2.66 (sub 6), revision b'56420M'. b'Release'
build date: b'2013-04-30', b'21:31:38'
platform: b'Windows:32bit'
%%%

%%%I forgot: tested with: version 2.66 (sub 6), revision b'56420M'. b'Release' build date: b'2013-04-30', b'21:31:38' platform: b'Windows:32bit' %%%

Thomas Szepe commented

2013-05-01 18:24:56 +02:00

%%%The properties "activations" are working correct on my PC.

But you need 4 frames to get the correct result from your script, because the collision sphere will be replaced with the "Reset Distance" sphere.

By the way. Every new pulse collision will react on the "Reset Distance" size because the sensor is still trigged.%%%

%%%The properties "activations" are working correct on my PC. But you need 4 frames to get the correct result from your script, because the collision sphere will be replaced with the "Reset Distance" sphere. By the way. Every new pulse collision will react on the "Reset Distance" size because the sensor is still trigged.%%%

Porteries Tristan commented

2015-10-28 22:17:54 +01:00

Added subscriber: @panzergame