Dieter @ DWorks

This is defined by the Story above.....and yes the top Story has no vertical definition, this I have experienced is a faulty set-up because my wall definitions are bound to certain predefined DLs (e.g. slab DLS)on and above the actual Story, however walls on the top floor then don't have anything to bound to because these default DLs don't (need to) exist there..... Your walls will be fine if you have a separate story for you roof... But then again, I have never had the situation that all of my walls are bound to the same thing....

Then where do you set this thickness/height? And what's the height of the topmost story then? Stories are actually groups of levels (through design layers), with each such group a base z value. Thats all, nothing more, nothing less...

Check also your wall style and make sure they aren't references, because if they do, and you have set the option to edit the class attributes by the reference, this can happen.

NO. The layer height is a setting that hasn't anything to do with the stories. The stories and their levels (layers) are all about levels (Z coordinates). The layer height is something from before stories and can be used separately. I use the height only for my spaces, so they can show the height of the room.

That's what I have been saying all along.... The auto-hybrid shouldn't be another object, it should be a feature of the symbol object we have, so you can have all benefits of the symbols with it: placing multiple instances, getting it in worksheets, .... PLUS it will be more consistent and easier to understand.

This happens when VW hasn't enough memory for displaying them. I have this also sometimes, they show good and then after working some hours on VW they don't show at all (gray box). Try restarting VW and check your memory.

Reinstalling your system is sometimes the only solution because programs can adjust your installation and can mess up your pc.

You can set the bottom and top of the wall to bound to a level. If you then change these levels, the walls will stretch accordingly.

A story doesn't have a height, only a layer does. A story is just a level you set and can have other levels attached to it, each with a level type. You need to look those story and level types as just key levels (= z values) that objects can bound to. When you then change a level, objects will follow. The thing with VW is that for defining a level, you have to make a layer, and the z-height of that layer is the level. Apart from all those levels, layers also have a height, which you can use separately to also bound to. A good setup of stories and layers will result in an easy workflow where things are easy and quick to adjust, but you have to think it through and experience which way works best for you.

1) You can with my tool: http://www.dworks.be/Products/Plug-ins/DUpdateTitleBlocks/ 2) It can be done through scripting, but VW doesn't have it out-of-the-box.

They will be in your resource browser. You then just save the file and add it to your favorites folder so it Always end up in your resource browser favorites for easy use. This folder can be found in /Library/Favorites, either in your user folder, workgroup folder or program folder. If you work alone, just put it into your user folder. If you work with other people who also want to use this, put it in a workgroup folder (can be any folder you make on some kind of network) and add this folder in the VW preferences. If you want them to popup when you need to select a hatch as attribute, you can put the file in /Library/Defaults/Attributes - Hatches

You can import one of your Autocad drawings and have the hatches. It's as simple as that.

Renderworks is really worth it's price! I know its extra, but you can get so much out of it.

If you don't have Renderworks, then you can do: 1. Annotate with hatches 2. Create planar objects in 3D space with hatches (like sketchup)

I think a solution to the file size when sending could be some sort of command that clears the viewport cache? So that it's always on and that the user needs to clean the cache when they want it and need it.

In VW, you have two enters, the normal enter is the one on by your numeric keyboard. The 'soft' enter in VW is the one you use while typing tekst.

I once tried to work with the option off for the reason to get the file size down. I was wrong doing this. You then have to re-render viewports that where finished days ago and weren't affected by the changes you made in the meantime. You don't have a clear view on what each viewport shows when just opening the drawing. ....

Those objects just doesn't work. It's far better to use symbols instead.

VW doesn't put the text on multiple lines by itself. You need to enter your text in the larger text box with soft enters between the lines.

Have you checked if the window uses the wall line style or the wall component wall style. (Settable in the wall.)

I would never think to insert these in walls. It just doesn't feel right to me. And like you said, most of the time, the only thing you need to insert in walls are windows and doors, or custom symbols to cut out/reshape walls.

YES! This is the simplest solution if the symbol doesn't have to cut the wall! Why didn't I think of this....

You Can't do it in once step. You need to have two symbols that together represent the one you want. You place each symbol in one wall and then it will be like it is one symbol.

Yes. For Sheet name and sheet number, you can use your record with fields named ...._SD and ...._SN. Make sure the automatic annotation preference is on in the document preferences. For file name, date, you can use http://www.dworks.be/Products/Plug-ins/DUpdateTitleBlocks/

The first two work with the eyedropper tool, but it's a pain when working with the same classes in each drawing and having to set the visibility and overrides each time to the same values....