Jump to content

the frog

  • Content Count

  • Joined

  • Last visited

Posts posted by the frog

  1. No very strangely the marionette objects cuts the wall directly so I never tried to cut it another way. My next try is to get Marissa’s rectangle to move from the 00 position so I could put a 2d point at the beginning of the script.

    At last I will add a 3d I don’t know what in front of the object with the Y in the OIP to be able to change the apparent place of the object.

  2. Alan thank you for the help

    Yes you where right the script was a mess

    I rewrote it completely starting with the famous “rectangle” and as well having the center of the visible part of the glass as non-moving point. This way the size of the showcase in the OIP is what you need to see and not the technical parts.

    At the end the script is heavy because when you want to hold the glass at the right place you have to dig into the base and add some sides (cut as well) and everything is related.

    At this minute I encounter:

    - a “problem” with the rectangle and the center connection in the node. Applying a point 2 or 3d won’t change the rectangle place, it stays at the 0,0 of the plan.

    Of course if you use the old code with “origin” in the script we are back to the beginning the insertion point is at the bottom left.

    -I don’t know:

    - how to change the insertion point of the resultant object

    - how to change the insertion possibilities in the OIP for a wall

    Thus to be able to decide exactly where my showcase is in the deepness of the wall (see picture)

    Last thing; please untill this object is finished it is not to be shared. You can download it to test or play but not diffuse it Thanks

  3. hello Alan

    No the object is not a symbol (see the file) the purpose is to get a multi choice showcase where deepness can be change in the OIP easily. Therefore it is important to be able to change the insertion point to be able to place the case where I want it, the frame being align, or in front of the wall. The next step will be to manage for the frame (cadre in the file) not to be taken into consideration at the minute it pops out of the wall.Then the wall would be against the sides.

    excuse the mess in the script cleaning is on its way

  4. Hello Stephen

    I had a quick glance at the scripts

    if you have a number in the name it can bug. If you pass 9 the next digit is A than B (=11) etc up to F. We are on an hexadecimal base.

    In your case size is not understood try "2size" and "1rotation". A lot of other signs are bugging factors and for the moment no real way of changing the order. I dropped the case having too many problems when I worked on the customizable baluster(left in the M shared forum).

    Now concerning the go back factor, it seems that when you change the value in the OIP you don't change the "real" or "dim" values in the scrip.So when you copy and paste you get the original values and not the changed ones. Better! if you change the value, you open the script and without changing anything you close back the script, the copy and paste work!!!!

    Have fun


  5. Marissa thanks a lot

    I started going crasy.

    What I don't understand is the reason why when you make a copy you get at the end 3 objects (in my case original, copy I use and the one you deleted).

    Another subject is why, having the last French version, my move node as a different script than the last German version? this brings me to the last question: is it safe to replace the node in the "operation" file in the lib?



  6. Thank you Patrick for the new version.

    I tried but nothing changes. it does the same thing.

    I looked in the script to see the diferences (see picture)

    This is of no help because I don't understand it

    when I devide the script (see picture) what is in the square works with both versions of "move"

    So there must be another node involve in the pb

  7. Hello

    This is the work on the keyboard. It joins the Polygon origin problem found by Alan.

    I am not a programmer but from what I read about Python it is a Tuple function in the Eval node that causes the impossibility of moving the poly. For no programmer (like me) Tuple means that the value you give stays even if you write later in the program to change it. So with the Sequence function nothing moves.

    What I found (music) is that all white notes have a different size of key.

    That’s why you have this huge list of vectors to start the keys.

    Happy New Year again

  8. Hello

    I am trying to name some 2d vectors node in the OIP name part. When you use letters no problem, when you start putting signs like /\ ( - “ you get an error return. So for ex there is no way to use: “Bob 1,5” as a name.

    I know that using a number to start in name gives the wrapping order in Marionette.

    Is there any way to use anything but letters to get the names I want?

    Happy New Year to all

  9. thanks for the try but it does'nt work. the rectangle stays as a rectangle and the new poly won't move all the corners.


    by the way I am using "real" and not "dim" because of the scaling issue when you change units (mm to cm)in the VW page ->units. The object changes size.

  10. Hi

    No you are not “missing something”. I have tried for the last days to solve the problem by changing the script using the rectangle and the move nodes as example. Wanted to change the piano keyboard from rectangles to 3 types of Poly still using the sequence node: impossible.

    From what I understand of the Python script once you’ve set the vertices they are unmovable. Why is that? If you work with height and width, not only they move but they duplicate, this is the reason why sequence node works. I wanted to dive in Python this morning but maybe someone has the solution.

  11. hello the piano makers

    I worked from your files (keys and shape)and added some. Still missing lots of parts!

    Strange things are coming out.

    Copy a "move" node from one file to the other gives an error pop up when I execute. If I delete the node and replace it with one from the Marionette palette No problem. if I copy from my own file No problem. Same with group.

    The strange last thing when I execute everything is ok but for the piano side, would not appear. As you can see in the script I cut the last link and execute it alone: No problem

    If you have any idea ?

  12. Hello

    Your node is real nice!

    I apologies in advance for what I did in the script…

    Modified (it’s the first time in VS or Python) to allow the turning direction and at the same time the “??? “of the holes, changing the phi value. I understand if we only wanted to change the direction the script should have a Boolean but this I don’t know how to write.

    Let’ see what we can do with it (Art of course)

    The frog

  13. hello

    The answer lies in the vector script manual in the appendix. It shows the color palette with the numbers. the same for the patterns.

    It is more difficult with the Pantone ™. What I did : made a rectangle went to the color palette, change to Pantone™, fill the rectangle and export to vector script (see the screen capture) You get values for the FillBack 61680,48573,57825 in this case magenta 0521 C. You can try the other figures they work the same.

    It would be easier to have in the palette those numbers as VW like RGB instead of going through all this…

    Hope this helps

  14. hi

    I have a problem ordering the inputs attached to the wrapers.

    When I use the numbers and then wrap the script it returs a string error. If I have a number at the end of my text it is the same, like if a number in the string was considered as ordering number wherever its place is in the name.

    Whith the file essais balustre 2 (in the other Marionette post)without number the script wraps fine, with it bugs.

    Any idea?

  15. Sorry for not replying lots of other things to do

    This is my first attempt to program so I have been looking in the forum how the scripting was working. Each node has an explanation button to understand what is needed for the node to work. About the ordered points I don’t think the French version have more nodes, I must have found it somewhere in the forum but double check in the list...

    I found a script mistake trying to play with the scales because the mathematical relation between the size of the multiplied object and the offset is wrong.

    I’ll have to correct it than it would be nice if a baluster specialist would give the node the right names (I know them in French).

    Then on the same principle I will expand the script to be able to change easily from circles to squares and get a full baluster library.

  16. hello

    found a way to make it work... long because all the points have to be written on paper and then entered into the list.

    you can see the result.

    It's in french but easy to understand a baluster model where all the pieces can change size.

    of course with get texture at the end...it would be better

  17. I am lazy so I dream of a reverse tool.

    Tryin to design a specific curve this is easy to do in nurbs with the right amont of degrees.

    I would love to be able to design the curve and get the marionette scrip the same as export vector script.

    Being new in scripts I tryed from:











    So my question in that case is what is the equivalent of ArcTo in Marionette?

  18. I think the solution is found

    Yes using the bulb texture is fine (sometime the simpler is the faster), but it?s not enough. I had to duplicate the rectangle and apply the glass texture to find back my shadows of the rectangle. Two images for you, to visualize. The next step is to change the structure of the fluo lamp to get the right kind of shadow on the side of the wall (the tube is 60in so the shadow shouldn?t be sharp.

    I will then explore the way to modify the structure of the frostin the script


    NewField('NNAMaxon Glass Transparency','Family','3',1,0);

    SetObjectVariableBoolean(GetObject('NNAMaxon Glass Transparency'),900,FALSE);

    NewField('NNAMaxon Glass Transparency','Prototype','13',1,0);

    SetObjectVariableBoolean(GetObject('NNAMaxon Glass Transparency'),900,FALSE);

    NewField('NNAMaxon Glass Transparency','Version','1',1,0);

    SetObjectVariableBoolean(GetObject('NNAMaxon Glass Transparency'),900,FALSE);

    NewField('NNAMaxon Glass Transparency','Transmission (%)','0.94999999',3,0);

    SetObjectVariableBoolean(GetObject('NNAMaxon Glass Transparency'),900,FALSE);

    NewField('NNAMaxon Glass Transparency','Index of Refraction','1.5',3,0);

    SetObjectVariableBoolean(GetObject('NNAMaxon Glass Transparency'),900,FALSE);



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