Overview
Autodesk® Project Vasari is an easy-to-use, expressive design tool for creating building concepts. Vasari goes further, with integrated analysis for energy and carbon, providing design insight where the most important design decisions are made. And, when it’s time to move the design to production, simply bring your Vasari design data into the Autodesk® Revit® platform for BIM, ensuring clear execution of design intent.
Project Vasari is focused on conceptual building design using both geometric and parametric modeling. It supports performance-based design via integrated energy modeling and analysis features. This new technology preview is now available as a free download and trial on Autodesk Labs
http://labs.autodesk.com/utilities/vasari/
Tuesday, November 16, 2010
Wednesday, November 3, 2010
AutoCAD 4 MAC
AutoCAD® for Mac® software—it’s AutoCAD, for the Mac, bringing robust 3D free-form design tools and powerful drafting capabilities to your platform of choice. It takes full advantage of the Mac OS® X platform, with an intuitive, graphical user interface that makes it easy to bring your ideas to life. And because it’s AutoCAD, you’re working natively in DWG™ format, so you can easily share files with clients, suppliers, and partners around the world, regardless of platform.
http://usa.autodesk.com/adsk/servlet/pc/index?siteID=123112&id=15597568
http://usa.autodesk.com/adsk/servlet/pc/index?siteID=123112&id=15597568
Tuesday, August 3, 2010
Revit Workset Best Practices
Close worksets from the Worksets dialog box to globally turn off element visibility, instead of turning them off in the Visibility/Graphics dialog box.
Specify visibility when creating worksets. When creating new worksets, there is a check box in the Workset dialog box that makes a workset visible by default in all views. Select this check box only if necessary.
Verify that the same Revit® build is installed on all computers that share worksets.
Use the Reload Latest command available on the File menu to update your copy of the project without changing
the central file. This saves time by eliminating the need to reload the file during the save-to-central process.
Use Review Warnings available on the Tools menu in order to identify and fix posted warnings prior to allowing local copies.
Periodically open the central file with the Audit option selected and then save the file. If corrupted elements are encountered during the audit, they are deleted if possible and the user is notified.
Periodically save to central with the Compact Central File (slow) option selected. This option is used to reduce file size when saving workset-enabled files. The process of compacting rewrites the entire file and removes obsolete parts in order to save space. Because the Compact process takes more time than a normal save, it is strongly recommended that you only do this when workflow can be interrupted.
Ensure that a sufficient number of backups are being created. At a minimum, you should have at least one backup for each member of your worksharing team in order to increase the likelihood that each team member’s data is saved as part of the backups.
When creating a workset, leave the Visible by default in all views option selected. Clearing this option can render the workset completely invisible and problematic in multi-discipline workflows where feature visibility can be of paramount importance.
Close unneeded worksets. This will release allocated RAM for the Revit platform's use in memory-intensive tasks such as printing and exporting.
Checking out a workset may occasionally be of use if certain model elements, such as the building grid or linked files, need to be protected from accidental change. In that event, BIM managers or team leaders can check out a workset containing project elements that should not be casually edited or relocated
Specify visibility when creating worksets. When creating new worksets, there is a check box in the Workset dialog box that makes a workset visible by default in all views. Select this check box only if necessary.
Verify that the same Revit® build is installed on all computers that share worksets.
Use the Reload Latest command available on the File menu to update your copy of the project without changing
the central file. This saves time by eliminating the need to reload the file during the save-to-central process.
Use Review Warnings available on the Tools menu in order to identify and fix posted warnings prior to allowing local copies.
Periodically open the central file with the Audit option selected and then save the file. If corrupted elements are encountered during the audit, they are deleted if possible and the user is notified.
Periodically save to central with the Compact Central File (slow) option selected. This option is used to reduce file size when saving workset-enabled files. The process of compacting rewrites the entire file and removes obsolete parts in order to save space. Because the Compact process takes more time than a normal save, it is strongly recommended that you only do this when workflow can be interrupted.
Ensure that a sufficient number of backups are being created. At a minimum, you should have at least one backup for each member of your worksharing team in order to increase the likelihood that each team member’s data is saved as part of the backups.
When creating a workset, leave the Visible by default in all views option selected. Clearing this option can render the workset completely invisible and problematic in multi-discipline workflows where feature visibility can be of paramount importance.
Close unneeded worksets. This will release allocated RAM for the Revit platform's use in memory-intensive tasks such as printing and exporting.
Checking out a workset may occasionally be of use if certain model elements, such as the building grid or linked files, need to be protected from accidental change. In that event, BIM managers or team leaders can check out a workset containing project elements that should not be casually edited or relocated
Monday, June 28, 2010
Some Revit Architecture Modeling Best Practices
Try to limit the use of joining geometry.
Do not over constrain objects. Try to keep constraints to a minimum. This will help keep “Can’t keep joined” errors to a minimum when moving objects. This may also help prevent workset ownership issues where a user may unknowingly take editability for an object.
Minimize view depth, if possible, in elevation, plan, and section views. In addition, use section boxes when working in 3D views.
Groups are heavier than families. You can use an array to copy and associate objects together. However, after the array is complete, you can ungroup the arrayed objects to increase performance by removing the parametric associations of the copied objects. You can also clear the Copy and Associate check box when creating the array.
Close unnecessary windows. When working in a 3D view, most of the file is placed into RAM. It is also strongly recommended that you close these views when saving to a central file, because these views are regenerated as part of the process. It is best to save a 3D view with minimal visibility and then copy it to create new views faster.
Avoid opening additional views, if possible. It is better to not open a view at all rather than opening one and then closing it, as not all memory is reclaimed when you close a view.
Turn off shadows in most views. (Turn off shadows when printing views if not absolutely necessary.)
When making significant changes to a project (for example, moving a level or making major geometry changes) it is strongly recommended that you perform these operations when no other users are working on the file and they have relinquished all elements. Then have user make new local files.
Using the Paste Aligned command in a closed view actually opens the view (which takes time) and then closes it. If you want to paste several times in a view, open it first.
Limit the use of rooms in design options, as additional time is spent detecting room option conflicts. Use separate models for variations of the whole wing with rooms.
Try to limit the use of joining geometry.
Do not over constrain objects. Try to keep constraints to a minimum. This will help keep “Can’t keep joined” errors to a minimum when moving objects. This may also help prevent workset ownership issues where a user may unknowingly take editability for an object.
Minimize view depth, if possible, in elevation, plan, and section views. In addition, use section boxes when working in 3D views.
Groups are heavier than families. You can use an array to copy and associate objects together. However, after the array is complete, you can ungroup the arrayed objects to increase performance by removing the parametric associations of the copied objects. You can also clear the Copy and Associate check box when creating the array.
Close unnecessary windows. When working in a 3D view, most of the file is placed into RAM. It is also strongly recommended that you close these views when saving to a central file, because these views are regenerated as part of the process. It is best to save a 3D view with minimal visibility and then copy it to create new views faster.
Avoid opening additional views, if possible. It is better to not open a view at all rather than opening one and then closing it, as not all memory is reclaimed when you close a view.
Turn off shadows in most views. (Turn off shadows when printing views if not absolutely necessary.)
When making significant changes to a project (for example, moving a level or making major geometry changes) it is strongly recommended that you perform these operations when no other users are working on the file and they have relinquished all elements. Then have user make new local files.
Using the Paste Aligned command in a closed view actually opens the view (which takes time) and then closes it. If you want to paste several times in a view, open it first.
Limit the use of rooms in design options, as additional time is spent detecting room option conflicts. Use separate models for variations of the whole wing with rooms.
Thursday, June 17, 2010
Trelligence Affinity - Check it out!!
Trelligence Affinity software is an extension of BIM that adds the Program Model into the architectural business process of planning, designing and constructing a building. Affinity focuses on architectural programming and schematic design giving the entire AECO (Architecture, Engineering, Construction and Owner/Developer) team a platform for communicating the requirements for a building project. Affinity fast forwards the BIM model into the pre-design phase delivering time and cost savings and more successful and cost-effective project outcomes.
Once the project program is captured, Affinity allows you to try out any number of building layout scenarios using intelligent, 3D building blocks such as spaces and openings. As you create conceptual floor plans and stacking diagrams, Affinity analyzes each element and tracks whether the initial design is in compliance with the requirements in the program.
Once the team selects a plan, you can bring the schematic into your favorite CAD or BIM tools to develop the detailed designs and construction documents. Affinity includes bi-directional integration with SketchUp, enabling manipulation of the building envelope as well as building exterior rendering. Bi-directional integration in the Affinity for ArchiCAD and Affinity for Revit plug-ins allows you to continue to track the detailed design against the initial requirements. You can even update the requirements in ArchiCAD or Revit using the features of Affinity.
http://www.trelligence.com/
Once the project program is captured, Affinity allows you to try out any number of building layout scenarios using intelligent, 3D building blocks such as spaces and openings. As you create conceptual floor plans and stacking diagrams, Affinity analyzes each element and tracks whether the initial design is in compliance with the requirements in the program.
Once the team selects a plan, you can bring the schematic into your favorite CAD or BIM tools to develop the detailed designs and construction documents. Affinity includes bi-directional integration with SketchUp, enabling manipulation of the building envelope as well as building exterior rendering. Bi-directional integration in the Affinity for ArchiCAD and Affinity for Revit plug-ins allows you to continue to track the detailed design against the initial requirements. You can even update the requirements in ArchiCAD or Revit using the features of Affinity.
http://www.trelligence.com/
Subscribe to:
Posts (Atom)