Jump to content


  • Posts

  • Joined

  • Last visited


1 Neutral

Personal Information

  • Hobbies
    Woodworking, music
  • Location
    Williamsville, NY, USA

Recent Profile Visitors

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

  1. Hi, I'm looking at this 2022 Help webpage: https://app-help.vectorworks.net/2022/eng/VW2022_Guide/Start/Getting_started.htm I want to create a Vectorworks application backup plan. I have a plan for my drawings and scripts. Midway down that page is a paragraph containing these two sentences: Your software license allows for one copy to be made for backup purposes. The Vectorworks application should be backed up on a regular basis. They seem contradictory. The first sentence saying one backup and the second saying regular (many) backups. Of the approximate 48,000 files that the trial version installed, I think they reside in these basic folders/directories. In the Windows 10 world the Vectorworks executable and related files are stored here: C:\Program Files\Common Files\Vectorworks 2022 C:\Program Files\Vectorworks 2022 C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Vectorworks 2022 C:\ProgramData\Nemetschek\Vectorworks Cloud Services upgrade The windows Registry contains info: Computer\HKEY_CURRENT_USER\SOFTWARE\Nemetschek\Vectorworks 27 The installation process also creates these folders/directories based on the name of the user that installed it: C:\Users\All Users\Microsoft\Windows\Start Menu\Programs\Vectorworks 2022 C:\Users\All Users\Nemetschek C:\Users\Bill\AppData\Local\Temp\Nemetschek C:\Users\Bill\AppData\Local\VirtualStore\Program Files\Vectorworks 2022 C:\Users\Bill\AppData\Roaming\Nemetschek I am assuming that there are some words missing from that "backup" paragraph. Question: How would you rewrite those two sentences and how would you clarify what folder/directories should be backed up? Thank you.
  2. Thanks for the good news. The reason I thought that Architect didn't support Sections was: https://app-help.vectorworks.net/2022/eng/VW2022_Guide/Viewports2/Cutting_sections.htm Cutting sections In the Vectorworks Fundamentals workspace, the cutting section commands define ... and Creating section viewports (Vectorworks Design Suite required) https://app-help.vectorworks.net/2022/eng/VW2022_Guide/Viewports2/Cutting_2D_sections.htm the Cut 2D Section command (Vectorworks Fundamentals workspace only) https://app-help.vectorworks.net/2022/eng/VW2022_Guide/Viewports2/Cutting_3D_sections.htm From the Vectorworks Fundamentals workspace, the Cut 3D Section command Thank You
  3. Hi, I am experimenting with the 2022 trial version. After looking at the Help, am I correct that: 2D & 3D Sections are only available in the lower priced Fundamentals version Section Viewports are only available in the higher priced Design Suite version? I.e. with the mid priced Architect version I cannot create a section. Thanks, Bill
  4. Is anyone successfully running Vectorworks v11 on Windows 7 or Windows 8?
  5. Katie, I'm still using v11, and they are not menus, so this may not be valid. Joists In a brand new file I can insert a Joist using the Joist tool in the Objects palette. With nothing select, if I then click on the new joist, it takes a little over 3 seconds with my 2 ghz, 1 meg of memory, Windoze 2000 PC, for the Object Info Palette (OIP) to show the info for the joist. If I create two or more joists, it takes that 3 seconds for OIP to show the info for the first joist that I click on. If I then click on another joist, the OIP is updated instantaneously. Maybe what is happening here is that the Joist plug-in is loaded from disk and translated to some "excutable code" and that is causing the time lag. But when you click on something other than a Joist, VW throws the translated version of the plug-in away, only having to "re-translate" it the next time you click on a joist. Classes I have one drawing with about 180 classes. When I try to view that list via Organize, Classes, it takes about three seconds for the the window to be displayed. This is something that is super simple to do, just showing data that is sitting somewhere in memory. But, Organize, Classes Visibilities, is instantaneous and so is its sorting. Sorting is more complicated than just displaying a list of classes, as in the nornmal old classes, list that I mentioned above, where you can edit a class. And now having said that, I think that it is redundant to have both of those "Classes" choices in the Organize menu. The sorting capabilities in the "Classes Visibilities" list should be part of the normal "Classes" window, and likewise for Layers.
  6. Kevin, Thanks for the idea. It makes sense. Regarding this forum's software, I think you will get used to it. Most of the ones I visit are like this and I am used to them. The others seem to be of an older style, older technology, and less user friendly, too me at least.
  7. Looking at the Title Block created for a ConDoc. It contains two circles with lines going through their centers horizontally and vertically. What are those cirlces used for?
  8. Katie, It is astounding how Vectorworks lets me use the flyover tool while rendered in Open GL. There are a ton of calculations that take place for every single thing in the drawing. And all of this happens fast, for me with a 2.0 Ghz, 1 mb PC. The code that nmakes that happen is probably written in C or some other compiled language. Maybe starting with V10, I too noticed some things that are comparatively much simpler than the flyover tool, yet taking more time that I thot necessary. In Ben's case, something like a drop down menu should almost finish before it starts. I'm guessing that some things in Vectorworks are not implemented in C, but use VectorScript. VectorScript isn't compiled, it is interpreted/translated, like having someone translate from English to French. The time to communicate increases. Is it possible that some things are being implemented in VectorScript?
  9. Short story Objects created via the board plug-in and then rotated 90 degrees around the x or y axis are sometimes mysteriously being rotated back 90 degrees by the time I open the file to do more editing. Long story I am using the board plug-in to create the pieces/objects for a frame and paneled box. For the side pieces of the box I create the board and then rotate it 90 degrees around the appropriate axis to make the board stand up. I have side pieces for the top/lid of the box and the bottom. Periodically, the top or bottom side pieces will fall over. I don't think they have both done it at the same time. Thinking I might be accidentally doing something I fixed everything then duplicated the top twice and moved each dupe to a separate layer. The only difference between the copies in the separate layers was that for one of the layers all the pieces were in a group, which is the way they were in the original working layer. Today when I opened the file, all three versions of the top had their side pieces fall over. I'm save multiple copies of the drawing plus exporting it as a vectorscript with the hope that when it happens again, maybe I will see something in the vectorscript file. Question Anyone else seeing any wierd behavior with the rotated board plug-in objects? My guess is that, randomly, the information that indicates that the board has been rotated around an axis is being lost when the file is saved or is not being used when the file is opened.
  10. Ramond, I tried the root volume shortcut idea. In windoze terminology I open "My Computer" and opened another window and navigated to the VW folder. Then I dragged by d-drive as a short cut to the VW folder. I first tried this as the include but it gave me my original error: code: {$INCLUDE D:\wff\vw\Scripts\EraseBanana.vss}[/code][/indent] Then I decided to look at the file name of the actual link. This is the file that it created in the VW folder: code: Data Disk 1 (D).lnk[/code][/indent] And this wierd looking VectorScript include worked: code: {$INCLUDE Data Disk 1 (D)\wff\vw\Scripts\EraseBanana.vss}[/code][/indent] I then renamed the long d-drive lnk file to: code: d.lnk[/code][/indent] And this include worked: code: {$INCLUDE d\wff\vw\Scripts\EraseBanana.vss}[/code][/indent] Thanks for the interesting tip.
  11. Raymond, Test 1: using "D:" If you literally meant to use "D:\..." I don't know how to get that to work, i.e. use a ":". Since this worked: {$INCLUDE d\wff\vw\Scripts\EraseBanana.vss}, I thought that I just needed to copy "d.lnk" to "d:.lnk". But, that put the file named ".lnk" on my d-drive. Trying to rename it resulted in a DOS syntax error. (I'm playing around in a command prompt window). With this shortcut file: code: C:\Program Files\VectorWorks 11.5.0\Plug-Ins\d.lnk[/code][/indent] I got the error on this include: code: {$INCLUDE d\wff\vw\Scripts\EraseBanana.vss}[/code][/indent] I copied d.lnk up to the VW folder and it worked. Test 2: Using the Plug-ins folder To make things a little simpler I put a script with this name in the Plug-Ins folder: FakePlugin.vss. I.e. no short cuts involved. This include gave that same error: code: {$INCLUDE FakePlugin.vss}[/code][/indent] But, if I moved it up to the main VW folder the that same include worked. If I moved the file back to Plug-Ins, this include did work because plug-ins is in the main VW folder: code: {$INCLUDE plug-ins\FakePlugin.vss}[/code][/indent] Therefore , I think that VectorScript includes have a bug and only allow you to include from the main Vectorworks folder. If you want me to try anything else for you, let me know.
  12. Raymond, I'm sort of glad you are having the same problem on the Mac, at least I'm not crazy. I experimented with your hint about the shortcuts (links, aliases). I was able to put a shortcut, in the VW program folder (c:\Program Files\VectorWorks 11.5.0), to my script on another disk. This is the file name of the sortcut created by windoze: code: IncludeErrorFromLnk.vss.lnk[/code][/indent] This include worked: code: {$INCLUDE IncludeErrorFromLnk.vss}[/code][/indent] I also put a shortcut, in the VW program folder, to another folder, not just a file. That folder was also on another disk. This is its folder name: code: IncludeError.lnk[/code][/indent] I was then able to include scripts from the folder: code: {$INCLUDE IncludeError\IncludeError.vss}[/code][/indent] I submitted a bug report on 4/29 to vs_support@nemetschek.net. No response yet. Thanks for the tip.
  13. This has a semi-happy ending ... Thanks for the ideas, however nothing worked, but as you will soon see, they did lead to something else to try. Before I get to that, I wrote a little script to see if I could read the file, instead of $include it, and that did work. As a variation on Alexandre's idea I put the file in C:\Program Files\VectorWorks 11.5.0, instead of in C:\Program Files\VectorWorks 11.5.0\Plug-Ins. I.e. I put the file in the folder/directory where the VectorWorks executable is. And guess what, this worked: {$INCLUDE TestInclude.vss} So it seems there is a bug in $include that is preventing it from handling fully qualified file names. [ 04-27-2005, 12:37 PM: Message edited by: Fozz ]
  14. Hi Jeff, Page C-1 of VS Language Guide,"C:\Program Files\VectorWorks 11.5.0\VWHelp\Additional Documentation\VSLanguageGuide_11_5.pdf" Show this as an example of the synatx of $include: code: {$INCLUDE MyHD\VectorWorks\Projects\VS\mycode\math.vss}[/code][/indent] I.e. it implies that this is valid: code: {$include d:\TestInclude.vss}[/code][/indent] Question Is the Language Guide wrong? Question When you said: quote: an include path begins at the folder that contains the application. is the application MY application and the folder is the folder that contains my xyz.mcd file?
  15. I'm experimenting with VectorScript includes. This is the main chunk of code: code: Procedure TestIncludes; Begin {$include d:\TestInclude.vss} End; Run (TestIncludes);[/code] And this is the contents of d:\TestInclude.vss: code: SelectAll;[/code][/indent] When I run it, I get this error: Line #5: {$include d:\TestInclude.vss} { Error: Could not open INCLUDE file. } If I replace the include with "SelectAll;" it works fine. I can copy the file name from the "$include" and paste it after the windows "dir" command and it works fine. Any idea why it can't open the file?
  • Create New...