DOTS Visual Scripting 5th experimental drop

Hi everyone,

Drop 5 of Visual Scripting for DOTS is ready for you to try!

You’ll need to create a project using 2019.3.0b6
(Unity 2019.3.0b6)

New features / nodes

  • On key events

  • Move to

  • Get input / key – with pressed & released mode

  • Random

  • Wait until

  • Tracing by frame and by steps

Fixes

  • VSB-331 False positive loop detected if two branches are reconnected together
  • VSB-323 Errors flags not showing anymore on graphs
  • VSB-315 Editing sticky note background is black on black
  • VSB-314 Changing the value of an Enum or string based constants doesn’t update code
  • VSB-310 Live edit is broken when modifying components
  • VSB-268 Stickynotes disappears after adding new node

Known issues

  • Nothing special for this version

As with the previous experimental drops, this is work in progress that we share to engage in an open discussion with our community. Expect issues and weird workflows as we work our way up to a more final product.

Most notably, we are still far from the final user experience, the complexity you see here is not representative of what we want to deliver. We have not yet created high level nodes to reduce the number of operations or finalized our UI to make interactions as intuitive they can be.

So kindly take note of the usual disclaimers:

  • Not for production use.
  • Early picture of Visual Scripting, not be representative of the final version.
  • You will need to be tech savvy to use this version. Not yet ready for everyone.
  • Things will change.

As always, we are looking for your comments.

Enjoy!

6 Likes

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 :slight_smile:

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.

3 Likes

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.

3 Likes

got it, thanks

1 Like

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?

2 Likes

We’re aware. We decided to ship a work around using the old system while waiting for the new system to be DOTS ready in order to enable early users and get feedback. Swapping the implementation of a few input nodes won’t be that much work for us.

4 Likes

Thank you for the report. Have you connected the Move To “translation” port ? if you’re using the current query translation, just remove it, it will be used by default anyway.

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!

7 Likes

to move something, see our tutorial video below:

https://www.youtube.com/watch?v=9EuGd2WmDvU

whole series link:

https://www.youtube.com/watch?v=bptCy1ZDQ2g

6 Likes

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.

2 Likes

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

Thank you Wilson.

1 Like

Yes, that’s true. We’ll record the translation value in the MoveNext method instead of when passing the translation argument.

1 Like


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.

1 Like