Enabling better data flow between graph tools
The following is intended for informational purposes only, and may not be incorporated into any contract. No purchasing decisions should be made based on the following materials. Unity is not committing to deliver any functionality, features or code. The development, timing and release of all products, functionality and features are at the sole discretion of Unity, and are subject to change.
If you have accepted to use functional cookies and logged in using your Unity ID at the top right of the page, then sharing feedback is as simple as clicking a card below, selecting a topic’s importance, adding your point of view, and submitting. If you prefer not to accept functional cookies or log in, you will be prompted to enter an email address and validate it, so we know how to reach out when the topic evolves. For more information read the Feedback and privacy terms.
Our current migration to a common UX and data model for graph tools across the Unity editor, creates an opportunity to address interoperability of data between those tools.
We are investigating how this interoperability could serve our users. For example:
- How data would flow between visual scripting and shader graph, should visual scripting consider a shader graph as a shader or as a graph?
- How data would from between visual scripting and visual effect graph, what is the data collaboration expected between a visual script and particle simulation?
- ...