Touch Sensor missing. #37561

New Issue

Lance Flavell · 2013-11-21T03:33:32+01:00

Lance Flavell commented

2013-11-21 03:33:32 +01:00

System Information
Operating system and graphics card
N/A - happens both on my 64 bit Linux with Nvidia GTX 580 Classified, and on a school computer running 32 bit MS-Win.

Blender Version
Broken: Blender-2.69 r60991
Worked: Blender-2.8a r58536

Short description of error
The option to add a Touch sensor is missing from the "Add Sensor" list.

Exact steps for others to reproduce the error
Open Blender, go into Logic Editor and hit "Add Sensor" button. From the resulting pulldown list, Blender 2.69 has the last option (Touch) missing:

Actuator
Always
Collision
Delay
Joystick
Keyboard
Message
Mouse
Near
Property
Radar
Random
Ray
Touch <== this one is missing in Blender 2.69

**System Information** Operating system and graphics card N/A - happens both on my 64 bit Linux with Nvidia GTX 580 Classified, and on a school computer running 32 bit MS-Win. **Blender Version** Broken: Blender-2.69 r60991 Worked: Blender-2.8a r58536 **Short description of error** The option to add a Touch sensor is missing from the "Add Sensor" list. **Exact steps for others to reproduce the error** Open Blender, go into Logic Editor and hit "Add Sensor" button. From the resulting pulldown list, Blender 2.69 has the last option (Touch) missing: Actuator Always Collision Delay Joystick Keyboard Message Mouse Near Property Radar Random Ray Touch <== this one is missing in Blender 2.69

Lance Flavell commented

2013-11-21 03:33:32 +01:00

Changed status to: 'Open'

Lance Flavell commented

2013-11-21 03:33:32 +01:00

Added subscriber: @lancer-1

Brecht Van Lommel commented

2013-11-21 04:37:39 +01:00

Changed status from 'Open' to: 'Archived'

Brecht Van Lommel closed this issue

2013-11-21 04:37:39 +01:00

Brecht Van Lommel self-assigned this 2013-11-21 04:37:39 +01:00

Brecht Van Lommel commented

2013-11-21 04:37:39 +01:00

The Touch sensor was removed and replaced by the Collision sensor.

b9b806e0a0.

The Touch sensor was removed and replaced by the Collision sensor. b9b806e0a0.

Brecht Van Lommel commented

2013-11-21 04:39:01 +01:00

This was somehow missing from the 2.69 release notes so I've added it now.

Lance Flavell commented

2013-11-21 05:34:46 +01:00

Thanks for the update. I'd also looked up the documentation (and a range of user forum posts) before submitting - couldn't find any mention of it so posted. Pages like http://wiki.blender.org/index.php/Doc:2.6/Manual/Game_Engine/Logic/Sensors/Touch should perhaps also be updates to say the Touch Sensor has been depreciated, although I'm not sure who the correct authority for such documentation would be.
Currently unable to get the collision to act like touch was doing for me, but I'm probably missing something obvious like physics properties needed to make it kick in / pulse etc, so I'll play some more.

Thanks again.

Thanks for the update. I'd also looked up the documentation (and a range of user forum posts) before submitting - couldn't find any mention of it so posted. Pages like http://wiki.blender.org/index.php/Doc:2.6/Manual/Game_Engine/Logic/Sensors/Touch should perhaps also be updates to say the Touch Sensor has been depreciated, although I'm not sure who the correct authority for such documentation would be. Currently unable to get the collision to act like touch was doing for me, but I'm probably missing something obvious like physics properties needed to make it kick in / pulse etc, so I'll play some more. Thanks again.

Brecht Van Lommel commented

2013-11-21 05:43:26 +01:00

Added subscriber: @Moguri

Connor Schilling commented

2014-02-10 03:16:36 +01:00

Added subscriber: @ConnorSchilling

Connor Schilling commented

2014-02-10 03:16:36 +01:00

I noticed this issue as well. I'm quite devoted to the BGE as a quick sandbox, and the collisions sensor doesn't behave the same way, and is incredibly more complicated when you have to set up a property you don't need. I don't know why the developers would remove it...

Mitchell Stokes commented

2014-02-10 04:13:02 +01:00

The collision sensor should behave exactly like a touch sensor when set to material mode (the touch and collision sensor shared the same code for this).

Lance Flavell commented

2014-02-10 04:57:55 +01:00

It is actually quite straight forward. There is an M/P option in the collision sensor to toggle between Material or Property.

If set to M (material) the collision sensor will detect any object with the named material (same as the earlier Touch sensor)
If set to P (property) the collision sensor will detect an object which has a game property of that name. Game properties are made in the left margin of the Logic Brick window (game editor). It's the one you're looking at already if you've got sensors, controllers and actuators in front of you. The value of a property is irrelevant for collision detection; there just needs to be a property of the specified name.

If they fail to detect, check that the objects are set to something like "dynamic" (static does not work for collision detection, which I think is a key difference between the current Collision and the older Touch sensors). Also, it pays to have box boundaries or similar or collisions won't happen when objects end up inside each other.

Hope this helps.

It is actually quite straight forward. There is an M/P option in the collision sensor to toggle between Material or Property. - If set to M (material) the collision sensor will detect any object with the named material (same as the earlier Touch sensor) - If set to P (property) the collision sensor will detect an object which has a game property of that name. Game properties are made in the left margin of the Logic Brick window (game editor). It's the one you're looking at already if you've got sensors, controllers and actuators in front of you. The value of a property is irrelevant for collision detection; there just needs to be a property of the specified name. If they fail to detect, check that the objects are set to something like "dynamic" (static does not work for collision detection, which I think is a key difference between the current Collision and the older Touch sensors). Also, it pays to have box boundaries or similar or collisions won't happen when objects end up inside each other. Hope this helps.

Connor Schilling commented

2014-02-13 00:17:55 +01:00

Thanks.
I was quite unaware that you could just use materials like the Touch sensor, and had been creating properties specifically for this purpose, which was a bit of a waste. My main confusion was that the Collision sensor doesn't seem to detect objects as well as the Touch sensor did. Like you say, if the Collision sensor doesn't detect static objects, that would be the issue. That does bring up some restrictions in the use of the sensor.

Thanks. I was quite unaware that you could just use materials like the Touch sensor, and had been creating properties specifically for this purpose, which was a bit of a waste. My main confusion was that the Collision sensor doesn't seem to detect objects as well as the Touch sensor did. Like you say, if the Collision sensor doesn't detect static objects, that would be the issue. That does bring up some restrictions in the use 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

Touch Sensor missing. #37561