KennethEvans

Members
  • Posts

    6
  • Joined

  • Last visited

Everything posted by KennethEvans

  1. I found I don't have to locate the camera in the plan. It is enough to select anywhere on the line to the focal point and double-click or use the Open the View Associated with this Object icon. This is easy to do and is a reasonable solution to what was formerly an annoyance.
  2. I just found that for the objects that moved on coping, they were set to Elevation Reference=From Floor (in Open Object). This apparently is the default. Changing them to Absolute fixed the problem. Then they don't move when copied. It also made them easier to position accurately. There are also options for From Terrain, Ceiling, or Roof. So this seems to be a fairly easy way to add a building to a terrain-only plan. Once the building is there replacing it or removing it, may be a little problematic but probably doable. I haven't tried that yet.
  3. When a plan is saved and reopened, the camera views that were open do not get reopened. At least in my experience. I have been opening them by locating them on the plan and using Open the View Associated with this Object icon or double clicking. This is tedious, and overview cameras are often a long ways away from the plan. In addition, the cameras are small and hard to find and to click. It knows what cameras are included. Is there a way to find this as a list that is easily clicked? I suppose I could change the default camera size to make them easier to find, but this clutters up the plan, and it is still a tedious procedure. Thanks.
  4. I have searched fairly extensively for this topic but have a not found a workable solution. It seems to be something that others would want to do as the Terrain can be resource intensive. It is not easy to copy the terrain only to another plan, or at least I have not found a way. I can copy the perimeter, which becomes a polyline. I can then create a new perimeter of the same size. I can then shift-select every terrain item and copy them to the plan with the new perimeter. This seems to work but is tedious and error prone. I can retain just the Terrain in a plan. In another plan with the building I can do Edit | Edit Area | All Floors, then draw a marquee and copy the building. However, when I paste this into the new plan, some things move. I ones I have caught are Doric Columns (Millwork) and foundation supports I added as to support the columns, which are Geometric Shapes. These have a Floor to Bottom distance in Open Object. This and the other parameters have not changed. What seems to be happening is that what it thinks is the Bottom has changed. This can be seen in the screen shot. The plates which are up on the columns were under the columns in the original plan. Some of the 18 x18 foundation posts, which are Geometric Objects, have moved up, but not all of them. I have not checked if copying the Terrain does not also have this problem. I only tried it with a simple model. 1. So a good procedure for developing the terrain apart from the building would be really useful. 2. Some explanation of what it thinks the floor is and how to get around the problem that happens in the screenshot would also be useful. Thanks.
  5. Eric, Thanks. That did it. Had to set it to 200. Not something I would have guessed to do. Makes it much easier to do the elevation, now.
  6. I am trying to build a terrain for a lot with a complicated topology. It is next to impossible to distinguish Elevation Data from the rest. I can change the fill but not the line weights. That is, I can change them either in the Display Options or in the Open Object for the object, but they don't change in the UI. In the attached screen dump, the selected line has a line weight of 30 (default was 18), but it isn't any different from the rest. Note that I _have_ redefined the fills for some objects. I do have Line Weights selected on the left. Selecting or not selecting it makes no difference. This is making it very hard to define the terrain. For example I was getting glitches that I finally traced to short stray lines apparently generated when trying to connect splines. I could not see them.