Stomp command doesen't seem to work as expected.
1. The stomp command is applied to both the relative and absolute layer, regardles of where the phaser is. In my oppinion only the layer that has a running phaser should be affected.
2. Instead of knocking in the last single step value on the absolute layer it sometimes brakes the preset reference but I get the right values, sometimes it knocks in a random value that is found somewhere in the sequence. Sometimes it works as expected though. It's really not possible to use at the moment due to this inconsistency.
If I'm using the command in the wrong way, please tell me. I'd be happy if MA looked into this quite quick. I think all the new functions and features of MA3 is great. However I do think that MAs priotities is a bit of the rails when functions that worked perfect on MA2 don't work on series 3 yet. Like mentioned Stomp. But also X-buttons, Brake cue and I could make the list longer, but I won't right now.
In my oppinion, the priority should have been making what worked and what programmers used everyday on MA2 to work first. After that adding new functions.
It would be interesting to hear you fellow MA3 users oppinion in the matter.