It seems to me a great idea. I had thought of a command called Overlap, similar to Collision, but that specifically ignores parallax. However, I fear it would take more time to implement.
These are users who have the same problem. I am looking for others to find a temporary solution in the meantime.
I’m a bit confused because I’m getting used to moving the camera.
I have noticed that if an object on a layer that is moved by the camera collides with another object on a layer that is not moved by the camera, the collision does not work.
Example: Let’s say it’s a side-scrolling platform game and there is no scroll to go back and there is a wall marking the left edge of the screen. I put that wall on a layer that doesn’t move the camera, this way even if i move the character then the wall alw…
When you rotate the layer camera, you’re doing just that - rotating the layer camera - and not rotating the scene. It just rotates the view of the layers. In this case, you’re rotating what gets sent to the screen by 90 degrees in a clockwise direction. So when you’re moving the red square from right to left on the screen, it’s movement is really rotated by 90 degrees anti-clockwise, and it’s really moving it down the scene.
To understand this better, add a third object above the red one, and s…
debugging video
I recorded a video to show what’s happening when I run the Vertical Slice. Debugging is enabled and if that looks confusing, I can take another video without the debugging and collisions shown.
Do collisions only work if they’re on the same layer? I’m asking because BookSprite is on the GUI layer and Locked in on a different layer. I don’t think I could put them on the same layer, though