Chapter 26. Using Okino's Polytrans Software

Table of Contents

Translating with Modeling in Pro/E
Assembly-level cuts
Family tables
Coloration
Missing parts
Importing hoses and cables
Translating with Bentley Software
Translating with AutoCAD Software
Translating with JT Files
Translating with 3DS/Max Files

Translating with Modeling in Pro/E

Assembly-level cuts

Features added at the assembly level of the model tree that affect parts' appearance do not translate through PolyTrans. This includes cuts, holes, and welds made at the assembly. The following workarounds are available:

  • Open the affected parts individually and apply the operation necessary to transform the part at the part level

  • Activate the parts and use references in the assembly to cut the parts individually. This method better follows the design intent of the assembly-level operations, but it can cause circular references if it is implemented improperly.

Family tables

Family tables can be used in Pro/E to define parts with repeated features and to define parts in different locations in the same assembly. This can simplify the creation of a large assembly, but problems can arise when the assembly is translated through PolyTrans.

Part appearance

If the appearance if individual parts is dictated by a family table (e.g., a spring's length and compressions are determined by a family table), parts appear in the generic instance in the translation.

A workaround for this problem is to save a copy to a different location and change the name of every part. This strips the family table information from the parts. A backup of the model does not strip the family tables and will not fix the translation problem.

Assembly location

Items can be assembled in location using a family table. This can show two or more locations for an individual item (e.g., a stored location and a use location).

A workaround for this is to open the instance that will be translated and make a backup of this assembly. If two different locations are desired in the translation, make two different backups, one of each location.

Coloration

There are two separate issues with coloration:

  • Items that seem to be colored in Pro/E appear without color in the translation

  • Colors within Pro/E do not appear to match colors within PolyTrans or colors within VE-Suite

No colors within VE-Suite (blinding whiteness)

This is usually a result of coloring at the assembly level. Most models that have this problem do not exhibit whiteness throughout the entire model; they only have a few parts with blinding whiteness.

To fix this, clear all surfaces at the assembly level after saving any colors that you want from the model. Then create a map-key that colors, saves, and closes a part. After the map-key is created, you can color the model by opening each part and activating the map-key.

Colors in Pro/E

Colors in Pro/E do not appear to match the colors within PolyTrans and VE-Suite because the lighting scheme in each program is different. The lighting scheme in Pro/E is relatively easy to change, but there is no known way to save the changes to apply automatically between sessions of Pro/E or to new windows that are opened. Changing the lighting within VE-Suite is much more difficult.

Missing parts

If you have missing parts in your Pro/E assembly, the following steps should solve the problem.

  1. On the Hierarchy Optimizer, press the Option...

  2. Disable the "Delete hidden objects" checkbox

  3. After import, select "Unhide all" from the Edit menu of the "Selector Window" menu. Those items will be on blanked layers according to Granite terminology.

Importing hoses and cables

To import Pro/E hoses or cables, first save the data in the Pro/E neutral format. This format will preserve the hose and cable surfaces so they can be imported into PolyTrans and then into VE-Suite. During the import of the neutral format, choose a fine-grained tessellation so the hoses and cables have a realistic appearance.