Known Issues

Known Issues with IdeateApps for Revit

This topic includes up-to-date information about any known issues related to IdeateApps.

Ideate ReNumber

Unexpected elements

In some cases the list of elements to be renumbered may exclude/include elements that are unexpected. This condition can occur when using the Path, Vertex or Auto-Number methods.

For example, in an elevation view, even though elements may be hidden, they would still be included as long as they exist within the view. This can be fixed by adjusting the far clip value of the view. This condition is demonstrated within this advanced numbering video.

Another example, that might occur more typically within a plan view when a equipment family or door family has an access area or ADA clearance area that makes the family much larger than otherwise expected. In these cases the Path methods might unexpectedly intersect those families. In this case you may need to adjust the vertex of the 2d path to avoid the family.

Rooms not recognized by the ‘Renumber by Renumber by Vertex’ method

Projects where the z value of the project base point has been changed do not work with the Vertex path method. This bug will be fixed in the next release. Please contact [email protected] if you need help with this issue now.

Ideate QuickSelect

There are no Known Issues yet.

Ideate SmartDelete

Deleting the active plan view using SmartDelete: It does not display dependents when the user is deleting the level the active plan view is based on.
Deleting reference planes: If a reference plane has elements constrained to it, these constraints currently do not show up as dependents.

Ideate XRay

Visibility Reasons

Plan Regions are not yet supported.
Elements from linked Revit files are not yet supported.
Section Views: If a section view reference is hidden by a filter, Revit API is not allowing XRay to detect this state, and it will return a "XRay is not yet able to determine why your Views element is invisible..." as a result.

Ideate SpellCheck

No Errors Found — Windows 10

If Ideate SpellCheck does not find any errors, then it may be that the operating system does not yet have an installed dictionary. When running on Windows 10, it may not work because platform spell-checking capabilities are available only for languages present in the input languages list. In Windows 10, when a language is added to the list of available keyboards, Windows automatically downloads and installs a corresponding Feature on Demand (FOD) package that provides spell-checking capabilities. By adding the language to the input languages list, the spell checker will be supported.

To fix this issue, go to the Control Panel>Languages and add the required language.

Revit Spell Check Settings Ignored

Ideate SpellCheck will ignore the Revit spellcheck settings and will always do the following:

find misspellings, even if the words are all in CAPS
find misspellings, even if the first letter is capitalized
ignore with numbers

Dependent Views

Ideate SpellCheck does not yet check the text on a parent view when the dependent view is placed on the Sheet. Text that appears as part of a dependent view can therefore only be checked by selecting the parent view.

Level:Name not excluded by default — Resolved in July 2020 release

In previous versions of SpellCheck, the Level name was not always excluded by default. If you see this conditions, make sure that you are running the latest release of SpellCheck, and thay you are not using a custom exclusion file.

Parameter Exclusion File Missing Error — Resolved in July 2020 release

If you see this error on startup, check that you are running the latest version of IdeateApps.

Supported Revit Versions

Ideate SpellCheck is supported in Revit versions 2017 and newer. Due to API limitations in Revit 2016 it does not appear on the Add-ins tab by default, but can be manually enabled. Please see here for more info.

Unsupported Data Categories

Ideate SpellCheck will be unable to check and correct errors in unsupported data categories, such as material takeoff or analytical data. Please see here for more info.

Ideate Sheet and View Tools

Ideate SheetManager

Views and Sheets that are filtered by the Project Browser are not filtered by Ideate SheetManager. Instead, these Views are noted as < No Folder >.

When edits to Sheet Number are made in Sheet manager, these are not always shown in Project Browser until Project Browser is refreshed. This is a known Revit issue.
Workaround: Toggle back and forth between two projects or force a refresh by toggling the Sheet Browser choice.

Ideate Align

Rotation On Sheet (Viewports)

Viewports that have a ‘Rotated on Sheet’ value other than 0 will be aligned by the crop box boundary instead of by model coordinates.

Ideate Clone

Sheet Assemblies

Sheets that are part of Assemblies are not currently supported by Clone. An Assembly-based Sheet that is created via Clone will be duplicated, but will not be able to be filed within the Project Browser under the Assemblies as expected.

View Titles

When cloning views together with the sheet, the relationships of the view titles to viewports are not maintained. This is due to Revit API limitation; Ideate Clone has no control over the view title.

Ideate ViewCreator

Assembly views

Ideate ViewCreator currently does not support Assembly views.

Copying Color Schemes

Due to Revit API limitation, the view property 'Color Scheme' is ignored by Plans to Levels and Apply Dependents methods. Use a template to apply or assign the correct value to this property. The Duplicate Views method is handling this property correctly.

For more details about using a view template to apply properties, see the Copy to Option topic.

Copying Scope Box Visibility Settings

Scope box visibility is set per view and can vary on dependents. There is also an override property of the scope box views visibility, which is currently ignored by Plans to Levels and Apply Dependents methods. The Duplicate Views method is handling this property override correctly.

Copying Scope Box Visibility Settings in IdeateApps

Copying View References or Callouts

Revit API currently does not support copying and altering of view references, or copying of callouts.

As a result, the Plans Levels method does not copy view references or callouts to newly created views, and Apply Dependents does not copy view references to newly
created views.

Note: The Duplicate Views method mimics Revit behavior for Duplicate, Duplicate with Detailing and Duplicate as Dependent; and it is able to copy view references and callouts.

Global Parameters

Using Global Parameters in view properties, or to drive view properties is currently not supported.

Rotated crop boxes

The rotation of crop boxes are currently not copied when creating new views by the 'Plans to Levels' and 'Apply Dependents' methods. The "Duplicate Views" method does correctly handle crop box rotation.

Regular non-rotated rectangular and polygonal, horizontally or vertically split crop boxes are handled correctly.

Using Plans to Levels to copy shadows settings and VG for lighting, design options or linked files

Due to Revit API limitation, the following properties will not be directly copied over during the 'Plans to Levels' workflow, and need to be applied by a view template: shadows (On/Off); Visibility Graphics settings for: lighting, design options, linked files.

Note: Copying VG settings for linked files is supported in IdeateApps 2020.1, only in Revit 2020 and up.

For more details about using a view template to apply these properties, see the Copy to Option topic.

Submit feature or issue request for Ideate Software

Thank you for taking time to inform us about a bug or feature request.