Marissa Farrell

Alan, you're correct that the line of code at the top prevents you from making edits to the node until you alter/remove it (more on altering it later...) This allows us internally to track changes made to the default content which we could not do before.

Attached is a modified Popup List node that does what you would like. If you need any help understanding this method, please let me know. Marionette_Post46263-popup_MFarrell.vwx

@nicovanderschaaf What you want to use in this case is the "PIO Handle" node in the Object info category. The "PIO Handle" returns the handle to the resulting Marionette Object and can only be used in Marionette Objects. The best way to combine these together is with a "pass" node. I've attached an example. Let me know if you need further clarification. IfcEntity_MFarrellEdit.vwx

Hi Patrick, Have you run the "refresh libraries" command from the Resource manager? If you still don't see them after that, restart vectorworks. That's been working for me, let me know if it doesn't for you and I'll help you troubleshoot further.

I don't believe so. There was new functionality introduced, though I haven't worked with it enough to properly explain it, that will allow users to define parts to be textured within Marionette so that you can modify them with the OIP. I'll hopefully get a handle on that soon and put out a demonstration, and hopefully that will solve some of the issues people are facing.

Hey Alan, It appears that the Get Object Count node is improperly labeled at its ports. The input should actually be a LAYER, as the node will count all of the objects on a specific layer. I think that for what you're trying to accomplish, you can use "Get List Length" from the Data Flow category. I'll be sure to update that node to be more user friendly as soon as I can. Thanks for pointing this out!

Great! Let me know if you run into any further issues with it.

I haven't really gotten a final say on what state it is in, but as for the numbering not working past 9, try going through the alphabet instead of 10. so ... 7, 8, 9, A, B, C, ... Can't promise that will be the solution, but it may be the logic they've used on the back end secret to me. I still don't bother using it, and although I hate suggesting you don't as well, if you run into things like this the only thing we can do is wait to see if it gets accepted as a bug or not.

@herbieherb Are you using VW 2016 or 2017? Unfortunately in 2016, the Mirror node does not work. This was fixed in 2017, though, and in that version you should have no issues.

They apparently can tell when all of the mods are offline, or in my case sleeping...

@jmartinarch Using a 45degree guideline between where they exist and where you want them to exist, find where that line and the extension line from your middle object intersect, then you can rotate ccw. Does this help?

We try to catch them before you all see them! (Sometimes we just aren't around.)

I'm not sure of the current standing on internal testing, but as soon as we do a final round of rigorous testing with the official release of an operating system we can usually sign off on it. You can check here http://www.vectorworks.net/sysreq to see if the status has changed on an internal standpoint. I haven't seen many 'bad situations' with users on the forums, so far, but they can likely share their experiences with you prior to the official Vectorworks stamp-of-approval.

Please see this post:

I made sure to tell the right authorities that it's missing. I'll bother them again in a minute.

@zoomer I think it's funny because when I went to link to Jim's post about it, I saw you had even participated on the thread!

This is a known issue, my understanding is that there's an incompatibility with Safari 10 and VW Help. You can probably use another browser, or install Safari 9, at least that's what I've heard. We're waiting on support since it's not something we can fix directly.

It may also be useful to reference this post in this thread, as someone else has had a similar question.

I'm glad you've got it worked out! I think some of what you're running into when editing may be that you're editing the symbol that's already inserted into the wall, so the door position may look offset from the center. I usually edit the definition itself from the Resource Manager. I have sometimes found it hard to reference the other parts of the object while I'm various edit modes, but it sounds like whatever you're doing is still working out for you!

The Planar Boolean node set to 'subtract' is the same as clip surface. This node is in the 'operations' category, if memory serves correctly.

@Dubman I'm attaching a revision of your file that I hope is along the lines of what you're looking for. In short, here's what I've done. 1) For your hole-in-wall, it's necessary to make that object an extrusion. You can see what I used if you select your custom door symbol and go into the "Edit 3D Wall Hole Component". I basically just created an extrude thicker than your door, but with the same width. 2) To define where the object gets inserted in 3D, you can align your 3D parts of your object with its internal grid. I shifted yours slightly so that the center of the jamb is aligned with 0. You can see this if you go into the 3D part of your symbol and going to a Top view with the grid on. Does this help? Do you need more of an explanation? MyCourtRoom-3D_MFarrell.vwx

Have you tried inserting a new symbol fresh from the Resource Manager? Does a new instance show the wall hole?

My understanding is there is a back-end string comparison going on to compare naming conventions. I think it's still in a slightly unfinished state, some things haven't been matching up with what I would assume right out of the gate. I know they're still working to identify where the naming issues are.