Jump to content

Marissa Farrell

Marionette Maven
  • Content Count

    1,225
  • Joined

  • Last visited

Everything posted by Marissa Farrell

  1. Marissa Farrell

    Marionette Stair Tool

    I've been trying to hold back from sharing this before it's ready - but I guess I'd also do much better with it if I had input from users! The colors of the steps can be ignored - I just had too much fun with it. I started this yesterday morning and still have much more work to do with it, but a sneak peek is always fun [img:center]https://techboard.vectorworks.net/ubbthreads.php?ubb=download&Number=13705&filename=MarionetteStairTool_InProgress.png[/img]
  2. 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
  3. Marissa Farrell

    EAP with a non destructive path

    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.
  4. Marissa Farrell

    Marionette Stair Tool

    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.
  5. Marissa Farrell

    EAP with a non destructive path

    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!
  6. @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
  7. Marissa Farrell

    Arrange, Distribute, Align

    @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.
  8. Marissa Farrell

    Marionette Piano Key Layout

    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!
  9. 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.
  10. Marissa Farrell

    EAP with a non destructive path

    An alternative, although not a true fix: A Marionette Object that uses control geometry to define the path! This network pulls in 'Symbol-1' as it's profile and allows a user to define a path. To do this: 1) Right click on the Marionette Object (EAP) 2) Select 'Edit Control Geometry' 3) You can either modify the polyline I have there, or delete that and draw something completely different. Each time you go into the control geometry it will still be of whatever type you drew it in initially (i.e. will not convert to NURBS, because that is done in the Marionette Script) To see the script involved, go all the way back out to the main drawing screen, right click on the Marionette object, and select 'Edit Script' Let me know if you have any questions. Marissa
  11. The following light nodes included in @ahedley's "Marionette Nodes Vol 1." can be found here, free of charge. 25. Create Light 26. Contains Light 27. GetBeamAngle 28. GetLayerAmbientColor 29. GetLayerAmbientInfo 30. GetLightColorRGB 31. GetLightDirection 32. GetLightFalloff 33. GetLightInfo 34. GetLightLocation 35. GetSpreadAngle 36. SetBeamAngle 37. SetLayerAmbientColor 38. SetLayerAmbientInfo 39. SetLightColorRGB 40. SetLightDirection 41. SetLightFalloff 42. SetLightInfo 43. SetLightLocation 44. SetSpreadAngle I would also like to note that the nodes referring to a layer's ambient info/color are misleading. There is no way to set a specific layer's ambient info. Furthermore, by no means discouraging the desire to monetize off of Marionette content, all of the nodes that may be creating using this reference, that will still work in 2016, have already been planned to be released for free on the forums as well as possibly in Service Packs.
  12. Marissa Farrell

    Objects - Lights

    Hi Everyone, Attached is a folder that includes light nodes, since currently Vectorworks does not ship with them. Let me know what you think and I can continue to expand upon them! Since the default library does not have an RGB input node, you can use the "Vec3" node to input RGB values. These values range between 0-65535. Feedback is welcome and appreciated! -Marissa
  13. Marissa Farrell

    Objects - Lights

    A note on using light nodes in a Marionette Object: I have had mixed results on whether or not the light would display as 'on' while rendering in renderworks - where you would REALLY want it most. If you were to just use the nodes in a network and produce something, they should render in all modes - again, the Marionette OBJECT has been my only issue, and not even always. I'm working to find a way around it, but I just wanted to share this knowledge before someone may ask about it. Thanks! Marissa
  14. Marissa Farrell

    Modelling a pyramid shape

    Laughing at my desk now. But thaaaaanks
  15. Marissa Farrell

    Modelling a pyramid shape

    Just for fun - A Marionette object that allows inputs for A, B, & C.
  16. Marissa Farrell

    Pull input from worksheet

    You can either zip it up and attach it to this thread, or you can send me an email at --- It's really whatever you're most comfortable with!
  17. Marissa Farrell

    Pull input from worksheet

    Okay great! I can definitely try to mock something up for you. Just to make sure I have everything correct in my head, could you give me a file with an example of how things should be laid out? It doesn't have to be extensive, just a couple examples! Thanks!
  18. Marissa Farrell

    Pull input from worksheet

    Hi Diana, Are you asking if you can use Marionette to locate an excel file to import from? I'm going to guess that no matter what you're actually asking for, it can be done. Worksheet nodes just haven't been implemented in any of our release versions. I'm working on a worksheet node library now, but if you give me a good description of what you'd like done, I can try to put something together for you to use! Thanks, Marissa
  19. Marissa Farrell

    Golden Angle Node

    Update: The golden angle node in this file should allow you to reverse the direction via checkbox (boolean) in the OIP, and it allows you to set where the centerpoint of the spiral is... you can also use the output orientation to set the orientation of the object being drawn to face towards the center. This still needs to get fixed when you check 'clockwise' but I'll have it fixed soon! Let me know if you run into any issues with it, or if there's another way you'd like it improved! Marissa
  20. Marissa Farrell

    Create a 3D Grid of objects

    So here's another method of accomplishing your task, though I'm sure there are many other ways! This reduces the use of that duplicated part of your network by using lists. Let me know if you want me to go into more detail! Marissa
  21. Marissa Farrell

    Marionette - Versioning System

    I want to second this statement. I work with the Quality Assurance team, as my primary position, and there are a few of us who are obnoxiously passionate about improving user experience. Unfortunately, things take time and we need to get our opinions further up the food chain in order for anything to really make it into the software. My personal on-the-side project is improving Marionette as a whole, my current contribution is making sure that the default content that we ship with is up to par, and unfortunately a lot of iffy stuff slipped through the cracks, but we are definitely working to clean it up. Version control has been near the top of our list as to improvements for Marionette, and although it won't have been implemented at the beginning as it should have been, we can take the current status of the nodes and consider that our 'first version', once we all decide that's the way to go. Sure, it may not entirely reflect how many times we've edited it up to now, but it at least helps us moving forward. I also want to make it very clear that Marionette is VERY MUCH in working condition. There is absolutely nothing preventing a user to create a network and have it do as he/she wishes. I will honestly say that there are currently nodes that aren't up to par, but that in no way prevents usability of Marionette on its own.
  22. Marissa Farrell

    Roof and Slabs

    Looking into this, I believe there are some issues with the roof nodes. I've gotten close to getting the results I want, but it hasn't been easy. Let me take a look further and see if I can get a working example, and see if the nodes are even working as intended (which I don't believe they are). Thanks for your patience! Marissa
  23. Marissa Farrell

    Marionette Method SetLinksObjects()

    I'll have to skim through my current resources and notes and see what I can put together. I often come across things that I didn't already know and have to track down someone to help me learn what exactly certain lines of code will do, and unfortunately my desk is just covered in sticky notes about Marionette as a whole... I really should sort them out sometime. But I definitely plan to compile a list of helpful information that isn't very intuitive to non-programmers! Luckily, since I now help with developing new content, I should be able to help you and other users as I learn more on my own. If you haven't looked at the Marionette Basics or Marionette - Implement a Node, these would be a great place to start while I poke around. There is a lot of information on the second link that will help to show some obscure tricks for custom nodes, although it's not extensive.
  24. Marissa Farrell

    List of Nodes not recommended for use

    It's not necessarily that the node *won't* work, but there's a better node to use. Some deprecated functions that were replaced slipped into the nodes for Marionette, including the one that 'Set Arrow Style' uses, but it's better practice to not use that function and use the one inside of the "Set Object Marker" node instead. Although those nodes may work as described, they are using outdated functions and will most likely be removed or replaced in the node library in the future, so it's better to get used to the proper nodes now before the outdated ones disappear.
  25. Marissa Farrell

    List of Nodes not recommended for use

    Through my testing of Marionette, I've encountered nodes that will not (likely) ever work or may use outdated functions. Below is a list of nodes that should be avoided in your networks for the time being, and are being taken care of for future dates to either be replaced or removed. If there is currently another node that can do what the node listed cannot, it is mentioned as well. Nodes to avoid: - Get Arrow Style -> use 'Get Object Marker' instead - Get Marker -> use 'Get Object Marker' instead - Set Arrow Style -> use 'Set Object Marker' instead - Set Marker -> use 'Set Object Marker' instead *note: these nodes will produce results, but are outdated, and the Set/Get Object Marker nodes are a better practice to use. The following Texture nodes will not work as-is, but we are working on another method to be introduced at a later time. - Get Texture Shader - Get Texture Shininess - Get Texture Space - Get Transparency - Default Texture Space - Set Texture Expanded - Set Texture Shader - Set Texture Shininess - Set Transparency - Is Texture Expanded - Attach Texture Space - Delete Texture Space - Edit Texture Bitmap - Set Texture Size - this will update the size of the texture resource, but will not apply the changes to the object unless you click "Reset to default mapping" in the OIP, currently. I will look into a solution. - Mirror -> will *hopefully* get implemented properly soon.

 

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.

×