Jump to content

the frog

Member
  • Posts

    120
  • Joined

  • Last visited

Posts posted by the frog

  1. Hello

    On my computer, when I use the radio button, strange things append.

    When I enter the script to change Option 1 into another name, even changing one letter of the script, the popup changes into a one mode with all the texts on the same line.

    You can try by editing the script, deselect and reselect the node.

    This button works perfectly in 2021, the scripts are alike…

    Any idea?

    Capture d’écran 2021-12-02 à 10.44.29.png

    2021.png

    2022.png

  2. Hello

    Thank you for the answer.

    How evident and simple it is when you look at the solution.... and you know how to script nodes.

    My next step is to find a way to give name to objects directly from an excel file, or with a marionette script..

  3. Hello

    My goal is to count symbols or objects in a specific space and automatically show them in a label.

    I started remembering the webinar where you put points in a poly.

    First easy step, I want to make a network where a symbol is or not in a poly (easier I think than try with space)

    So, I draw an object and name it AA. I convert into a Symbol named AA-1

    I draw a poly and name it.

     

    Built a network beginning by giving a name (bottom of the OIP) to a symbol and get the symbol location, get x,y convert into a point and use the intopoly node with the poly name.  This works if I give a name to the symbol like BB-1 and I have the true or false value. This is of no help because if I have to rename each object it’s useless. So I tried to use the symbol name AA-1, but this returns nothing. If I use the object name it’s the same.

    I know there must be a way because you can count symbols in the sheets, but not in a specific space and show it in a label.

    Any idea?

     

    In the attached file the original webinar, the network that works with the object and a strange network (with the move node) that changes the place of the rectangle without changing  its selection place. In this case I am using the name of the object in the symbol!

    into poly v2021.vwx

  4. THANK YOU

    it works and I improved my knoledge about variables. 😞 I didn't see the missing (

    The next step is to transform this script in a Marionette node. "convert 2d points to 3d"

    Crazy the amount of received plans where you have to convert 2d points to place them at the right high.

    • Like 1
  5. Thank you for the script

    No pb to insert in in a plug in but…

    I am getting strange result. First it erases all the other objects in the file (only one layer). I assume the h is valid for the other objects and not only the locus.

    Second it introduces in the center (0,0) new 3d points as many as the number of deleted objects and last, all the locus are not converted.

    Trying on my side based on your script...

  6. Thanks for the method

    So this morning I tried (with my little knowledge) by using the marionette nodes and their scripts.

    On my test file I put 4 points and used object by criteria node, set selection, get location. I made lists to see the result and use "is locus" to find out that 17 is 2d and 9 is 3d

    objType = vs.GetTypeN(h)

     

                b = ((objType == 17) or (objType == 9)).

    In the marionette script if I use the delete node, I can remove all my 2d point (locus) but how do I insert the 3d points ?

    Capture d’écran 2021-09-02 à 11.35.19.png

  7. Now we have another subject!

    I edited both nodes from the script and beside the “locker” they are alike. You have another group node with more lines.

    If you start from the original file and run the network the 19 is working and not the 20.

    By deleting the first 2 lines in the 20 the network works on my version of 2020 SP3/ build 537701 French version.  Marionette mystery…

    A copy of the scripts bellow

    Capture d’écran 2020.png

    Capture d’écran 2019.png

  8. Hello

    I have tried to understand the differences between the scripts.

    In the node “group” at the end    

     

     

     

     

    1098747222_Capturedecran2020-08-28a22_43_39.thumb.png.353e39502e27be1d8a504c6f72c2eb24.png

     

     

     the only one is the beginning: #COMMAND;READONLYREFFILE;[VWLibDef]/Operations\Group.py;

    #Modified April 2017

     

     

     

    If you take this out of the script the node works perfectly fine. Don’t ask me why ??? And you get the same result as in 2019

    What is weird is that this text is only a reference about the node and shouldn’t interfere in the node process.

  9. hello

    Should I be afraid to switch to 2018 when it's release in France? Some nodes where not changed in the french last sp version. Being, I think, one of the only one using (i try) Marionette in France should I start " flippin' like flag on a pole" or let the good times roll?

    • Like 1
  10. @Marissa

    I would love to have a list and a file with all the debugged nodes from 2016 and on.

    I must be one of the only French trying to work with marionette, so I am not surprise my SP4 version could be left with old nodes.

    What I intend to do is to check the scripts (yes one by one and line by line) that have been modified between the French and the American versions and send the package to Cesyam for them to make a patch to our sp4.

    my goal, like most of the users, is to be able to produce from marionette so the work is easier.

  11. When you wrap the script the 2 rotation nodes are left behind but in fact if you change the rotation parameter in the OIP it works normally. Now once the script is wrapped, if you delete the nodes it still works. Willofmaine have invented the ghost nodes!

    In my case (French version) that’s what I get. What about you with your version?

    To answer your question yes when moving the 2 nodes it wraps ok

     moving only the top one no changes

    moving the bottom one wraps ok

  12. I went through your scripts 14 and 15

    In 14 I get an error message as soon as I want to change a value in the OIP

    I converted in centimeters and tried again from the script and it worked. Then I changed the texture to attribute. This helps but will not change the fact that when you wrap the rotation node wouldn’t follow the fist time (see the next post). Then VW crashed.

    Started again and only changed the values in the script, this is working. I haven’t understood the use of the first rectangle (in pink) but this is just a matter of curiosity.

    Going to 15 this is totally insane.  I have tried many options from center true to taking out the second knob. I get funny situations but I cannot fin a reason why when you apply you option to the first knob then the cabinet door flies to the its high and the knob is at the right place. The same with the rotation the unique knob rotates around the center but with two knobs it works. I thought it could come from the fact that when you center in x the knobs (going to true in the OIP) in fact you have 2 knobs at the same place, but then you don’t need to take out the knob later so there is no reason from my point of view, it would affect the rest of the script.

    Hope someone can find why…

  13. Back in the discussion

    Another way to operate is to go back to vw use of symbols. I’ll try to make myself understandable. First I build my object from the symbols in 2 or 3D and the marionette script, including the scale part (see earlier in the post). Second I duplicate the object and create a symbol of the object. Then I have the choice, or I use the object (copy paste etc…) and it becomes easy to change its size as a unique object, or I decide I will need to change all the objects so I draw with my symbol and edit it if necessary using then the scale function of the script. In that case all the objects are changing.

    Again for me marionette is a tool like all the others, sometime it’s faster to draw a rectangle than to use marionette sometime not. At the end what count’s is the gain of productivity (and the pleasure of achieving scripts!).

  14. here is the way I scale symbols in marionette

    Take a look at the script "frame3" once the popup is changed to a group you can scale in x or y even z if you change for a 3D point. What is nice is the fact that using the same symbol you can have objects with different sizes

    frame 3.vwx

  15. Hello

    From my experience working (not playing) with marionette object is difficult.

    You are right, taking a 2016 script and put it in a 2017 file is more than dangerous.

    In 2017 scales are taken into account (not in 2016) so the first thing to do is to transform the 2016 file into a 2017 starting at the same scale with the 2017 document. I found it easier because once it’s done you don’t have to redo it each time you want to use the object.

    Mirroring stays a “problem” when working because mirroring in the script is one thing, mirroring in real life is another. Once you work with your objects in a project it would be better if they could act like all the non marionette objects and not like?!?!?. Of course it is possible to have the mirror function appearing in the OIP but again when you work you don’t want to think when you mirror just use the shortcut.

    Last from what I understand about textures maybe the solution would arise if there was a way to place the parametric functions in the texture part of the OIP. I think once the object is built when you change some parameters at a point the texture part of the OIP “sends, overrides” the script (see the showcases). Changing the place of the texture functions would as well simplify the OIP (hope for 2019?)

    At last I can add that the first thing you have to do when working with marionette object is to change the automatic recording to 2mn in your preferences due to the frequents crashes. Loosing to 2mn is one thing loosing 15 is another.

×
×
  • Create New...