DOTS Visual Scripting 5th experimental drop

Does it support Unity 2020.1.0.a3?
I got error messages here, and I couldn't find VS window and code view window on main menu.

 

compiling error when using coroutine with recorder.
seems problem of return ref.

 

"You'll need to create a project using 2019.3.0b6" 2020.1a3 is a lot older than .3b6

 

I'm a bit confused, why develop nodes that support the legacy input system when, by the time this is released, the new input system will likely become the default for the editor? The new system is also quite visual in the set up of actions and bindings so if anything it compliments visual scripting way better.

 

It will not become the default just yet, and it doesn't really support DOTS well yet.

 

On top of what I said in my previous post, the input system team are apparently looking at supporting DOTS for their package in the future. These developments need to be aligned better IMHO.

 

got it, thanks

 

2020.1 is not supported for that drop. There is a lot of new features that unfortunately breaks Visual Scripting and we need to tackle theses for the next drop.

I'll have a look at that one, there is a lot of unknown still there with coroutines but we smash the bugs as we see them. can you provide the graph where you had that issue?

 

Hello, Where can I get information to start the tests? How to do to move my character at least. ... sorry my english. What I want to say is that, I want to implement visualscripting tests to make my character move. Where will we get information? Thank you. Is posible test in 2D?

 

new tutorial video uploaded
It's the last one of this series. Hope you like it!

 

to move something, see our tutorial video below:

whole series link:

 

Yes I did, but disconnecting the translation node seems to be just a temporal solution to prevent recorder working here?

 

Hi! I'm translating your video subtitles into Russian. Chapter 1, 2 have already been translated, perhaps you can already approve them.

 

Sorry I didn't notice them. Subtitle just approved, many thanks!!

 

Thank you Wilson.

 

Bug report: I created a custom Function(as above), after saving and building all, 1) the customFunction used in the main thread turned into a error node and lost its connections with other nodes. 2) I cannot select or delete this bug node.

 

Will visual scrips get something like in this tutorial ? , called a super unit, kind like like a prefab for pieces of code.

 

It already has that functionality and so does, shader graph and VFX graph.
You can see it here in this video -

 

hub sez "project invalid"
how do you install it?

 

Honestly, 100% agree. Final DOTS visual scripting is a future thing. The disclaimer is "not for production" and new input is actually kinda OK for production so if it's not supporting that first then it's kind of odd.. I'm not seeing a rationale to keep old tat around.

 

Bug report:
Hereby I generated three "while loop", all of their indexes have the same default name "index",
In case their names conflict with each other, I changed their names, as shown in the pic.
But in code line 35, one index' name was not updated automaticly(VS Tool only updated its name in line 36), it cause error message in line 36.
The other two names, in line 42 and 49, were updated by VS Tool correctly.

 

Yep I thought so, I was implying that it would probably change much later anyway.

 

How efficient are those? For instance, afaik, Blueprints are way slower than C++ code that does exactly the same thing.
Do these get compiled into burst jobs or something? That would make them faster than my current code

 

Added the drive .zip in a project. At first this didn't work. Now it's fine

 

Overall feedback: a good preview of things to come, near impossible to debug. I think once proper console integration is added and zero occlusion policy in force it'll be very good.

PROS:

1. Drag and drop gameobject to create a query
2. click drag from an output circle auto ads a node
3. Will morph to updated code as DOTS changes (I presume)
4. graph wire snap is very good the way it shows the snap solution as a ghost wire
5. zoom on mouse cursor

CONS:

1. nearly impossible to debug: double clicking on a console error doesn't open the faulty graph!! For example "input axis is not setup" well it is but double clicking on that error doesn't open the point where it thinks there is a mistake.
2. create component is clunky, the save button is too small, the color scheme is wrong and it's at the bottom requiring too much unnecessary mouse travel and the code window keeps popping up, explicit only please, I don't care what the code looks like until I want to see it (check box option or "save and view code" button)
3. nonstandard GUI: The blackboard panel isn't in the panel menu item but a button yet it creates a panel, this is non standard and I've been looking for blackboard in quicksearch which doesn't see it. Make it part of the visual script panel or make it a panel
4. nonstandard GUI: + disappears and only shows up when hovering the title bar of the blackboard, this sort of web gimmick doesn't fit a professional app and occludes the real purpose of the blackboard
5. nonstandard GUI: Separator between visual graph windows is way too thin
6. node search requires space. this kills the muscle memory of someone who's spent years typing c# code so you need to accept search terms like "getinp" to find "get input"
7. the nodes are way too wide, the layout of drop 4 was much better: take for instance GetInput node, it's about 3x wider in drop5 than in drop4, no added information excuses that
8. the blackboard doesn't update the name when a graph is renamed, it needs to be clicked
9. when a required input isn't there, like the input choice of GetInput, the cell should be red, at the moment it's the same color as a valid entry
10. nonstandard GUI hard to see black on dark gray
11. big lag in scroll and dolly
12. very hard to know what's wrong, I think the code generated some times doesn't update, for example I don't see a system I just created (query from drop, onupdate, translate, 2 get input like Linda's tuto), and earlier it took me to close rider for deleted system to stop filling the console with red

WISHLIST:

1. The objects that match a query show up in some way, or at least a (#match) that can be clicked to highlight all objects in the project and the hierarchy. It's because making valid query is hard, that SQL stuff is a knew way of thinking so any help is appreciated.
2. auto save
3. when clicking on the title, blink the graph in the project view, when click sliding on the title, rename the graph
4. algebra is super unreadable in graph representation, add an arithmetic node that allows simple things, like input1+input2*input3*deltatime

BUG: illegal graph

 

Yes the background and the nodes are to close in color, that's why I asked to be able to change the black background to a custom color, to at least be able to fix it myself

 

Thanks!

+ 1 for configurable colors

 

@theor-unity Thanks for your reply. What is the next drop's focus?
How will it integrate with the unity GOAP?
I see there is a timeline that fills in when the record button is pressed, it looks like a trace timeline, which is WOW, hopefully I can make a system that works very soon. Perhaps I should start from scratch because I think this project got corrupted. (note to the team: give us a view of all the graph stuff that's floating around in memory, the entity debugger isn't showing this system but maybe it's because the system's query is faulty?)

12. I had to nuke and redo the system. It never happened again and I think it was an illegal GUI operation (a.k.a me fault) that wasn't caught by the GUI and wasn't caught by the generator as invalid. I think your generator does whatever graph the GUI tells it to.

wishlist:
2. save automatically on every change. And I realize that a save means a recompile but I know you folks have some ideas how to stream code. Perhaps also validate each system before pushing a compile, since they are independent of each other (got I love ECS for that)
4. just did, it's very nice how new nodes appear when a non recognized word is typed. Details like these make my day

 

is that record stuff the new timeline trace ?

btw: lerp in the expression node spits out a double instead of a float

 

I am collecting a few more oddities:

-1. can't space-create an expression when pulling it from the float output port of an input node in a macro. expression needs to be created by pressing spacebar in the background with nothing selected
0. can't pull 2 connection from the output port of an input node (in a macro), it creates an extra input node
1. get property doesn't seem to work intuitively, the current workflow is to chose from the context menu the get property value. what it should be is expand the get property node shows all available properties
2. in get property, values requires a context menu interaction, what it should be is click on the expand icon near the value word expands the value into its "ports"
3. I used the timeline tracer, the problem with it is when a node has input the values no longer show up, so instead of hiding the input field, gray it out so we can look at values as we scrub the timeline.

4. multiplication of queries might might be less performant?



Off course it's awesome to have such a low barrier of entry to ECS, I mean here I am with

 

Bug report:
1. cannot create a double type variable in componentdata.
2. it happens occasionally: unable to add componentproxy to object in hierachy list when there is no graphic asset in the project.
3. the sticky node's border is sticked to my mouse' pointer and cannot be released while adjusting its width.
4. no connection line is auto-created while creating a property node by dragging out of other node's slot.

 

When will drop6 be released?

 

a few new bugs:

Is it expected that play takes 5 seconds to spin up? I need to keep domain reload on or it craps out which seems weird since I don't use static variable, only visual ecs. can you explain why it needs domain reload?

Can't build a project that uses visual graph in beta 2019.3b11

Also proxys shouldn't show any such warning since they're commonly set by user. There is a [codethingy] for that you can add during generation.
SetComponent should have a vector as well as axis option like the rest. this one is for a float3

how do I get the 3 ports from an float3 expression node?
How does the expression node handle vectors stuff like this?

How do I build a float3 like say float3(sign(
How do I get ports from a v3 property?


So delta time is less than time ... someone on the team loves mobile phones a bit too much so get him on a week phonefree diet like these kids https://cbsloc.al/351VG9h


tooltip of a expression in-port should update to display the input type

 

alright can't add more than 5 images so i'll add a post for these bugs:

the way drop4 handled setComponent is better, a bit more intuitive. drop5 set component is probably buggy.
how are supposed to use set component to change the value of a component that is already in the query? i keep getting "Assets/BulletControl.asset: (26,60): error CS0103: The name 'bullet QueryEntity' does not exist in the current context". non of those names match what i see in the graph UI, there is a space between "query" and "entity" in the section that's below the "on update entities" title (this section needs a title)
does set component need another entity than the query of onupdateentity?

tried adding the entity and got this

direction is in the query at the top...

the other bug that just hit (was trying to make a macro to get 3 ports from one float3, can't figure that one out)
lost all links after deleting a macro made from a graph with floating nodes, a bug has been reported on this one, ill update with bug# when fogbugz finishes its big nnnnnggggg push

 

Damn! one more month to wait for drop#6, it's going to be rough because I'm loving this graph thing and wanted to do a lot of things with it but...

Graph is currently so buggy that it's unusable. And from the video I see that drop4 UI was better which means that you guys are not immune to BIS (Bad Idea Syndrome) and those eat up your time.
Because of that I'd rather see a very humble list which focuses on UX and bugs, and iterate more rapidly until the basic graph and codegen work. Then adding nodes will be easy on us as things won't break left and right ... and also we can do ECS stuff over the new year break.

 

Thanks!
We’re working on our next tutorial: Create a Neural Network with DOTS VS Tool and implement Back-Propagation.

 

Glad to see the progress, When will it be production ready ?
Will we be able to use Dots Visual Scripting with C# coding the traditional way ?