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
Not sure exactly how this is handled on the backend, but it would be nice to have the ability to assign the player and things like notes/walls to the same track, then use either method of position control to affect both objects.
So for example if you have both the player and notes assigned to the same track, you could use "position" on an AnimateTrack event to move everything in meters, or "offsetPosition" to move everything along the notes grid.
I get asked all the time how to move both the player and notes at the same time with V3, and I can never come up with a solid answer.
If there is something that's better than "move the notes with one event, then move the player with another, but multiply every value by 0.6", or "try some janky shit track parenting and see if that works maybe possibly", then feel free to close this and possibly update the documentation around player movement to mention that strat.
The text was updated successfully, but these errors were encountered:
Not sure exactly how this is handled on the backend, but it would be nice to have the ability to assign the player and things like notes/walls to the same track, then use either method of position control to affect both objects.
So for example if you have both the player and notes assigned to the same track, you could use "position" on an AnimateTrack event to move everything in meters, or "offsetPosition" to move everything along the notes grid.
I get asked all the time how to move both the player and notes at the same time with V3, and I can never come up with a solid answer.
If there is something that's better than "move the notes with one event, then move the player with another, but multiply every value by 0.6", or "try some janky shit track parenting and see if that works maybe possibly", then feel free to close this and possibly update the documentation around player movement to mention that strat.
The text was updated successfully, but these errors were encountered: