[Released] uNode - Visual Scripting [Support C# Import/Export]

@wahid_rachmawan
Thank you, working with uNode is getting more and more enjoyable.

But we still have some work...
Next ---> error when trying to compile:


P.S.
"""............................Also after parsing, there are problems with nodes "Divine", changes the output to the object type <--------->
Can you send me the script for i can test?..................."""
Do you still want this file? have you already repaired?

 

This bug also has been fixed .

Yes i need a sample script to fix it.

I'll upload new update on sunday.

 

I have:

Code (CSharp):

1. using UnityEngine;
2. using System.Collections.Generic;
3.  
4. public class A_TEST1 : MonoBehaviour
5. {
6.     public int variable0 = 10;
7.     public int variable1 = 0;
8.  
9.     public void NewFunction()
10.     {
11.         variable1 = (variable0 / 2);
12.     }
13. }

parsing... --->


And the compilation back to the C # code... --->

(Despite the errors the code is OK, although the "(int)" part is unneeded.)

 

@wahid_rachmawan

Performance --->
I think the loopObject variable is unnecessary, because tempVar can be used directly.


Also I think it's better to define the loop variable inside the for loop, instead of using a class variable.

And... parsing error --->

Code (CSharp):

1. using System.Collections.Generic;
2. using UnityEngine;
3.  
4. namespace test
5. {
6.     public struct S_Human
7.     {
8.         public string Name;
9.         public int Age;
10.         public Vector2 Position;
11.     }
12.     public class A_TEST3 : MonoBehaviour
13.     {
14.         public S_Human Create_Human(string name, int age, Vector2 position)
15.         {
16.             return new S_Human() { Name = name, Age = age, Position = position };
17.         }
18.     }
19.    
20.    
21. }

I also can not use initializers at all for such defined structures.

 

Fixed, will available in next update.

This is a bug, previously it use tempVar when you use 'Value' on the next flow.
Will be fixed soon.

I'll investigate and fix it ASAP.
Edit: It likely reflection can't obtain a parameterless constructor of a struct because it does not exist. I'll find another way to fix it.
Edit2: fixed in the next update.

Thanks for report it.

 

@wahid_rachmawan
Thank You very much.

Suggestion:
There should be a possibility to assign a starting value to a variable (both class and local), which isn't always possible now - for example in case of custom structs. And there should be a possibility not to assign it when it's not needed, which would produce cleaner C# code.

 

You can assign starting value for both class and local variable.
For assign starting value for local variable just double click on variable and it will show popup window which you can assign a starting value:


For struct the only way to have starting value is by auto creating default constructor which assign variable value, this will available soon.

 

Yes, I know, apparently I was wrong and it was all about my own structures.
(But... there should be a possibility not to assign value when it's not needed, which would produce cleaner C# code.)

Meanwhile, my current node reduction record:


The King is dead, long live the King!

 

Ah sure, for local variable you can leave it not assigned by destroying the instance value but on generate only struct type will leave empty and for class type will have null assigned to it (because to prevent error when you're generating code: get variable that is not assigned, i know it useful for newbie but assigning start value to null not have impact on performance).
For not assign value for classes will available soon.

Cool reduction, you can also reduce more by using Action nodes. With you current graphs i think using Action node reduce up to 4 more nodes.
Action node can be used to invoke or set value of a variable just like flow node do but the limitation is it's not supported interact with value node.

Thanks for your suggestion.

 

For now, I'm learning basic things...

next --->


And... --->

In general, there is something wrong with parsing scripts with enumerators. All of my C # scripts worked correctly, so ...

P.S.
Anyway, I will wait patiently for better and better uNode.

 

Can you send me the sample script for i can fix it....
Hope i will fix it before launch new update.

 

ok...
I have two scrypts:

Code (CSharp):

1. using System.Collections;
2. using System.Collections.Generic;
3. using UnityEngine;
4.  
5. public class A_test_enum : MonoBehaviour
6. {
7. }
8. public enum Enum_0
9. {
10.     small = 0,
11.     medium = 1,
12.     large = 2,
13. }

and...

Code (CSharp):

1. using UnityEngine;
2. using System.Collections.Generic;
3.  
4. public class A_test : MonoBehaviour
5. {
6.     public Enum_0 variable0 = Enum_0.small;
7. }
8.  

When I try to parse a second one, I have this error --->


EDIT//
If I have everything in one script - then parsing works correctly --->

Code (CSharp):

1. using System.Collections;
2. using System.Collections.Generic;
3. using UnityEngine;
4.  
5. public class A_test_plus : MonoBehaviour
6. {
7.     public Enum_1 variable0 = Enum_1.small;
8. }
9. public enum Enum_1
10. {
11.     small = 0,
12.     medium = 1,
13.     large = 2,
14. }

 

What the method do you use for parsing? (MonoScript, Source, or File)

Edit: Fixed in next update, this cause when parsing enum outside of source the type name is included.

Thanks.

 

Always MonoScript.

 

uNode v1.7.2 has been submitted for review!

changelog v1.7.2:
-New realtime C# Preview Windows.
-Added PerSecond value node.
-Improved CSharpGenerator
-Improved CSharpPreviewWindow
-Improved Editor
-Improved ErrorChecker
-Fixed bugs parsing property set accessor.
-Fixed bugs error on parsing enum type outside of source.
-Fixed bugs ErrorChecker error on check divide operator.
-Fixed bugs ErrorChecker error on check SetValue node.
-Fixed bugs error on generating property and constructor.
-Fixed warning related to null texture on draw node.


Download here : http://maxygames.com/download/

The new realtime c# preview windows with syntax highlighter help you learn c# with uNode.

Keep note that the c# output from preview window may have different with the final c# (this because final c# uses more options for make code more less and readable ex: remove type namespaces)

How to enable syntax highlighter:

• Need at least Unity 2018.1 or higher.
• Import CSharpParser.
• Syntax highlighter is now enabled.

 

Thank You very much.
Where to get my invoice number? EDIT// i have it

P.S.
Error when using IF in property setter also is fixed? (post 293, third error)

 

https://crazyminnowstudio.com/unity-3d/lip-sync-salsa/downloads/how-to-find-your-invoice-number/

Sure it fixed:

The If node is not the bug, the bug comes from property and constructor.

 

@wahid_rachmawan
Thank you so much, now I am going to sleep ... but I will check tomorrow.
I noticed that the error with the node "break" also applies to the node "continue"

I guessed.

 

Do you mean the warning?
I think i have fix it too, just check it out when you wake up.

I just post in this thread and my discord channel.

 

uNode v1.7.2 has been released on the Asset store.

 

I checked all reported bugs except constructors - and everything works, thank you.

But I have new ones.

I have three scripts --->

Code (CSharp):

1. using UnityEngine;
2.  
3. public class Script_0 : MonoBehaviour
4. {
5.     public System.Collections.Generic.List<UnityEngine.Vector2> Var_vector0 = null;
6. }

Code (CSharp):

1. using UnityEngine;
2.  
3. public class Script_1 : MonoBehaviour
4. {
5.     public static Script_0 Var_script0 = null;
6.  
7.     public static Script_0 Prop_script0
8.     {
9.         get
10.         {
11.             return Var_script0;
12.         }
13.     }
14.  
15. }

Code (CSharp):

1. using UnityEngine;
2.  
3. public class Script_2 : MonoBehaviour
4. {
5.     public int Var_int0 = 0;
6.     public int Var_int1 = 0;
7.  
8.     public void NewFunction()
9.     {
10.         Var_int0 = Script_1.Prop_script0.Var_vector0.Count;
11.         Var_int1 = (Var_int0 + 1);
12.     }
13. }

Parses the third script --->

Everything looks good when parsing, but when I try to do it myself in the uNode editor, I have errors suggesting that this is a non-static property - hence the request for instances


EDIT//

The compilation seems fine, but there is still error information - it applies to the four selected operator types.

 

Will be fixed ASAP.

Thanks for report it.

 

@wahid_rachmawan

next ----->
I have script:

Code (CSharp):

1. using UnityEngine;
2.  
3. public class Script_0 : MonoBehaviour
4. {
5.     public int NewVariable = 0;
6.  
7.     public void NewFunction()
8.     {
9.         switch (NewVariable)
10.         {
11.             case 0:
12.             case 3:
13.                 NewFunction1();
14.                 break;
15.             case 1:
16.             case 2:
17.                 NewFunction2();
18.                 break;
19.         }
20.     }
21.     public void NewFunction1()
22.     {
23.     }
24.     public void NewFunction2()
25.     {
26.     }
27. }

After parsing ----->

After parsing, I must manually delete unnecessary nodes "break". Besides, it would be nice if the compiler did not repeat the code.

P.S.
It's nice that I can help in improving this extremely cool tool.

 

Will be fixed ASAP.

Thanks for reporting it.

 

@wahid_rachmawan
Thanks.

Next --->
I Have script --->

Code (CSharp):

1. using System.Collections.Generic;
2. using UnityEngine;
3.  
4. public class Script_0 : MonoBehaviour
5. {
6.     public List<int> List_int = new List<int>();
7. }

I create second script in uNode ... --->


An attempt to compile --->

 

The bug will be fixed in next update.

Thanks.

 

@wahid_rachmawan
--->


In case of nested loops there are still private class variables used. For more clean code it would be better to always use in-loop variables, of course they should have a different name in each loop.

 

It look like bugs flow body is not detected by the generator, prev i just test with one node inside of flow body. The class variable should be used when foreach value is used by node outside of flow body, this to prevent error happened.
I will find solution to fix it ASAP.

And the warning unreachable block inside of switch statement i could't fix it in sort time because need a code analizer which is complex stuff.
For now need to manually remove block node to fix it.

 

Ok.
The most important are errors from post 321 and 325.

 

[Edit]
sorry, i just find required "Import CSharpParser" for about syntax highlighter issue
--------------------------------------------------------------------------------------

Hello, I just find an issues

issue on unity 2018.2.14f1 or above
-uNode runtime not work


issue on unity 2018.3.0f2
-red text color in editor
-uNode runtime not work


Thanks for good tool and support

 

@wahid_rachmawan
I create and compile to C # such a script:


And then the second one and when I add a variable an error appears --->



This error doesn't occur when everything is in one script.

 

Hi,

Can you tell me how to reproduce it?

Can you send the prefab of that bugs?
I couldn't reproduce the error.

 

import uNode 1.7.2 to new projects of Unity 2018.1, 2018.2, 2018.3 (import CsharpParser and change script runtime to .Net 4.x equivalent as well)

issues
-uNode runtime not work (2018.1, 2018.2, 2018.3)
-editor wrong to show red text (only 2018.3)

Thanks

 

Fixed in next update, thanks for report it.

 

@wahid_rachmawan
I did one more clean test project

First step (I create and compile to C # the first script) --->

All is ok.

Second step (I create a second script) --->

All is ok.

Third step (I add a variable of type Class_0) --->

Errors in the inspector and console

Unity version: 2018.2.18f1
uNode version: 1.7.2
I attach files --->

 

Fixed in next update, thanks.

 

@wahid_rachmawan
The private class variables that are used in loops cause problems with static functions, because (for obvious reasons) they can't be used in them.

 

Ah i see, it will be fixed soon.

 

@wahid_rachmawan
I met the first serious error.I could not reproduce it in laboratory conditions, but I decided to report it.
When I removed the function parameter - the uNode editor was completely clean and errors appeared in the console. --->


Closing the editor and restarting allows to open the script, but when I mark the function (left mouse button) in which I removed the parameter - the contents of the windows disappear again.
the only salvation was to remove this function (right mouse button) and arrange it from scratch.
I hope that you may find a clue in this matter - it is the first really serious error.

 

Fixed in next update.

Thanks for report it.

 

@wahid_rachmawan
Writing a serious issue - I mean one that spoils what is already done.

Small issue with nodes "Increment-Decrement" (no "energy" on exit) --->


P.S.
I wrote a letter to Santa asking for a new version of uNode on Christmas.

 

Fixed in next update.
I just forgot to generate the exit.

I'll upload new version before the Christmas.

 

@wahid_rachmawan
I found another issue --->


Nested IFs don't work properly, in this case there are 2 problems:
1. The first instance of "first finish" shouldn't be there.
2. "second finish" should be inside the else block.

P.S.
Also it would be nice to have an option to put the opening '{' in separate lines, for some people (like me) the code looks more clear this way. (like this) --->

Code (CSharp):

1. public class test_001 : MonoBehaviour
2. {
3.     public bool NewVariable = false;
4.     public bool NewVariable1 = false;
5.    
6.     public void NewFunction()
7.     {
8.         if (NewVariable)
9.         {
10.             Debug.Log("first true");
11.         }
12.         else
13.         {
14.             if (NewVariable1)
15.             {
16.                 Debug.Log("second true");
17.             }
18.             Debug.Log("second finish");
19.         }
20.         Debug.Log("first finish");
21.     }
22. }

 

Fixed in next update.

For the other code options, i think will be using code formatter after the code generation.
My plan will available in v.1.8, ofc the minimum unity version will be 2018.1 (this for make new feature which need to use .Net 4.x Equivalent)

Thanks.

 

What does this attached file do? I downloaded it but the issues are still there.

 

Got it, work on state flow but not work on regular flow.
Here is the updated nodes:

 

@wahid_rachmawan
This is probably the first serious issue - because it still does not work.

 

@wahid_rachmawan
I'm sorry, I did not notice that I forgot to include a screen with an error
This issue --->

 

Sorry for late reply, lately i very busy.

Ah this why i couldn't fix it, but its okay.
Try the new script:

 

@wahid_rachmawan
There is still an error that compiles false as true, if I do not connect anything to the true