You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to "re-open" an old issue from Google Code, where a Box2d sensor blocks the ray casting used by box2dLights. The part of the code to return -1 in the callback when the Fixture is a sensor, is still commented out, hence the blockage.
While people could amend the source themselves, they'd have to do so on every release of box2dLights, which is obviously an inconvenience.
Edit: Just to let others know, filters set on the light via setContactFilter() works, but you'll have to set the the appropriate category / group / mask bits, for it work.
The text was updated successfully, but these errors were encountered:
I'd like to "re-open" an old issue from Google Code, where a Box2d sensor blocks the ray casting used by box2dLights. The part of the code to return -1 in the callback when the Fixture is a sensor, is still commented out, hence the blockage.
While people could amend the source themselves, they'd have to do so on every release of box2dLights, which is obviously an inconvenience.
Edit: Just to let others know, filters set on the light via setContactFilter() works, but you'll have to set the the appropriate category / group / mask bits, for it work.
The text was updated successfully, but these errors were encountered: