|
发表于 2022-7-8 20:40:30
|
显示全部楼层
Point taken on the excessive lag, however this was subsequently resolved by setting things to Coarse, Medium and Fine Detail which brought it back down to normal performance. And for the record, the only reason why the stair lagged so much was because the risers were a perforated aluminum plate, in which he used an Adaptive Component with Voids to create the perforated effect. In other words, TOO much detail, lol. But Revit is still fast if you're in wireframe mode, which is common for AutoCAD users. It's only when in Hidden mode that performance begins to be affected, and most Revit users do not ever use the Wireframe Visual Style for self evident reasons.
On to your last question: Linking is straight forward, however there are ways to Link things into Revit for best results. Anytime we receive steel files, we try and export as IFC first (using an AutoCAD vertical product), then in Revit go to File > Open > IFC. This runs the IFC file through a conversion process into native Revit objects. You'll get mixed results with this. But Revit 2015 allows native IFC linking as well, which is an options we've used lately with great results as well, although you can lose visibility control on isolated and individual objects. Again with this, mixed results.
Another way is to use a sacrificial Revit model and import the DWG file inside an In-Place Model component under a relative Family category, such as Structural Framing. Save this as an RVT file, and then Link (aka "XREF") this file into your main project. This gives you the most versatility for a few reasons... number one, native DWG files do not inherently support Revit's infamous cutting functionality in Plan, Sections and Elevations. You'll see the entire file in all Views which kills functionality and ability to show rich levels of detail. So embedding a DWG inside a cuttable Revit Family, the DWG can now support cutting ranges. Number two, you have much more flexibility in controlling your Views, View Templates, etc, since the DWG models inherit the Family Category it's embedded within. There are a few other reasons why this is the preferred method but those two are the main points.
I understand your stance on this point. This is what will make or break Revit for you. I can tell you now, when you start getting down to very fine level of modeling you will hit serious road blocks that you'll find frustrating. Revit doesn't allow things to be modeled at the 100ths of an inch. It's not that it's incapable of it mathematically, it's that the program intentionally doesn't want you to get down to that level of precision. It drives a lot of people nuts when they're used to AutoCAD creating a line that is 0.0025" long, even though they don't need it, they want to be able to. But tackle the tight-quarters with a different approach is all I would suggest.
Benefits of Revit aren't in the super fine-detail areas of modeling as much as it's the intuitive areas of modeling. A for instance in your case would be bolt sets for slip-on and weld neck flanges. You can build a flange to flex per ANSI standard sizes, use Voids to create the bolt holes (that flex and add/subtract bolt holes when sizes change), then add a shared nested Family of the nut and bolts that can follow the bolt pattern, add/subtract as needed and quantify the bolt sets as you place each flange in the model, including the gaskets. Every Family has a cost and material parameters for BOM and scheduling purposes. These are the benefits that Revit offers, not an infinite free-form solid modeling environment that AutoCAD is known for. |
|