I am making a sidescroller in which the player can only move from left to ride.
I have noticed a frame runs very slow when there are a lot of objects (static physics) in it, regardless of them being far from the window and the objects' "inactive when far from window" property is set to either Yes or Automatic. The objects have to actually be destroyed in-game in order to improve the performance significantly. It doesn't matter if you are at a spot with close to zero objects or in an area where whole constructions are made of separate parts.
So I have considered changing everything so that an object will only be created when the player is near it. However, that is very complex to do, especially with physics stacked on top of each other. Besides, I would expect the "inactive when far from window" means pretty much the same thing. Why does it seem to make such little difference?