obj.raycasted is ignored when an object is hidden and again visible
#152
Comments
jscastro76
added a commit
that referenced
this issue
Dec 21, 2020
jscastro76
added a commit
that referenced
this issue
Jan 5, 2021
Minor version by [@jscastro76](https://github.com/jscastro76), some enhancements and bugs. #### ✨ Enhancements - #111 Show the dimensions of a model - #151 Remove auxiliary test method on `CameraSync` used to debug #145 - #156 Create an Orthographic view mode - #159 Create an example for FOV and Orthographic. - Added to [09-raycaster.html](https://github.com/jscastro76/threebox/blob/master/examples/09-raycaster.html) as it impacts in raycast and shows fill-extrusions and 3D models together - #161 Remove obsolete code that is avoiding to be used from React #### 🪲 Bug fixes - #152 `obj.raycasted` is ignored when an object is hidden and again visible. - #157 Bug draggging after removing an object. - #160 Bug using `utils.equal` #### 📝 Documentation - #158 MERCATOR_A constant unused, added an code comment to explain why it was deprecated (nor removed) - Updated [documentation](/docs/Threebox.md) (`tb.orthographic`, `tb.fov`) - Updated [README.md](/). - Updated [Examples](/examples) documentation.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Weird use case tested using blueprints that can be hidden dynamically through zoom ranges, once they are hidden and visible again.
There's a bug in
obj.visibility, is always making the objects visible for the raycast, not considering the value ofobj.raycasted. if an object is not raycasted, it should prevail unless it's changed through the property.The text was updated successfully, but these errors were encountered: