Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Old issue regarding Ray #72

Open
adam-law opened this issue Jul 24, 2015 · 2 comments
Open

Old issue regarding Ray #72

adam-law opened this issue Jul 24, 2015 · 2 comments

Comments

@adam-law
Copy link

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.

@rinold
Copy link
Contributor

rinold commented Jul 31, 2015

Think, we could add some global switch that can be used to turn on/off the sensors ignorance.

@adam-law
Copy link
Author

adam-law commented Aug 3, 2015

thanks :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants