DOTS Visual Scripting first experimental drop

Does it work with 2019.2 beta?

 

Ah, a lovely Monday surprise! What time do you think this will get off google drive and be a preview package? During 2020.1alpha/beta or before?

 

Thanks for letting us test it out!

 

I hope people will see it as something a bit new and DOTS-centric rather than the potential clone of blueprint some might be mistakenly expecting.

 

This is pretty important.
Just takes one official post stating this to avoid many months of misunderstandings, and all sorts of bad consequences really.
People are ravenous for an official blueprints clone as we've seen in the many threads over the years.

 

Would it not make sense to auto compile when packaging the game?

 

Nice!

Looks like the node gets blurry after you zoom out, and then click a node on the mini map ('report a bug' window wasn't working)

 

I don't dislike anything, I'm very happy. I'm just pointing out that you haven't actually explained the differences in thinking between the DOTS VS and general VS solutions at large.

The users coming in might need orienting better, is my point, else some won't know what opportunities this better design is offering them and will quickly drag you back to whatever it is they already know.

 

Will the DOTS VS support jobs(or does it currently?)? I've only fiddled with it briefly, but I didn't see any indicator of it being in there
- edit nevermind literally just read the double clicking the background to enable job support!

 

Sorry, but as someone who admittedly jumped ship to Unreal in part due to not wanting to code anymore (I forgot my last semicolon or bracket in this lifetime, it's not for me), will you be able to do full game using only Visual Scripting?

I ask, because the announcement with the switch to DOTS focus makes it sound (to me), like it's only a companion to that system and C# is still required to get a full game out the door...

Also, with the hundreds of add-ons from the asset store which already have custom editor UI and might not get updated for this anytime soon, will the Visual Scripting system automatically be able to hook into old add-ons, or will it require all add-ons to be updated in order to be able to talk to them?

 

Do I understand correctly that the graph doesn't exist in real game's runtime? (So it is a code generator and not a behaviour tree of sorts, and I could not live edit programmatically in the real game.)

 

Don't know about you but I had to remove both the Analytics and TextMesh Pro packages to get it to work.
I'm on a Macbook using Unity 2019.2.0a14 on Mojave.

 

Sorry, I guess my terminology is a bit fuzzy since stopping using Unity. What I meant, will Visual Scripting be able to set and get gameobject component parameters like these here, for example, without updating the purchased assets (Final IK in this case):

 

have you tried to re-import all? if not, can you try it and tell me if it works.

thanks!

 

Same result.

Code (CSharp):

1. Assembly 'Packages/com.unity.analytics/Unity.Analytics.Editor.dll' will not be loaded due to errors:
2. Unable to resolve reference 'UnityEngine.UI'. Is the assembly missing or incompatible with the current platform?

And errors all over about UI, Button and such being missing.

 

feel free to attach the full project here, ill try to have a look, im also using Mojave and didn't had this error

 

Does this aim to provide any value to those of us who like writing our code as code, or is it here just to be an alternative?

I like the way it looks. Will a version of this same interface be used for the full version of the entity debugger?

 

I'm loving the preview. The potential is insanely huge...

Though it appears unusable for me atm. I'm using Windows 10, 2019.2 a14:

I'm not sure how this happens yet, but my visual scripts always get corrupted eventually. The generated code is fine, so runs ok, but I can no longer use the visual script. I can't fix it, or add anything new. For example, I'm doing a simple ship moving sideways and rotating a bit based on user input:

So it applies a transform, and rotate, but as you can see below, the (Edit) Transform is gone, and disconnected from the inputs:



This happens anytime I create a basic game object, tag it with a ComponentData, then use it in a visual script, and try to do something like rotate / translate.

 

In case I wasn't clear, I was able to fix it by removing those two packages, I was just letting you know that it might not be working for everyone off the bat.

Drive link
What I did in this link:
- Unzipped the project and opened with Unity
- Re-imported the project
- Confirmed that the error persisted
- Deleted Library and zipped everything else

If you need Library too, let me know.

 

I'd like to see the concept of FrameGraph.Where:

• Pass is a single job processing data(components or other data) implemented by C# or VS
• FrameGraph is build/compile from Passes configured by C# or VS.

And then we can achive many great feature with it like:

• auto job dependency
• force decuple
• transient variable auto lifetime
• may auto generate netcode with some meta info
• switch feature or swap pass at runtime by dynamic build/compile

And here's pictures to show some idea.

 

Hi, I think your library might be corrupted, I am getting similar errors in our build server that get fixed if you clean the library.

Here I am trying to get more info about it https://forum.unity.com/threads/uni...pted-in-our-build-server.677338/#post-4540753

Hope it helps

Ruben

 

I'm getting the same issue. The translate node is broken. It corrupt my scripts.

 

I'm on the personal version of unity and graphs are looking weird with light skin on top of the visual script dark skin.

 

Is this going to be merged with Unity Tiny?

 

Great to see Unity working on this... I assume the horse has already left the stable however 'VS' in this thread is very confusing due to the association with Visual Studio. Can see this only getting worse and muddying the google waters as it proliferates.

Some sort of named title (like 'blueprints') avoids the problem but also probably easier for new comers... food for thought.

 

Perhaps UVS? Unity Visual Scripting

 

That has potential confusion with texture UVs.

 

I'll second this. It might seem like quibbling but it makes life slightly harder for everyone for basically forever!

It's damn hard to find stuff about the VFX graph because the official name is wordy and generic and everyone picks their own abbreviation.

 

While it makes sense to use abbreviation of VS for Visual Scripting, I would be voting, to find alternative naming, to avoid naming conflicts. GS Graphical Scripting, VDOTS, or DOTSV / DOTSVS as per thread naming. Just a thoughts.

 

^
That or simply DOTS Editor (DE) or even DOTS Designer (DD). Hard to confuse that with anything even outside of Unity.

 

All good

DE= Germany
DD= is double D

 

I like that propositions.
Just an extra thought, to expand upon.
VDE, VDD, as Visual Dots Designer / Editor

 

Did you try search for Unity DE, or Unity DD?

Is hard to avoid 100% any ambiguous dual meaning however.
But desired meaning can be obvious, in the content we are searching.

 

Yea Its all good, I'm already very happy that we get this toolset, no matter what the name

 

DOTS VS, or DOTS Visual Scripting is very clear to me.

The DOTS prefix is ideal because it's clear what break there is with mono land and you'll have DOTS Physics or DOTS Audio... etc

Simply pefixing anything with "Unity" when it's all inside Unity? not so useful

 

My further random thoughts.
DOTS Architect?
Some form of synonym of Blueprint.
I think people would like in general avoid of having VS in abbreviation, to avoid potential confusion (If justified?).
I suppose anything will be accepted. More is about deciding, which naming will generate less rant

 

No, keep it real. DOTS means Data Oriented Tech Stack and VS means Visual Scripting.

It's better to just tell people what something is rather than add a catchy name. Mecanim and Shuriken are bad ideas, Animator and Particle System are good ideas.