feat(physics): add optional range to raycasts #798
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a fairly uncontroversial change, except for the part where it doesn't actually work - the
physics
example doesn't produce any raycast results with a set distance, even when the cube is obviously within 5 -Z units of the ground.I tried chucking in a
![image](https://private-user-images.githubusercontent.com/707827/265772319-c112e8f5-4dec-4299-8c2e-916328771e3f.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTgzNTc3ODMsIm5iZiI6MTcxODM1NzQ4MywicGF0aCI6Ii83MDc4MjcvMjY1NzcyMzE5LWMxMTJlOGY1LTRkZWMtNDI5OS04YzJlLTkxNjMyODc3MWUzZi5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNjE0JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDYxNFQwOTMxMjNaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1mNWJhOWU1N2Y0OTEzYmEwYzYxNWIzNThiNDQ4ODgyM2Q3OWI2ODFjZjUxOGVhZDFhNTUyNGVjN2FkNzY1MDg3JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.aPoLGwuu0e5mf7XbQye-_DJ-xnW5kK_2rAD8Yvmpe48)
dbg!
to see what the range being passed into the raycast was:but that results in the runtime crashing on startup:
@FredrikNoren did you use
f32::MAX
for a specific reason? Any FFI nasal demons I should be aware of?