-
-
Notifications
You must be signed in to change notification settings - Fork 428
Preflight Checks need to be more specific #1267
Copy link
Copy link
Closed
Labels
EnhancementEnhancement request [class->Improved #{number}: {title}]Enhancement request [class->Improved #{number}: {title}]Extension ChecksIssues related to pyRevit extension checks [subsystem]Issues related to pyRevit extension checks [subsystem]ToolsIssues related to pyRevit commands [subsystem]Issues related to pyRevit commands [subsystem]
Metadata
Metadata
Assignees
Labels
EnhancementEnhancement request [class->Improved #{number}: {title}]Enhancement request [class->Improved #{number}: {title}]Extension ChecksIssues related to pyRevit extension checks [subsystem]Issues related to pyRevit extension checks [subsystem]ToolsIssues related to pyRevit commands [subsystem]Issues related to pyRevit commands [subsystem]
The Preflight checks are an incredible way to keep the team following Revit best practices, but the preflight checks are too vague to really make any proper changes if an issue comes up.
An example of this would be the reference planes check which told us we had 44 unnamed reference planes in our project but did not tell us any locations or how to fetch them. we went through each view and found 40 of the 44, but 4 of them are eluding us.
Another example would be the schedule checker. the preflight says we have over 100 schedules and 103 are not even on sheets, but the schedules section within Revit only shows 30 schedules overall. It would be nice to see what the preflight is considering to be a schedule. (Even if it's just a static list of schedule names that I can right-click within the project browser and search for it)
This feature is such a good tool and can't wait to see it developed further!