You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After making a tween, the transform position seems to be affected in a weird way. Even thought we see the position where we expect, if we query the Transform component, we get very weird numbers.
This example scene was broken by changing utils.path to using the Tween component. You can now only push each box once. See in the video that we're logging the position of the item before moving and after moving. Even though the item moves just a couple of meters, the end position is something completely absurd.
Screen.Recording.2024-01-03.at.17.53.51.mov
We go for example from (8 , 0.16 , 7) to (-36 , 0.1599999964237213 , 85)
What's weird is that the item does still look like it's in the right place
The scene was in coordinates 84,-5
I tried changing the coordinates of the scene to 0,0 and suddenly everything was fixed!!! The only thing I changed since the last video was the coordinates in scene.json.
Screen.Recording.2024-01-03.at.18.01.03.mov
That would also explain why I haven't been able to reproduce this issue in the Playground, because there we're always in 0,0
Here is a scene that works perfectly well: link
I have a strong feeling that this also explains the problems we have with tweens + trigger areas
The text was updated successfully, but these errors were encountered:
After making a tween, the transform position seems to be affected in a weird way. Even thought we see the position where we expect, if we query the Transform component, we get very weird numbers.
This example scene was broken by changing utils.path to using the Tween component. You can now only push each box once. See in the video that we're logging the position of the item before moving and after moving. Even though the item moves just a couple of meters, the end position is something completely absurd.
Screen.Recording.2024-01-03.at.17.53.51.mov
We go for example from (8 , 0.16 , 7) to (-36 , 0.1599999964237213 , 85)
What's weird is that the item does still look like it's in the right place
Find the scene here:
https://github.com/decentraland/sdk7-goerli-plaza/tree/main/push-box-puzzle
The scene was in coordinates 84,-5
I tried changing the coordinates of the scene to 0,0 and suddenly everything was fixed!!! The only thing I changed since the last video was the coordinates in scene.json.
Screen.Recording.2024-01-03.at.18.01.03.mov
That would also explain why I haven't been able to reproduce this issue in the Playground, because there we're always in 0,0
Here is a scene that works perfectly well:
link
I have a strong feeling that this also explains the problems we have with tweens + trigger areas
The text was updated successfully, but these errors were encountered: