Moved cell/sec too high with TiledBackgorund

Link to .capx file:

drive.google.com/file/d/0BxoHB3AGjIpYMmpGN09XdlJGQnc/edit

Steps to reproduce:

1. Add a lot of Tiledbackground with physics behavior.

2. Set Immovable to Yes.

3. Check Tiledbackground collision in event.

4. Run Debug Layout.

Observed result:

We can see "Moved cell/sec" very high (Moved cell/sec = 480) because there aren't moving objects, but with sprite no problems (Moved cell/sec = 0).

Expected result:

I expect the same result of sprite, (moved cell lowest).

Browsers affected:

All browser.

Operating system & service pack:

Windows 8 x64.

Construct 2 version:

    From r155 to r158.2.

Sorry for English.

It would be nice to turn off permission in Google drive

Ops sorry. Try now :).

I'm not sure what you're looking to accomplish, you know tiled objects don't use collison polygon.

Yes, I know. I think that also with Immovable TiledBackground, moved cell should be 0 because no object are moving in the layout.

Closing as won't fix. This really does not matter significantly; moving cell is really cheap and quick and it's only 8/tick. It happens to objects along cell borders due to the origin being off-center so the Physics behavior seems to want to update the bounding box every tick. But this is pretty much inconsequential.