'invert' sensor option doesn't trigger controllers unless it's positive once #32181

New Issue

Dalai Felinto · 2012-07-25T07:12:00+02:00

Dalai Felinto commented

2012-07-25 07:12:00 +02:00

Category: Logic

%%%how to test it:
0) select the default cube

create an Int property and set value 37
create a property sensor - mode Equal, Prop: prop, Value: 37
connect it with a Motion Actuator with rotation 1 for Z
play the game, the cube will rotate
now select invert in the sensor and set the controller to NAnd.
play the game, the cube will not rotate

I consider that a bug, though it's been around since 2.49 at least.

The same happens if I use an Expression Controller: to replace the And controller use 'sensor=True' to replace the NAnd use 'sensor=False'
(replace sensor by the name of the sensor)

attached is a sample file demonstrating that in trunk (>2.63)
%%%

**Category**: Logic %%%how to test it: 0) select the default cube 1) create an Int property and set value 37 2) create a property sensor - mode Equal, Prop: prop, Value: 37 3) connect it with a Motion Actuator with rotation 1 for Z play the game, the cube will rotate 4) now select invert in the sensor and set the controller to NAnd. play the game, the cube will *not* rotate I consider that a bug, though it's been around since 2.49 at least. The same happens if I use an Expression Controller: to replace the And controller use 'sensor=True' to replace the NAnd use 'sensor=False' (replace sensor by the name of the sensor) attached is a sample file demonstrating that in trunk (>2.63) %%%

Dalai Felinto commented

2012-07-25 07:12:00 +02:00

Changed status to: 'Open'

Dalai Felinto commented

2012-07-25 07:19:33 +02:00

%%%note: setting Level to true makes it work as I expected. So maybe not a bug after all. thoughts?%%%

Dalai Felinto commented

2012-07-25 08:01:31 +02:00

%%%note2 : setting pulse negative on also 'fixes' it. so yeah there are workarounds. Mitchell, any thoughts?%%%

Jorge Bernal commented

2014-05-27 11:02:59 +02:00

Added subscriber: @JorgeBernalMartinez

Jorge Bernal commented

2014-05-27 11:02:59 +02:00

I think this is not a "bug" related to the Nand controller. I mean, as you can see in the blend I've attached if you set it during runtime (pressing spacebar) the combination invert + Nand controller works right.

The issue I think is the following:

The initial State of the sensor seems that is set to FALSE. When you check for a TRUE condition (for example no "invert" press) at the beginning a pulse is generated. Also if you set the conditions during runtime it works OK.

But when you check at the beginning for a FALSE condition (invert button pressed) there is no change of state and no pulse is generated at the beginning. If you set it during runtime it works because the sensor state pass from a TRUE state to FALSE state and a pulse is generated.

BTW, If you check for FALSE condition (invert button pressed) with the false leveling pressed, it will work but it will do spending more processing resources as it will generate a pulse with each tick.

I think the possible solution would be setting the initial state of the sensor to something different to FALSE (i.e INITIAL_STATE) as it will generate a pulse at the beginning when it pass to TRUE or FALSE condition. I will check the code related to see if I can do a fix.

P.D. the best web page for BGE sensor pulses is http://gameblender.wikia.com/wiki/Sensors

I think this is not a "bug" related to the Nand controller. I mean, as you can see in the blend I've attached if you set it during runtime (pressing spacebar) the combination invert + Nand controller works right. The issue I think is the following: The initial State of the sensor seems that is set to FALSE. When you check for a TRUE condition (for example no "invert" press) at the beginning a pulse is generated. Also if you set the conditions during runtime it works OK. But when you check at the beginning for a FALSE condition (invert button pressed) there is no change of state and no pulse is generated at the beginning. If you set it during runtime it works because the sensor state pass from a TRUE state to FALSE state and a pulse is generated. BTW, If you check for FALSE condition (invert button pressed) with the false leveling pressed, it will work but it will do spending more processing resources as it will generate a pulse with each tick. I think the possible solution would be setting the initial state of the sensor to something different to FALSE (i.e INITIAL_STATE) as it will generate a pulse at the beginning when it pass to TRUE or FALSE condition. I will check the code related to see if I can do a fix. P.D. the best web page for BGE sensor pulses is http://gameblender.wikia.com/wiki/Sensors

Aaron Carlisle commented

2019-06-29 02:20:35 +02:00

Added subscriber: @Blendify

Aaron Carlisle commented

2019-06-29 02:20:35 +02:00

Changed status from 'Open' to: 'Archived'

Aaron Carlisle closed this issue

2019-06-29 02:20:35 +02:00

Aaron Carlisle self-assigned this 2019-06-29 02:20:35 +02:00

Aaron Carlisle commented

2019-06-29 02:20:35 +02:00

This task is being closed because the BGE has been removed in Blender 2.8.

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

'invert' sensor option doesn't trigger controllers unless it's positive once #32181