Jump to content

the frog

Member
  • Content count

    109
  • Joined

  • Last visited

Community Reputation

8 Neutral

About the frog

  • Rank
    Journeyman

Personal Information

  • Location
    paris france
  1. It's snowing

    just great
  2. Updating Node

    when the 2018 is released I will try my "old" scripts and see how they convert. Then if I have broken network I'll post again
  3. Updating Node

    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?
  4. Prefix & Suffix for Marionette Text

    Very easy when you know where to search, took me a while!
  5. Prefix & Suffix for Marionette Text

    or you can use the data part of the OIP. A long time ago (April 2016) with Marissa's help I made this script. Now not only the names appear but I can use the figures in the data base. The post was name 'Data base and OIP' rail script.vwx
  6. Convert a planar NURBS Surface to Polyline

    hello Maybe it’s because of the bug inside the covert to poly node see convert to polygon doesn't work in marionette object
  7. Door Knob Position Unexpectedly Doubled...

    from what I understand DomC node is based on a vs moving a 3D object and Marissa on a vs in 2D am I correct?
  8. Door Knob Position Unexpectedly Doubled...

    @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.
  9. Nodes Excluded when Network Wrapped

    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
  10. Nodes Excluded when Network Wrapped

    no use found the file in the other post
  11. Door Knob Position Unexpectedly Doubled...

    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…
  12. Nodes Excluded when Network Wrapped

    can you post the vw file so I can try on my computer ?
  13. Scaling 3D Symbols

    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. Scaling 3D Symbols

    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. Marionette Dysfunctional for Me...

    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.

 

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