Why are the weights and volumes being doubled on my shop ticket?
This problem is usually seen with our warpable structural framing families (double tee, T girder, etc.) when the user has inadvertently added both the flat and warped state of the structural framing family to the assembly. Removing the warped version of the family from the assembly usually resolves the problem.
Why are the weights and volumes showing as zero on the shop ticket?
This is most commonly caused by incorrect or missing material on the structural framing element. The structural framing element within the assembly must have a Structural Material assigned to it that contains the term "PRECAST CONCRETE". This PRECAST CONCRETE material should also be applied to the geometry within the family that makes up the structural framing element. The weights and volumes calculated by the Ticket Populator and Ticket Title Block Populator tools are based on PRECAST CONCRETE material within the assembly.
Why do the MEMBER_WEIGHT_CAST and MEMBER_VOLUME_CAST values differ from the weight and volume populated on the shop ticket?
MEMBER_WEIGHT_CAST and MEMBER_VOLUME_CAST are populated by the Add-on Hosting Updater tool. This tool calculates these values based on the structural framing element itself and any add-on elements that it finds to be intersecting the structural framing element. It will only account for elements that have a material assigned to it that contains "PRECAST CONCRETE". The weights and volumes populated on shop tickets by the Ticket Populator or Ticket Title Block Populator tools are based on all PRECAST CONCRETE material contained within the assembly, not on what has been processed by the Add-on Hosting Updater. So if an add-on was not successfully processed by the Add-on Hosting Updater but was included in the assembly then the weights and volumes on the shop ticket would be inclusive of that add-on whereas the MEMBER_WEIGHT_CAST and MEMBER_VOLUME_CAST values would not.
Can I add our custom shared parameters to the EDGE^R shared parameters file?
It is recommended that you maintain a separate shared parameters file for your custom shared parameters. This is because each time you install a new version of EDGE^R, we overwrite your existing EDGE^R shared parameters file with the newest version. Maintaining a separate shared parameters file for custom shared parameters will prevent you from losing that information with each new install of EDGE^R.
Why do I get a warning about an incorrect file path when trying to run Project Shared Parameters?
This is most commonly caused by an incorrect mapping for the EDGE^R shared parameters file. Before running Project Shared Parameters, open Shared Parameters to confirm that the "Shared parameter file" path is set to C:\EDGEforRevit\Shared_Params_2015_v01.txt. Another common cause is that the Shared_Params_2015_v01.txt has been moved and no longer exists in the following folder path: C:\EDGEforRevit. This file must exist within this folder path in order to successfully run the tool.
When should I use EDGE AISC families and when should I use Revit AISC families instead?
When adding steel members to a model for coordination, we recommend using the Revit out of the box AISC families. These families already have a comprehensive type catalog built and are easy to use directly in your model. When adding steel members to connection families or anything that directly interfaces with the precast work flow, it is necessary to use the EDGE AISC steel shapes. These profiles for the steel shapes have a comprehensive pre-built type catalog for different sizes.