Bl
Bl
Bl
Bl
Bl
You are here:   Home »  Products »  PolyTrans|CAD+DCC  
Bl

Home > Supported File Formats > PTC Creo to PLY


How to convert PTC Creo (Pro/Engineer,.asm,.prt) to PLY (Stanford .ply)?


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.

     

PTC Creo

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.

     

PLY

PLY can generally be considered a simple, 1990s-era, university research oriented polygonal (mesh) 3D file format designed to store data from 3D scanners. It was developed by Greg Turk and others in the Stanford graphics. Its design was inspired by the Wavefront .obj format.

PLY was meant to be a simple, easily parsable file format and hence only conveys basic geometry information for a single object definition with polygon vertices, vertex colors vertex normals and UV texture coordinates. No materials nor hierarchy, lights or cameras are supported.