1<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
2<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-US" lang="en-US">
3<head>
4<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
5<meta http-equiv="Content-Style-Type" content="text/css" />
6<link href="../../html/common/main.css" rel="stylesheet" type="text/css" />
7<title>Saving and Merging Files</title>
8</head>
9<body>
10<h1>Merging Model Files</h1>
11<p>This section explains the process of merging Model files.</p>
12<ul class="sub_page">
13  <li><a href="#merge_treatment">Merging</a></li>
14  <li><a href="#merge_overview">Uses of Merging</a></li>
15</ul>
16<h2>Overview of the Merge Process</h2>
17<p>Model file merging is a feature that takes the <B>node</B> and <B>material</B> settings of a Model file edited and saved with 3DEditor and applies those settings to a Model file that has been exported from the 3DCG tool.</p>
18<p class="image"><img src="images/model_file_merge.png" alt="Schematic of Model file merging" /></p>
19<p><a name="merge_treatment" id="merge_treatment"></a></p>
20<h2>Merging</h2>
21<p>This section describes how merging is used.</p>
22<h3>Normal method of use</h3>
23<p>You can configure the Export plug-in of the 3D CG tool to predefine which Model file will be merged when the model data is sent to 3DEditor.</p>
24<p>By doing this, the specified Model file will be automatically merged when the model data are output from the 3D CG tool and sent to 3DEditor.</p>
25<p>The flow for this task is as follows: </p>
26<ol>
27  <li>Send model data from the 3D CG tool to 3DEditor.</li>
28  <li>Edit the material settings and other settings using 3DEditor and save the Model file.</li>
29  <li>Set the Model file saved in step 2 as the model file for merging when data are sent again from the 3D CG tool.</li>
30</ol>
31<p>In this merge process, the default operation is the merging of nodes and materials that have the same names.</p>
32<h3>Content altered by the merge process</h3>
33<p>Merging results in changes to the following content in the Model file exported from the 3DCG tool:</p>
34<ul>
35  <li>The model's culling settings.</li>
36  <li>The settings of the nodes that are targets of the merge (the property settings and the 3DEditor task information).</li>
37  <li>The settings of the materials that are targets of the merge (the property settings and the 3DEditor task information).</li>
38</ul>
39<h3>Content not altered by the merge process</h3>
40<p>The following content does not get changed in the Model file exported from the 3DCG tool:</p>
41<ul>
42  <li>The node structure in the model.</li>
43  <li>The material structure in the model.</li>
44  <li>The model's polygon shapes and their vertex data.</li>
45</ul>
46<h3>Textures referenced from models</h3>
47<p>When Model files are merged, the textures are processed as follows:</p>
48<ul>
49  <li>If the target model and the model that is being merged into the target both reference a texture with the same name, the texture referenced by the target model takes priority.</li>
50  <li>Any texture that is referenced <I>only </I>by the model being merged into the target gets added during the merge process.</li>
51</ul>
52<p><a name="merge_overview" id="merge_overview"></a></p>
53<h3>Uses of Merging</h3>
54<p>With NintendoWare, the creation and adjustment of 3D model data is done using both the 3DCG tool and 3DEditor. The flow of this procedure is as follows:</p>
55<ol>
56  <li>Using the Export plug-in, send to 3DEditor the model data that was created with the 3DCG tool.</li>
57  <li>While previewing, use 3DEditor and the Viewer to configure the hardware-specific (the CTR-specific) material rendering settings and other settings.</li>
58  <li>Using 3DEditor, save the configured model data in the format of a 3D intermediate file.</li>
59</ol>
60<p class="new_hint">Steps 1 and 2 of the above procedure can be repeated.<br /> By using this Model file merge feature, the node and material settings configured in step 2 can be applied to model data re-exported from the 3DCG tool.</p>
61<hr><p>CONFIDENTIAL</p></body>
62</html>
63