Explanation video: http://screencast.com/t/zOCapfDV
Physics objects are put to sleep when they leave the screen. If you zoom the map out using mte.zoom you should see the physics hybrid display dim the offscreen objects (except for tiles, which are culled). You can add the cullingMargin parameter to your goto() call to specify how far beyond the normal screen boundary the engine should maintain the map and physics objects in an active state.
For example:
mte.goto({locX = locX, locY = locY, blockScale = blockScale, cullingMargin = {top = 400, bottom = 400, left = 400, right = 400}})
Doing this will increase the number of simultaneous onscreen tiles and may impact performance.
Physics objects are put to sleep when they leave the screen. If you zoom the map out using mte.zoom you should see the physics hybrid display dim the offscreen objects (except for tiles, which are culled). You can add the cullingMargin parameter to your goto() call to specify how far beyond the normal screen boundary the engine should maintain the map and physics objects in an active state.
For example:
mte.goto({locX = locX, locY = locY, blockScale = blockScale, cullingMargin = {top = 400, bottom = 400, left = 400, right = 400}})
Doing this will increase the number of simultaneous onscreen tiles and may impact performance.