I submitted version 1.4 to the Assetstore
– Class based versions of OSCEventTarget and OSCDispatcher
You can now handle OSC messages in classes that don’t derive from MonoBehaviour. This makes it possible to work only in code and in editors
– Created a demo editor to show the new class based feature to use in Unity Editors
– Added a demo scene with class based sending and receiving
– Fixed a bug with the explicit connection mode (OSC data of OSCEventDispatchers was always
reset when a status changed event was fired from a OSCConnection)
– Added a ClearData method to the OSCEventDispatcher class so you can clear the OSC data
– Added an OSCMessageReceived event to the OSCEventTarget classes. This event is additionally fired when the OnOSCMessageReceived method is called
This new update is more for coders who want to create a OSC setup from scripts. I tried to provide all the features you have with components. The only thing you can’t create from code is a OSCConnection.
I submitted version 1.3 to the Assetstore:
– Explicit Connection option:
This option is very handy if you have a setup where you want the flexibility to change your port or IP-Address of a OSCConnection, without to reconfigure all your OSCEventTargets or OSCEventDispatchers. So now you have the option to bind to a connection and don’t have to specify a given port or IP-Address.
– Updated the Mobile.Demo scene where you now can change the port/Ip-Address of your OSCConnections at runtime.
I submitted version 1.1 to the Assetstore:
Session file support:
– Store the latest data that comes with a OSC message
– Send all data to update the GUI state of an external app like TouchOSC
– Change in OSCsharp lib: made the TypeTag property of a OSC message accessible
-Type of the OSC data could now be verified with the Typetag string. (No GetType() necessary if you have performance problems)
– receiveAllAddresses property is now accessible via the component inspector
– UniOSCEventArgs could now be filtered by Group, AddressRoot or AddressIndex if the OSC address matches a specific pattern
– Documentation update
We finally submitted our UnoOSC asset to the Assetstore!
Hopefully the review process will be finshed quickly so we can provide more information and a link to the Assetstore.