The error goes away when I instantiate BoundingBoxRenderer after Scene is created, however that would feel like a big breaking change for such a minor release.
Before reaching this workaround/solution, I tried to remove any babylonjs code containing substring bounding, but that didnt help. What other used features might be potentially causing this?
I am unable to reproduce this in playground yet, but if I’ll manage to do that, I’ll post an update here.
Thanks for the fix. While this indeed fix the error, it’s still somehow a breaking change which should be most likely addressed in the docs/changelog.
Previously the bounding box worked out of the box, now there needs to be an instance of BoundingBoxRenderer created to make it work.
For example the following page in docs:
It says that all you need to do is sphere.showBoundingBox = true;, which works in the playground (I assume BoundingBoxRenderer is somehow automagically created there?), but it doesnt work locally.
Just to be sure it’s not something in my project, I tried that with the following project template from Raanan, and it doesnt work there neither:
Huh, you are right. I am now slightly bamboozled, because I was using bounding boxes for sure, as I was posting about them a few times in the forum already. But now I have noticed that I cant see them. I’m not sure what has changed. Grepping my git repo for boundingBoxRenderer shows that I was never using it, and yet the bounding boxes were working for me previously
