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
I'm using Unity 2017.1.1 with the latest version of UnityOSC from github. The profiler reports 1,4ms execution time and 72KB GC allocation on my script, which I can trace back to the OSCHandler.Instance.SendMessageToClient() call. The function is being called three times per frame as I'm sending three parameter values out via OSC. See the screenshot for profiler details:
Unfortunately, having two instances of the script running in a scene doubles both, execution time and GC alloc, so this doesn't scale well. What can be done about this? Is this the expected behaviour or am I doing something wrong?
System is Win10x64 with an i5-3380M.
The text was updated successfully, but these errors were encountered:
To be honest, I haven't done any profiling on UnityOSC recently with latest Unity version, so I can't tell what should be ok numbers.
The library has some optimisations, but it hasn't been maintained since a while ago, so please feel free to carry out any optimisations you may need for your project and then do a pull request if you consider it.
I'm using Unity 2017.1.1 with the latest version of UnityOSC from github. The profiler reports 1,4ms execution time and 72KB GC allocation on my script, which I can trace back to the OSCHandler.Instance.SendMessageToClient() call. The function is being called three times per frame as I'm sending three parameter values out via OSC. See the screenshot for profiler details:
Unfortunately, having two instances of the script running in a scene doubles both, execution time and GC alloc, so this doesn't scale well. What can be done about this? Is this the expected behaviour or am I doing something wrong?
System is Win10x64 with an i5-3380M.
The text was updated successfully, but these errors were encountered: