We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This probably applies to other Serial devices as well.
In a Bonsai workflow run from unity, HARP device nodes / associated branches will not throw errors, but no data will be received from them.
Culprit is likely to be DataReceived callback which is raised on a secondary thread and may not be accessible to Unity runtime.
The text was updated successfully, but these errors were encountered:
Related issue in Unity discussions: https://forum.unity.com/threads/serial-communication-and-serialport-datareceived-event.139157/
If confirmed, we'd need to rethink how to workaround the integration.
Sorry, something went wrong.
Another related issue in unity bug-tracker: https://issuetracker.unity3d.com/issues/serialport-bytestoread-returns-null-reference?page=2#comments
An interesting comment can be found in the comment thread "Solved after set Script Runtime Version to Experimental (.Net 4.6 Equivalent)"
No branches or pull requests
This probably applies to other Serial devices as well.
In a Bonsai workflow run from unity, HARP device nodes / associated branches will not throw errors, but no data will be received from them.
Culprit is likely to be DataReceived callback which is raised on a secondary thread and may not be accessible to Unity runtime.
The text was updated successfully, but these errors were encountered: