Pat Stanford

You can fully customize the look. Change fonts/sizes, change cell borders, etc. If you post a file with a few of the symbols you want to use, I can give you a basic worksheet you can use as a starting point to develop what you need.

I would probably consider using a Worksheet to do the count and then include the worksheet as part of your title block. You could probably also do it using the Data Tag. How are you identifying each bit of information? Symbol Name? Record.Field? Class? Something else?

The best option is to set you design layers at "close" to the desired output size. So if you are going to do your plans at 1/4", site plane at 1/8" and details at 3/4", you probably want your design layers to be at 1/4". That way the line weights and test sizes are close to WYSIWYG. For the viewports that are at other scales you can click on the Advanced... button at the bottom of the OIP and set the Line and text scaling options so you have consistency acrosss the entire set. Others will probably be able to offer more specific advise.

Check the plants in the Render pane of the OIP and see what Sketch Style they are set to. It is possible they are set to No Sketch.

More information about what version of VW, what operating system, and what the user is doing before the crashes would help with debugging this. This is not a usual occurance. Take a look at this thread for some basic troubleshooting.

I don't believe you can override the visibilities or attributes of referenced viewports from inside another viewport. The workaround is to duplicate the referenced viewport and change the visibilities/attributes there and then control which version is seen in which viewport. I hope I am wrong and someone else can tell us both how to accomplish this without duplicate objects.

Probably because 1/4" is probably the most common scale for Single Family Residential in the US. I don't ever remember a setting for default scale.

I can't help with the trusses. Sorry. You might have to actually model them.

You will have to set the Texture on the wall you want to see through to be transparent. You probably want to use Plain transparency and not Glass as the Glass textures require lights instead of just the default lighting. Alternatively, could you use the Clip Cube and just move it up to eliminate the wall in you need to be transparent? You would still be able to fly around and not have the wall in the way. But that won't work if you need things to show between the viewer and the wall.

Please check that the text is at zero rotation on the design layer. If it is rotated more than 0.01 degrees then Adjust Flipped Text does not function. See this thread for more information. If this is not the problem, ask again. If you can, please post a sample file for us to look at.

This can also be done relatively easily. FSymDef returns a Handle to the first Symbol Definition in the file. You can then use NextObject to step through all of the symbol definitions and check for a specific record and edit as appropriate. Let me know if you need a sample script.

Python: def vs.AddWSColumnOperator(worksheet, databaseRow, column, operatorType):    return None With an operatorType of 2. The inverse function is vs.HasWSColumnOperator. I have no idea why these are named this way instead of using the standard Get and Set names.

Set the scale and then save the file as a Template. You can also store any resources that you nearly always use as part of the template. If you really want to have the template with your preferred scale open when you select new (instead of having to select the template), you can save the template with a name of default.sta in Applications:Vectorworks XXXX:Libraries:Defaults:Templates. Replace the XXX with the name of your application folder.

When you create a new Class there is an option in the Class dialog box where you can choose if the class will be Visible/Invisible/Grey in existing viewports. If you Duplicate a class you won't get the dialog box and it will use the same setting as what you used the last time you where in the Class dialog box.

Alternatively, if you want your dimensions to be Red, you can use Layer Overrides or Class Overrides to make everything but your dimension classes to be Black/White and the Dimension class(es) Red.

Save Viewport Cache. Large Textures/Images in the Resource Manager. Try Tools:Purge and see what happens when you remove unused resources. 19MB is not at all an unusually large file size.

@Haydenovative Just to be sure. This is a Vectorworks Title Block Border object we are talking about and not just a symbol you have created to use as a title block? The Convert to Plugin Object option is equivalent to the Convert to Group. If you have more than one object selected when you make the symbol you with get an option of Convert to Group. If you only have a single object then you will get a Convert to Plugin Object if it is a PIO or Symbol or Convert to Group is it is a single object, but you won't actually get a group when you insert it, but rather the single object.

And you also get the added complexity of all those modules and the "benefit" of nesting of code being determined by the number of space or tab characters. IMNSHO, I you only want to do things inside of Vectorworks, Vectorscript, especially if you have Pascal experience, is the better choice. Lots more code samples available to learn from. If you want to make something that is beyond the capabilities of Vectorworks, then you need to consider Python or the SDK. You can go a long way with any one of the options. Written by someone who had to try and debug Fortran 77 what was white space delimited and who can no understand why ANYONE would create a language where characters you can't see matter in how the code runs. ;-)

@MullinRJ is correct as usual. The caveat I would make is that it is not an ELSE IF. It is an ELSE that uses and IF as the if condition. Subtle difference but important. There are languages which specifically have ELSEIF syntax. Vectorscript (and Pascal on which it is based) don't. Nested IFs can be very useful, but also very complicated to debug. Be careful with your parentheses, Begin/End statements, and indentation. I always use double indentation, one set for the nesting of a Begin/End pair and then the code inside the begin/end is indented again. That makes it easier for me to read the code.

Instead of trying to get 6 to work at once, get one working to get the format then expand. The basic format is IF(some condition) THEN Do Something Else Do Different Thing; I often include Begin and End inside an If function even if I only have a single line of code in the thing I want to do so that if I need to add more code later the structure is already there. IF(Some Condition) Then Begin Do Something; End ELSE Being Do a Different Thing; End; Note that there is no semicolon after the end before the ELSE. If you are using a single line you must not have a semicolon before the ELSE either. IF COUNT((R IN ['Wohnung']) & ('Wohnung'.'Whg-Nr'=NR) & ('Wohnung'.'Zimmertyp'='Wohnen') | ('Wohnung'.'Zimmertyp'='Zimmer') | (('Wohnung'.'Zimmertyp'='Arbeitszimmer'))=1) THEN EINZW := EINZW+1; So this looks to be fine syntax as long as you don't need an Else. Are you sure that your conditions are being met? Try simplifying it and see if you can get EINZW to increment. Maybe just count the objects that have a Zimmertyp='Zimmer' The source for general syntax for Vectorscript is the Vectorscript Language Guide. It can be downloaded from this page of the Developer web site. https://developer.vectorworks.net/index.php/VectorScript

Someone pointed out to me that the functionality pointed out by @markdd is called Select Coincident Objects. You can either do it Mark's way by holding down the "J" key while you select the top object or you can right click on the objects and choose Select Coincident Objects from the Object Context menu. Thanks Steve.

What objects switch to rotated plan view when you double click them?

Glad to help. Especially when a new version is just released it is easy to blame bugs. But there are enough beta testers that something like this would be (in my NSHO) unlikely to have never been reported before. That makes we want to take the "deep dive" and make sure you have checked everything else before claiming a bug. There most certainly are bugs that get through, but if there was really a font import problem I think someone would likely of have found it before release.

Or you can use the Custom Selection menu command in combination with the following scripts. This first one is the most important as it restores the visibility of everything that you hide using the second script; Show(All); The second one here hides (makes invisible) all selected objects. Hide(SEL=TRUE); Create New Scripts from the Resource Manager with the text above. Then either select the objects you want to hide, or select the objects you want to show and then use Invert Selection from the Edit menu and run the second script. When you are done, run the first script and you will restore the visibility of everything you hid. Class and Layer visibilities will still apply.

Opacity only applies to 2D objects. In 3D you would have to apply a transparent texture to the objects to get them to display like this. If you texture by Class, you should be able to override the texture in a viewport to get the image you want.