I'm a programmer and sometimes teach new-media tools such as Lens Studio and Meta Spark in Taiwan. Most of my students do not have coding skills, so Script Graph is a really nice feature to let them get hands-on making interactive experiences, and is also very easy to teach. (And they like the Patch Editor in Meta Spark a lot)

Although Lens Studio 5 hasn't officially supported Script Graph yet, as someone who is interested and cares about visual scripting, I have tried it out and would like to provide some feedback.

It seems to me that Script Graph does not necessarily need to cover all the scripting APIs, which might be more friendly for target users, and also can reduce lag.

-- About the Lag

In my experience with the current version of Script Graph (even though it's not officially supported yet, I can still add nodes), the biggest issue is the lag. When I try adding a node to the graph and right-click, there is about a 2-second delay before the list appears. In visual scripting tools, users will open this list very frequently, since we need many nodes to accomplish a task, this open-menu action should have no delay. A 1 or 2-second delay makes this tool basically unusable. (Imagin when you writing a script, and each time you write a function call or declare a variable it has to pause for 1 second)

-- Too Many Options

Additionally, when I right-click to access the API menu, there are like thousands of functions in the list. The lack of categories makes it hard for users to browse and learn. Given that the main target audience for Script Graph is those not familiar with scripting, this is scary to them. So it seems to me the function nodes list does not need to cover the entire scripting API; instead, it could focus on providing a more user-friendly selection of functions.