Touch x,y position serious problem after Crop/Overscan in 0.10.1 [VIDEO]

DanielDoe

Original project is in iPhone 5 resolution and after switching to iPhone 4 resolution project change position of some elements and change Camera.origin.X to keep everything visible. The problem is that after changing Camera.origin.X to -30 all elements that are touched change position to -30 relative to real touch.

Please check the video to make everything clear... Does anyone has the same problem?

mrpacogp

Private video ^^

DanielDoe

Thanks, now is public..

DanielDoe

No one really has this problem?

wpaten

I cannot speak to the Crop Overscanning issue yet but we always create our games for the ipad first and then go back and make it for the iphone next (changing all the scenes to 960x640. In some cases we had to adjust the placement of the camera by 40(y). We had to then go back and offset the touchable elements by a -40 to account for the new camera placement.

So basically this is not a Overscanning issue, but rather a Camera issue from what we have seen.

okpc

For my experience using a negative number in Camera.origin will cause issues on display.
So i avoid to do this.

DanielDoe

Thank you, so the solution is to move all the elements (in crop mode) to the right side insted of left and than use positive camera.origin.x.

DanielDoe

Unfortunetly positive camera.origin.x cause the same problem

RUPAS

then you will have to use letterbox ... how bad it will have black bars

Manto

What I would do is to change the constrain x behaviors when the game is played on iPhone 4.


Rule: if game.Screen.Size.Width = 480
constrain self.x to mouse.x - 30 (You may need to adjust this value)
otherwise
constrain self.x to mouse.x