I’ve been playing with IanniX with OSC for a short while and haven’t been able to figure out how to trigger collision OSC messages to be sent. Presumably it should happen when the cursor on one curve meets another curve?
If a cursor’s message has at least one of the collision_* variables, then the parameter’s value is sent as part of the message, but only while the cursor is actually colliding with a curve. While no collision is occurring, that variable’s value is omitted from the message.
This means that the collision_* variable(s) would preferably be at the end of the list of variables in the message. Otherwise the position of the non-collision variables will shift depending on whether a collision is occurring, causing, for example the variable in position #5 to be in position #4 when a collision is not occurring, causing miss-assignment in the receiving application.
– Chris
Ah thank you, I see now.
I had thought collision messages were sent out on their own, not as parameters on a cursor message.
@heuermh wrote:
I had thought collision messages were sent out on their own, not as parameters on a cursor message.
Have you been discussing the branch by Chris or the main 0.8.21 version?
There is a collision message sent out on its own, and that is when a cursor has a collision with a trigger object. This is not a cursor OSC message, rather, it is a trigger OSC message. I don’t know about any other “collisions” in 0.8.21.
Cheers,
–Bob
I thought the question was about the collision_* family of cursor messages (see below).
Bob is right, that triggers send messages when collided with by cursors.
In 0.8.21 there are also these variables that can be used in cursor messages:
– collision_curve_id
– collision_xPos
– collision_yPos
– collision_value_x
– collision_value_y
When included in a cursor message, these are sent, when the cursor is colliding with a curve, and suppressed otherwise. (However note that there is a bug that prevents collisions with single-line curves from being detected.)
– Chris
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |