Home > Supported File Formats > Pro/Engineer to OBJ

How to convert Pro/Engineer (ProE,Pro/E,.asm,.prt) to OBJ (Wavefront .obj,.mtl)?

PolyTrans|CAD+DCC performs mathematically precise CAD, DCC/Animation, GIS and BIM 3D file conversions into all key downstream 3D packages and file formats. Okino software is used and trusted throughout the world by many tens of thousands of 3D professionals in mission & production critical environments, backed by respectable personal support directly from our core development team.

Pro/Engineer

Creo is a family of Computer-aided design (CAD) apps supporting product design for discrete manufacturers and is developed by PTC. The suite consists of apps, each delivering a distinct set of capabilities for a user role within product development. They generally compete with SolidWorks, UG NX, CATIA, Solid Edge and Autodesk Inventor.

For over 3 decades Okino has been a primary conversion partner of PTC, especially for our core business focussing on the conversion of their native ProE/Creo (ASM and PRT) and ProductView (PVS, PVZ) files.

Their current product naming can be a bit confusing:

• Creo Elements/Pro - previously Pro/Engineer
• Creo Elements/Direct - previously CoCreate
• Creo Elements/View - previously ProductView

Okino licenses the real and actual ProE/Creo runtime toolkits from PTC directly and hence can guarantee perfect file conversions. Suggested conversion methods include:

• Via native 'Creo Elements Pro' (Pro/E) files, .asm and .prt.
  
  
• Via PTC .neutral assembly and part files.
  
  
• Via STEP and IGES files.
  
  
• Via native ProductView PVS/PVZ files.

OBJ

Wavefront OBJ is a little understood but highly used and prevalent 3D "polygonal mesh" file format used throughout the 3D graphics world. Okino, Alias Research and McNeel made it popular in the early to mid 1990s as a general purpose, simple-to-read, storage and transmission 3D file format, especially for the then-new companies who began to sell 3D mesh models via the Internet.

Relatively speaking, OBJ is a rather simple file format but a bit better than STL although similar to the more modern 3MF format.The OBJ format allows for 1 or more unique polygonal mesh objects to be defined, each with optional UV texture coordinates and vertex colors. Material definitions can be linked to the mesh geometry as defined in the separate 'MTL' file. The material definitions are rather simple (ie. no PBR material support) but acceptable, and with varied levels of texture mapping support. OBJ format does not provide support for object hierarchy, local transformations, meta data, lights, cameras, skinning or animation. Most notably, OBJ does not allow for 'object instancing' and hence 1000 copies of a screw would be saved to OBJ as 1000 explicit copies, rather than 1000 references to one master object.

A short history: In the 1980s there was a program called Wavefront Visualizer which ran on UNIX and ran its early rendering pipeline as a series of tee'd command line 'applets'. The data flowed from one applet to another via various ASCII based files - OBJ for geometry, MTL for materials and other ASCII files for animation, skinning, deformation, etc.

Okino knows of the Wavefront OBJ file very well as it provides the one and only full implementation of the OBJ file format and with the ability to consume exceedingly large OBJ files quickly and efficiently. This includes the only known implementation of OBJ-centric 'NURBS geometry' (surfaces and curves) within the OBJ file format (which is little or not used) other than that from the McNeel Rhino-3D software.

Pro/Engineer import converter's overview

OBJ export converter's overview