Jerk seeks an answer

I get a 1 second freeze around 4 seconds after my level loads. I thought it was the mp3 audio starting but removing the audio made no difference.

I don’t instantiate anything or run any complex scripts on startup, and all the objects in my level are present (and visible) at the start, so I’m not sure what is causing the freeze.

I also get the occasional big frame rate drop…

I am wondering if it is related to sections of my landscape coming into view - a single 4000+ poly mesh, without occlusion culling (its not really possible to add culling, as the landscape has no rooms, or hidden areas). Otherwise the app is running at 30fps.

Any ideas why everything jerks to a halt sometimes?

one thing that can easily lead to such drops is the transfer of the texture to the graphics memory as the object comes in to view

also avoid to do useless string operations you can avoid as they will generate a lot of trash that has to be collected (cache getComponent calls and alike)

Thanks. The landscape itself uses one 512x512 texture, which is tiled across it, so the texture is always visible. It is large and does have a lot of polys though.

I can live with the occasional frame drop, but the 1 second freeze shortly after the level loads is irritating.