Shader Graph UX Improvements
Version: Lens Studio 5.15 (latest Spectacles compatible as of writing)
Feature requests:
- Batch auto-creation and wiring of input nodes with matching type based on the empty input sockets of a processing node (such as custom code).
Documentation on:
- the compilation life cycles of nodes
- the way ss_graph are stored in cache
- how updates to their contents are saved and guidelines for source control.
Auto layout of nodes in the graph or some approach to prevent overlaps.
Error translation layer for the logger, as current error messages can hard to decipher.
Bugs / Oddities:
- If an input node is wired to a processing node that's fed into the shader graph output, then renaming it will cause freezes and cursor movement midway through.
Autofill of input node 'Title' based on 'script name'
Custom code nodes do not support early returns, unclear if bug or current limitation.
A. Sumo
shared this idea
-
Thank you so much for the feedback and checking out 5.22! We're glad you're enjoying the Graph YAML update. It's a big one for us, too.
We like your idea of batch auto-creation and wiring of input nodes, auto layout of nodes, and autofill of input nodes' title based on the script name. We'll add those to our backlog.
Your points on the documentation are sort of implicitly resolved with the YAML update, but let us know if you have any other specific questions. Finally, code nodes do support early returns now.
Thanks again and let us know if you have any more suggestions or run into issues.
-
A. Sumo
commented
The biggest issues seem to be solved solved with Lens Studio 5.22.0 update.
The small oddities, even if they persist are background noise, because YAML Graph is a groundbreaking update.
Huge thanks to the team!
