Odd Issue with Get 3D Info Node

[ATalbot]

Hi Everyone, 

I'm having an odd issue with the Get3DInfo node and wanted to make sure I'm not missing something as this seems like a glitch.

 

I have a tool that builds video wall arrays by bringing in a symbol from the library and arraying them based on user input. I'm trying to add a feature to add a 'half row' at the bottom of the wall using a different smaller tile type. My idea for how to set z-height on this bottom row was to get the bottom Z height of the main array and then place the half row at that z-height, but the node does not seem to be functioning in that way. This Get3d node is getting 3D info from the group of the built video wall array, and does not seem to be getting any information from bottom z or top z on the node, as the move command doesn't do anything when given either z value, and nothing prints when I use the print debug node.

 

Am I missing something here? Is this node unable to get 3D z data from a group of symbols, or a nested group?

[Mirko Guhr]

Hi @ATalbot,

 

i tested the node on my system and it doesn’t seem to work properly.

If I open the node and then recompile it by clicking OK, the node works without any problems. However, I must open it first.

I haven’t done any further tests to see if the node remains stable when placed in a wrapper, or if reopening is necessary after a restart, etc.

Additionally, I don’t know if other users who use the script but have never opened the node will still encounter an error.

Maybe @Marissa Farrell or @DomC can help further.

 

 

Best regards

[Marissa Farrell]

If the issue is resolved on your computer by opening and closing the node's script when it's placed on the drawing area, then a fix would be to navigate to the Marionette Default Library.vwx file, edit the 'Get 3D Info' Symbol in the Resource Manager, enter and exit the script there, and save the vwx. 

I'm looking into why this is still an issue, but it seems like when an update to the python scripts (which are stored separately from the vwx) was made, the symbol for whatever reason didn't get refreshed with our update script.

 

Editing to add:

How we typically update Marionette nodes is to edit the python file and then run a script to push the update to the existing nodes within the vwx file to sync them up. Each time you open a Marionette node's script in the script editor, it reaches out to the referenced file and pulls from there which is why opening/closing the node fixes the issue.

[Mirko Guhr]

I understand, thank you for the response.