Hydratec Inc.

AutoCAD Based Cards

Total: 700

Page:

* On smaller devices swipe left to view hidden table data

Ribbon/Toolbar (Software) Button Function Error Type Description
Ribbon/Toolbar (Software) Button Function Error Type Description
Card 269 View Collaborate (AutoCAD Based) Navisworks Toolkit Export Piping To Navis None

1. Navis was installed before autocad nwdout any Autocad

Card 436 View Collaborate (AutoCAD Based) Navisworks Toolkit Export Piping To Navis None

Date set in "options" of navis do not match version of Autocad Missing objects Navis

Card 476 View Collaborate (AutoCAD Based) Navisworks Toolkit Export Piping To Navis None

When in the Pipe Model Settings window (Setup window in Navis toolkit), the user cleared the text box for "Layer Name prefix" Dialog Box Acad 2016+

Card 412 View Collaborate (AutoCAD Based) Create Revit Mep Link To System Model None None

AutoCAD entities too far out in space for revit to handle

Card 370 View Collaborate (AutoCAD Based) Create Revit Mep Link To System Model None None

1. dry pendent sprinkler is defined in the drawing and cannot be generated as Revit content Retrieve content Revit revit Link 4-2

Card 411 View Collaborate (AutoCAD Based) Create Revit Mep Link To System Model None None

Unknown, but likely that creation of Revit content will still be accomplished.

Card 403 View Collaborate (AutoCAD Based) Create Revit Mep Link To System Model None None

Revit Link was not installed with Admin Rights

Card 1180 View Cleanup (AutoCAD Based) Draw Pretty Pipes None Unhandled Exception

When starting the Pretty Pipes command, you get an Unhandled Exception error including 'Could not find a part of the path'

 

Another error may mention blockoffsets.dat

 

Card 995 View Cleanup (AutoCAD Based) Draw Pretty Pipes None Einvalidlayer

Starting the Pretty Pipe process, you get this error;

Unhandled exception has occurred...  eInvalidLayer

Card 912 View Cleanup (AutoCAD Based) Draw Pretty Pipes None Unhandled Exception

Unhandled Exception has occurred in a component in your application.

One of the identified items was in an invalid format



Page: