Jump to content

the frog

Member
  • Posts

    120
  • Joined

  • Last visited

Posts posted by the frog

  1. Hi

    Thank you for the proposal of using symbols. I though about it but not two frames in the exhibit are alike so at the end you have too many symbols with too many names.

    What I am trying to achieve is a tool that anyone in the office can use (they are phobic about symbols and 3d so the path is long). That’s why having to change the measures in the OIP as they work in plan view seems to be a good start. Marionette is a try; when I want to go fast I work in VW the normal way with section and path extrude etc.

    I tried you idea of ending with attributes node, the script is working even when you envelope but not if you convert into object.

    As for the texture problem it shows in my showcase example we spoke about where textures are switching without advice if you move some sizes in the OIP. For an exhibit,in the showcase I should have a texture for the back, one for the glass and I can have one for the sides. So we are talking of 2 different classes for 1 showcase, not including the glass (same for all showcases) and the external frame (usually painted the same as the wall). If I have 30 showcases my class palette is too long to be efficient, the way it works in the OIP (scrolling) is the good solution.

    The truth is that being curious I want to understand the why of this situation.

  2. This new topic refers to disappearing object between 2d and 3d. This time part of the frame becomes invisible after crossing the path extrude node when you switch to resultant object. If you only envelope no pb the script works fine.

    any idea (Alan I have been trying almost everything I could)

    Second part of the topic

    Textures are turning crazy as soon as you change a number in the OIP if you are in open gl or in render mode. Usually ‘Verre mineral’ becomes ‘R_Verdure1’ or something else

    Please help

  3. The goal is to be able to add a second frame to doors inserted in walls. For the moment if you add a frame it goes only on one side. I would like to have it on both sides.

    Thanks to webinar IV, I know how to get the info about the door (object by criteria, get parametric records, etc) in this case you only get the first set of info 17 parameters very useful to shape a new frame but…

    Where do I get the second set of info (advanced button in the OIP) that gives the size of the frame so I could link them to my new frame. As well I need to get the wall info and in this case execute the script returns and error (see picture)

    any idea ?

  4. No thanks a lot

    I will use the "image from url" node (slightly modified) to place the paintings right in the back of the frame. The goal is to get the info out of a Filemaker base where all the infos about the paintings are stored and link the frame size to it. This way at the instant I pick up a painting it will be at the back of the frame at the right size, a good way to highjack Sarah’s script in the last webinar session.

    Not all paintings have glass and then reflexion will be too long to calculate for my poor render (usually 4 to 8 bounces).

    If you have any idea why textures are getting crasy or why the frame does not appear...

  5. Alan

    I opened your file and you encounter the same problem as I do

    See the pictures top view object and top view wrapper

    When you convert into object, the only part you get to see is the back rectangle of the frame. The path extruded part, where you can change the size and the deepness of the frame, does not appear if you stay in wrapped it works.

    Concerning the textures I don’t know why they are moving from one name to the other, what I found out is that when you try a texture it won’t appear unless the texture is already in the document. Then if you change a parameter in open gl mode (like a size) the texture at the end of the script will switch to a new name.

    Truly when I am finished with the museum objects modeling I would like to use them to work and at this minute the marionette textured object is not safe enough to be included in a project where I can have lots of different textures.

    At the end Marionette should make us gain time and not flip out because rendering is crazy inside the script

  6. Hello

    I use the same topic for a new problem

    I made a script to frame my paintings. It works fine but when I convert it to object it becomes invisible. The only part I see is the last rectangle (retrait in the OIP).

    If I try the script without the path extrude node all parts are shown. Is there a pb with my script?

  7. Be sure your script is not the only one that crashes VW, Personally I record every 5 to 10 actions switching from name V1 to name V2 and keep the VW backup file as well. This way I don’t have to rewrite my title name every 1mn (this is the frequency of crash if the script is wrong somewhere).

    About the crash it depends of the mac system version I don't crash the same way in 10.10 and 10.10.5

  8. THANK YOU Sarah

    It is great

    The object runs fine and I added an insertion point in the OIP. So now it moves inside the wall the right way.

    The last bizarre thing comes with the textures. If I change dimension in the OIP being in open GL or render the glass texture switches to another randomly. If I change being in wired? (filaire in the French version) textures are kept the way they should be.

    :)

  9. hello

    there is something I don't understand in the way you want to work.

    If you modify a symbol all the symbols in the plot will be modified, so you cannot change the Z value of each symbol otherwise every same type of fixture would end at the same high.

    If you want to change the whole plot at once (or a class or a sheet) you group what you want, you name it in the OIP, then apply the script (see image). You get a new place that will depend of your plot size. From that point (get bounding)with the math node you can write a script to get the centerline and use the deepness of the stage to get the center point.

    But if you are in a 2d view the new object will still be in 2d view so no “Nice view”. To change the view you would have to rotate in 3d the group.

    In the script I used the topz but of course you can use the bottom for stage 0 level.

    Hope this helps

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

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

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

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

    Gerald

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

    best

    gerald

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

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

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

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

    searching...

    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.

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

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

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

×
×
  • Create New...