BlackMojito Posted April 8, 2018 Share Posted April 8, 2018 Setting maximum and minimum directly does not update the interval vectors and yet...we have some algorithms based on those vectors such as inFustum(). This can lead to bugs which are really hard to detect... Quote Link to comment Share on other sites More sharing options...
Wingnut Posted April 8, 2018 Share Posted April 8, 2018 Hi bMoj. You bring up SUCH great issues... thanks for your reports on these things. http://doc.babylonjs.com/playground/?code=refreshBoundingInfo Perhaps, this is what the refreshBoundingInfo() call... is to be used-for (after direct-setting bbox min and max). Not sure. I thought I should tell you about it. Stay tuned... more comments likely. Quote Link to comment Share on other sites More sharing options...
Guest Posted April 9, 2018 Share Posted April 9, 2018 they are not supposed to be overwritten actually I suggest recreating a new bounding box if you need to manually change them Or we can think about adding a function to force the complete rebuild of the bounding box Quote Link to comment Share on other sites More sharing options...
Guest Posted April 9, 2018 Share Posted April 9, 2018 Actually I went ahead and added a bbox.reConstruct API adam 1 Quote Link to comment Share on other sites More sharing options...
BlackMojito Posted April 10, 2018 Author Share Posted April 10, 2018 14 hours ago, Deltakosh said: Actually I went ahead and added a bbox.reConstruct API Haha. since beta4 or later? Quote Link to comment Share on other sites More sharing options...
Guest Posted April 10, 2018 Share Posted April 10, 2018 In the next npm update (likely in a few hours) Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.