Jump to content

Marissa Farrell

Marionette Maven
  • Content Count

  • Joined

  • Last visited

Everything posted by Marissa Farrell

  1. Could you be more specific about this? Does this mean you're naming the initial poly that you use for the rest of the generation, or are you naming each of the created solids? Also, while playing with this file, the network appears to be occasionally unstable. I'm not sure that this has anything to do with the issues you're getting, but wires are getting redrawn funny while I play with it. That may not matter in the end, as Marionette is more intelligent than its redraw capabilities, but you never know. When did you start creating this file, and what Service Pack are you using? Thanks! Marissa
  2. Whoops! You're right. I missed some logic. Should have tested a little harder before I shared Edit: My above post now reflects a node with the proper logic. I was summing to the wrong list initially!
  3. Marissa Farrell

    Bug Report

    Currently, Marionette doesn't account well for all types of user error, which is the case in these instances. Marionette runs the same way as a script in the script palette would upon execution. In scripts, there is no current check on whether or not a user would end up in an infinite loop, it's completely in the user's hand to be sure that is prevented. Because of this, I'm not sure how much error handling we can truly provide for Marionette, but sharing these encounters may definitely help us to handle things a bit better in node development. As for the request to have a button that terminates execution, that will likely not happen soon since, again, the network runs EXACTLY how a script would, and there is no way to break an infinite loop in that circumstance either, at least with how scripting is currently implemented, to my knowledge. (I also would LOVE this feature, I break Marionette frequently when creating new nodes) I'll keep my ear open for anything that may help in these situations.
  4. Hi Patrick! I'm attaching a file with a node 'Add Sequence' which should do what you're looking for. I'm up for an alternative name for the node, that was just the first I came up with this morning. Let me know if this helps! Marissa EDIT: The attached file has a revised (hopefully) working node!
  5. Ah! Okay! That's it. Because you created an object with them, it appears that they work correctly. If you were to just run an unwrapped/non-object network, they don't behave the same way. So essentially, it appears that within a Marionette Object (essentially a plug-in object) the nodes will behave as desired, but if you run an unwrapped network, results may not be as expected. I don't think that tweaking the node will be enough to get it to properly work outside of the Marionette object. I'll see what can be done on our end to *hopefully* get it to behave as expected more often. It's most likely an underlying issue with the application's implementation of Marionette as a whole. Thanks for helping me recognize this! Marissa
  6. @Stephen Sorenson, Have you tested these send nodes? I created the same ones months ago and found that they didn't behave as expected in a Marionette script, which is why I never shared them with the board. Just want to see if you've had better luck! Thanks, Marissa
  7. A wonderful example of light node use! Great job!
  8. Hi Alan! I'm attaching a file that hopefully you can use to follow along with. Control geometry is one of my favorite features of Marionette. Basically, you can use a piece of geometry that you've drawn on screen to create results. (Thinking back to your screen creation on this thread, I believe it may be faster to use control geometry, even! I'll put an example there.) In this file, the top Marionette object shows the result of using control geometry as a path to essentially 'duplicate along path.' At the bottom, there is the network I used as well as the control geometry. To create the object above, wrap the network, select both the network and the control geometry, right click on the wrapper, and select "Convert to Object Node." This should give you the same object as above. If you'd like to alter the path, you have two options. If you double click on the object, or use the reshape tool, you can alter the path the same way as reshaping any other NURBS curve. You can also right click on the Marionette object and select "Edit Control Geometry" where you can replace the current polyline object with any other object, such as a rectangle, circle, etc. There are many more ways you can use control geometry, this is just the way I most commonly use it. It's great for creating string lights Let me know if this helps or if you need more of an explanation. I'll also try to either have Jim create a tutorial at some point (if he hasn't already), or just make one on my own. Marissa
  9. @digitalmechanics, Assuming you know where your 2016 User Folder is, there is a folder in there called "Plug-ins" and inside of that "Marionette." Delete this "Marionette" folder and restart Vectorworks. Does the issue persist after that?
  10. Hi CarlJdP and Alan! Marionette uses mostly the same functions that the software uses when you use menu commands/tools/etc. Since the italics are lost using only the menu command, I don't believe we will have a solution for Marionette until that is looked into. I'm not sure if there's another solution for this, but at least with Marionette, I can't think of a way. Marissa
  11. Kevin, Yes. You're right. I do occasionally see the issue in SP2. I mostly work with versions that haven't been released to the public, and didn't think to check SP2 prior to replying to this thread. Since I don't currently see this with the version I'm working in, it may be cleared up in a future Service Pack, but as for SP2, the workarounds are the best bet for getting results when the script fails. Marissa
  12. Hi Alan, An alternative method to placing your polys at different locations of your screen would be to have them saved as a symbol and then insert them at each of the points you want them. Let me know if this is what you're looking for, or if you have any other questions. Marissa
  13. @CarlJdP, I'm not able to reproduce the issue you're describing. What are you changing the Dim node value to? I've played with a handful of numbers and have had no problem getting a new group output drawn on screen. Thanks! Marissa
  14. Last week I posted about my Stair Tool in progress, but I'd like to draw your attention to the potential of Curved Stairs! This is VERY VERY VERY basic, and cannot currently loop through more than 360 degrees (I promise I will build upon this), but here is an outline of how to get steps that rise circularly! It's also super ugly at the moment, this is really just a geometry test, but feel free to play around with it! [img:center]https://techboard.vectorworks.net/ubbthreads.php?ubb=download&Number=13762&filename=CurvedStairs_InProgress_MFarrell.PNG[/img]
  15. Keep in mind: All of this flattery is the only reason I keep posting But seriously, thank you both (and all) for your positive (and critical) input on what I present to you. It also gives me much more entertainment during the work day, which currently mostly consists of creating new nodes and trying to come up with something neat to create in a network and share. You all inspire me to solve your problems and requests - so keep them coming!
  16. Tried to upload this yesterday... But this one behaves better.
  17. Unfortunately no, this node will be more difficult to fix as the problem isn't with the script inside of the node, but rather the lack of a link to the software. I will push to have things move forward with it, and I will try my best to create a node that *may* be able to do the same functionality without having to wait for a service pack, but I cannot make any promises.
  18. So in this case, the "origin" refers to one of the corners of the rectangle - with this file, it is the bottom left of the rectangles. In order to have everything grow together, we need to create more relationships. Let me put together another example (I should have it ready and posted by tomorrow, latest). I would not have taken the center point approach, personally, but I can mock up an example using that method as well. Thanks for your patience! Marissa
  19. The attached file has a checkbox value in the OIP that will force a redraw with the updated symbol. In order to do this, I modified the "String" node in the script (it is named 'Symbol' to appear in the OIP) I'll try to think of a better way to implement the updating, but for now, this seems to work quite well! Let me know what you think.
  20. How bizarre! I can't even think of where the problem may be with regards to this, but the hang it produces is terrible... I'll try to isolate the issue and upload a revised file.
  21. Yes, you're right. The script that defines the geometry will only be updated if you alter it in someway - a way that you could "trick" it is to give it some sort of parametric control in the OIP that you could alter (that wouldn't actually change anything) in order to reset the object. I'll look into this and let you know if I find a sneaky solution!
  22. @ScottBFM: The problem isn't with the origin input, it appears to be with the "move" command. I'm not sure why this doesn't work well with Marionette Objects, but I have attached a revised network that when you convert to an object node looks as expected. In order to accomplish this, I added to the initial origin to offset the following rectangles. Take a look and let me know if you have any questions. Thanks! Marissa
  23. @ScottBFM A while back I created nodes to move front/back/forward/backward, but they proved to be unreliable in a Marionette network. This is being looked into, but for now it doesn't seem like the control is available. I will keep this thread updated if any progress is made. As for distribute/align nodes, I have not yet began creating them, but I can certainly move it up on my list! If I'm able to produce anything that will reliably work, I will share it here.
  24. Hi! So the 2D shapes you were seeing exist because my original network sort of became a hybrid object. I wasn't able to keep this functionality once you incorporated your additions (which I LOVE by the way! Very impressive!) What I changed in this file: I grouped many of your output shapes, just to clean up the object a bit (I couldn't get the 'extrude along path' object to group without disappearing... so that still just exists as is.) Inside of the "Keys" wrapper, I removed the 'copy' nodes from the script (that's where the 2D keys were coming from). I think that's all I did. Don't hesitate to ask anything else on this! And if you continue to add to this piano, please show me! I'm very interested!
  25. I can see that I may have come off as harsh and/or abrasive in my previous post, and that was the one thing I was trying to avoid most. Adrian, I also am very glad for your enthusiasm as you have generated many nodes that aren't readily available from us, and I commend you for it. I started after Marionette had already been almost completely developed for how we shipped it in the initial release, and it took me until a month or two ago to even have the passion I have for it now. Since then, I have been working on it as a side project - unfortunately I do have other obligations to my real role as a QA Specialist, so my time can't be 100% devoted to developing new content. I believe that what you have done definitely deserves compensation, if users were to use what you develop, but I suppose I would have had a different business plan in mind - such as providing them as separate packages so that a user could just purchase, say, worksheet nodes, or utility nodes, from you - rather than a whole chunk of nodes from different categories. My biggest concern was that I know (since I'm making them) that the other content will be available at some point, but if someone did not wish to wait, you could very well provide the resources. (I also cannot provide a set date as to when they will be released for a fair amount of reasons.) As for your arch networks, I very much wish for you to continue offering those! That is very exciting. If I could do the same with the definitions I create, I would absolutely do the same, but instead since I work with this fabulous software-producing-company, I just end up offering my creations for free to inspire others to learn by example. So to sum this all up - I am sorry for hindering you, I'm just looking out for the well being of all of our users. Oh - and just to clarify more how the ambient layer nodes work - the only way I've gotten that function to work is if I pass the handle to the active layer into them. Ambient light info isn't attached to just one layer, it is attached to the document, and that function works only if the active layer is passed into it, otherwise the values will not stick. It's most likely because somewhere between versions we changed how ambient light info works. Therefor, in my lights nodes, the "___ layer ambient ____" nodes are named without the "layer" part. I absolutely wasn't trying to say that you created anything incorrect, I just think there may have been a misunderstanding. I hope you continue to develop more Marionette networks because you make me feel like my attention to Marionette as a whole is worth it.


7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114


© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

  • Create New...