<!DOCTYPE html
  PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<!--
Copyright (c) 2006 UGS Corp.

All Rights Reserved.

This software and related documentation are proprietary to UGS Corp.
-->
<html>
   <head>
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <title>VRML</title>
      <script language="javaScript">
        abridged="false";
        displayConditions=new Array();
      </script>
      <link type="text/css" href="../css/main_styles.css" rel="stylesheet">
   </head>
   <body class="bodydocs" onload="top.pageLoader()" bgcolor="#FFFFFF">
      <div class="title_topic3" id="xps10_pagetitle"> VRML</div>
      <hr noshade="true">
      <p class="para_topic"> VRML (Virtual Reality Modeling Language) is a special 3D definition ASCII file format that is supported by the newer Web browsers. The VRML function provides the ability to import VRML representations into the current NX work part, creating NX-equivalent static representations.</p>
      <div class="title_division">Import VRML Dialog</div>
      <table border="0" cellpadding="2" cellspacing="3" align="center">
         <tr>
            <td bgcolor="#c0c0c0" colspan="1" rowspan="1" valign="top">
               <p class="para_td"> Option</p>
            </td>
            <td bgcolor="#c0c0c0" colspan="1" rowspan="1" valign="top">
               <p class="para_td"> Description</p>
            </td>
         </tr>
         <tr>
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1" valign="top">
               <p class="para_td"> Hide Smooth Edges</p>
            </td>
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1" valign="top">
               <p class="para_td"> Hides edges of the faceted bodies, depending on the Angular Tolerance setting.</p>
            </td>
         </tr>
         <tr>
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1" valign="top">
               <p class="para_td"> Angular Tolerance</p>
               <p class="para_td"> Coarse Medium Fine</p>
            </td>
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1" valign="top">
               <p class="para_td"> The setting of the Angular Tolerance ranges from Coarse (high) to Fine (low).</p>
            </td>
         </tr>
         <tr>
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1" valign="top">
               <p class="para_td"> Generate One Model</p>
            </td>
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1" valign="top">
               <p class="para_td"> Generates all IndexedFaceSet nodes into one faceted model. This is useful when importing a VRML file that contains fragmented models.</p>
            </td>
         </tr>
         <tr>
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1" valign="top">
               <p class="para_td"> All Levels Of Details</p>
            </td>
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1" valign="top">
               <p class="para_td"> Determines the behavior of the parser when importing a LOD node. When it is toggled ON, all children are represented. When it is togged OFF, only the highest level of detail is represented; all other children are ignored.</p>
            </td>
         </tr>
         <tr>
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1" valign="top">
               <p class="para_td"> VRML File Units</p>
               <p class="para_td"> Meters Millimeters Inches</p>
            </td>
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1" valign="top">
               <p class="para_td"> Specifies the size of each VRML unit in the NX representation. For example, selecting Millimeters means that each VRML unit will be represented as 1 mm in the NX work part. The units' type of the work part does not affect this option.</p>
            </td>
         </tr>
         <tr>
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1" valign="top">
               <p class="para_td"> More Summary Details</p>
            </td>
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1" valign="top">
               <p class="para_td"> When toggled ON, additional information will be included in the summary that displays at the end of the import. The extra details are: the VRML nodes used, the number of topologies created, the total number of facets generated (excluding object primitives), and how long the import took (in seconds).</p>
            </td>
         </tr>
         <tr>
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1" valign="top">
               <p class="para_td"> Suppress Warning Messages</p>
            </td>
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1" valign="top">
               <p class="para_td"> Prevents the display of warning messages. It does not affect the warning count that displays in the end of import summary.</p>
            </td>
         </tr>
      </table><br><p class="para_division"> Both VRML 1.0 and 2.0 file formats can be imported. (Variants of these formats are allowed, but any additional VRML node types defined in these variants are ignored). The file can be in standard ASCII format (uncompressed) or zipped (compressed). All of the VRML nodes within the file will be fully parsed, regardless of whether a NX equivalent is available.</p>
      <p class="para_division"> Geometry is represented in NX as faceted bodies. Representations are provided for the following geometry types:</p>
      <ul>
         <li>
            <p class="para_item"> VRML 1.0 - Cone, Cube, Cylinder, IndexedFaceSet, and Sphere</p>
         </li>
         <li>
            <p class="para_item"> VRML 2.0 - Box, Cone, Cylinder, IndexedFaceSet, and Sphere</p>
         </li>
      </ul>
      <p class="para_division"> When a VRML file is imported, the representations' colors are matched to the colors of the models in the VRML file as closely as possible, using NX` standard 16-color set. If no diffuse color field is specified, but an emissive color field is specified, the RGB component from the emissive color field is used instead of the default diffuse color RGB.</p>
      <p class="para_division"> Instances (DEF and USE nodes) are fully supported. Instances are represented as geometry copies within the work part, not as components, Instances can have identical names.</p>
      <p class="para_division"> Grouping nodes are fully supported, but with minor behavior changes:</p>
      <ul>
         <li>
            <p class="para_item"> Depending on the setting of the All Levels of Detail toggle, all children or only the child of highest detail are represented.</p>
         </li>
         <li>
            <p class="para_item"> With the exception of LOD and Switch, the field values within the grouping node are ignored.</p>
         </li>
      </ul>
      <p class="para_division"> VRML inlining (Multi File Format) is supported, except that inline filenames cannot be direct references to the World Wide Web (e.g., http://xxxcom/filename.wrl).</p>
      <p class="para_division"> Prototyping of VRML nodes is not supported.</p>
      <p class="para_division"> After a VRML import, a summary is displayed in the Information window. (This report does not appear if no errors or warnings occur during the import and if the More Summary Details option is toggled OFF.) Details of the summary include:</p>
      <ul>
         <li>
            <p class="para_item"> The number of errors and warnings</p>
         </li>
         <li>
            <p class="para_item"> A list of the file's VRML nodes that are not represented</p>
         </li>
         <li>
            <p class="para_item"> A list of undefined VRML nodes which are not processed</p>
         </li>
         <li>
            <p class="para_item"> AN &quot;***Import successful***&quot; message at the bottom of the report, if the import was successful.</p>
            <table border="0">
               <tr>
                  <td valign="top" align="left"><img align="left" src="../graphics/note.gif" alt="Note" title="Note"></td>
                  <td valign="bottom" align="left" width="100%">
                     <div class="para_note">
                        <p class="para_note_body">  Imports can be successful even if errors or warnings occur, but in those cases the representations may be displayed incorrectly.</p>
                     </div>
                  </td>
               </tr>
            </table>
         </li>
      </ul>
      <div class="title_division">Error Messages</div>
      <div class="title_division"> File not found</div>
      <p class="para_division"> The file to be imported cannot be found.</p>
      <div class="title_division"> This is not a VRML file</div>
      <p class="para_division"> An attempt was made to import a file that is not VRML code. (If the file is VRML, but does not have the .wrl extension, this error will not occur.)</p>
      <div class="title_division"> This VRML file is an unsupported version</div>
      <p class="para_division"> The file is a version of VRML that is not currently supported, such as VRML97.</p>
      <div class="title_division"> Corruption found in file</div>
      <p class="para_division"> A decompression fault was detected during a decompressing check of the file, which is performed before any import attempt is made. No attempt will be made to import the file.</p>
      <div class="title_division"> The parser has failed. You will be unable to import any more VRML into your session.</div>
      <p class="para_division"> If an internal error has occurred in a previous VRML attempt, the parser will destabilize.  </p>
   </body>
</html>