Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by _c_

  1. _c_

    No Stories, No Problem

    Thank you Zeno, ūüėÄ ... I just have been reproached that I speak a total mix between German and English! I think that we will do a common zero for the project. We must use the coordinates during IFC export, so, let's go for "common zero".
  2. _c_

    No Stories, No Problem

    Ciao Zeno, do you use a common Z for all buildings or every building has its own project zero? Accordingly, how do you set up the Reference Elevation in the Export IFC Project settings?
  3. Hello all, Vectorlab is now forever down. TWK, I can send you the List Browser article privately.
  4. Hello, we have the request by our planning partners to set slabs to the story above. It flips our wall/slabs settings. As architects, we usually see the slab below. What do you use? What do you prefer? Below a basic test floor as example
  5. Thank you Ruben, Good to know. I am considering splitting floor finish from structural slab. That would make our 2D much easier, since the structural engineers don't ever get to see them, but they could stay for display in plan, as we need. It is quite schizophrenic, all in all.
  6. _c_

    No Stories, No Problem

    Expanding, every Vectorworks user sees a Design Layer, whose elevation and wall height are set, as a storey.
  7. _c_

    No Stories, No Problem

    Ciao Wes, when layer-less levels where introduced I asked for storey-less levels. I don't understand why do we need storeys since we can simply map them during export.
  8. _c_

    No Stories, No Problem

    Storeys are not difficult to understand, but their interface in VW is. It is messy. There are too many cryptical alerts and levels appear/disappear in too many flavours, across various quirksome dialogs.
  9. What a suggestion, no please? No symbols. It is a nightmare to maintain -the various widths, the various vertical positions, etc. etc. I did try, I even had special symbols changing by layer scale, this far before the current implementation of "2D components". The 3D can be as it is, we need this in 2D scale 1:50 or so. Take the object of Archicad, that would do very well here.
  10. Dear Marissa, we are a large nameless crowd with one voice, this forum. VW must put here a person with the power of taming a crowd. This isn't a gift everyone has. Jim had it. While VW is "listening" we do brew any kind of fantasy as to the possible answers to our complaints -or lack thereof. There is no limit, in any direction, to the kind of suppositions we can make. As a rule -such is the nature of a crowd - these fantasies are not positive nor good for you. Ciao, _c_ PS You are too kind for being thrown into this pit, get out of it!
  11. This is so basic, we have been asking for this for at least a decade. Please. Stop. Ignoring. Our. Needs.
  12. _c_

    Update Vectorworks fails (Mac only)

    Hello, I'd like to thank you for this procedure, it worked most of the times. Whereby I must add that simply resetting the Permissions didn't help, we needed also to create a new name in the list of the users. Only then, after propagating the rights to the enclosed items, could we finally update successfully. We still have 2 users where the update couldn't succeed. The updater won't update itself and silently quit without any error. A fully new installation didn't help. For these there must be some further trouble. Best, _c_
  13. _c_

    What mouse do you recommend?

    @Wesley Burrowstry a Wacom Intuos. I had carpal pains so strong, that once I had to go to the hospital. The Wacom healed it fully. Now I can also use a mouse again.
  14. _c_

    Until Next Time

    Dear @Jim W, I wish you all well. You have been the heart of VW, you'll be missed like no-one else before. VW lost his soul. Hugs, your very, very sorry _c_
  15. _c_

    Date format in current plot date

    No! It is THERE! Nikolay, wonderful! There was people here not using the old title block because the date format would be "strange"!
  16. _c_

    Post-Brexit support for UK VWX architects

    Oh, finally the strong elbowed freelancer residing in Kenya that I am sure every British office was waiting for, to replace the in-house European colleagues. So trustable. Are you spam or do you simply sound like it? One is wary of clicking on your link, just for you to know.
  17. Carl, jump back in! You'll love it! Vectorscript evolved quite a lot since then and it's lot of fun. We have the Developer wiki now, a little obsolete but still of great usage is also Vectorlab.info. And the community shifted more into this forum rather than the v-list. And if you are wiser than me, you'll do the jump into Phyton right now rather than later. _c_
  18. Ciao Carl, I am very pleased to see you here. I remember you very well from a rather remote past ... making something out of VW logs...the Time Clock! here it is. Welcome back! You won't remember me, it was many alias names away. I don't even remember myself which one I used then. _c_
  19. Nice, danke Patrick
  20. _c_

    Issue with "Extrude Along Path"

    Hello, by chance I stumbled upon this discussion. I know it's late but it might save a lot of searches later for others. You must "flatten" the path object, you can also use SetPlanarRefIDToGround. Example: RectangleN(x, y, 1, 0, w, h); pathObj := LNewObj; SetFPat(pathObj, 0); SetPlanarRefIDToGround(pathObj); { without this, your ExtrudeAlongPath will be extruded along any view you happen to be in } pathObj := ConvertToNURBS(pathObj, FALSE); obj := ExtrudeAlongPath(pathObj, profileObj); { profile object is a poly, rect, oval etc. }
  21. _c_

    Project sharing workflow

    Ciao Christiaan, I am of the opinion that live sections are just an edit tool. No need to have that also published, they also require a different set of attributes. BTW, only now, by the released SP3, am I able to use the sections as live tool, they were simply too crashy and had an ugly performance making them unusable.
  22. _c_

    Project sharing workflow

    Ciao Hans-Olav, I find it impossible to have a singular file. No idea how to archive and manage the obsolescence of the Viewports in that structure. The file size! We have this structure below, which is close to your one. It is very flexible and stable. We don't use project sharing where we issue (Sheet layers). What you call Target files. So the answer is: no, I'd advise you not to use PS in target files. Our structure: Folder 0 1 or more project files (.vwxp) containing everything excluding sheet layers 0 or more normal files (.vwx) containing 2D details, variants, etc. excluding sheet layers reference across these mainly old style, no automatic update Folder 1-5 (data collection, preliminary, project, permits, construction drawing) plot files, data etc. thematically sorted, all references old style to folder 0, no automatic update Archive of the issued files above: as soon as we issue a set, we archive the whole file. On top of the folders remains the last used file set Worgroup: 3 Workgroup folders for the office, project specific resources are never there. No problem with Project Sharing and referencing in this workflow, as far as I am aware.
  23. _c_

    Geometric Algorithms (a.o Voronoi)

    Indeed, what a strange link it generated. Here it is in a more old fashioned way: link Dave, there is nothing there that you won't know and probably already surpassed ages ago with your own algorithms. But it offers us a readable introduction to things which are otherwise far beyond our reach.


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.