Can you explain why this was removed? More than it just works now? The correlation between this and the scratch value and the entities actual bounding sphere all still feels a little funky to me.

If we do still want to remove this we will need to go through the deprecation process as this is part of the public API and people may be relying on it.

I have no answer for you @jjspace.

@jjspace I recognize that I have no idea why "it just works now!"

Even this bounding sphere parameter inside EntityView.update looks weird: why would you offer this as a parameter when there is no way to get a bounding sphere from an Entity in the public API?

In #3954, the bounding sphere was moved from EntityView constructor to update method, but again, why would you impose to provide a bounding sphere to EntityView (which is related to the high level Entity API) when you don't have the ability to get this bounding sphere from Entity's high level API?

Before #3954, the bounding sphere parameter in the constructor was documented as:
@param {BoundingSphere} [boundingSphere] An initial bounding sphere for setting the default view.

This "initial" aspect has completely disappeared. My guess is that it should be restored, AND that the Entity's bounding sphere should be computed from inside the EntityView implementation and should disappear from the public API.

Otherwise provide a public Entity.computeBoundingSphere method...