Page 1 of 1

Nodes erasing themselves

PostPosted: Sun Sep 02, 2018 8:36 am
by djrappa
Anyone else seen this cool new feature?

Have a project that when it opens throws an error saying “value can not be null, parameter:key” and when you look amazingly just at random settings have wiped from nodes all over the project. Including within composite nodes.

It’s put a holt on 3 days of commissioning to a massive install and means we’ll have to fly back to this site at great expense to fix so I’m keen to solve it.

I’ve if course sent this to support.

Re: Nodes erasing themselves

PostPosted: Tue Sep 04, 2018 1:05 pm
by Christian Hinxlage
Hi Clint,

sorry, you ran into this problem, but I'm glad we were able to help you.
Also, thanks for reporting.

For everybody else, this is already fixed and will be implemented in the next release.
For now you can avoid running into this issue by directly selecting the target variable after creating a variable output node.

Step 1: creating a variable output node
Step 2: select the target variable within the node properties.
Don't save between step 1 and step 2.

Best regards,


Re: Nodes erasing themselves

PostPosted: Sat Sep 08, 2018 5:26 am
by djrappa
Just came here to post the exact above for anyone else also.

Should be noted that a rapid response was required to this problem over a weekend so whilst I have mixed feelings on there being so many persistent bugs in the software, credit must be given to the support team for jumping on this so quickly!

Thank you