Jump to content

orso b. schmid

  • Content Count

  • Joined

  • Last visited

Community Reputation

22 Great


About orso b. schmid

  • Rank

Personal Information

  • Occupation
  • Homepage
  • Hobbies
  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. orso b. schmid

    Scripting stories

    Hello, I finally made a manager for stories for transferring story data across documents. There are a few relevant limits, but it is roughly possible to get a decent command doing the bulk of the job. A couple of things are not clear to me: Does anybody know if there is a difference between these two? * VW 17 (2013): GetStoryLayerInfo(index: INTEGER; VAR name: STRING; VAR scaleFactor: REAL; VAR layerLevelType : STRING; VAR elevationOffset: REAL; VAR defaultWallHeight: REAL): BOOLEAN; * VW 20 (2015): GetLevelTemplateInfo(index: INTEGER; VAR layerName: STRING; VAR scaleFactor: REAL; VAR levelType: STRING; VAR elevation: REAL; VAR wallHeight: REAL): BOOLEAN; I don't see any difference, and I tested really extensively. But, as always, I might be missing the obvious. ūüôā Does anyone know how to check if the suffix is actually used as a prefix? Thank you, Orso
  2. orso b. schmid

    Post-Brexit support for UK VWX architects

    The things one says for greed.
  3. orso b. schmid

    NumCustomObjectChoices(pioName, pParamName)

    Dear Sam, can it be that you are running it too early? Not in kParametricRecalculate?
  4. orso b. schmid

    Messages and Includes

    Julian, is this what you are looking for? {$INCLUDE ..\BlaBla.vss} --> go up 1 folder from current file location (= file containing the running script) . {$INCLUDE ..\..\BlaBla.vss} --> go up 2 folders from current file location {$INCLUDE ..\..\MyFolder\BlaBla.vss} --> go up 2 folders and enter MyFolder from current file location Edit: this is platform independent.
  5. orso b. schmid

    VW 2017 Network Setup

    I always wanted to write something for team work in VW, postpone this since years. It would take some time, not last because workflows are very different depending on national habits/rules and output.
  6. orso b. schmid

    VW 2017 Network Setup

    Jim, if I was to start enumerating the times you gave me/us reason to thank YOU!
  7. orso b. schmid

    VW 2017 Network Setup

  8. orso b. schmid

    VW 2017 Network Setup

    Hello, you don't need to re-install VW. Some user settings are not OK. For example, all these crash logs are certainly not to be copied and are a hint that something was already wrong. You want a very controlled, clean, perfectly working new copy of the user settings. Let VW do it ... SEQUENCE TO GENERATE A NEW USER FOLDER CONTENT: quit Vectoworks delete the content in the User folder on Mac it would be by default the folder [userName]/Library/Application Support/Vectorworks/2017 on Windows it would be by default the folder [userName] /AppData/Roaming/Nemetschek/Vectorworks/2017 delete the folder "2017" start Vectorworks make all changes in the preferences as you need (particular care on the Backup path, see previous post) quit Vectorworks Now you have a fresh set of user settings. Please take a lot of care to have a working local User folder, because, if the server fails for some reason, VW will go back to that. You ALWAYS need a perfect local User folder. SEQUENCE TO MOVE USER FOLDERS ELSEWHERE (FOR EXAMPLE ON A SERVER): To work in team we need to be able to clean up the mess that accumulates on the user folders, so we need access to these folders without going to each machine: the only way is to place them on a server. From there, a CAD Administrator can maintain them comfortably using VPN from home, in the night. quit Vectoworks Create in the wished location on the server a folder dedicated to contain all your user folders, call it something like "VW-users" (see screenshot "User Folders.png" in my previous post). In "VW-users" create a folder for each user, for example "P1, P2, P3, etc." (it doesn't matter how you call them, I use here the same names as in the screenshots of my previous post). Observe that these folders are empty: you want VW to create a new content. go to each user's machine and perform this sequence: launch Vectoworks launch the Vectorworks Preferences > tab User Folders click on Choose... click on Yes when prompted to decide if you really want to change the User folder choose the dedicated User Folder in "VW-users" a dialog prompts you to ".... copy the contents of the existing User Data...": say "No". You want a clean new content. If you didn't want a new content you could say "Yes" and VW would copy the previous content. My advise is never to copy the old content a dialog prompts you to save changes if you have an open document. Do as needed Vectoworks shuts down. Restart it and all is well. Now you should begin analyzing one User Folder in detail. You must know what each preference does in those xml settings. Try until you know everything. If you are savy on those prefs, you can edit them from home, which is very fast and easy. Your target is to create and maintain a common set of preferences for all your users. When you have that, you'll create a template that you can use to install new users or to clean up fast "sick" user folders. If you are on a Mac you'll want to use TextWrangler, a free application which allows you to manipulate text very, very efficiently. You can for example batch edit all users on your network with it (you'll need grep) or compare two folders, or two files. If you don't know it already, you should begin learning Vectorscript (in the Pascal or better Python version) since it's the key to efficiency in VW and it's unconceivable to manage a network of users without. By the way, that of "beginning" learning VS is a permanent state . As a final note: Settings and Libraries is the only thing you need to grant common settings for all users in an office, the rest can be generated by VW as needed and a lot will be in the Workgroup folder. What can be in the WG and what not, how exactly is the optimal way to set up a network, when to use aliases, and when not, all these questions are too detailed to be answered in this place.
  9. orso b. schmid

    VW 2017 Network Setup

  10. orso b. schmid

    VW 2017 Network Setup

    Thank you Alan. I hope it can be useful for others. I attach here also a screenshot of the VW prefs and the Office library since I can't edit the post any longer:
  11. orso b. schmid

    VW 2017 Network Setup

    Hello, I work since 4 years as in-house CAD manager for 40 users in an architectural office in Europe. We are a Mac-only environment, but I worked in Windows-only environments too (17 years). Our system is slightly deviated from the "canon" but it is very robust and serves us well. The office does Architecture and Expositions. The teams are from 2 to 7. As typically European, colleagues come from any part of the world (this is relevant for character encodings' issues, aside of the fun and privilege to be in daily contact with different cultures). 2/3 of the team changes every 6 months, I am in a constant cycle of schooling and setting up VW. They might work day and night. I am available thus day and night. But I am not alone. The Vectorworks team helped us, me -such a PITA of a user- countless times out of impassable situations. Quietly, efficiently, dedicatedly, patiently, unregarded the quirkiness of my requests. I'll take the seldom chance to state my gratefulness publicly: thank you! My advises as of VW 2017 SP2 (latest available public release): STABLE AND SHORT PATHS Shared directories: use mapped drives on Windows (this was true in the past, VW engineers, can you please confirm or correct this statement ) Network protocol on Mac: coerce afp server side if you can. If you can't, please join the lot in asking Apple to fix the most buggy implementation of smb ever. Path Length: all file/folder paths within your libraries must be very short. Avoid nesting in folders. Encoding: don't use any special characters in file/folder names. Stick to ascii 128. This is indispensable on mixed Mac/Win environments. All users should use operative systems with compatible encodings. It is problematic to have working stations using French or Italian or German or whatever. Accented letters such as √§√∂√ľ or √®√©√ß etc. (outside ASCII 128) get quite in the way when exchanging files. Vectorworks is Unicode complaint only in certain parts, such as xml. VW dialogs are not unicode compliant, so you can't reliably display any unicode text (such as xml). This makes sharing Callout databases between Windows and Mac mission impossible. Backup folder: every 40 operations (not minutes) in a chosen location locally the same for each user, for example "Documents". Not on the server (see screenshot "Backup location.png") Workgroup Folder Basic setup: (see screenshot "WG Basic setup.png") one parent WG (workgroup) folder: create a generic folder for Workgroups. Give it a short name, for example "_VW". Put that in the same folder where the projects reside. one or more WG folders: in "_VW", create a folder for each VW version ("VW_2016", "VW_2017"...): it's needed at the yearly upgrade while you prepare the new libraries. For a short time you'll need two versions. The old one will be deleted at each accomplished upgrade. For a seamless transition from one VW version to another -where the users don't even notice- I can write another post. a database folder for Callouts. This is not subject to conversion so it can stay outside the VW versions. WORKGROUP FOLDER (DEFAULT CONTENT) <> WORKGROUP FOLDER (OFFICE LIBRARIES) <> USER FOLDERS Split Default content from Office libraries. It is not the same thing, they should not be together. Store the user folder on the server if you want to keep control. VW prioritize the User Folders. This is undesirable in a Workgroup workflow. WG library with Default Content: only for the default content and similar technical resources. This shouldn't be touched by the users (again see "WG Basic setup.png", thus the icon with the "forbidden" sign) Office library: one folder that must contain a folder named "Libraries" where the complete office library is placed. This is needed to make it display in the Resource Manager (see screenshot "RM.png") User folders: place all user folders on the server, below more infos (see screenshot "User folders.png" ) FAVORITES Make them small and few (see screenshot "Favorites.png"). don't use the Favorites folder for the whole office library: cumbersome to maintain, slows down Vectorworks' start considerably create a file with the most used resources place only few aliases/links to files that must appear in every Resource Manager at every user. USER FOLDERS Keep them on the server, not local (again, see screenshot "User folders.png" ). place it outside the project folder clean up regularly user folder from user settings colliding with office settings, such as: workspaces, dwg/dxf preferences, Space and Stair preferences make yourself comfortable with mass-editing user preferences in Settings. Learn Grep. Applescript on Mac is very comfortable. Do the cleaning in the night keep a copy of a generic user folder which you'll install on the server for each user: you'll need to edit the path to the Backup folder APPLICATION FOLDER Cut it to the office's need. Anything more will slow down or confuse users (such as needless default hatches, wall styles, etc.). create a version of the application folder with less items: remove all you know to interfere with your office libraries. Change plug-in strings where needed. Conform plug-in parameters to your needs. prepare this adapted VW folder at each service pack release. copy this adapted VW by every user never run the installer If you think that this is a hell of a job, yes, it is. But the CAD admin works more once, so that all others work less always. Being a scripter/programmer AND having a solid experience in the real architectural praxis will help you considerably in this job.
  12. orso b. schmid

    Chicago Summit- who's there?

    Actually much longer, since long before birth...
  13. orso b. schmid

    Chicago Summit- who's there?

    Sooo... as you see in my new avatar I grew up. I'm almost 16 now. I CAN'T wait any longer for the Summit! I have only two days left for getting ready! It goes without saying that I didn't do a thing until now -barely managed to book a flight before it to be impossible- and will securely miss all I need. Who cares! Orso
  14. It's difficult. I began this and didn't finish. It really does take quite some math, I was surprised myself. If I finish it I let you know here. Orso PS: my plug-in based on the Fresnel integrals algorithm, should you want to give it a go yourself: http://people.sc.fsu.edu/~jburkardt/f_src/special_functions/special_functions.f90 by Shanjie Zhang and Jianming Jin. Modified: 17 July 2012 Shanjie Zhang, Jianming Jin, Computation of Special Functions, Wiley, 1996, ISBN: 0-471-11963-6, LC: QA351.C45.
  15. orso b. schmid

    Dash styles vs Line Types

    This was due since long: Vectorlab's index pitfalls have been updated to reflect the beautiful mess of the new Line Types vs Dash Styles vs Line Styles. Get lost in the labyrinth of indexing between omitted dash-gap pairs and nameless names. Whoever is interested: http://www.vectorlab.info/index.php?title=Index_pitfalls Orso


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.