Robert Anderson
-
Posts
3,233 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Articles
Marionette
Store
Posts posted by Robert Anderson
-
-
Giovanni, jnr, and Suzanne,
As moderator of this portion of the forum, and as a manager for the VWA product, I have been reading this discussion with great interest. There are several issues expressed here, and the practical solution for them might be either straight-forward or difficult, depending on what we agree the problem really is. So let me begin by posing several potential complaints, one or more of which we could be discussing here:
A. I delete doors but they still show up on the door schedule.B. I don't want doors that have no ID mark to be on the door schedule.C. I can attach a door record to anything and it will show up on the door schedule, even if it's not a door.D. It's too easy to "double-insert" a door into a wall such that one door obscures another.
It's worth noting that I have listed these problems in approximate order of their programmatic ease of fixing, from easy to difficult. Some of them might even be fixable in the settings that VWA has as defaults. Let me discuss the problems in order above:
A. I DELETE DOORS BUT THEY STILL SHOW UP ON THE DOOR SCHEDULE: At its simplest, this might be failure to recalculate the door schedule worksheet. The user can open the worksheet (most easily with a right-click) and choose recalculate off the worksheet menu. This problem might also be related to problem C below.
B. I DON'T WANT DOORS THAT HAVE NO ID MARK TO BE ON THE DOOR SCHEDULE: Door (and window) objects in VWA default to having their "on Schedule" property set to TRUE. This means when you draw a door, it's going to show up on a schedule as a "blank line" even if it's an existing door, a door in the shell building (when I'm doing a tenant finish plan), or some other door that I must represent but I don't care about. We can solve this problem by having doors and windows default to having this property FALSE (so they won't create a line in the schedule) until they are "blessed" with the ID tool, which will turn on this property and allow you to fill out the fields. However, this entails a change in the default behavior of the program, which is always an issue for existing users.
C. I CAN ATTACH A DOOR RECORD TO ANYTHING AND IT WILL SHOW UP ON THE DOOR SCHEDULE, EVEN IF IT'S NOT A DOOR: This problem arises out of a desire to have the ID tool be flexible -- who's to say that a user doesn't want that polyline-shaped thingie to be a door? However, we can make perhaps make this less of a problem by having the ID tool more stringently test the object that is selected and if it doesn't meet some basic tests (i.e., it's not a symbol or a door/window object), ask the user to confirm that he wants that group or polyline to be a door.
D. IT'S TOO EASY TO "DOUBLE-INSERT" A DOOR INTO A WALL SUCH THAT ONE DOOR OBSCURES ANOTHER: While users speak of "ghost doors" and "moving doors to see if there is another one underneath", I have personally found that while it's possible to double-insert a door, it's not easy to do so casually. Am I wrong here? Are stacked doors a common occurence in your collective experiences?
You'll notice that I have explicity NOT discussed the worksheet here. While I'm sure we can add functionality to the worksheet and ease its UI regarding borders, etc., that lies a little outside my own personal repsonsibility and I'd like to make sure that the real problems we are discussing here aren't something that can be solved at a more basic level (i.e. a level that I personally can do something about.) So I'm looking for more feedback -- does solutions of the above-stated problems substantially solve your problems with the scheduling feature? If so, I'll get these items bug-listed and we'll begin work on them. Or am I off-base here? I will follow this discussion with interest. Thank you all for your previous and future postings in this area.
-
antonio, please send a copy of the file to
randerson@nemetschek.net
Thanks!
-
What version of VW are you using?
-
Please see my posting under the Axonometric thread.
RFA
-
VectorWorks has two projection types for creating plan obliques. These are the so-called "cabinet" and "cavalier" projections. Cavalier projections are isometric. X is presented along X, Y along Y, and Z at either 45 or 30 degrees from X depending on which of the two Cavalier projections you use. Cabinet projections are the same, except the Z value is at 50% of isometric. This gives a less vertically exaggerated view. Both of these are in essence rotated "axonometrics" (at least, that's the way I learned to draw "axos" in school). So plot one of these from your 3D model, rotate the paper 30 or 45 degrees, and there's your axo. Note that there are some rendering limitations -- you can use only the "native VectorWorks" methods of rendering -- hidden line, dashed hidden line, and the various polygonal renderers. This is because none of the "standard" rendering libraries (OpenGL or Lightworks) support these projections. VectorWorks is in fact one of the few CAD programs that supports these projections.
HTH, Robert
-
This is fine. I should get the file. Sorry about not posting my email, which is randerson@nemetschek.net.
-
Jim, send me the file and I'll take a look at it. One picture is worth, etc.
-
Jim, I'll try and address your questions below as best I can:
"...The essential problem that I have is that the modifiers seem to cut into the hillside only around the perimeter of modifier, but the interior volume that should have been cut away is still mostly there..."
One possibility here is that you're still viewing the Existing DTM which is blocking the "cut" areas of the site. Select the Existing DTM symbol instance and set it to an invisible class.
"...An example would be if I?d setup a square slab as a modifier and updated the DTM, I?d be left with something that looked (roughly) like a square shaped trench dug into the DTM (not a whole cube carved into the land). This seems particularly prone to happen with the roadway object I?m using for the driveway (I get little mountain peaks at roughly the height of the original DTM jumping out of the middle of the roadway)..."
This occurs when you don't have a fence modifier surrounding your pad modifiers. Think of a fence as a "limit of construction". The fence causes the DTM calculator to ignore "original" site data that it surrounds. When creating multiple modifiers for a single DTM, do you draw one ?fence? line around the whole thing?
This is one way. You can also draw a fence around each individual pad. Just remember that the DTM will try and "fit" the site to the pad beginning at the limits established by the fence.
Exactly what class should the modifier objects (the 3d Polys) be? Exactly what class should the fence (the polyline boundary) be?
Pads should 3D polys of the class "Site-DTM-Modifier". Fences should be 2D polys of the -same- class.
Exactly what class should the DTM itself be?
This doesn't matter.
Is there some ordering dependency for the DTM, the modifiers and the fence? Does the fence need to be ?in front of? the modifiers, and the modifiers ?in front of? the DTM?
No.
When making changes, is it better to update the existing ?Proposed DTM? or to simply re-create the proposed DTM from the original site DTM?
Update.
For the modifiers and the fence line, are there any requirements in terms of fills?
No preferences. Should operate on class only.
Hope this helps. Let me know what results you get.
-
Jim, which product are you using? VW Architect or VW LandMark?
-
Use the "Update to v2 Objects" command. On Tool/Utilities submenu.
-
Erich, the callout notes are not regenerating because they have a parameter value that is causing them to fail. If you send me the file (to randerson@nemetschek.net) I will look at the file and determine which setting is causing the problem. If possible, send me a file with only one object in it -- an "invisible" callout. This will make diagnosing the problem easier.
-
The short answer to your last question is 'yes'. You can set the default class (the "auto-class") of a plug-in object using the Create Plug-in... command (sometimes referred to as "the Plug-in Editor").
To set the default class of a plug-in object: 1. Choose Organize>Create Plug-in... 2. Select the plugin object whose auto-class you want to set. 3. Click the Properties button. 4. In the Default Class field, enter your desired auto-class.
Note that the class will be created in a document if it does not already exist.
To set the default class of a symbol definition: 1. Select the symbol in the Resource Palette and click the Edit button on the RP. 2. In the Edit Symbol dialog that comes up, choose "Insertion Options" and then click the Edit button. 3. Choose the class from the Class pulldown in the dialog.
Note that the class for a symbol has to be pre-existing, so you will need to create it if it does not already exist.
HTH
-
There is no definitive listing. Our technical publications (documentation) department, while they do a fine job, can't keep up with our development staff.
Plugin objects were originally intended to be "self-documenting", i.e., simple enough that the user should just place an instance of the plugin, move to a 2D or 3D view, whichever is more relevant, and play with the parameters to learn it. For very complicated plugins, this is not practical. However, with each release, we add ease-of-use features to plugins, and you can expect this to be a continuing process, so maybe we can get back closer to our 'self-documenting' ideal.
No offense on the PDF comments. These are really just for users who want a printed catalog.
-
The Complex Window 2 object has a "Top Pane" parameter. Choose the "Round" option.
-
There is currently no automated features in VectorWorks Architect for SIPS. However I know there are VW users out there doing SIPS projects. Hopefully we'll here from them on this topic.
-
David, a few tips:
1. DWG/DXF export is view sensitive. If you're in plan view, 2D stuff will be exported. If you're in a 3D view, 3D stuff will be exported.
2. I don't know what version of VW you're using, but DXF export is one feature that is improved in virtually every version. So, especially for DWG (but in general also), later is better.
3. If you want more general exposure for this problem, you might try posting it on the VectorWorks General discussion list, instead of the VW Architect list. Our DXF/DWG experts prowl that list.
HTH, Robert
-
I'll try to address some of these issues:
1. VectorWorks and VWA have what is called 'hybrid' objects. These objects (including but not limited to walls, roofs, slabs, doors, windows, etc.) are both 2D and 3D. Creation, changes, edits, etc. made in 2D views are simultaneously reflected in 3D views. Editing in 3D views, while somewhat more limited that editing in 2D views, also reflects in those 2D views. Certain kinds of editing (such as altering the profile shape of a wall) can be done only in 3D view. However if you move a window or door in a wall from a 3D view, that change will also be reflected in the 2D view.
2. VectorWorks and its product line currently support live elevation and perspective views using its "layer link" feature, but not live sections. Sections (2D or 3D) may be made automatically, but they are not updated.
3. VectorWorks has extensive 2D drafting capabilities that go beyond the 2D representation of the model, so you can create virtually anything in VW that you would do by hand-drafting. The "look" of the drawings produced in VW is one of our strong points. In addition, VW may be used as a simple graphics or sketching or 3D-massing program, allowing you to attack your design problem from any direction you desire.
I hope these comments are helpful.
-
The property bounds tool was significantly expanded (non-tangent curves, etc.) and is now available only in VW Architect and VW Landmark.
-
If the doors do not cut the wall, it means they are not inserted in the wall. Try giving your wall a fill so it is easier to "pick" with the door tool OR "pick" the wall on one of its surfaces instead of in the middle of the wall.
-
The two layer modes:Show/Snap Others andShow/Snap/Modify Others
work only if all the pertinent layers are of the same scale and in 2D view (Top/Plan View).
HTH.
-
The rafters are disappearing because they are plug-in objects, also known (more generically) as "container" objects. Other types of container objects are symbols, groups, and certain types of 3D/hybrid objects such as slabs and columns. Container objects have a "container" that can be assigned a certain class while it has internal objects that can be of a different class. Your rafters disappear because you have set their container class to 'Rafter' while the internal components of the rafter are still in 'None' class. Normally this is fine (i.e. hide the 'Rafter' class and your rafters will 100% go away because you've hidden their "containers") =unless= you hide the None class =or= set the class options to 'Active Class only'. The simplest way to avoid this is to:
1. Always have the None class visible;2. Don't use 'Active Class only' mode except for certain very specific tasks
HTH.
-
Create Roof from Polygon requires a 2D polygon, and it should be a closed poly.
-
This bug occured when you updated a reference and weren't in plan or top view. If you had your references set to automatically update and didn't remember to save in top/plan view, references would move. This bug was fixed in VectorWorks 9.0.
-
The only way to change the edit history of the titleblock is manually using the OI palette.
Door Wars
in Architecture
Posted
Thanks, Giovanni, for your description of the limitations. I'm not sure what you mean we are "still talking about this" -- your first posting was on 8/29 and now it's, what, a week later? I'd say we're making progress!
With your forbearance, I'd like to restate your comments as wish statements:
1. Wish: Doors that are demolished should automatically have their 'on schedule' property set to FALSE so they don't ever show up on schedules. (This can now be done manually using the OI palette.)
2. Wish: when I create a schedule, I want an option to create the schedule for either the whole file or a subset of layers in that file. (This can now be done manually using Database Criteria.)
3. Wish: I want a quick and easy way to copy information from one door/window (i.e. any scheduled item in a wall) to another.
4. Wish: doors should not default to being on schedules. The use should consciously have to enable their presence on schedules by selecting them or clicking on them. Using the ID tool should automatically enable this property.
5. Wish: OLE of Excel worksheets. Heck, let's throw in Word documents, too. ;-)
6. Wish: automatic way to turn a database-style worksheet into a "static" worksheet, preserving all formatting, etc. (This can be done manually by exporting and then re-importing the worksheet, but formatting is not preserved.)
7. Wish: "Door auditor" that would identify in the drawing doors whose records are incompletely filled out and allow the user to fill them out easily.
8. Wish: "live" editing of database cells in worksheet.
Giovanni, are these accurate descriptions? How about you others? One very important part of our development process is to reconcile potentially divergent directions, so it's important to get input from as many users as possible.