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<!-- InstanceBegin template="/Templates/default_template.dwt" codeOutsideHTMLIsLocked="false" --> 4<head> 5<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 6<meta http-equiv="Content-Style-Type" content="text/css" /> 7<!-- InstanceBeginEditable name="CSS の相対パス指定" --> 8<link href="common/manual.css" rel="stylesheet" type="text/css" /> 9<!-- InstanceEndEditable --> <!-- InstanceBeginEditable name="ページのタイトル" --> 10<title>Currently Known Bugs</title> 11<!-- InstanceEndEditable --> 12</head> 13<body> 14<div> 15 <div class="body"> <!-- InstanceBeginEditable name="本文のタイトル" --> 16 <h1>Currently Known Bugs</h1> 17 <!-- InstanceEndEditable --> <!-- InstanceBeginEditable name="本文" --> 18 <h2 id="VERSION_1_0_1">Version 1.0.1 (2010/08/25)</h2> 19 <h3>Currently Known Bugs</h3> 20 <ul> 21 <li>Textures are not applied when <B>Transfer to viewer</B> is selected after a texture name has been changed. 22 <ul> 23 <li>If a texture name has been changed and then <B>Transfer to viewer</B> is selected without saving or reloading that texture, the reference is not resolved correctly and the texture is not displayed on gfxviewer.<BR> Similarly, textures are not displayed if <B>Transfer to viewer</B> is selected without saving or reloading cubes that can be created from the menu. You can work around this problem and resolve the reference correctly by re-configuring the texture image or saving it to file and then reloading it.</li> 24 </ul> 25 </li> 26 </ul> 27 <h2 id="VERSION_1_0_0">Version 1.0.0 (2010/07/29)</h2> 28 <h3>Currently Known Bugs</h3> 29 <ul> 30 <li>Frames do not get applied when frames are skipped in the Timeline panel. 31 <ul> 32 <li>Frames do not become applied when Skip forward and Skip backward are done repeatedly.</li> 33 </ul> 34 </li> 35 <li>Names do not become applied between the <B>Contents </B>panel and the <B>Properties </B>panel 36 <ul> 37 <li>When a name that cannot be configured is specified in the <B>Properties </B>panel, the name before the change does not restore.<br /> It will restore to the original state if you either specify a value that can be configured, or change the selection state.</li> 38 </ul> 39 </li> 40 <li>The selection in the tree view of the <B>Contents </B>panel does not change. 41 <ul> 42 <li>When you click on a selected item that is highlighted, its selection status does not change.<br /> You can change the selection by selecting some other item that is not highlighted</li> 43 </ul> 44 </li> 45 <li>Parameter settings are not configured for a newly added texture in the material <B>Properties </B>panel. 46 <ul> 47 <li>Parameters are not configured for a newly added texture in the Texture management part of the material <B>Properties </B>panel because a texture coordinator is not registered.</li> 48 </ul> 49 </li> 50 <li>Inappropriate values can be set to the Texture combiners in the material <B>Properties </B>panel. 51 <ul> 52 <li>Depending on the number of combiner stages, there are certain values that cannot be set to the Texture combiners, but currently these can get set from the UI.</li> 53 </ul> 54 </li> 55 <li>Cannot distinguish multiple materials in the <B>Curve Editor</B> panel. 56 <ul> 57 <li>When a model with multiple materials is selected in the <B>Contents </B>panel, those materials cannot be distinguished in the <B>Curve Editor</B> panel.<br /> This problem does not arise if you select materials in the <B>Contents </B>panel.</li> 58 </ul> 59 </li> 60 <li>Increases/decreases in animation elements are not reflected in the<B> Curve Editor</B> panel. 61 <ul> 62 <li>When the editing of a content object adds or removes animation elements, this is not reflected in the tree view in the <B>Curve Editor </B>panel.<br /> You need to re-select the content object or close and reopen the <B>Curve Editor </B>panel.</li> 63 </ul> 64 </li> 65 <li>Changes to names of content objects are not reflected in the display. 66 <ul> 67 <li>You can change the name of a content object from a panel, but the name on display in the Camera and the Lookup table set does not change.<br /> The change is reflected in internal operations, so the post-change name gets output to the intermediate file.</li> 68 </ul> 69 </li> 70 <li>When there are multiple spotlights, they must all have the same angular attenuation setting. 71 <ul> 72 <li>When multiple spotlights exist, the angular attenuation settings for input and scale must be consistent.<br /> If the angular attenuation settings differ, the settings for other lights will not be correctly applied and displayed, so attention to this is required.<br /></li> 73 </ul> 74 </li> 75 <li>A multi-texture material will display even when the texture coordinators have not been properly set. 76 <ul> 77 <li>To apply multiple textures you need to set the correct number of texture coordinators. However, under certain conditions the material will display even if the setting has not been properly configured,</li> 78 </ul> 79 </li> 80 <li>Animation cannot be set to newly added texture coordinators for a material. 81 <ul> 82 <li>Newly added texture coordinators do not display in the <B>Curve editor</B>.<br /> You can set them by saving the file once and then reloading.</li> 83 </ul> 84 </li> 85 <li>When you input a file for a material that is being animated, the animation stops being applied. 86 <ul> 87 <li>When you input a file for a material that is being animated, the animation stops being applied.<br /> To restore to the normal state, save the file and then reload the file.</li> 88 </ul> 89 </li> 90 <li>The system crashes if Undo is performed after a particle set has been deleted.</li> 91 <li>The display loses integrity with <CODE>gfxviewer</CODE>. 92 <ul> 93 <li>Lose of <CODE>gfxviewer </CODE>integrity and inability to display has been confirmed for the following cases: 94 <ul> 95 <li>When an effect and a 3D model are shown at the same time.</li> 96 <li>When an effect is displayed immediately after the tool has started (Improves once skin model is shown).</li> 97 </ul> 98 </li> 99 </ul> 100 </li> 101 <li>In the Timeline panel, the state of the playback button reverses. 102 <ul> 103 <li>During playback, if a file is loaded or some other process is preformed the state of the button sometime reverses.</li> 104 </ul> 105 </li> 106 <li>Settings remain after Texture combiners have been deleted 107 <ul> 108 <li>For a model with numerous materials, sometimes the settings remain even after Texture combiners have been deleted.</li> 109 </ul> 110 </li> 111 <li>When multiple texture objects are used for the same texture for the same material, the display may look different on the development hardware 112 <ul> 113 <li>Due to the OpenGL specifications, the filtering settings may differ between the development hardware and the NWCS using POD.</li> 114 </ul> 115 </li> 116 <li>In the settings in the Merge Wizard dialog to associate target files the <B>Select a merge target</B> turns blank. 117 <ul> 118 <li>When switching between Model and Texture tabs the display of the selection state becomes blank.<br /> Although it appears blank, the setting is active because the association setting stores the state of the merge target.</li> 119 </ul> 120 </li> 121 <li>There is a problem when Undo is performed after a curve has been edited 122 <ul> 123 <li>When Undo is performed after curve editing, sometimes the editing of the curve is no longer applied.</li> 124 </ul> 125 </li> 126 <li>The render order of opaque materials differs on the development hardware and CreativeStudio 127 <ul> 128 <li>Because of the way material comparisons are implemented on CreativeStudio, the display will differ from that on the development hardware.</li> 129 </ul> 130 </li> 131 <li>The particle rendering order feature does not work 132 <ul> 133 <li>This is not supported by the development hardware, so the feature has been temporarily disabled.</li> 134 </ul> 135 </li> 136 <li>When Camera is reset, binding is removed 137 <ul> 138 <li>When <B>Reset </B>is done in the camera <B>Properties </B>panel, the property binding is removed and the values will not be applied until you switch back to the panel.</li> 139 </ul> 140 </li> 141 <li>No error is generated when binding a camera animation with a different mode 142 <ul> 143 <li>When Projection mode is set as the view mode for Camera and the animation is not set to the same mode, binding can nevertheless take place with no generation of an error.<br /> When that happens, animation with invalid parameters in the current mode get deleted.</li> 144 </ul> 145 </li> 146 <li>Values get reset in the camera <B>Properties </B>panel when the updater is changed 147 <ul> 148 <li>When updater is changed in the camera <B>Properties </B>panel the values are not saved and get destroyed.</li> 149 </ul> 150 </li> 151 <li>During animation playback, the values change for elements to which keys are not set 152 <ul> 153 <li>This occurs in procedures like the following: 154 <ul> 155 <li>A key is set for the R element of emission color.</li> 156 <li>The value of the G element is changed in the material <B>Properties </B>panel</li> 157 <li>When animation is played, the G element reverts to its value before the change</li> 158 </ul> 159 </li> 160 </ul> 161 </li> 162 <li>When textures are shared, the repeat and filter settings do not get applied to the texture mappers. 163 <ul> 164 <li>Repeat and filter settings cannot be applied to the separate texture mappers for a shared texture.<br /> Separate settings are applied in the development hardware.</li> 165 </ul> 166 </li> 167 <li>Cannot edit <B>IsLightEnabled</B> in the <B>Properties </B>panel for lights 168 <ul> 169 <li>You can set animation to <B>IsLightEnabled </B>in the <B>Curve editor</B>, but this cannot be edited in the <B>Properties </B>panel.</li> 170 </ul> 171 </li> 172 <li>When a non-zero value is set for the camera's <CODE>wScale</CODE> the polygon offset does not get applied 173 <ul> 174 <li>When a non-zero value is set for the camera's <CODE>wScale</CODE>, the polygon offset feature in the material settings does not work.<br /> The setting is applied in the development hardware.</li> 175 </ul> 176 </li> 177 <li>When the same particle is registered multiple times to <B>Particle link</B> they do not preview correctly 178 <ul> 179 <li>Preview does not work correctly when the same particle is registered two or more times to a single <B>Particle link</B>.</li> 180 </ul> 181 </li> 182 <li>The save operation for <B>Particle link</B> does not support <B>Save all...</B> and other saving methods. 183 <ul> 184 <li>To save a <B>Particle link</B> to the intermediate file, you must use <B>File </B>> <B>Save </B>> <B>Particle link</B>.</li> 185 </ul> 186 </li> 187 <li>Spotlight type vertex light displays oddly when the distance to the object being illuminated is zero and the light direction is orthogonal to the surface being illuminated. 188 <ul> 189 <li>When using spotlights, make sure you locate them such that the distance to the object being illuminated is not zero.</li> 190 </ul> 191 </li> 192 <li>Binding of light to animation with different kinds of light sources does not generate an error 193 <ul> 194 <li>When the light source set for fragment light and vertex light does not match that for the animation, they will bind anyways without generating an error.<br /> When this happens, animation with an invalid parameter for the light source of the light will be deleted.</li> 195 </ul> 196 </li> 197 <li>Cannot edit lookup table sets with broken links 198 <ul> 199 <li>In the settings for lookup tables in the <B>Properties </B>panels for materials and fragment lights, you cannot edit lookup table sets correctly if links have been broken. </li> 200 </ul> 201 </li> 202 <li>Cannot display multiple models and animations in Simple viewer 203 <ul> 204 <li>There is no support for the viewing of multiple models.<br /> Operation becomes unstable when you load multiple models and animations.</li> 205 </ul> 206 </li> 207 </ul> 208 <!-- InstanceEndEditable --> </div> 209 <div class="footer" /> 210</div> 211<hr><p>CONFIDENTIAL</p></body> 212<!-- InstanceEnd --> 213</html> 214