DOTS Visual Scripting 4th experimental drop

Dear Mr. @ans_unity

When I try to launch the project using 2019.3.0b1, I get the below error message.

Could you provide a list of steps to follow for the cleanest resolution of this problem?

Thank you

 

"Floating Graphview tool windows (you can move and dock the blackboard and the minimap)"

Does this mean there are now separate editor windows for each of those?

 

I am getting the same error in 2019.3.0b4.

When i click continue the Unity Editor loads but I do not get any of the Visual Scripting menus...

When I go to the Package Manager the list of packages does not load.

I also get an a lot of errors...

Packages/com.unity.visualscripting.entities/Runtime/EventSystem.cs(13,89): error CS0246: The type or namespace name 'EntityManager' could not be found (are you missing a using directive or an assembly reference?)

Packages/com.unity.graphtools.foundation/Editor/VisualScripting/Editor/Elements/Node.cs(6,19): error CS0234: The type or namespace name 'Searcher' does not exist in the namespace 'UnityEditor' (are you missing an assembly reference?)

 

thanks for the report, I'm investigating it... not sure why it's failing

 

Hi, are the following currently supported?

1) EntityCommandBuffer operations
2) ComponentDataFromEntity/BufferFromEntity
3) I see you can mark a comp as Subtractive, what about "Any"?
4) Creation of custom nodes from code (not Macros)
5) Custom/Multiple Worlds (e.g. how does live editing work when the system is running in multiple worlds?)

Also another thing... when I try to double click on EcsStencil, it just opens my text editor (with the yaml). EcsStencil is for changing the system dependencies right? I'm using 2019.3.0b4.

Thanks.

 

Hello,

Just a heads up, it seems the On Event node is broken in this version, seems to be a copy/paste error

Code (CSharp):

1. // GraphElementSearcherDatabaseExtensions.cs : Line 94 in the OnEvent block should be
2. data => data.CreateNode<OnEventNodeModel>(name, n => n.EventTypeHandle = eventType.GenerateTypeHandle(db.Stencil))

Other than that, this already feels very solid, good job!

 

(Since previous thread was closed.)
1. Will it be possible to access all of Unity API in Visual Scripting? The particular thing I am interested in is mesh data. I want to procedurally generate mesh.
2. Also, are we able to write our custom nodes and components in C# without vs? [it's important because sometimes developers want to be able to write code in C# but make high level custom nodes out of it], and how will the process look like?
3. Is there a possibility that we could write custom nodes with data for things like [example] Dialogue graph that supports branching on conditions, executes different actions... etc. Or should we aim to write our own graph solutions based on UIElements and GraphView to support this kind of behaviour?

 

Ok, 2 things.

First, when I Dock the Visual Script Window I can't see the nodes, they are still there since when I Box Select It gives me the option to change the color of the nodes, but I can't see them.

Second, Currently there is no Save System, Not a surprise being Just a prototype The Question is Will there Be an Intergraded Save System at Launch and How Extensive will it be?

 

Just want to say how much I appreciate the effort to make DOTs as usable in a practical sense as possible. Great work guys!

 

I got a error message of "missing VSArrayExtension" while trying to instantiate an entity with random position.

 

I would like to be able to change the background color from black to a grey color, could you pass this background color control to the unity color settings, so I can choose my own color?

 

Yes thanks!
This is the menu I'm referring to

 

Please allow us to use visual scripting to create custom editor, scriptable, timeline custom clip and tracks!

 

Yeah, I completely understand. There's definitely a lot works involved, I really hope unity's visual scripting solution can be deeply integrated into different development processes just like unreal blueprint (and better!).

 

How can I create a new array in this VSTool? I click on the "Array" checkbox and get an error message. And there seems nothing changed in Code line 20.

 

Is Unity VS going to be able to code an entire game when released or at some point?

 

I'd say that will come down to three things:

Which parts of Unity do not quickly get a DOTS/ECS equivalent.
Whether the Unity VS tools plug some of these gaps by deciding to go beyond the purely ECS world in some areas.
What sort of game.

Possibly the safest assumption is that as this is a long journey involving multiple immature systems that are still evolving, there will be a long period where a hybrid approach makes the most sense for many projects. One where ECS is used for certain core aspects of the game that require the performance benefits it offers, and this is what the visual scripting tools will be used for. Over time ECS will expand into more areas of Unity, and various tools including the visual scripting will take account of this. And help bridge other gaps, depending on what needs and pain points emerge.

 

I made a simple demo using Visual Scripting Tool. It's an ideal tool help me understand how ECS works.

 

VS Tool is the best coding tool of ECS Framework. It let me focus on game logic, rather than get frustrated with daily updated Struct Interfaces and tedious declarations.

 

I created a custom MacroNode as pic-1, and edit that node like pic-2, when I quit that node, and re-enter it , I got a new auto-layout as pic-3. Can you keep the user custom layout? Because those auto-layout nodes are overlap with each other. Another Question: how can I create an array of boolean in a custom node （in order to check if they are all true）?

 

Thank you for your reminding, I forgot bool4 works in this case. I wonder if BoidExample can be realized by VS-Tool, that example use a lot of Nativearray and NativeHashmap, that's why I mentioned about using array in VS-Tool for several times. I'm inplementing a tree-search project which also need array.

 

There might be another bug: sometimes when I click on GetProperty Node and press space bar, my unity crash at the moment.

 

What sort of limitations does DOTS have ATM? At one point it wasn't easy to use a prefab or use physics, and what can the VS package do right now? Can I learn it now or will I come to a barrier that will stop development?

 

theory-unity, is another experimental drop coming soon?

The good thing about the new 2019.3 betas is that ShaderGraph and VFX Graph are now working and I am thinking of using the VS Scripting to try to turn on/off some flags/tags for those 2 new features!

I have had trouble trying get the b1 drop to work with the newest betas ( i. e. b8 ).

 

Hey guys, we're creating a series of Visual Scripting Tool Tutorial video. Hope you like them!
youtube link:

 

Thanks!

 

This is really getting amazing.

Do you have any predictions of when a beta might arrive?

 

How do you reference a specific entity/GameObject rather than querying for a bunch of them?

 

Chapter 3： Instantiate Entity and Create MacroNode in VS Tool
Hey guys, hope you like our new tutorial video.

We also met some bugs during recording the tutorial and VS graph was crashed. Some of the connect lines disppeared when click play run button. Remind: ALWAYS BACKUP YOUR GRAPHS IN A SEPERATE FOLDER, OR YOU'LL LOSE ALL YOUR WORK WHEN CRASHED.

 

When will we be able to throw some code in via include or custom function node like in shader graph? The custom function feature within the graph being optionally include or code is such a lovely feature from shader graph that I'd probably actually switch our project structure to it.

As it makes a proper bridge between the real programmers and the designers.

 

see our video link above, it do support Macro Node.

 

Awesome, thanks. Not sure how I missed that.

 

See our Tutorial Video above, Chapter 3, to see how to grap a singleton entity and instantiate it.

 

Chapter 4: Boundary Detection and Destroy Entity within PostUpdate Command.
Our new tutorial is coming. Hope you like it!