cfravel
commented
9 months ago I am closing this issue for now. If I can get a version of the model in which the bones and content are all entirely within the limits of the scene, and if it still laggy, i'll reopen this to get it looked at.
I have had a large amphitheater scene at 1,112 in the Conference Center for several years under SDK6 and previous versions, which had animated plants, as if moving in a breez. It worked in SDKs before SDK7, but in some version of SDK6 it stopped rendering.
I've now ported the scene to SDK7
When deployed as SDK7 it is terribly laggy if the amphitheater model is present. (But it is not laggy in the SDK preview)
The structure of the amphitheater is unusual, and probably the source of the reason it stopped rendering at some point in SDK6 and is very laggy in SDK7.
In particular, the modeller put some animation control bones and planes very far outside the ampitheater (and hence out of the scene boundaries.) However, these do not prevent the deployed scene from rendering the model
For now, I have removed the animations and bones from the model that I've now deployed at 1,112 in SDK7.
But I have alsso deployed a version that can be configured to use the model WITH animations as a lag-demo at -148,-137. As a courtesy to neighbors, this very laggy scene doesn't automatically render the model. There is an orangish box that toggles the model on and off. Initialy, each time the model is rendered, animations are off.
If my cloud database configures the scene to use the animated version of the model, you will also see a blue box, which can turn the animations on and off. You can can see that the lag is not due to the animations actually playing, because it gets very laggy just by rendering the model. (try turning or walking when it is displayed). If you turn the animations on with the blue box, you will see plants moving, and the lag doesn't actually get worse.