Custom Node GUI

Li Ting Lee reporter

For a start, we would like to process fbx assets on import and create prefabs out of them (which is similar to the dragon game example you showed at Unite). We have a naming convention within the fbx hierarchy for each child, and that name will decide what basic properties that particular child transform would have. With the current version of the asset graph tool, we'll be trying to generate a JSON/ScriptableObject to serialise all properties in the whole fbx, and store it within a new prefab as part of the workflow. i.e. 1 FBX => 1 Prefab with Serialised Properties

At the same time, we'd like to use the asset graph as an editor tool to allow customisation of individual assets (which I believe the tool doesn't yet support?). i.e. when i right click on a single prefab with serialised properties (as above), i can open a separate graph that shows the properties of the asset in separate nodes (which is where the node gui would be useful), and be able to further customise those properties by referencing other assets (assigning multiple materials, meshes etc), and lastly see the preview of the selections within the respective nodes. These customisations can then be re-serialised and stored onto the prefab, so that they can be edited again anytime via the graph tool. We need all these so that the serialised data within the prefab can be deserialised at run-time to get the properties.

Let me know if there are any parts above you need me to elaborate on. And thanks very much for reading this ticket!

2017-11-08T03:36:30+00:00

Comments (5)

Hiroki Omae
Hi, there is no close plan for node UI customization, but this is one of the feature I would like to enable in future. What do you want to do and how do you want to interact with the GUI? I would like to hear more about your needs.
- 2017-11-07T05:47:18+00:00
Li Ting Lee reporter
For a start, we would like to process fbx assets on import and create prefabs out of them (which is similar to the dragon game example you showed at Unite). We have a naming convention within the fbx hierarchy for each child, and that name will decide what basic properties that particular child transform would have. With the current version of the asset graph tool, we'll be trying to generate a JSON/ScriptableObject to serialise all properties in the whole fbx, and store it within a new prefab as part of the workflow. i.e. 1 FBX => 1 Prefab with Serialised Properties

At the same time, we'd like to use the asset graph as an editor tool to allow customisation of individual assets (which I believe the tool doesn't yet support?). i.e. when i right click on a single prefab with serialised properties (as above), i can open a separate graph that shows the properties of the asset in separate nodes (which is where the node gui would be useful), and be able to further customise those properties by referencing other assets (assigning multiple materials, meshes etc), and lastly see the preview of the selections within the respective nodes. These customisations can then be re-serialised and stored onto the prefab, so that they can be edited again anytime via the graph tool. We need all these so that the serialised data within the prefab can be deserialised at run-time to get the properties.

Let me know if there are any parts above you need me to elaborate on. And thanks very much for reading this ticket!
- 2017-11-08T03:36:30+00:00
Hiroki Omae
- changed milestone to 1.5
- 2017-12-08T08:15:18+00:00
Li Ting Lee reporter
Thank you!
- 2017-12-09T06:08:32+00:00
Hiroki Omae
- changed status to closed
This project is now migrated to Github. Open issues will be addressed in following page:

https://github.com/Unity-Technologies/AssetGraph/issues
- 2020-03-03T15:35:18+00:00
Log in to comment