Stomp bugg?

BECOME PART OF THE COMMUNITY - Sign up here
  • 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.

  • 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.

    Very much disagree. Both familiar tools & workflows we're used to from grandMA2, and also new and more powerful functions should, indeed must be worked on at the same time. If you don't work on the new stuff early on, then once you've duplicated everything from grandMA2, you're back in the exact same place you were before. The groundwork for new core functionalities, for example Recipes, needs to be implemented early or else you have to tear down and redo lots of work later on which risks breaking things all over the place. Additionally, implementing something new, such as Recipes, early on allows users to help shape the direction of the new workflows and interactions while things are still fairly easily malleable.

  • Very much disagree. Both familiar tools & workflows we're used to from grandMA2, and also new and more powerful functions should, indeed must be worked on at the same time. If you don't work on the new stuff early on, then once you've duplicated everything from grandMA2, you're back in the exact same place you were before. The groundwork for new core functionalities, for example Recipes, needs to be implemented early or else you have to tear down and redo lots of work later on which risks breaking things all over the place. Additionally, implementing something new, such as Recipes, early on allows users to help shape the direction of the new workflows and interactions while things are still fairly easily malleable.

    That is absolutely a good point. I don’t agree completely, but interesting to hear your oppinion.

    However, I still would like this funktion to work.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!