Same here on the duty-point note and the Data status field — once that is in the schedule, people actually check it. Retiring the custom item when the catalogue product lands is also cleaner than trying to morph it.
On weight and clearance we split them on purpose.
Weight stays in the product...
Vent relief at offsets
I don’t model the relief/yoke vents as finished pipework on day one. Offsets still move while structure is coordinating beams and transfer zones, so early vent runs just get deleted. What I do instead:
Lock the soil stack route and the offset geometry first (real...
I've been through this on a few multi-storey jobs where stacks had to dodge transfer beams. MagiCAD stays coherent if you treat the drainage network as MagiCAD objects from day one rather than mixing in generic Revit pipes.
I model the main soil stacks first with MagiCAD drainage tools, then...
We’ve run into this on almost every project that isn’t 100 % catalogue. A generic family is a last resort; we treat the custom MagiCAD product as a real calculation object from the start.
Essential parameters we always fill: connection sizes and types, flow/capacity range, pressure drop (or Kv...