TextureEditor can handle the following files:
Texture project file (TPF) |
The file that manages a number of "pictures," where texture image files (TMF) and texture lookup table files (TLF)are registered together.
Expressed as a Makefile-like texture file. |
Texture image file (TMF) |
The file that handles the texture image. This file is an uncompressed binary image file. |
Texture lookup table file (TLF) |
The file that handles CI texture colors. It is also called the palette This file is an uncompressed binary image file. |
BMP file� (BMP) |
BMP files can be handled as TMF/TLF. When the BMP file is read, the TLF is automatically extracted and created from the BMP. (The number of colors must be reduced to 16 or 256 colors.) Saving this with a TMF name makes it a TMF. The reverse is also possible. This file cannot be handled unless it is an uncompressed 4bit/8bit BMP file. |
The Import functions enable different-format files to be inserted into an image during editing.
These are functions added from the plug-ins.
The Import plug-ins automatically perform color reduction (reduction to 16/256 colors) and paste the file into the currently edited TMF/TLF. The current version does not perform this color reduction correctly. The cause is currently being investigated. If the conversion does not proceed well, we recommend using another image editing application to perform the color reduction, and then importing the file.
BMP files | Windows (uncompressed) bitmap files |
RGB files | SGI (uncompressed) image files |
The Export functions enable an image file to be converted into another format.
These are functions added from the plug-ins.
BMP files | Windows (uncompressed) bitmap files |
RGB files | SGI (uncompressed) image files |
C language source files | The texture image file is turned into a compilable C language source file by CC/GCC. This file is just a binary image converted into a source file, so it alone cannot actually be displayed on the screen. It requires the use of a suitable display list. |
The following directories are used with N64 CITextureEditor:
The directory with .TPF files.
The directory with .TMF files.
The directory with .TLF files.
The following objects are handled by N64 CITextureEditor:
A project manages pictures using the TPF file.
N64 CITextureEditor can only edit one project at a time.
A picture is an object comprising an
image (TMF) and
palette (TLF).
The image and palette can be referenced from another picture.
This object is stored in the project (TPF)
An image is the TMF, the file with image data detached from the palette.
This object can be referenced by a picture.
Currently, only 4bit/8bit CI textures can be handled.
[Restricted] The picture editing functions do not support Undo/Redo and Cut & Paste.
Plug-in functions expand the functionality of the application. A plug-in module is the module which carries out that plug-in function.
There is a PlugIns subdirectory in the application folder where these plug-in modules are stored. When the application starts up, it automatically identifies these modules.
(Details about the plug-ins can be viewed in the About dialog.
Here we explain about the four plug-ins that were introduced from the start.
Basic operations
Click below to reference the documentation for the development of plug-ins.
Click below to reference the documentation regarding the file formats handled by the N64 CITextureEditor.
Return |
Copyright (C) 1998 NINTENDO Co.,Ltd. Copyright (C) 1998 NINTENDO OF AMERICA, Inc. Copyright (C) 1998 MONEGI CORPORATION. Copyright (C) 1998 INTELLIGENT SYSTEMS Co.,Ltd. All rights reserved. |