General feedback of KHR_interactivity support #892
Description
Hi folks, as discussed in the Khronos Interactivity TSG meeting I'd like to summarize some feedback from tech artists and software devs about authoring interactivity with UnityGltf. These feedback is from a hackathon in July so it may be a bit outdated, but raising it here in case it's helpful.
The Good
First of all, thanks everyone for working on this. Many people are familiar with Unity and found the visual scripting easy to integrate with their existing Unity workflow. It's great to have glTF Interactivity support in a fully featured editor.
Constructive feedback
- Searching for nodes (particularly that glTF support) is a tough process.
- Would have appreciated warnings earlier in the process about how the animations would fail to export! I exported several times and only saw them towards the end.
- Some weird issues that weren’t documented or intuitive. Sometimes iterating over child nodes was not possible, so you would have to attach a graph to each object to animate it as an example.
- Debugging (both during development and export) lacks a lot of detail making the process difficult
Suggestion
I believe runtime playback for Interactivity like #849 will be very useful for other interactivity runtime developers and interactivity graph authors. This makes iteration faster - we won't need to export and upload the glb to somewhere else for validation. It's not great to manage a dozen versions of the same asset.
Steps to reproduce 🔢
N/A
Files to reproduce the issue ♻
No response
Editor Version 🎲
2021.3
Render Pipeline and version
N/A
UnityGLTF Version
N/A
Operating System 👩💻
macOS
When does this problem happen?
- Editor Import
- Runtime Import
- Editor Export
- Runtime Export
Additional Info 📜
No response
Validations 🩹
- I have searched existing issues: no issue already exist that reports the same problem.
- I follow the Code of Conduct
- I provided a minimal reproducible example, including files when necessary.