Jump to content

Marissa Farrell

Marionette Maven
  • Content Count

    1,261
  • Joined

  • Last visited

Everything posted by Marissa Farrell

  1. You could still take some of the recommendation from @m.graf and duplicate the rectangle, convert to poly, retrieve points, then delete. You'd just need to sort values to find the corner you're looking for.
  2. Right now my suggestion is to use the Get Width and Get Height in the Object Info category for those values, I'm looking into the best method for the referenced point while rotated since the naming of those points when rotated may not be accurate. I've also submitted a bug to update the Get Rectangle node once I've gotten a good solution.
  3. I'm looking into this right now.
  4. @AlHanson This is a known issue and is being worked on.
  5. This file has updated GetPixRGB and ReadImage nodes that should work across all versions after 2017(?) (I can't recall which version we added the install library commands) ImgProcessing_(2)_v2019_v2020.vwx
  6. I have a fix for this. Let me find the revised nodes and I'll get back to you.
  7. My approach to this would be to use 3D control point nodes. If you can provide a small file or image demonstrating a simplified object you're trying to create, I can mock up a small network for you.
  8. @GRZEGORZ This is a known issue! I'm working on resolving it but I think it's not quite there yet. Let me see if I can find the latest node revision and you can let me know how it's working for you.
  9. I'm not seeing the error message, but I am seeing this not draw correctly. I'll try to diagnose/repair this for you.
  10. Next time you see this happen, can you send me the file you're working in with as many of the previous steps you remember taking before noticing the issue? I also don't mind collecting the files that you've encountered it in, but without narrowing down what you're doing it's going to be hard to find the culprit.
  11. Hi Neils! Can you provide me with a file that presents this issue? We're working on tracking this one down but haven't been able to find a reproducible case.
  12. @Benson Shaw I've also got a bug in for this, and at this time is is WAD. I'll try to get it updated for our next version, but we can't change the functionality of nodes in service packs because it can break existing networks. Thanks for sharing your findings, all!
  13. @Dob I'm actually not seeing this convert the poly to a group, the output from ConvertToGroup is empty. I'll try to find some time to look at this more, but currently the problem is there. @DomC appears to be the writer of this node, so maybe he can get to it before I can.
  14. Actually that is a great idea! Let me look into this since we added some functionality for scripting in worksheets recently. Are you still on 2019, as your signature states?
  15. One option would be to include a boolean input node with a name (so that it shows on the OIP) that you can toggle (I would attach it to the end of my network with a pass node) Running the command Tools > Utilities > Reset All Plug-ins should reset them, but it would also update all other plug-ins in the document. You could create a script that would only reset selected plug-ins, or that would only reset Marionette objects. (Let me see if I can find one I wrote a few years ago, otherwise I will try to find time to write a new one)
  16. Not the way that traditional styles work, but it would be possible to program some presets into a Marionette Object. Unfortunately it won't be a quick process.
  17. Can you give a specific example of what you're hoping to do? Marionette Objects aren't similar enough to PIOs to enable the same implementation of "styles", but there's a chance of a different approach to get you where you want to go.
  18. Hi! So if you want to attach the record to the outer container (the Marionette Object) you should use the PIO Handle node (Parent PIO when placed in the drawing) Wire that into the hObj port of the Set Record Field node and then tie the network together with a pass node at the end. I think this is what you're hoping for?
  19. A few years back we were running into an issue with Marionette that resulted in objects not being created correctly when run/updated in a 3D view. Code was added to store the current view, run the network in Top/Plan, and return to the stored view. I am assuming that plan rotation was not taken into account. I'll put a bug in for this 🙂
  20. Thank you! I'm seeing a variety of odd things, I'll get this sent along to the engineers 🙂
  21. @techdef Can you send me that file, either attached here or in a private message? Thanks!
  22. Let me take a look at the video as I haven't watched it (at least in a while... 🙂 ) I'll get back to you as soon as I find the time!
  23. Hi! I've attached a file with the 2020 version of the node - I can't remember when it was fixed, but it works for me now. Marionette (1) v2020 v2019.vwx
  24. It's possible there's a bug hiding somewhere in the Marionette tool that is causing this issue for you. A restart of the application, or reopening of the file, should remedy the issue until the buggy steps are taken again. I've been looking into this for a while now, but haven't tracked it down, so if you find yourself with a reproducible case, please let me know so I can report it for the engineers!

 

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...