Help Files
Video Library
Blog
Email Support
IdeateApps Help
  • 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 Vertex’ method — Fixed in September 2020 release.

    Projects where the z value of the project base point has been changed do not work with the Vertex path method.

    Ideate QuickSelect

    There are no Known Issues yet. 

    Ideate SmartDelete

    Ideate XRay

    Visibility Reasons

    Ideate SpellCheck

    .NET error on SpellCheck Launch

    This issue seems surface occasionally when the user is simultaneously running two Revit sessions (Note: Not two projects within the same Revit session!). Some customers reported that closing one of the sessions then allows SpellCheck to run correctly. If you experience this issue, we recommend that you make sure to use the latest release of IdeateApps due to other improvements that may affect this condition.

    Revit Spell Check Settings Ignored

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

    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 that 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.

    Performance in fields containing “underbar”

    Ideatae SpellCheck will be slower checking words that use the underbar (“_”) symbols. These characters are often used as part of a family or type naming system. In these cases you can use the Ignore button to skip spellchecking within that field.

    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.

    Split Schedules

    Split schedules introduced in Revit 2022 are not supported in the current release or IdeateApps. When cloning a split schedule, the ‘segment’ property will be lost.

    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 — Fixed in May 2021 release. 

    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.

    Note: The issue persists in Revit 2019 and it is not expected to be fixed unless a future Autodesk API update includes 2019.

    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 — Fixed in May 2021 release.

    The rotation of crop boxes is currently not copied when creating new views except when the ‘Duplicate Views’ method is used with one of the first three choices (Duplicate, Duplicate with detailing or Duplicate as dependent). This is expected to be resolved in the upcoming 2021 release.

    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.

    By entering your data above and clicking ‘SUBMIT’ you are consenting to the collection and use of that data to respond to your comments and inquires, as described in our Privacy Policy. We may also transfer the data you submit in the ‘Email Us’ form to our VAR partners for the limited purpose of a sales follow-up. Please review our Privacy Policy for more details on how and when we collect data and what we use it for.