Our PlantSpace database does not return properly scaled elements and the settings cannot be changed within the same database. This is characterized by custom components such as hoses, nozzles and branch pipes that we use from a contractor's database that do not match the structure of the PlantSpace standard settings file. How can we implement the database with these new items? AutoIsogen generates the *.pcf file but does not return an output *.dgn file. The steps we currently use to work around this is to to generate a *.jsm file from PlantSpace, process through AutoIsogen to get the *.pcf file, and then create a *.dwg file using a third-party application.
AutoIsogen is not able to properly create the DGN file because the models include components that are not defined in the AutoIsogen interface (Iso.lib). There are bound to be issues using these type of custom components in a standard Isometrics generation environment, for example:
Bentley's Product Advantage Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!