Motorola E680 Technical Manual - Page 30

Mobile 3D API File Format Support, Mobile 3D Graphics - M3G API

Get Motorola E680 - Smartphone - GSM PDF manuals and user guides View all Motorola E680 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 30 highlights

Mobile 3D API File Format Support The Motorola E680 supports both M3G and PNG file formats for loading 3D content. The E680 supports the standard .m3g and .png extensions for its file formats. Mime type and not extension will be used for identifying file type. In the case that the Mime type is not available, M3G files will be identified using the file identifier and PNG files using signature. Mobile 3D Graphics - M3G API The M3G API lets you access the realtime 3D engine embedded on the device, to create console quality 3D applications, such as games and menu systems. The main benefits of the M3G engine are the following: ƒ the whole 3D scene can be stored in a very small file size (typically 50-150K), allowing you to create games and applications in under 256K; ƒ the application can change the properties (such as position, rotation, scale, color and textures) of objects in the scene based on user interaction with the device; ƒ the application can switch between cameras to get different views onto the scene; ƒ the rendered images have a very high photorealistic quality. Typical M3G Application An application consists of logic that uses the M3G, MIDP 2.0 and CDLC 1.1 classes. The application is compiled into a Java MIDlet that can be downloaded OTA or embedded on the target device. The MIDlet can also contain additional assets, such as one or more M3G files that define the 3D scene graph for the objects in the scene, images and sounds. 30

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
30
Mobile 3D API File Format Support
The Motorola E680 supports both M3G and PNG file formats for loading 3D content. The
E680 supports the standard .m3g and .png extensions for its file formats. Mime type and
not extension will be used for identifying file type. In the case that the Mime type is not
available, M3G files will be identified using the file identifier and PNG files using signature.
Mobile 3D Graphics – M3G API
The M3G API lets you access the realtime 3D engine embedded on the device, to create
console quality 3D applications, such as games and menu systems. The main benefits of
the M3G engine are the following:
the whole 3D scene can be stored in a very small file size (typically 50-150K),
allowing you to create games and applications in under 256K;
the application can change the properties (such as position, rotation, scale, color
and textures) of objects in the scene based on user interaction with the device;
the application can switch between cameras to get different views onto the
scene;
the rendered images have a very high photorealistic quality.
Typical M3G Application
An application consists of logic that uses the M3G, MIDP 2.0 and CDLC 1.1 classes. The
application is compiled into a Java MIDlet that can be downloaded OTA or embedded on
the target device. The MIDlet can also contain additional assets, such as one or more
M3G files that define the 3D scene graph for the objects in the scene, images and
sounds.