If you open the Attribute Manager and select the “ALL” tab you will see all Attributes for the project in a single list. The Attribute Manager is a great tool to solve this problem. If the slow file is not fixed at this point, look in Element Attributes. Likewise creative use of Complex Profiles can also obviate the need for an over abundance of Solid Element Operations. I’ve found that much of what I used SEO for in ArchiCAD 16 can be handled with smart use of Building Materials and Priority Based Junctions in ArchiCAD 17. Before you jump to using SEO, think about creating the same forms with different tools. They are a great function of ArchiCAD, but it should never be the go-to solution. One more thing about Solid Element Operations. The fix to excessive SEO usage is to select all and cancel all operations in the SEO dialog box. The best way to prevent this is to be sure that all targets are related only to the operators they will trim to when performing the operation. This is an extreme case, but it certainly was enough to kill the file speed and cause regular file crashes. I recently came across a file that had an SEO operation with all walls as the target and all roofs as the operator. If cleaning up the libraries doesn’t fix the problem the next thing to look for is excessive use of Solid Element Operations. If you want more information about missing Objects, check out this post that talks about the value of the. You can then either delete or re-link these Objects to non-missing parts until the Library Manager comes out clean. Normally I search every story, elevation, section and detail window for the large dot (the dot color depends on a pen number assigned to the missing element) that signifies a missing Object. Getting rid of missing Objects is a little more tricky, and involves going through the entire project searching for missing objects.
Doing this makes it easy to weed out the duplicates between embedded objects and linked library objects. If you click on the library part name in the Library Manager window you will see the number of instances this object is used at the bottom of the manager window. Duplicate library parts are very common if you have a firm standard external library, and then embed some of these parts or name a new part with the same name in the embedded library. Techniques for Speeding up Sluggish Filesįirst, check the library manager for missing or duplicate library parts. Excessive use of solid element operators.Poor library management (how thick does the embedded library need to be?).Missing and Duplicate libraries (this comes up a lot and gets ignored a lot).Common causes for slow running Archicad files In fact this whole article came out of some discussions I’ve had with another BIM Manager and power user: Patrick May. There is also a range of possible fixes, some quick, others almost as annoying as the slow running file was from the start. The list below is not exhaustive, but it contains some common issues I have come across in my time as an Archicad user, BIM Manager, and someone who loves talking shop with every Archicad user I can find. Educating BIM users is the first step there are some critical things to do or avoid to prevent problems. These problems can and should be avoided. Increased crashes and slow files should not be a common occurrence. Even if a project doesn’t slow down, an ill-maintained and operated project can also cause more crashes than you should have to deal with. While Archicad becoming sluggish is bad in itself, this slowness often raises the potential for file crashes. Even the smallest of projects can get bogged down, decreasing the speed of everything from selecting an element to generating the 3D window.
0 kommentar(er)
