Marissa Farrell

Hi Will, Can you please post a screenshot? I think you're still using 2017 and I want to see if I'm seeing different things in 2018. Thanks!

Under what circumstances would you do that? I'm eager to find a solution...

Why not add a negative value? That would work.

With the Set Pen Color node selected, make sure Foreground is selected in the OIP.

ALSO. Instead of 0-255, the range is 0-65535.

A little trick, use the Vec 3D or 3D Vector node for your RGB values. EDIT: Vector, not Point.

So with my new align node, the network can be reduced to 10 nodes. I'll work on getting permission to add the newly suggested nodes to VW in the future. I know this doesn't help @Naos because he's still on 2013, but I did want to share anyhow. @Pat Stanford, you can use the XYZ nodes and skip the XY nodes. I think they were both created in hopes of reducing confusion, but if you wire an XYZ node to a 2D point port, it will only use the XY portion, unless I'm misunderstanding. Marionette_RevisionMarker002_MFarrell.vwx EDIT: You can do math on points just like this:

This is a semi-known issue. We had it fixed for a while, and then it broke again. I can confirm I've been seeing it here as well. I can say that using 2018 can help, if not completely solve, this issue though I see you're still using 2017. In 2018, we have a preference when you convert a wrapper to an object where you can suppress resetting on move (basically in 2017 and 2018 without that option checked, the object gets regenerated every time you move it in the document. In 2018, you can set the object to only redraw when you change a parameter in the OIP) The only way in 2017 to handle this when you have a buggy object is to move the object only in Top/Plan. What's happening is that the EAP object is using a coordinate space that doesn't align with your source geometry. I do believe that you can set your 3d position and then just nudge the object when you're in Top/Plan to get both objects using the same coordinate space. I may be wrong, but worth a try. (Just try to ignore that the object looks shifted in 3D, that 3D part is the thing that should move when you nudge in Top/Plan)

Honestly, @Pat Stanford, this looks like it would be my exact approach. EDIT: You are, however, inspiring me to create some alignment nodes, since I don't think we have any.

@Kevin McAllister It's no more helpful (arguably less useful) than using the Procedures dialog in the script editor, you really aren't missing out.

This is being looked into. Thanks, Mark!

It might not be directly a Marionette issue, but just out of curiosity, which nodes exist in both files? (that are being run) Also, are you using Undo at all? I've run into this a couple of times, but like you haven't been able to find the exact reproducible case so I can't report it yet.

@ChadL It looks like @Pat Stanford's post doesn't include the Marionette file, so I'm attaching my example here. For each class you want to add to your document, you would define the name in the OIP when a String node is selected. There are many other ways to define the list of names for your classes, but this is the most native. It's also possible to read them from a text file, or you could prompt the user for the names. In 2018 Marionette can create Menu Commands, which I think would also be useful; say you knew you would be using these classes in various projects but didn't want to create a template file. You could store this Marionette Network as a Marionette Menu Command and access it in whichever document you want to add the classes to. Please let me know if you have any questions. Marionette_CreateClasses.vwx

To delete a Menu Command, open the Marionette Commands file in the Marionette folder in your User Folder and delete the wrapper that corresponds to the command. I can't recall if you have to restart Vectorworks or not.

As assumed earlier, here's a Marionette example. This will randomize points within a rectangle (rudimentary, totally possible to do any shape you want) and create triangles within it. I then got a list of the points that shared corners with other triangles and gave them random Z values to make sure they all lined up. The result is a bunch of 3D polys.

Now, I know we all know I'm not trying to push Subdivision here (I'd be pushing Marionette if anything which I might once I get some time to mock something up), but I just wanted to show that you CAN do this with subdivision. I started with a rectangle primitive, split it into 32 rectangles (4x8) and added edges between corners to create triangles. I then moved some points in the Z direction and creased all faces. (Probably not ALL faces, because I can still see some imperfection, but you get the idea) If Kevin had creased his edges in his trial, you can get a lot closer to what you want than you would think. it's a bit of work, but here's a quick one I did. I'll attach the file as well. You can also later convert the subdivision to a mesh, if you wanted. The attached file has my original subdiv object as well as the object converted to mesh, then simplified with the new Simplify Mesh command. subdv.vwx

I want this, too. I've asked in the past, I'll ask again!

Just for another workaround until it makes it into a service pack (I'm not sure which one the fix will ultimately go into) If you select more than 2 objects to add surfaces, it will work. So instead of just drawing one rectangle over your hole, draw two that still stay within the bounds of the shape you want to fix, select all three objects, and add surface.

Works on both platforms.

The good news is that this was my first test, along with some other more complicated combinations, and all are working fine for me! Just have to wait for when it makes it out to you guys, which I can't say when.

I believe this is already resolved in internal builds, and I do recall reading a bug about it in our tracking system earlier in the cycle. Could you attach a simple file where it fails so I can check that your case is fixed here as well?

What types of objects are you trying to add? I'm not running into any issues here, but it could be something specific about the shapes you're using.

@twk A quick list of what's new in Marionette: Menu commands - Users can now convert their wrapper nodes to Menu Commands by right clicking and choosing 'Convert to Menu Command." These commands can be accessed by going to Tools > Marionette Commands Valve node - blocks the rest of the network from being run taking a boolean as input User Function node - Allows a user to define a 1-variable function in the OIP Marionette Preferences - allows users to cache the values in wires so when in debugging the network isn't repeatedly re-run to see what's running through the network. This is good for debugging networks with random values. File I/O nodes - Allows users to access information stored in external files such as .txt and .csv files. (Pretty much any text based file can be read/written with these nodes.) User Interaction nodes - These nodes will prompt users for input with a dialog box. Useful in Menu Command networks. These will hopefully all be gone over in files/videos. If you want any more information on any of them ahead of time, let me know and I can get into them deeper. EDIT: Users can now choose to prevent reset on move when converting a Wrapper to a Marionette Object. Prior to 2018, each time a Marionette object was moved, the entire network had to be run. This option will prevent rerunning the network inside of an object unless a change has been made to its parameters.