Messages on multiple collisions #39493

New Issue

Richard R · 2014-03-28T20:41:48+01:00

Richard R commented

2014-03-28 20:41:48 +01:00

System Information
Windows 7, 2.4ghz celeron cpu, 2gb ram, Geforce 8400GS

Blender Version
2.69 and 2.7

Short description of error
Message sensors that receive the same message from multiple collisions at the same time, where their collision sensors are hooked to message actuators, are only sending a single pulse to the actuator.

I am not sure if this is a bug or if there is something I am missing. I know that if I swap the mesh on collision, that happens on all accounts of a collision per object regardless if the collisions occur at the same time. However, if I send a message on a collision, the actuator hooked to a message sensor is only triggered once.

I included bge_collision_msg_test.blend to prove this. The problem is also in blender 2.69. It'd be better to open it in version 2.69 where material swaps work properly. Open the file and run the bge, then take note of the debug property. When the sphere collides with 2 boxes, only 1 of the messages is sent to the actuator, as can see the value of "prop" being set to 1. If it worked the way I expect it to: it should have been set to the value of 2. I first tested it using actuators; then I tested it using python with some additional unique information (object name). Using the additional information did not help.

I thought the problem could be solved if I introduced a randomized timer before the call to sendMessage; but, it is not working even with a large timer. I looked at the console window after running the bge, and I can see that it is printing 2 different sets of values from the timer; but, the message received on Cube.002 is still only setting the value once. After another test, it is receiving both messages. I set the Message sensor to hook to a python script: print(cont.sensors['Message'].subjects), and it prints to the console: ['ishit', 'ishit']. So why is it not triggering the actuator to add 1 to the prop value, twice?

bge_collision_msg_test.blend

**System Information** Windows 7, 2.4ghz celeron cpu, 2gb ram, Geforce 8400GS **Blender Version** 2.69 and 2.7 **Short description of error** Message sensors that receive the same message from multiple collisions at the same time, where their collision sensors are hooked to message actuators, are only sending a single pulse to the actuator. I am not sure if this is a bug or if there is something I am missing. I know that if I swap the mesh on collision, that happens on all accounts of a collision per object regardless if the collisions occur at the same time. However, if I send a message on a collision, the actuator hooked to a message sensor is only triggered once. I included bge_collision_msg_test.blend to prove this. The problem is also in blender 2.69. It'd be better to open it in version 2.69 where material swaps work properly. Open the file and run the bge, then take note of the debug property. When the sphere collides with 2 boxes, only 1 of the messages is sent to the actuator, as can see the value of "prop" being set to 1. If it worked the way I expect it to: it should have been set to the value of 2. I first tested it using actuators; then I tested it using python with some additional unique information (object name). Using the additional information did not help. I thought the problem could be solved if I introduced a randomized timer before the call to sendMessage; but, it is not working even with a large timer. I looked at the console window after running the bge, and I can see that it is printing 2 different sets of values from the timer; but, the message received on Cube.002 is still only setting the value once. After another test, it is receiving both messages. I set the Message sensor to hook to a python script: print(cont.sensors['Message'].subjects), and it prints to the console: ['ishit', 'ishit']. So why is it not triggering the actuator to add 1 to the prop value, twice? [bge_collision_msg_test.blend](https://archive.blender.org/developer/F83265/bge_collision_msg_test.blend)

Richard R commented

2014-03-28 20:41:48 +01:00

Changed status to: 'Open'

Richard R commented

2014-03-28 20:41:48 +01:00

Added subscriber: @remnar

Angus Hollands commented

2014-04-30 21:42:05 +02:00

Changed status from 'Open' to: 'Archived'

Angus Hollands closed this issue

2014-04-30 21:42:05 +02:00

Angus Hollands self-assigned this 2014-04-30 21:42:05 +02:00

Angus Hollands commented

2014-04-30 21:42:05 +02:00

This isn't a bug. It's a design of the system - logic brick sensors are only triggered once per update. If you want to handle multiple collisions, iterate over the hitObjects or read the number of messages in the subjects attribute of the sensor.

This isn't a bug. It's a design of the system - logic brick sensors are only triggered once per update. If you want to handle multiple collisions, iterate over the [hitObjects ](http://www.blender.org/documentation/blender_python_api_2_70_4/bge.types.KX_TouchSensor.html#bge.types.KX_TouchSensor) or read the number of messages in the subjects attribute of the sensor.

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

Messages on multiple collisions #39493