Should Haxe coding be the priority and let down nodes logic ?
This is from using logic nodes some days.
Many functions are only available in haxe and missing on nodes
Node variables can’t get a name and use references from other nodes.
This makes the nodes logic like spaghetti without references.
When you define a new vector variable the input is X,Y,Z , there is no input to store an existing vector into the variable with a connection only.
Many nodes are not working or incomplete
LookAt doesn’t work, it would need some axis as parameter to specify the angle we need. GetRotation and SetRotation doesn’t work, they should be quaternions instead of vector3.There is no CreateTransform from position and quaternion rotation vectors
Many nodes need rework
For example the node separateXYZ , should not exist , all vector3 should have as available outputs : Vector 3, X,Y,Z
Like transform should have as outputs : transform, location, rotation,scale
Lot of nodes are not in Nodes documentation, nodes documenation lacks details (for example degrees or radians usage).
Well, for me it’s a no go using nodes in Armory 3D, it’s only good for toying
I think Lubos would benefit a lot from letting down nodes and focusing on Haxe only, this would avoid to do double work on haxe and nodes.