This topic includes up-to-date information about any known issues related to Ideate StyleManager.
See Performance Tips for suggestions on how to reduce the processing time for certain methods.
Not all imported object styles that are embedded within families can be detected by Ideate StyleManager. Years ago Revit used to store imports in families by a different method. Ancient families made during that time carry about the “filename.dwg” object style rather than the newer “Import in Families: A-DETL” syntax. These families unfortunately cannot be detected by Ideate StyleManager when reviewed from within the project but can be discovered when viewed within the family editor.
Sketch lines of filled regions will display in the Usage pane only if they are custom line styles. If they are built-in styles they cannot be determined and will not be displayed in the results. See section about ‘reserved’ Line Styles
If a line style is used as a modification to a view via the Linework tool, and you want to fix the condition, your best bet is to duplicate the view (without the detailing).
If the border of cells that are part of the schedule header (not the title) are overridden with another line style, the process of Analyzing that line style will cause the cell border to revert to Thin Lines. This is an API bug that has been filed with Autodesk. The workaround is not override these cell borders. The borders that are part of the title (or above) are not impacted by this issue.
Built-in line styles within the revision schedule of a title block family are not displayed in usage results in a Revit model. Custom line styles correctly display the usage, but they must be managed from within the family editor.
The Built-in Line Pattern is ‘Solid’, and it is not displayed.
Duct and Piping System types allow for an override in Line graphics. This override is currently not reported when running Analyze, more over it is also being reset to default by running the Analyze command.
Some files will display multiple versions of the same fill pattern. While it is not possible to create a duplicately-named fill pattern using the Revit user interface, it is possible via the API. In these cases, we recommend that you use the merge or delete functions to fix these conditions. On occasion we have seen a duplicate of the built-in fill pattern called <Solid fill>. We do not know the source of this condition but have enabled the merge and delete buttons for these duplicates even though the delete function is typically not available for a built-in style. These special weird duplicates are flagged by Ideate StyleManager with an asterisk as shown. We recommend that you use the delete function on any “<Solid fill>[Name]*”. This will remove the duplicate and force any referenced element to revert to the true built in <Solid fill> pattern.
Note on the screenshot, the ‘correct’ built-in pattern has “-” usage and no “*” after the name.
Ideate StyleManager is currently under-reporting the material usage for custom object styles. Example: If a material is referenced by a custom object style but those custom object styles are not otherwise in use, then StyleManager is reporting the usage for that material as “0”. — fixed in July 2019 release.
For some joined wall conditions, the merge process cannot complete and will trigger a Revit error. We recommend that you use the Cancel option within the Revit warning. The results will show that the usage was not replaced. To resolve this error, select the wall/floor/ceiling type from the Usage pane, and use the Edit Type button to manually swap the material.
There are no known issues related to material appearance assets. Let us know if you have a support issue related to material appearance assets.
There are no known issues related to view templates. Let us know if you have a support issue related to view templates.
There are no known issues related to filters. Let us know if you have a support issue related to filters.
Merging scope boxes may result in (logical) Revit errors. Be careful when merging scope boxes that do not overlap. Let us know if you have other support issues related to scope boxes.
Thank you for taking time to inform us about a bug or feature request.