Dieter @ DWorks

If you use the command 'zet om naar polygonen' (Change into polygons?) and choose the option for hidden lines, VW draws all existing triangulated polygons. So what's not seen is there too! and all faces are triangulated into more then one polygon! Is this meant to be this way? Because when it is, this command is useless. The only way I want to convert a 3D look into polygons is because I want to change the thing.

I had a really big problem today: I was designing an elevation for a building and it was becomming so huge, that I had to push ctrl+shift+b 1 minute to send an object to its correct place. I mostly use the send to background or foreground command, but sometimes there are too many objects, that you can't do that. I want to have a way to see where the objects are in the stacking order and that we can send it somewhere in front or back of a certain other object. Maybe a command where the selected object can be placed 1 place before or after the next selected object. This tool would work as follows: * select the object that needs to be moved (back/forward) * select the tool (one for before and one for after, or a choice) * select the object where it must placed before or after Or maybe someone will have another idea?

The option is on. So that doesn't do anything. That option is for rendered views viewports. So the 2D view viewports still update when moving through the sheet.

You can specify the standard values, they should come up every time a symbol is placed. What are you trying to do? Because a symbol can have many instances and each of them can have different data, so using a record to specify information of a specific symbol 'type' is not a good idea, but I do not think there is another way?

This is the situation now: * all rendered viewports do not rerender untill you click the update button. * all the 2D views viewports rerender all te time, even if they don't change. The problem I'm having is that when you have lots of viewports with 2D views on a sheet layer, VW gets very slow to constantly update them when moving through the sheet layer. What I want is: * an option to choose if the 2D views vp should be rerendered automaticly or only when you click update. This way you can turn it off when you have a small project and turn it on when you have a large project. This should not be too difficult to implement. And it should be a great improvement in workflow.

The way I understand you is that you use two records with eacht a prefix, P_ and S_. You'll need to make 1 record, and the record fields must have a prefix of P_ or S_. This way the titleblock will work.

that's fine, and I've been there, but I'm looking for all the details. Charles: If you would, I'll be thankfull.

I'm doing a project on the history of VW. I'm looking for a list of all tools, menus and pio's of every version of VW. Does anyone knows where I can find those?

I do not know if VW has something to do with it. But if this is a VW issue, please fix it, I've got a small screen on my laptop: * I can't dock to pallettes above of each other, only next to each other (except for the tool pallettes).

I noticed that when I change the settings of a texture of an object, All objects become udated and rerender. This is a terrible nightmare because I have lots of those pio poeple in my drawing and they take a lot of time to render! How can I solve this? What can I do to workaround this? Any suggestions?

Susan, You may be angry, but just try to see that mike is just helping you out. I just don't see that you are angry after you bought the product, while you know the price before?

And it would also be great if this tool could be made more general (made one tool) and let it be used on all types of lines, circles, arcs, polygons, polylines, ....

??? In Belgium, we first built all our walls in brick and then lay the floor, so I have not a single wall that starts on the finished floor and thus not a single wall start at 0. And reasons why I use 2 walls instead of one with components: * You can't set the 'bot z' of the wall components, * You can't use classes for wall components, * You can't calculate the wall correctly, * The wall joins don't show correctly most of the time (when using special constructions and that's most of the time), * The cut of a symbol or pio is not realistic (the inner wall cut must be greater then the outer wall cut if you use bricks), * ... That's the main reasons of not use a wall with components, so maybe they can added to the wish list?: * 'bot Z' for wall components AND a 'bot Z' for the wall as a whole, * assign classes to components, * when using loci in a symbol/pio for creating the cut, make it so that each wall component can have a different cut (maybe this can be done when you set your loci where the wall component should be? You'll have more loci, but you'll have realistic cut.)* ...

Well, The way I think in VW is the following: The height of the layer is the height you have in your room. So If my room is 250cm, the layer is 250cm. This means that the level of my finished floor is the ground plane of my layer. I use a layer for the room and the underlaying floor package and slab. Now walls start from the slab. Thus the walls always need to be under the ground plane of the layer. You can set it in the info pallet now, but it would be very handy if you can set it in the wall style, so it's ok from the beginning (when they are placed in the drawing.) I draw my exterior walls with 2 walls because of several reasons. And I want my model as exact as possible. I hope my post is understandeble.

That's the point. When you draw a wall, it's always 0. So you'll need to change i everytime a wall is drawn. It's hard to not forget it. It would be great if you can set this in the wall style like the extra height.

I like the new walls of VW12, but I'm missing something. We can set our wall so that it gets the height of the layer. We can even set the extra height it must get. So we can have our walls to be the height of the layer + the floorpackage. If we import our walls, they are always on z=0. I always need to change it to z=-extra height. This is because of the floorpackage that's under the level of the layer. I think it would be a great improvement if we can set the z of the wall (relative to that of the layer).

If she doesn't I am intrigued about what sort of work she is doing. The added Australian content is almost totally for architecture and complements and enhances the capabilities of Architect. I find it hard to believe that it is of no value to anyone using Architect. I must agree on this. Maybe she'll have to consider to buy the pro version instead of the architect version?

It's normal that you pay more if they added a lot of extra tools. But I am still dissapointed by the way those tools get updated every version: they don't. So all the bugs that where in earlier versions are still there! That's a real shame. If they ask more, thy should also update their tools.

If only we can relate those to classes. That's one of the reasons I still draw in single walls.

It works on vista. It works even better on my vista pc then on my xp pc.

So what can I do NOW about those error messages?

The stair object does not seem to work correctly. this is what it not does: you can set the class of the 3D objects to style-n. but when the stair is created, the class is not style-n but instead it is the standard class for the whole object. Can someone check this? I also get the following error when trying to change the parameters of the stair: The stair works, but I can't edit anything, it stays standard, and it doesn't show like it should be showing.

Maybe if NNA add a new kind of thing like a tool, but a menu, like the toolbars in word where you can have new, save etc. This would be a real good improvement for those that like to work this way

We also don't use the space tool, but simple polygons with records on it. If you define them good from the beginning, it's easy to get your shedule out of it

You can snap, but only at endpoints, so if you want to snap to a line, use a loci