Marissa Farrell

I just want to add on to this information - It's also possible to add Plug-Ins as well as other settings to your workgroup folder. In that instance, you would want to also create a "Plug-Ins" folder to the root of your WG folder. (I often don't do this, but during some testing instances I realizes that my WG folder was sourcing a plugin from an outdated plugin file from a previous version, so just a useful tidbit.) I host my workgroup folder on the cloud (using OneDrive), though Vectorworks does not explicitly support this. I do this so I can test different Marionette nodes on my office Win10 machine as well as my office Mac machine, and my home Win10 machine. I haven't run into issues as long as my files are downloaded to the local path on my machine. And just to elaborate on @zoomer's visual on how your workgroup folder should be defined within the preferences - This is what my preferences/directory looks like.

The behavior you are all seeing is not intended, to my knowledge. I'll have to do some testing, but nodes should never get seperated/look different when you change your layer scale. The nodes/network should stay the same relative to your page scale. Copy/paste is a case I didnt test during development. If you come across any other situations where the networks look different than before the layer scale was changed please let me know.

@Kevin McAllister, this is known. The reason this happens is because the Button node does not have an input nor output port and the previews are generated based on those. I don't know what's in the pipeline for this, but I can certainly ask. This will not affect anything Marionette-wise.

Alan, if you move the nodes that you copied over, do they change size? Like the ones that seem small with long wires... Thanks in advance!

@the frog, unfortunately many new features for Marionette in 2017 cannot be exported back to 2016.

Or how about a dimmer for a lamp object!

Since @DomCshowed off some fun with the slider control... Here's where I want to use it most! Unfortunately for the time being it's sort of laggy with networks that create/edit a lot of geometry, but definitely still usable!

Noted! I'll work on getting that going as soon as I can.

I updated the file in my original post. The new one should work cross platform. Mac users, please test away! Let me know if you run into anything. Thanks again, @Tom Klaber, for pointing that out!

@Kevin McAllister, Patrick beat me to it! You want to use the Set Marker node And he even linked you to the important info - it's like he's doing my job for me! (Thanks @Patrick Winkler )

Alan, Thanks for the update. We worked hard to figure out the best way to make sure that shifting doesn't happen with Marionette objects in 2017. I'll put a note in about walkthrough mode, although as you said, it's not common or advisable to move objects in that mode. Let me know if you run into it in other situations! I tested as far as I could, but you may find something I didn't!

Yeah, I've had some trouble getting the same setup on my Mac... I'll let you know if and when I get it there!

Okay skip the Mac users for now... I know what the problem is. I'll try to have a revision tomorrow.

Hey guys! I'm looking for users who have 2017 installed to test a network for me... It's the file I was using before for image processing. It should be cross platform, so both Windows and Mac users are welcome to give it a go, but you MUST use VW 2017. This network WILL NOT work in 2016. Attached is a file with a test image and a network. My suggestion would be to not change the test image, but if you really, really want to give it a go, make sure it's still a small image. I would recommend under 100x100 pixels - this network takes a while to run if you use a large file. (One of mine took over a day...) Some additional information to be aware of: 1) This network will install an external python library from the web. The library will be installed into your userfolder/Python Externals. You can delete this at any time and it should not affect how VW runs. 2) This network will create a 'temp' folder in your user folder. This folder is created to store the image that is exported from VW, then imported later. This is done because the Pillow commands require an actual image time to query. You can delete this later, if you would like. Every time you run the network, the image will be re-saved to this location, unless you edit the code. 3) Again, DO NOT use a large image. I promise, there's a chance you would regret it. So I'll end this with a 'use at your own risk' clause, and I would suggest saving/closing any important files you have open in VW in the off chance that you encounter a crash/hang/whatever. Please tell me if you encounter a crash! Also, I'll field any questions you have. If you want more info before giving it a go, let me know, and I will do my best to answer them. This is a very limited script at the moment, I still have a lot more in mind. I just want to make sure it goes well small-scale before I go big ImgProcessing.vwx

In case anyone hasn't come across the good news - the mirror node works in Vectorworks 2017! Be sure to check it out and see if it helps you in your workflows!

I see me!!! Weeeeeee!!!

This computer in my brain does not compute what you're getting at here...

Yes! It's a new function. It was actually created during 2016 and was intended to be implemented (which is why the node snuck its broken self in...) but never actually got approval to be merged in since it was written around the time of SP2, if I remember correctly, and not before the initial release of 2016. This is another reason why I mention every so often that we can't update the VS/Python API between releases. Please do test it thoroughly, though. I believe we can still FIX the API between releases. Just not implement new functionality.

Ha! I guess I forgot it's 'new' since our broken version existed all the way through 16. (I even had to go to the operations category to figure out what you were talking about. Shame on me...) But Kevin's right! THE MIRROR NODE NOW WORKS! (please, hold your applause) I'll cover that in a tutorial later

Alan, That just means I'll have plenty of time to have materials ready for you to learn from! You won't have to do any guesswork when it comes to setting these nodes up

As promised, I wanted to highlight some new things you'll see for Marionette in Vectorworks 2017! I've made a little video with snippets of the improved features, and although I haven't gotten to it yet, I'll go into greater depth of the more complicated features and how you could incorporate them into your workflow! (I know, I'm a slacker, but I still haven't gotten over hearing my own voice... so recording more videos has been slightly traumatic.) If you have any questions, big or small, I'm available almost all of the time (while I'm not eating or sleeping) to obsess over Marionette with you!

@RussU You can set a custom profile by setting the Member Type in the Structural Member Settings to "Custom" and then pressing the "Select Shape" button. You'll need a symbol of your profile in your resources of the file. Hope this helps!

The QA team, of which I'm a part of, has spent quite a bit of time testing the Dropbox project sharing. We haven't had many issues overall, and those that we did come across in testing have been remedied prior to release. The changes are reflected nearly immediately from what I've seen, both when we were all sharing from the office and when one/more of us were working remotely for testing. As always, when using this feature, if you come across anything that seems wrong, please report it! We can't fix it if we don't know about it!

Don't you fret! I have something queued up for the morning.

It looks like you have "Type" summarized. If this is indeed the case, what you want to do is select row 2 by clicking on the gray 2 on the left (which will highlight the entire database row), and then you'll likely see a little box with 'sum' at the top of column 'C'. If you click and drag that out of the column, you should see all of the fields rather than a summary. I'm attaching an image in hopes that it helps.