Introduction
This tutorial is designed for the developers who want to start using MascotCapsule. Let's take a look at necessary items for development, and development procedures.
Development Procedures
Let's take a look at basic development procedures for creating the applications.
Step 1: Creating 3D data using commercial 3D design tools
- Supported Tools
- 3ds Max, Maya, LightWave3D, SOFTIMAGE|XSI, etc.
Step 2: Creating files for MascotCapsule
Convert the 3D data to the intermediate file format, using the plugin provided by HI CORPORATION. Use the converter to generate the special file format for MascotCapsule.
For details on the data creation flow of MBAC/MTRA, which are 3D data for MascotCapsule V3, please visit
this page.
Development Flow
![]() |
BAC and TRA intermediate file formats are independent from particular operators or manufacturers, and can be used for all profiles. |
![]() |
MBAC and MTRA are dedicated file formats for MascotCapsule, and specific for individual operators and manufacturers. BAC and TRA need to be converted using the specific converter for each operator and manufacturer. |
Step 3: Creating the application that executes 3D animation
Load the MascotCapsule files created in Step 2, and the texture data, in order to create the application that executes 3D animation. In order to control the actual rendering onto the screen, coding must accommodate each environment.
Necessary tools
Software development kit (SDK) and API document must be obtained for programming. API differs from carrier to carrier; please download it from each carrier's website. Please note that HI CORPORATION does not provide SDK.
Step 4: Testing the application
Test the application in the target environment, or on the PC emulator. If there is any problem, go back to Step 1 or Step 3, and fix the 3D data or application.
Necessary tools
Emulator
Similar to software development kit (SDK), please visit individual carrier's website and download it.
Note: If there is any problem, go back to Step 1 or Step 3, and fix the 3D data or application.
Step 5: Verification test in the target environment
Finally, verify the operation in the target environment. In general, verification tests must include release method, distribution environment, and installation.



