Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Docs: default CollisionType on Actor is incorrect
See original GitHub issueSteps to Reproduce
- Initialize a new Actor
const actor = new Actor() - Check collision type
actor.body.collisionType
Expected Result
Collision type is CollisionType.PreventCollision as per Docs
Actual Result
Collision type is CollisionType.Passive
Environment
"excalibur": "^0.26.0"
Current Workaround
Initialize Actor with explicit collision type
const actor = new Actor({
collisionType: CollisionType.PreventCollision,
})
Issue Analytics
- State:
- Created a year ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
No results found
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m closing this for now, we’ve update the docs to match reality and theoretically fixed the pointerdown issue when physics is disabled 👍
@ivanjermakov Thanks again for the issue!
Thanks for pointing out the issue with
ex.Physics.enabled = false!I think it’s unexpected that
pointerdownevents no longer work in that situation 😱