|
| 12 Jul 2015 12:37 PM |
As a developer, if you need a part in a certain place but don't want it seen/affecting anything, you make it transparent and cancollide false. Raycasting and the mouse's hit position in general still detect these parts and react with them.
My proposition is to either add a property to parts that keeps rays/other things (maybe even .Touched events), or to not let raycasts fire if the part is invisible.
I know this is scriptable, but it would make everything a lot easier if it was addressed. |
|
|
| Report Abuse |
|
|
Exail
|
  |
| Joined: 08 Jan 2010 |
| Total Posts: 13355 |
|
|
| 12 Jul 2015 12:43 PM |
| scriptable as you said. it'd be easier though. support |
|
|
| Report Abuse |
|
|
|
| 13 Jul 2015 08:33 PM |
| Bump, this could be very useful for any games that have raycasting, which is a lot of them |
|
|
| Report Abuse |
|
|
|
| 13 Jul 2015 08:35 PM |
People will cheat on obbys though.
Once I see an explosion, I know it's a Michael Bay movie |
|
|
| Report Abuse |
|
|
|
| 13 Jul 2015 09:10 PM |
| How could this possibly allow people to cheat on obbies? This is about raycasting |
|
|
| Report Abuse |
|
|