Old issue regarding Ray
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 265
- Forks
- 81
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the ray-casting callback used by box2dLights and inspect the commented sensor handling described in the issue. Confirm the expected callback behavior for Box2D sensor fixtures and verify that sensors no longer block ray casts while the existing contact-filter behavior remains unaffected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100