Jump to content

Marissa Farrell

Marionette Maven
  • Posts

    1,473
  • Joined

  • Last visited

Posts posted by Marissa Farrell

  1. 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 :)

    imgProc.PNG

     

    ImgProcessing.vwx

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

  3. 1 minute ago, Kevin McAllister said:

    Thanks Marissa! I look forward to learning more about all these items..... :D

    (There is one very important new node you forgot to mention.... its in the Operations folder. I'll let you say what it is.....)

    Kevin

     

    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 :)

    • Like 2
  4. Just now, Alan Woodwell said:

    YAY!!!!:) Cant wait to get into it, love the slider! Unfortunately here in AUS/NZ we have to wait for at least 4-6 weeks from the time 2017 is released before the AUS/NZ version is released.:(:(:(

    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 :) 

    • Like 1
  5. @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!

    structMember.JPG

    • Like 1
  6. 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!

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

     

    wkshtHelp.JPG

    wkshtHelp2.JPG

  8. I haven't seen it produce a closed poly in my testing, are you always in the same view? For 2016 we recommend always running networks from Top/Plan.

    You can always override that using the Set Closed nodes in the Poly categories. (Technically those nodes are interchangeable, they're basically identical in their scripts. I'll try to remember to simplify them into one later on.)

    setClosed.JPG

  9. Hey Alan!

    The problem is that the wire going into your Divide Curve node has 3 values going into 'divs', which essentially runs the network 3 times, so it's dividing that curve into 11, then 13, then 11 again.

    This can be remedied by adding in an 'add list' node (from Basic Math) between the 'int' and 'Divide Curves' node, as shown in the attached image.

    (I would upload a file, but I'm working in 2017 primarily and exporting back could show some upcoming changes you aren't allowed to see yet ;))

     

     

    Let me know if this helps!

    divideCurves.JPG

  10. You guys put a lot more work into this than I have for getting a distance, haha

    I usually just use the two points as input for a line (or NURBs curve) and use the length node from the object info category (I apologize if my node name/location are incorrect, I'm doing this by memory...). After I've returned the length, I just delete the line/NURBs. I guess it's the lazy in me!

    • Like 1
  11. 3 hours ago, dvdv said:

    yes I can imagine it is a huge work. But how can I find the old posts? internal search is much less efficient than google used to be. Plus I cannot find marionette forum anymore. Is it still there?

    Hey @dvdv!

    The Marionette forum can be found here

    And the Marionette Resource Share can be found here

     

    They're lumped into the 'customization' category on the forums list.

     

    Hope this helps!

  12. A magician never reveals her secrets ;)

     

    In all seriousness, I'll be more than happy to give you a run down of my tricks once I stomp out some of the work I've got going on here. I've been a little swamped with testing 2017 features/installers/etc., but I would imagine once we release I should have the reigns loosened up on me at least a little. (Not that they're incredibly tight to begin with - how do you think I learned Marionette AND Python in less than a year?!)

    I'll keep in touch on this :) 

    • Like 1
  13. Your animation reminds me of a Python script I worked on last fall - but my script animates along a path.

    I've been working on optimizing it for Marionette, but haven't had the time to complete it.

     

    Here's a video of the output if you're interested. (Please ignore at the very beginning - I used the freehand tool to draw my path and didn't clean up the sharp turns...)

    Also, please ignore how terrible the model is, it's a mockup of my apartment that I never finished. I promise, my television is not on the floor and I have more furniture/appliances than this...

     

     

    • Like 1
  14. I still stand by what Will quoted.

    It's being looked into, but I don't think enough progress has been made to say it's coming any time soon.

     

    Basically, the issue is that the OIP fields are only generated when you edit a script, not when you run it, since they're defined in the Params class. We can't push information there to update when the script runs at this time. I don't know what kind of backend work would have to go into it.

  15. 42 minutes ago, willofmaine said:

    Marissa - If Marionette objects can't be mirrored or duplicated, I feel like I've completely missed the point of Marionette... Am I trying to use it in a way that it wasn't intended to be used

     

     

    The original intention was for Marionette to have a 'mirror' node. Unfortunately it didn't make it into 2016, and since it was backend work, I had a hard time resolving it. (We can't fix/introduce API stuff between versions, to my understanding, due to the possibility of introducing bad code.) This should be resolved in the near future, which should then allow you to mirror the components within your Marionette object (and hopefully get rid of the current limitation you've encountered)

    As for mirroring a Marionette Object itself on the screen with the Mirror Tool, honestly, it could work. I haven't tested it, therefor I wouldn't recommend it. I'm not sure how VW stores a mirrored state of an object, and my thinking is that if you were to mirror an object, then change a parameter in the OIP, it may regenerate only parts of the object, or it would completely redraw the whole thing - if it redraws anything in a non-mirrored state, it would no longer look like what you intended. I could be wrong though, it could work regardless, I just can't imagine that we store a mirrored object the way that Marionette Objects would need to be stored.

    My suggestion is to wait it out until the Mirror node is working properly and then use that within your Marionette script to mirror your objects. (it will take in the handle to an object and two points of a line of which to mirror over, similarly to how the current Mirror Tool works.)

     

     

    Or again, once you have your Marionette object looking how you'd like, you can then ungroup it (which will detach it from the parametric script) and mirror that object instead.

    • Like 2
  16. 23 minutes ago, Kevin McAllister said:

    But the dots specifically? It doesn't seem to be tied to whether someone is a member or administrator. Some have many dots, others have only a few......

    KM

    The dots refer to how active you've been on the forums. (i.e. how many posts you've contributed)

    I agree that it looks misleading, but if you check out your profile it may help clear things up.

    • Like 3
  17. Currently I'm not sure that I would advise mirroring a Marionette Object - since it's generated by a script, I think that any adjustment could 'reset' it and revert it back to a state you didn't desire. What you COULD do, if you're 100% on mirroring it, is 'ungroup it' (which would detach it from the Marionette script) and mirror that (which would currently eliminate the parametric parameters for it, unfortunately), but it should certainly allow less mishaps when mirroring/duplicating/etc.

    As for duplicating Marionette objects - I think there may still be some logic missing on the back-end there. I looked into it for a while a few months ago because the object wasn't being generated properly (specifically using 'move by points') so, again, I would suggest 'ungrouping' the object before duplicating it (I know, it's not necessarily ideal... but it would also make your filesize smaller... :) )

×
×
  • Create New...