Marissa Farrell

@Patrick Winkler, there's a workaround that can keep the object attached to the network. The only issue I'm running into now is returning the object to pass out of the output port. @RuudB, let me know if this helps at all. Right now, you just won't be able to manipulate the object after it's composed, until I can figure out how to find it... MarionetteCompose_WIP_MFarrell_v2016.vwx

Here's a network that may be similar to what you're looking for. This one will divide the line by a dimension length, but there will be rounding involved, so the lengths may not be 100% accurate. MarionetteDivideCurveByLength_MFarrell.vwx

The Divide Curve node ships with our default content. It's located in the Marionette Content under Objects > NURBS > Operations - NURBS.

Here's the Marionette script. Currently, if you name the poly you want to divide up 'test' and run the script, it will cut it up into as many segments as the 'int' node specifies in the Object Info Palette equally by length. In order to use the resulting poly, you can just ungroup the result object to detach it from the Marionette network. Also, if you want your result to be a NURBS curve at the end, you can simply add a 'Convert to NURBS' node to the result of the Polygon 3D node. (I recommend unchecking the "Keep Original Object" checkbox in the Object Info Palette with the 'Convert to NURBS' node selected, just to keep your drawing clean.) MarionetteDivideCurve_MFarrell.vwx

If Jim's method fails, Marionette can surely help! I can write something up when I get into the office this morning

In my experience, it could work, but likely not how you would want. Unfortunately at this moment, OIP controls don't have the capability to dynamically update, so your list may not always be up to date. I think, although I'm not sure if it works every time, that if you modify your node script in some way any time you add/delete jpgs from your referenced directory that it may update to reflect those changes, although it's not documented to absolutely work. I'd be happy to go over the limitations and why it cannot do this the way that we all would need it to, if you'd like, and if you do end up giving it a try, please report back on your attempts. It's useful to see how users are trying to use Marionette and where it is lacking. Definitely helps when I go back to report enhancement requests to the backend stuff where I don't get to play around much!

Here's an example - if you define the list outside of your OIP control in the Params class, you can extract the information from it in the RunNode definition later. Let me know if it's unclear, I can go into further detail if you'd like. @Marionette.NodeDefinition class Params(metaclass = Marionette.OrderedClass): this = Marionette.Node( "ReturnNameInsteadOfIndex" ) this.SetDescription('') list = ['Add', 'Subtract', 'Intersect'] op = Marionette.OIPControl( 'operation', Marionette.WidgetType.Popup, 0, list) op.SetDescription('') out = Marionette.PortOut() out.SetDescription('') def RunNode(self): self.Params.out.value = self.Params.list[self.Params.op.value]

@klinzey *chanting* KEVIN! KEVIN! KEVIN!

@har, I'll have to inquire about this. I'm seeing this both with the green symbol you've created as well as if I were to make a red symbol. I think it MAY have to do with a naming conflict somewhere. The best advice I can offer you for now would be to duplicate your Marionette Object on the drawing area rather than trying to always insert it from the RM, at least that could help to alleviate the extra clicks you're having to do with your current process... I'll report back if I learn anything!

I've never worked with Revit directly, but I was always a big fan of the constraints in Inventor, which I'm sure is similar enough. I've mentioned it here before, but my voice isn't nearly as big as our users, so the best I can do is back all of you up and share my knowledge of how they work elsewhere.

I also wish the constraints worked better. To my understanding, they only work in 2D reliably, and even then there are sometimes restrictions that I didn't think I'd run into. If you push on them getting improved, I would suggest pushing hard on getting 3D constraints implemented! That should solve a lot of the limitations, and I will certainly back you up internally.

Entered into our internal tracking.

Thanks! Could you also tell me what the radius of your arcs are, as well as your layer scale? I am able to see some of what you're seeing here, I'm just trying to get a sense of when the issue is more apparent, since I'm not seeing as much of an offset as you appear to be getting.

This makes me uncomfortable. I don't think I could sit as sloppily as I do in this chair...

@Kevin McAllister Can you attach a screenshot? I'm not sure I'm seeing what you're seeing, at least on Windows. I'll check my Mac shortly.

I wish the cats were allowed here! Unfortunately we now have a 'no pets' rule And thanks! They're for when my feet are really cold here (so almost always...)

This is (the current state of) my cube. All of those sticky notes are things I have planned to do for Marionette. It's a mess. Also, notice my 'lazy girl' foot hammock. One of my best investments. My home workstation often includes the kitties in real life... Once we finish moving, I'll share that setup (PS. I almost NEVER touch the Mac. It's probably my worst enemy as a QA tester.)

This is the only behavior I recall, at least it follows what I remember for 2016. I'll replace the .mp4 with a youtube link once I get one properly uploaded, I just figured attaching it would be quicker

@Gilbert Osmond The third click is to define the offset of the dimension from the object. It sounds as if the tool is working appropriately. I'm attaching a movie in case there's a misunderstanding. ConstrainedChainDim.mp4

Officially reported into our tracking system

Have you restarted Vectorworks since downloading them? I noticed that the cloud icon didn't go away until I restarted, even if I refreshed the libraries within the Manager. (This case is while downloading from the package manager while VW is running)

Yes, I see this as well. I moreso wanted to state that they do get installed properly, just not at the root of the folder which I think is what was being expected. They are somewhat scattered, unfortunately.

I believe the Arroway textures you downloaded go into the 'flooring' folder within the default content. I'm attaching a screenshot before and after the installation of those libraries. Do you see this?

My understanding follows your findings. Based on the hierarchy, if you have resources with the same names, only the one at the top of the hierarchy will show. That's why when I was referencing an older build with my workgroup folder, the plug-in was using an outdated reference, causing it to not work. I no longer reference older builds with my workgroup paths because of this.

It's also worth noting that it's generally required to either "Refresh Libraries" in the Resource Manager in 2017, or restart VW in order to get your custom objects to appear.