Currently Known Bugs
Version 1.3.0 (2010-12-13 )
- Parameter settings are not configured for a newly added texture in the material Properties panel (Details mode).
- Parameters are not configured for a newly added texture in the Texture management part of the material Properties panel (Details mode) because a texture coordinator is not registered.
- Inappropriate values can be set to the Texture combiners in the material Properties panel.
- 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.
- A multi-texture material will display even when the texture coordinators have not been properly set.
- 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,
- When textures are shared, the repeat and filter settings do not get applied to the texture mappers.
- Repeat and filter settings cannot be applied to the separate texture mappers for a shared texture.
Separate settings are applied in the development hardware.
- Settings remain after Texture combiners have been deleted.
- For a model with numerous materials, sometimes the settings remain even after Texture combiners have been deleted.
- When multiple texture objects are used for the same texture for the same material, the display may look different on the development hardware
- Due to the OpenGL specifications, the filtering settings may differ between the development hardware and the NWCS using POD.
- The render order of opaque materials differs on the development hardware and CreativeStudio
- Because of the way material comparisons are implemented on CreativeStudio, the display will differ from that on the development hardware.
- The system crashes if Undo is performed after a particle set has been deleted.
- Creation of a particle set cannot be redone.
- Limits on values entered for particle lifespan
- As the initial values for lifespans, set minimum and maximum values that differ by no more than 65,534. If this range is exceeded, only a portion of the range of entered values will be applied.
- When the same particle is registered multiple times to Particle link they do not preview correctly
- Preview does not work correctly when the same particle is registered two or more times to a single Particle link.
- Particle links cannot be saved correctly when using "Save all" or "Merge and save files."
- Particle links are not saved correctly (an empty file is saved) when using the same menu as other intermediate files. To save particle links correctly, you must save using File > Save > Particle link.
- When there are multiple spotlights, they must all have the same angular attenuation setting.
- When multiple spotlights exist, the angular attenuation settings for input and scale must be consistent.
If the angular attenuation settings differ, the settings for other lights will not be correctly applied and displayed, so attention to this is required.
- 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.
- When using spotlights, make sure you locate them such that the distance to the object being illuminated is not zero.
- Binding of light to animation with different kinds of light sources does not generate an error
- 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.
When this happens, animation with an invalid parameter for the light source of the light will be deleted.
- No error is generated when binding a camera animation with a different mode
- 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.
When that happens, animation with invalid parameters in the current mode get deleted.
- Values get reset in the camera Properties panel when the updater is changed
- When updater is changed in the camera Properties panel the values are not saved and get destroyed.
- When a non-zero value is set for the camera's
wScale
the polygon offset does not get applied
- When a non-zero value is set for the camera's
wScale
, the polygon offset feature in the material settings does not work.
The setting is applied in the development hardware.
- Changes to names of content objects are not reflected in the display.
- 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.
The change is reflected in internal operations, so the post-change name gets output to the intermediate file.
- If other content is selected while the link flag is set, link settings will reflect it.
- If other content for which no link setting is made is selected while the link flag is set, the link setting is sometimes applied to the selected content as well.
- Cannot distinguish multiple materials in the Curve Editor panel.
- When a model with multiple materials is selected in the Contents panel, those materials cannot be distinguished in the Curve Editor panel.
This problem does not arise if you select materials in the Contents panel.
- Increases/decreases in animation elements are not reflected in the Curve Editor panel.
- When the editing of a content object adds or removes animation elements, this is not reflected in the tree view in the Curve Editor panel.
You need to re-select the content object or close and reopen the Curve Editor panel.
- There is a problem when Undo is performed after a curve has been edited
- When Undo is performed after curve editing, sometimes the editing of the curve is no longer applied.
- The Transform.Rotate unit is radians not degrees.
- During animation playback, the values change for elements to which keys are not set
- This occurs in procedures like the following:
- A key is set for the R element of emission color.
- The value of the G element is changed in the material Properties panel
- When animation is played, the G element reverts to its value before the change
- In the settings in the Merge Wizard dialog to associate target files the Select a merge target turns blank.
- When switching between Model and Texture tabs the display of the selection state becomes blank.
Although it appears blank, the setting is active because the association setting stores the state of the merge target.
- Names do not become applied between the Contents panel and the Properties panel
- When a name that cannot be configured is specified in the Properties panel, the name before the change does not restore.
It will restore to the original state if you either specify a value that can be configured, or change the selection state.
- After an object with a parent-child relationship is deleted, the parent-child relationship cannot be restored by an undo operation.
- If there are objects with a parent-child relationship on the Contents panel, such as models and materials, the parent-child relationship is canceled if either the parent or child is deleted. The relationship cannot restored even with an undo operation.
- Frames do not get applied when frames are skipped in the Timeline panel.
- Frames do not become applied when Skip forward and Skip backward are done repeatedly.
- The color field always points to the lower right if black (0,0,0) is specified using the color picker
- The S component resets if black (0,0,0) is specified using the color picker
- The display loses integrity with
gfxviewer
.
- Lose of
gfxviewer
integrity and inability to display has been confirmed for the following cases:
- When an effect and a 3D model are shown at the same time
- When an effect is displayed immediately after the tool has started (Improves once the skin model is shown).
- Cannot display multiple models and animations in gfxviewer.
- There is no support for the viewing of multiple models.
Operation becomes unstable when you load multiple models and animations.
- Textures are not applied when Transfer to viewer is selected after a texture name has been changed.
- If a texture name has been changed and then Transfer to viewer is selected without saving or reloading that texture, the reference is not resolved correctly and the texture is not displayed on gfxviewer.
Similarly, textures are not displayed if Transfer to viewer 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.
CONFIDENTIAL