Pat Stanford

In imported data, it is quite possible that you have "curves" that are actually hundreds or thousands of line segments. That will certainly slow down a file. If you are only using the Acadias data as backgrounds, it is usually better to import it into a separate file and then do a referenced viewport into your working file. That way you isolate all of the Acad "Layers" (VW Classes) to the other file instead of contaminating your drawing. I know that best practices are probably too late for this project. About the only other thing I can suggest is check for duplicated objects. Run the Purge command using the "Coincident Duplicate Objects" options. Perhaps things got doubled or tripled and you can get rid of them to speed things up.

Could you possibly use Classes to isolate the imported object and group them? You can always enter the group and Cut/Paste In Place the items that you need to work on while leaving the rest as is. Or even just try a quick test to select everything on each design layer and Group them. At least that way you can relatively quickly see if that help with the speed.

One of the things that greatly slows VW is the calculating and redrawing of selection handles. If you can group a lot of the items so the selection handles don't have to be calculated (except for the 8 of the group) you might end up with a snappier drawing. A long time ago (in a galaxy far, far away) I did a test. I tried a file with something like 60,000 lines. To Select All or Deselect All took multiple minutes. I then Grouped everything and the time to Select All went to just a few seconds. Your mileage may vary.

Several possibilities, but none of them are really a "link". 1. Put the image into the symbol and set the class to all of the images to the same class. When you Recalculate the worksheet, make sure the class the image(s) are in is turned on and the classes that the other parts of the symbol are turned off. 2. Put the images into individual symbols. Store the symbol name in a Record.Field attached to the symbol. You should then be able to use the name of the "image symbol" to use the image symbol for the image in the worksheet.

What version of Vectorworks? If you have Fundamentals, I don't believe that it contains the Door Tool, so you can't modify Door objects, but you can view them.

You could probably use Saved Views to accomplish this, but there is no way to do this (that I know of) using general layer switching routines.

Place Stake objects where you need the elevations, select them and use the Send to Surface command in the AEC:Terrain menu (in the Designer workspace. Probably the same in the Landmark workspace.).

You will be able to Open VW2014 files, but they will be converted to VW2021 file format. You can export back to VW2016 but not VW2014. If you are trying to work with someone who is still using VW2014 you will not be able to round trip the files.

Every Var does need to be defined somewhere, but that can be in the Global Var declaration, in a sub procedure Var declaration, or as part of the Function/Procedure parameters.

Very nice. My first count was 10 lines. You did 10. But you don't need the global Var declaration. Since H is defined as a part of the StopFlipping procedure, it only needs to be defined there. So 9. ;-)

It does not look like there is a way to change the default. It appears to be hard coded in the Viewport creation code. :-( A script to change all viewport would be pretty easy though. @michaelk?

When you Ungroup a PDF you typically end up with 3 items. A bitmap of the PDF on top. A white rectangle (we think it represents the paper). And finally at the bottom a Group containing all of the vector linework and text that VW can extract from the file. It sounds like you had ungrouped the PDF and deleted the bitmap but not the rest. Glad you found the problem.

Be careful with Update All unless you are sure of what you are doing and don't have a bunch of high resolution renderings. I ran that ONCE on a file with about 300 viewports and it hadn't finished in 36 hours when I finally force quit it. This was about 15 years ago so the machine was much slower than current machines, but even so, think about it before you tell it to start.

How complicated is your drawing? You might try exporting back on version to a VW file and then updating that back to your current version. Is there any specific action that causes the lines to show? Have you tried to Purge unused objects?

I just tried this in a later service pack and while you could not fillet a poly line that crosses itself, it does not crash for me. Are you running SP1?

In the Mode bar you have the No Interactive Scaling option (first item. The double diagonal arrow with the Red Circle with diagonal (Don't) line.). Select either the second (Single Object Interactive Scaling Mode) or the third (Multiple Object Interactive Scaling) and you should be able to make the adjustments you need.

Because this is just very simple Vectorscripts, I would expect this to work for a long time to come. Things in Vectorscript are rarely deprecated unless they break something else.

@JuanP ??

Yes, you can Batch Convert. It is in the File menu. What about making a folder of Aliases to the referenced files and Batch Converting that folder? The challenge may be that Batch Convert may want to change the file names. You might be better off just cloning the entire folder structure and batch converting everything with just a new name or year on the top level folder.

VB = Vectorworks Bug. Shorthand from the programmers and Beta testers. Just go to Bug Submit at the bottom of this page and choose Bug Submit in the Community column.

Can you post a sample file for us to look at. Nothing that you show above gives me any idea about what is going on.

Take a look at these threads. Ask again if you need more help.

Escape will exit the Flyover tool. To go back to Top/Plan it is exactly the same as it has been forever. Either select Top/Plan from the View menu:Standard Views. Or use the keyboard shortcut of Command-5. Or use the Numeric Keypad and hit the Zero key.

You can do multiple viewports from a single Shuttle File. You can put them on different layers or just set the Class of the viewport to separate them. You can (I think) just make the first Referenced Viewport then duplicate it and edit the Viewport visibilities to get the other ones you need. Ask again if you need more clarity.

Take a look at the Set Record Field node in the Record & IFC section. You should be able to use String nodes to set the Record Name, the Field Name, and the Field Value. One Set Record Field node for each of the extrudes in your Marionette should be all you need. You will need to already have created the Record Format in the drawing prior to running the Marionette. Or you could use the Create Field node to build the Record Format from inside the Marionette. But in MNSHO, it is safer to have it already created.