Jeffrey W Ouellette

What version of Quicktime are you installing?

Scott, This is a know bug. It is a memory leak related to VPs. The application does not properly "release" RAM that is used during the VP rendering/update, after it is complete. Please submit a bug and attach the file for testing. http://www.nemetschek.net/support/bugsubmit.php

You can also select other Oblique and Cavalier projections for a section viewport. Add that with defining a Finite value for the Depth Range of section display in the "Advanced Properties...", and you get a pretty cool view of a wall section.

Bug submit. http://www.nemetschek.net/support/bugsubmit.php

For version 12, try moving the COUNT column in front of/before the width and height columns.

Doug, Email me the file.

Shaun check out this earlier thread: http://techboard.vectorworks.net/ubbthreads/ubbthreads.php?ubb=showflat&Main=21301&Number=99374#Post99374

Get the 12.5.3 updater from the website. http://www.nemetschek.net/downloads/index.php

Sorry Christiaan, looks like everything is 3D or 2D plan only.

Jody, In VW12, this should work without drawing extra lines in the annotation space of the VP, although not as well as in VW2008, but it is possible. With the Angular Dimension tool selected, at the top of the window, in the mode bar should be three small "mode" icons. select the third, last one on the right. It is the reference line mode. Trace the lines/edges/objects you wish to dimension; drawing "virtual" lines for each edge. No need for the extra step of extra lines. If you want more, gotta upgrade...

Rick, Best practice is to put all custom resources in the Support folder. Updates will overwrite/erase any custom resources in the Application folder. This is how plug-ins worked in VW12 and how all custom resources work in VW2008 (...and beyond...).

One last time, keeping it simple... 1. Be sure data bar is set to "Use floating data bar" (or "Use floating data bar only when tab key is pressed") - SEE ATTACHED IMAGE 2. Select line tool 3. Either click on start point, the data bar should appear when you begin to drag the cursor away from the click point (OR hit TAB to invoke the data bar). 4. TAB to highlight the first value of the data bar, 5. Type in value, doesn't matter from which keyboard you use. 6. TAB to accpet the value and move highlight to next value on the bar, 7. RETURN when you're done entering values to accept and end.

Jeff, Simple answer: hit TAB a second time, after getting the HUD to appear, this will highlight the first filed, then type your number, then hit TAB again to accept this number and move to the next field. When you've entered all the values you want, hit ENTER/RETURN.

Doug, Sorta sounds like a bug. I would have to take a look at this to be sure.

Luke, The ID tag SHOULD NOT affect the insertion of the symbol at all. Could you submit this as a bug and attach the file? http://www.nemetschek.net/support/bugsubmit.php

Mike, "Horses for courses"?????????

David, I don't have a problem with the request, I'd like it too. I have no problem with the "marzipan" method, but I often see it implemented incorrectly. What I am trying to get across is that modeling (at any phase) requires a lot more (fore)thought. Simply adding the capability of doesn't "fix" the issue, but I think highlights existing and future workflow, data structure and representation issues.

Pat, I think "composite floors" are a viable concept. I know ArchiCAD uses them. I would like to see the ability in VW, too. While it would help the "marzipan" model, I don't know what value it may have in a more detailed BIM process. Walls have similar shortcomings. How? When a BIM-cpcable contractor needs a BIM for a project, more often than not, the architect's model is NOT useful, because it is not detailed enough. While the architect has enough information to show a virtual design intent, the contractor needs to show virtual construction, directly reflecting reality (though maybe leaving out all the nails and screws, eh David?). So while two points a thickness parameter and a height parameter may be enough implicit representation for the architect, the contractor needs to be more explicit, showing framing, the "stuff"/services in the wall, the sheathing of the wall and the connection relationships between the wall and the horizontal surfaces above and below. Ideally, the BIM would be able to be "transformed" as it moved along in the process from architect to contractor, without the contractor having to rebuild a new, highly-detailed model from scratch. This requires apps to do things that they don't do yet...

Mike, That assumes drawings are the ultimate output. While, practically and legally, drawings are the standard output now, models are becoming increasingly important and used. The predominant scenario of the future of BIM eliminates paper CDs as we know them today. Any "drawings" will merely be purpose-driven snapshots of the model at any given time. That will require that models, even at early stages, be more "considered", not necessarily more detailed/complete, but at least conscious of the potential for detailed development and completion. I can see, in my own future of architectural practice, the opportunity of projects being conceived and completed WITHOUT 24x36 sets of "blueprints". Instead, an intelligent model will be the basis for all design, permit/review, cost and construction processes. It is starting to happen now.

While the idea of a Floor object being used as a general "marzipan" representation of a floor/ceiling assembly between floors is common, it isn't a good "virtual reality". We all know, in fact, they are really two different systems/surfaces with entirely different characteristics that are held together/apart with an entirely different structural system. If one were to more accurately model reality, one would create a floor object for the structural floor sheathing above, another floor object for the finish floor material above, framing for holding up the floor and a separate extrude or floor object for the ceiling below, directly adjacent to the framing. On the sides of the entire assembly, you would create a wall type that was exterior wall sheathing and exterior wall finish only, drawn directly adjacent to the framing extents (in plan) and directly above the corresponding wall components of the walls above/below. For the interior surfaces, you would have a wall type of just gyp bd sheathing that wraps the edges of the extents of the exposed edges of a floor slab.

Why not just use DLVPs?

Doug, Please download the attached .VWX file with a "type summarizing" Door Schedule. You can either import or compare and adjust your worksheet's formulas accordingly.

Sorry, Mike. No curved section lines.

There are no text kerning functions currently in VW. But this is a good wishlist item.

Martin, In the file folder: Applications>Utilities, There is a program called "Console". Open it. From the top Menu Bar, select View>Show Log List. On the left hand side of the window you should see a file tree. Expand all the little triangles. Look for CrashReporter. Under CrashReporter you will find "VectoWorks.crash.log". Select it and it will populate the window. From the top Menu Bar, select File>Save a Copy As... I suggest saving to your desktop and then sending that copy along.