Jump to content

Peter Vandewalle

Member
  • Content Count

    55
  • Joined

  • Last visited

Community Reputation

1 Neutral

About Peter Vandewalle

  • Rank
    Apprentice

Personal Information

  • Occupation
    Customer Support - Design Express
  • Homepage
    www.designexpress.eu
  • Hobbies
    Architecture, Music, Mac
  • Location
    Belgium

Recent Profile Visitors

231 profile views
  1. Peter Vandewalle

    How to embed user nodes in Marionette tool list

    After creating the marionette node, turn it into a symbol with the "convert to parametric object" option on. This way the node will become a "red" symbol. To create a category, just create a symbol folder and move the node symbol in there. To add your own nodes to the default library, insert it into a Vectorworks file and store that file in the (user) folder "Users/<username>/Appdata/Roaming/Nemetschek/Vectorworks/2018/Libraries/Defaults/Marionette/". Update you library and you're done.
  2. Peter Vandewalle

    Disappearing columns

    We’ll need the Vectorworks file to be able to solve this issue.
  3. Peter Vandewalle

    multiple intersections

    Select all trusses and add solids first. Then intersect solids.
  4. Peter Vandewalle

    vLookup function

    The from data is in spreadsheet cells. I didn't need it from database rows... Sounds interesting though.
  5. Peter Vandewalle

    vLookup function

    I only used it in a database row. But I think it should also work in a spreadsheet row. Thanks for the manual!
  6. Peter Vandewalle

    vLookup function

    I recently created my own vlookup function. See attached file. Check the remarks at the beginning for the way to use it. WSVLookup.py.zip
  7. Peter Vandewalle

    One year later... still having problem with stories

    Split levels can be done by stories. I usually create multiple story levels for each level type: top of structure finished floor s_top of structure s_finished floor ... Then I create multiple wall styles: base to base, split to split and if needed base to split and split to base. Same for floors.
  8. Peter Vandewalle

    model origin in section viewport

    I'm trying to create a kind of benchmark that could also modify the Story levels. I can do that, but then the section viewport needs to be positioned so that the origin of the model in the viewport matches the origin of the sheet layer. I'm trying to modify it so that it would work also when, the section viewport is positioned elsewhere on the sheet layer. I have been thinking about the elevation benchmark tool, but I can't read the indicated height value from the PIO object, there's no parameter for that...
  9. Peter Vandewalle

    model origin in section viewport

    Hi Boh Doesn't work. Copy-pasting a 3D locus into a viewport annotation isn't possible. Copy-pasting a 2D locus will paste it onto the origin of the sheet layer inside the annotations. No luck so far...
  10. Peter Vandewalle

    model origin in section viewport

    Is there a way to get the origin of the model in a section viewport? Since the Elevation Benchmark Tool is able to create a value based on the Z-origin, I suppose it should be possible. I just can't seem to figure out how...
  11. Peter Vandewalle

    hatch not rendering

    It's pretty hard to see what's wrong without the vwx file...
  12. Peter Vandewalle

    Refresh Viewport

    I'm trying to modify the story level and update the viewport in one script. I think the modifications to the story level are effective only after the script has ended. So the viewport update doesn't return the wanted result within the same script. If I run the script twice, the viewport will update... Too bad.
  13. Peter Vandewalle

    Refresh Viewport

    Is there a way to refresh a (section)viewport in a script?
  14. Peter Vandewalle

    vs.GetFStory()

    This does the trick: import vs hLayer = vs.FLayer() hStory = vs.GetStoryOfLayer(hLayer) while (hStory == ""): hLayer = vs.NextLayer(hLayer) hStory = vs.GetStoryOfLayer(hLayer) sStory = vs.GetName(hStory) Thanks for the help!
  15. Peter Vandewalle

    vs.GetFStory()

    Thanks for the reply, Pat. GetStoryLayerTemplateName returns the name to the first layer in the story template. That's not a handle to the story :-(
×