Home > Supported File Formats > U3D to Unity

How to convert U3D (Universal 3D, 3D PDF) to Unity?

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.

U3D

U3D is a semi-obsolete 3D mesh file formats from the 2000-2009 era of the 3D graphics world and whose history is little understood outside the confines of a few 3D graphics companies. Even so, U3D is still a fine 3D file format as a pipeline to get 3D data embedded within 3D PDF files, especially with the full and extensive implementation made by Okino.

For more details on the U3D file format, its core features and limitations, how to embed U3D files within 3D PDF files and the features of the Okino U3D import/export converters, please refer to this WEB page.

Generally speaking, U3D was implemented by a few 3D companies in the mid to late 2000s when it was pushed by Adobe+Intel as part of the line of 'Acrobat-3D' software packages. In very loose terms, U3D is used to convey and embed 3D model data within 3D PDF files, where PDF would be the container for the 3D data.

U3D started off in the 1990s as Intel's "IFX" gaming toolkit which was than thrust upon Macromedia, Alias Research, Softimage and other similar companies around the year 2000 to be accepted as a new "industry standard" 3D file format called "Shockwave-3D". The dotCOM bubble caused SW-3D to die pre-maturely after 2001 only to be rebranded as U3D or the "Universal 3D file Format" in 2004 (ECMA-363). Its specification PDF document described it as "An extensible format for downstream 3D CAD repurposing and visualization". However, U3D was highly profit/sales motivated/biased and not consumer/end-user motivated. As such, partly due to the 2008/2009 recession, those companies and their investments in U3D died away.

Okino is and was critical of U3D back in the day as it was the company which created the main conversion implementation of U3D for both import and export. It understood the limitations of U3D well and of its false promotion as a "universal file format" whose title should really have gone to those such as COLLADA, FBX, VRML2, etc. When implemented well U3D is a fine file format by itself but few companies invested enough time and money to support U3D import and export in a most ideal manner.

Unity

Unity is a cross-platform game engine developed by Unity Technologies, first announced and released in June 2005. The engine has since been gradually extended to support a variety of desktop, mobile, console and virtual reality platforms. It is particularly popular for iOS and Android mobile game development.

Okino has long supported Unity as the first and main 3D conversion program to do so. In the simplest terms possible, conversion from Okino software to Unity is done via the FBX file format.

For those who may be unaware of Okino software, for over 30+ years we have been the pioneer 3D conversion company that wrote the rule book on how DCC, animation and MCAD data is to be cross-converted between all major 3D programs and file formats. Key uses of our software for Unity users has been for the conversion of all major MCAD data formats into a highly optimized and efficient form for realtime usage within Unity. We also invented the processes for animation + skinning/bones cross conversion so that is well supported for Unity. As a minor point of interest, Okino was also the very first implementor of the FBX file format as of 2002, long before Autodesk bought the bankruptcy assets of Alias Research and provided free access to the FBX SDK; hence, we provide highly reliable and robust FBX v5/v6/v7 support.

Limitations of the U3D File Format

U3D import converter's overview

Vist the Unity WEB Site

FBX export converter's overview