WO2023008647A1 - 3d data conversion and use method for high speed 3d rendering - Google Patents

Abstract

A 3D data conversion and use method for high speed 3D rendering, according to the present invention, comprises the steps of: analyzing a 3D data structure and converting same into a hierarchical structure of a GUI engine; binarizing converted 3D data; reading the binarized 3D data to use same in a GUI content; and registering and processing, for the read 3D binary data, the point coordinates of a 3D model, a camera, light, a texture to be shown on the surface of the 3D model, etc. by using a graphics library function stored in an Open Graphics Library for Embedded Systems (OpenGL ES), and then outputting the read 3D binary data to a screen.

Description

How to convert and use 3D data for high-speed 3D rendering

The present invention relates to high-speed processing of 3D rendering used in a GUI, and relates to supporting display of complex and large-capacity 3D data on a display screen of a vehicle at high speed.

The prior art related to the present invention is posted in Republic of Korea Patent Registration No. 10-0932977 (2009. 12. 21. notice). 1 is a configuration diagram of the conventional stereoscopic image display device. 1, the conventional stereoscopic image display device includes a display unit 100, a barrier 100', a scan driver 200, a data driver 300, a light source 400, a light source controller 500, and a timing controller 600. and a data conversion unit 700 . The light source 400 is formed as a planar light source and is formed on the rear side of the display unit 100, but for convenience, it is shown that the light source 400 is formed on the lower side of the display unit 100. In addition, the display unit 100 includes a plurality of scan lines (not shown) for transmitting selection signals, a plurality of data lines (not shown) formed to intersect with the plurality of scan lines and transmitting data signals (not shown), and It includes a plurality of sub-pixels (not shown) formed at intersections of data lines. In this embodiment, it is assumed that a red sub-pixel for red (R) display, a green sub-pixel for green (G) display, and a blue sub-pixel for blue (B) display form one pixel. In addition, in this embodiment, the plurality of pixels of the display unit 100 are pixels corresponding to images for the left eye (hereinafter, referred to as 'pixels for the left eye') and pixels corresponding to images for the right hand (hereinafter, referred to as 'pixels for the right hand'). including) Here, the pixels for the left eye and the pixels for the right eye are formed such that they are repeatedly arranged. Specifically, the pixels for the left eye and the pixels for the right eye may be arranged to be repeated in parallel with each other to form a stripe shape or a zigzag shape. The arrangement of pixels for the left eye and pixels for the right eye may be suitably changed according to the barrier 100'. The barrier 100' is disposed on one surface of the display unit 100, and includes opaque areas (not shown) and transparent areas (shown) formed to correspond to the arrangement method of pixels for the left eye and pixels for the right eye of the display unit 100. did not). The barrier 100' separates and provides a left eye image and a right eye image projected from pixels for the left eye and pixels for the right eye of the display unit 100 in directions for the left eye and right eye of the viewer, respectively, using opaque regions and transparent regions. . The opaque regions and transparent regions of the barrier 100 ′ may be formed in a stripe shape or a zigzag shape according to an arrangement method of pixels for the left eye and calcination for the right eye of the display unit 100 . also. When explaining how an observer feels a 3D image through the display unit 100 and the barrier 100', a left eye pixel and a right eye pixel can be viewed through a section cut in the II' direction of the display unit 100 and the barrier 100'. It shows how to observe a three-dimensional image through. In addition, the display unit 100 includes a plurality of left-eye pixels 150 and a plurality of right-eye pixels 160 that are repeatedly arranged, and the barrier 100' includes a plurality of left-eye pixels 150 and a plurality of right-eye pixels 160 . An opaque region 150' and a transparent region 160' are repeatedly arranged in parallel in the same direction as the arrangement direction of the pixels 160. The pixels 150 for the left eye of the display unit 100 project the left eye image onto the left eye 180 through the transparent area 160', and the pixels 160 for the right eye of the display unit 100 are transparent to the barrier 100'. The right eye image is projected onto the right eye 170 through the area 160'. The opaque region 150' of the barrier 100' allows the pixels 150 for the left eye and the calciner 160 for the right eye of the display unit 100 to project images to the left and right eyes through the transparent region 160', respectively. to form a light projection path. In addition, the image for the left eye projected from the pixel 150 for the left eye is formed as an image having a predetermined disparity with respect to the image for the right eye, and the image for the right eye projected from the pixel 160 for the right eye has a predetermined disparity with respect to the image for the left eye. It is formed as an image having a disparity of Therefore, when the observer recognizes the image for the left eye from the pixel 150 for the left eye and the image for the right eye projected from the pixel 160 for the right eye by the observer's left and right eyes, respectively, it is the same as viewing a stereoscopic object through the left and right eyes. You get the depth information and feel the three-dimensional effect. In addition, the scan driver 200 sequentially generates selection signals in response to the control signal Sg output from the timing controller 600 and applies them to the scan lines S1 to Sn of the display unit 100, respectively. The data driver 300 converts the applied stereoscopic image data into an analog data voltage to be applied to the data lines D1 to Dm of the display unit 100, and responds to the control signal Sd input from the timing controller 600. Then, the converted analog data voltage is applied to the data lines D1 to Dm. The light source 400 includes red (R), green (G), and blue (B) light emitting diodes (not shown), respectively corresponding to red (R), green (G), and blue (B). Light is output to the display unit 100 . Red (R), green (G), and blue (B) light emitting diodes of the light source 500 output light to the R subpixel, G subpixel, and B subpixel of the display unit 100 , respectively. The light source controller 500 controls the lighting timing of the light emitting diode of the light source 500 in response to the control signal Sb output from the timing controller 600 . At this time, the period during which the data signal is supplied from the data driver 300 to the data line and the period during which the light source control unit 500 turns on the red (R), green (G), and blue (B) light emitting diodes are the timing control unit ( 600) can be synchronized by the control signal provided by. The timing controller 600 corresponds to the horizontal synchronization signal (Hsync) and the vertical synchronization signal (Vsync) input from the outside and the stereoscopic image signal data input from the data conversion unit 700, and generates the stereoscopic image signal data and the generated control signal. (Sg, Sd, and Sb) are supplied to the scan driver 200, the data driver 300, and the light source controller 500, respectively. The data conversion unit 700 converts input data DATA into 3D image data and transmits it to the timing controller 600 . In this embodiment, the data (DATA) input to the data conversion unit 700 is data including 3D image contents (hereinafter, referred to as '3D image data'), and the stereoscopic image data is the calcination for the left eye of the display unit 100. and left eye image data and right eye image data respectively corresponding to pixels for the right eye. In addition, in this embodiment, 3D image data includes coordinate information (ie, X coordinate and Y coordinate) and color information corresponding to the corresponding coordinate. Here, the color information includes color information or texture coordinate values. Meanwhile, the data conversion unit 700 that converts 3D image data for a flat image into stereoscopic image data may be implemented in the form of a graphic accelerator chip or the like. Hereinafter, the data conversion unit 700 includes a geometric engine unit 710, a rendering engine unit 720, and a frame memory unit 730. In addition, the rendering engine unit 720 includes a start X coordinate calculation unit 721, an X coordinate increase unit 722, a start value calculation unit 723, a color information increase unit 724, and a memory control unit 725. . The starting X coordinate calculation unit 721 receives a left/right eye selection signal and a starting X coordinate (hereinafter referred to as 'starting X coordinate') for a predetermined line (ie, having a constant Y coordinate), and selects the left eye A start X coordinate corresponding to the signal or a start X coordinate corresponding to the right eye selection signal is generated and transmitted to the X coordinate increasing unit 722 . In addition, the X-coordinate increasing unit 722 increases the X-coordinate by 2 based on the starting X-coordinate transmitted from the starting X-coordinate calculating unit 721 and outputs the X-coordinate. That is, in this prior art embodiment, the X coordinate is increased by 2 in order to store only the coordinate values written (stored) in the frame memory unit 730 in the frame memory unit 730 . In addition, the start value calculation unit 723 determines the color information start value (ie, color information start value or texture coordinate start value) for the left/right eye selection signal and a predetermined line (ie, a constant Y coordinate) (hereinafter referred to as 'color'). (referred to as 'information start value') is input, and a color information start value corresponding to the left eye selection signal or a color information start value corresponding to the right eye selection signal is generated and transmitted to the color information increasing unit 724 . In addition, the color information increasing unit 724 includes a start X coordinate, an end X coordinate (referring to an end X coordinate for a given line, hereinafter the same), a color information start value, and a color information end value for a given line. (That is, the color information start value or texture coordinate end value) (hereinafter referred to as 'color information end value') is input to calculate the color information increment value, and the color information increment value is added to the color information start value to generate color information. do. Here, the distance between the start X coordinate and the end X coordinate is calculated using the input start X coordinate and the end X coordinate, and the color information start value and color information end value are calculated using the input color information start value and color information end value. The color information increment value (i.e., color information increment value, texture coordinate increment value) is finally calculated in consideration of these two calculated values and the X coordinate increment by 2 in the X coordinate increasing unit 722. That is, since the X coordinate increases by 2 in the X coordinate increaser 722, the color information increaser 724 uses the distance between the start X coordinate and the end X coordinate and the value difference between the start value of the color information and the end value of the color information. The color information increment is finally calculated by doubling the calculated increment. The color information increasing unit 724 generates and outputs color information by adding the calculated color field information increment value to the color information starting value. Here, a method for calculating an increment value using the distance between the start X coordinate and the end X coordinate and the value difference between the color information start value and the color information end value can be easily known to those skilled in the art based on the above description, so a detailed description thereof will be omitted. do. Next, the memory control unit 725 receives a predetermined Y coordinate, X coordinate output from the X coordinate increasing unit 722 and color information output from the color information increasing unit 724, and receives the input Y coordinate and X coordinate. Based on , color information is controlled to be stored in the frame memory unit 730 . At this time, since the input Y coordinate, X coordinate, and color information are values to be written (stored) in the frame memory unit 730, the memory controller 725 continuously generates a write enable signal (W) to write the frame memory unit 730. ), color information can be stored at high speed.

In addition, the prior art generally uses a 3D modeling tool such as 3D MAX, Maya, etc. to construct a 3D screen to create a text-based 3D output in FBX, OBJ, or DAE format, loads it from content, and displays it at a designated location. The 3D output created above consists of the point coordinates of the model, image information to be displayed on each side, the position and angle of the viewer, the position and intensity of light, and animation designation values, and 3D expression requires a lot of computation. It is generally supported in an environment where a GPU exists rather than a CPU-based environment, and a standardized graphic library such as OpenGL ES is used for GPU use. As described above, when a screen representation request for a product created using a 3D modeling tool occurs, the file must be read and analyzed, processed, and processed so that it can be applied to a graphic library such as OpenGL ES. The FBX, OBJ, and DAE formats, similar to XML processing, extract coordinate information, surface information, camera information, light information, and animation information necessary for 3D expression through string analysis. When the analysis of the 3D data is completed as described above, the OpenGL ES function is called so that the 3D data can be processed by the GPU using a graphic library that supports 3D expression, such as OpenGL ES, and the three-dimensional image is displayed on the screen through the OpenGL ES function. that can be displayed in the form

The standard GUI applied to the prior art configured as above is used by analyzing 3D data in real time and converting it into a hierarchical structure of the corresponding GUI engine. It takes a long time for the data to be output. This is a problem in that the 3D information to be displayed on the screen is not immediately output when the engine is started on the digital instrument panel of a vehicle using an existing GUI engine, but is delayed to be output on the screen several seconds after the engine is started. In addition, for 3D rendering, 3D modeling data is analyzed to extract coordinate information, Mesh, gaze angle information, Camera, light direction and intensity information, and animation, movement information of each model. Since the process goes through the string analysis step, it is time consuming and therefore requires a long loading time for 3D rendering. In addition, when 3D data is extracted, the corresponding information must be input and used in a graphics library such as OpenGL ES, but since the input form in the 3D Modeling Data and the Graphics Library is different, conversion of the 3D Modeling Data is required. will take a long time. As described above, it takes a long time to analyze and convert 3D data, so in the case of a digital instrument panel of a car, it may take a long time to start the engine and display the screen on the digital instrument panel. Therefore, the present invention for solving the problems of the prior art is to convert text-based 3D modeling data into a format used in a graphics library such as a GUI engine structure and OpenGL ES and convert it into a binary to enable fast loading and fast rendering processing it is for

3D data conversion and use method for 3D high-speed rendering of the present invention having the above object has the step of analyzing the 3D data structure and converting it into a hierarchical structure of a GUI engine, the step of binarizing the converted 3D data, and the binary The step of reading the converted 3D data for use in GUI contents and the step of outputting the read 3D binary data to the screen using the function of the Graphica Library stored in OpenGL ES (Open Graphics Library for Embedded System) that is characterized by

The 3D data conversion and use method for 3D high-speed rendering of the present invention configured as described above has the effect of enabling smooth and realistic 3D expression without delay by quickly processing 3D data generated by the user.

1 is a configuration diagram of a conventional stereoscopic image display device;

2 is a control flow chart of 3D data conversion and use method for 3D high-speed rendering of the present invention;

Figure 3 is a 3D data conversion and use system configuration diagram for 3D high-speed rendering of the present invention;

4 is a basic structure diagram of 3D Data applied to the present invention.

The method for converting and using 3D data for 3D high-speed rendering and the system for converting and using 3D data for 3D high-speed rendering using the same according to the present invention having the above object will be described based on FIGS. 2 to 4 as follows.

2 is a control flow chart of a 3D data conversion and use method for 3D high-speed rendering according to the present invention. 2, the 3D data conversion and use method for 3D high-speed rendering of the present invention analyzes the 3D data structure received by the converter, converts it into a hierarchical structure of the GUI engine, and transmits the converted 3D data to an importer to make it binary. (S11), the importer converts the received converted 3D data into binaries and stores them in the GUI content module, drives the GUI Engine module, reads the binaryized 3D data previously stored in the GUI content module, and converts the read out binaryized 3D data Transmitting to the GUI Engine module (S12), and the GUI Engine module generating a GUI Class based on the received binary 3D Data, storing the generated GUI Class in GUI contents, and transmitting it to the OpenGL ES module (S13 ), and generating Command Parameters using standard Graphiecs Library functions such as OpenGL ES while traversing classes in the GUI Class received by the OpenGL ES module and transmitting the generated Command Parameters to the GPU (S14), It is characterized in that it comprises a step (S15) of processing the Command Parameter of the GUI Class and transmitting it to the display unit to provide it.

In addition, if the step (S11) of analyzing the 3D data structure and converting it to the hierarchical structure of the GUI engine above is described in detail, 3D Data is a 3D File Format published by AutoDesk such as FBX and DAE, and the coordinates of the model, scene, and camera , Light, and Animation information, and in the 3D Data basic structure, Scene is the top of the node hierarchy and has one Root Node, and this Root Node can include 3D-related Mesh information, Light information, and Camera information. . In addition, the Mesh information may have Animation, Effect, and Texture information, and the Root Node may inspect the type of the child while traversing the children, and the types of possible children include Mesh, Light, and Camera. In addition, if the child type is a mesh type, mesh data such as vertex coordinates, normal coordinates, UV coordinates, translate, rotate, scale, animation information, texture information, and effect information are included. Information is included, and Camera information may include location information of an object viewed by the camera, Viewpoint, and Fov information.

In addition, when explaining the GUI hierarchy for executing 3D Data in the GUI engine, the GUI engine is Layer → Scene → Sprite … → It has the same structure as the Shape. In the above, a layer has one scene, a scene can include N sprites, and a sprite can have N child sprites and shapes. In addition, Sprite has Scene or Sprite as its upper display object and can have Transform information, Camera information, Animation information and Shape. In addition, Shape has Sprite as its upper display object and can have Mesh information, Effect information (fresnel, phong, projection, shape), and Texture information.

Therefore, the 3D data structure for expressing 3D data using a GUI engine should be applied to a graphics library such as OpenGL ES and converted into a GUI engine hierarchical structure using a converter for quick data processing. If the converter applied to the present invention is described above, since the formats for FBX, OBJ, and DAE are open, the 3D Scene Root Node can be obtained through the analysis of the corresponding 3D Modeling Data, and the child connected to the 3D Scene Root Node By traversing nodes, information such as Mesh, Light, and Camera can be obtained. In other words, to explain in detail that the contents of 3D Modeling Data are configured in a one-to-one correspondence with the GUI Class used in the GUI engine, first, a GUI Scene is created, and after reading 3D Data through File I/O, 3D Scene from 3D Data The root node is taken and a GUI sprite is created. The first GUI sprite created above is a root sprite, and the name of the 3D scene root node, transform information, mesh information, and animation information can be imported and stored in the root sprite. is to save Converter writes the above operation as a recursive function and calls this recursive function if there are children in 3D Data, so that GUI sprites that are created secondly can become child sprites. If the child sprite is a mesh type through type checking, a GUI shape is created, and the mesh data of 3D data is stored in the shape. To create and save instances of Effect Class and Texture Class. Also, if the type of Child Sprite is Camera, a GUI Shape is created, and an instance of a GUI Camera Class is created in the Shape, and name information, target information, Viewpoint information, and Far information are saved.

In addition, the step of binarizing the 3D data converted in Fig. 2 (S12) and the step of reading the binaryized 3D data for use in GUI contents (S13) are executed by the importer, and the importer is executed by the converter. The calculated properties (including all children of the 3D Data Scene Root Node) can be largely divided into Root, Creator, and Instance. The File Header and Scene Root of Binary File are classified as Root, and all child Class Children (instances in case of reusing exception objects) included in the Scene are classified as Creator, and when reusing already input/output objects, the corresponding object In the case of registering an object through its name, it is classified as an instance. In case the object has a name, the name is classified as a hash value, and everything else is distinguished by having each property hash value.

In addition, if you explain in detail about the creation of 3D Binary Data

First, the first information stored in the binary file is Header information.

id, offset: The first id stored in the binary file stores ClassID and the position from ClassID to Version Path in offset,

id, offset, overload: File Header is classified as root, and the hash value of the root is stored in id, and the position occupied from id to overload is stored in offset,

Name id, Name offset, overload, Name Lenth, Name str: The file name information is classified as Name, the hash value of Name is stored in id, the position up to id Name str is stored in offset, and the length information and file name of the file name are stored. save,

Version id, Version offset, overload, Major, Minor, Patch: The hash value of the version is stored in id, the position occupied from id to patch is stored in offset, and the version information of the GUI engine corresponding to Export is stored. Same as 1 below.

[Bottom 1]

Also, in the case of saving the Name and string in the figure 1 above and below, do the following.

id: hash value of Name,

offset: offset from id to Name str,

overload: 0;

Name Length : 13,

Name str: "abcdefghijklm"

Version is the same as the GUI engine version and is information to know if it is compatible through version customization.

After saving the Header File to a binary file, the next step is to save Scene information to a binary file.

Scene is the parent of Root Sprite in the GUI engine and the highest parent in the hierarchical structure.

From Scene, Root Sprite, Camera, Light, SceneProperty, Shape, Mesh... , going down from parent to child, all information is stored in a binary file as shown in 2 below.

[Bottom 2]

Also, if you explain based on the scenario exported to a binary file,

1. To store File Header (classified as Root Property)

One). Root Property- - id, offset Total 8bytes are initialized to 0.

2). Name Property - id, offset, overload Initializes a total of 9 bytes to 0.

3). Save Name Length, Name string. Nength is 4 bytes. A string occupies as many bytes as length.

4). 2). After moving to the starting position initialized in , the hash value of the Name Property and the position overload value occupied by the Name Property are saved.

5). Version Property - Initialize a total of 9 bytes of id, offset, and overload to 0.

6). Save version information. id : Version Property hash value, offset value, Major : 0, Minor : 9, Patch : 0,

7). 5). After moving to the starting position initialized in , save the hash value of the Version Property, the position occupied by the Name Property, and the overload value.

8). One). After moving to the starting position initialized in , save the root property. The File Header Class ID (0xFF584754) and the last offset of the Root Property are stored.

2. Explaining the case of saving a scene (classified as a root property, and the hash value is a hash value of "Scene", different from the id of the File Header.

One). Scene - Initialize a total of 8 bytes of id and offset to 0.

2). Scene is a root property in a hierarchical structure, so a total of 9 bytes of id, offset, and overload are initialized to 0.

3). Now, the property included in the scene is saved in the way shown in the 3 images below.

[3 images below]

4). All values written to the file are saved as binary in the form of Byte, Interger, Float, and Double that can be recognized by the computer.

5). If all are written to the file while traversing the property values, the creation of 3D Binary Data will be completed as shown in the 4 images below.

[Bottom 4]

3 is a configuration diagram of a 3D data conversion and use system for 3D high-speed rendering according to the present invention. 3, the 3D data conversion and use system for 3D high-speed rendering of the present invention analyzes the received 3D data structure, converts it into a GUI engine hierarchy, and transmits the changed GUI engine hierarchy to the importer (100) And, the 3D data converted to the GUI engine hierarchical structure received from the converter is binarized and stored in the GUI content module 250, and the binaryized 3D data is read from the GUI content module 250 and transmitted to the GUI engine module. An importer (200) and a GUI engine (300) that creates a GUI class based on the binaryized 3D data received from the importer, stores the generated GUI class in the GUI content module (250), and transmits it to the OpenGL ES module; The OpenGL ES module 400 receives and stores the GUI class from the GUI engine, generates command parameters while traversing the classes, and transmits the generated command parameters to the GPU, and controls to receive command parameters from the OpenGL ES module and display them on the display It is characterized in that it consists of a GPU 500 to perform and a Display 600 to express the received Command Parameters.

4 is a basic structure diagram of 3D Data applied to the present invention. In the basic structure of 3D data applied to the present invention in FIG. 4, a scene is at the top of the node hierarchy, has one root node, and this root node can include 3D related mesh information, light information, and camera information. In addition, the Mesh information may have Animation, Effect, and Texture information, and the Root Node may inspect the type of the child while traversing the children, and the types of possible children include Mesh, Light, and Camera. In addition, if the child type is a mesh type, mesh data such as vertex coordinates, normal coordinates, UV coordinates, translate, rotate, scale, each animation information, texture information, and effect information are included. information is included, and the camera information includes location information of the object viewed by the camera, viewpoint, and Fov information.

The present invention configured as described above allows the user to quickly receive the desired information as a 3D image by quickly expressing the image required for the instrument panel in a system requiring an instrument panel such as a car as a 3D image, so that the vehicle, drone, ship, aircraft and It can be widely used in the same device.

Claims (7)

1. In the method of converting and using 3D data for 3D high-speed rendering in an automobile instrument panel,

   The 3D data conversion and use method for the 3D high-speed rendering,

   The converter analyzes the received 3D data structure, converts it into a hierarchical structure of the GUI engine, and transmits the converted 3D data to an importer to make it binary (S11);

   The importer converts the received converted 3D data into binaries and stores them in the GUI content module, runs the GUI Engine module, reads the binaryized 3D data previously stored in the GUI content module, and transmits the read binaryized 3D data to the GUI Engine module. Step (S12) and;

   The GUI engine module generates a GUI class based on the received binary 3D data, stores the generated GUI class in GUI contents, and transmits the GUI content to the OpenGL ES module (S13);

   The OpenGL ES module traverses the classes in the received GUI class, creates a command parameter using the graphics library function, and transmits the generated command parameter to the GPU (S14);

   And 3D data conversion and use method for 3D high-speed rendering characterized in that it comprises a step (S15) of processing the Command Parameter of the GUI Class received by the GPU and transmitting it to the display unit.
2. According to claim 1,

   The 3D data,

   3D data conversion and usage method for 3D high-speed rendering characterized by including model coordinates, scene, camera, light, and animation information in a 3D file format released by AutoDEsk, such as FBX and DAE.
3. According to claim 1,

   The basic structure of the 3D data,

   It has a scene at the top and a root node at the bottom,

   The Root Node is a method of converting and using 3D data for 3D high-speed rendering, characterized in that it can include 3D-related Mesh information, Light information, and Camera information.
4. According to claim 1,

   The hierarchical structure of the GUI engine is

   Layer → Scene → Sprite … → 3D data conversion and usage method for 3D high-speed rendering characterized by having the same structure as Shape.
5. According to claim 4,

   3D data conversion and use method for 3D high-speed rendering, characterized in that the layer has one scene, the scene may include N sprites, and the sprite may have N child sprites and shapes.
6. In a 3D data conversion and use system for 3D high-speed rendering in an automobile instrument panel,

   The 3D data conversion and use system for the 3D high-speed rendering,

   Converter 100 which analyzes the structure of 3D data, converts it into a GUI engine hierarchical structure, and transmits the changed GUI engine hierarchical structure to an importer;

   An importer that converts the 3D data received from the converter into the GUI engine hierarchical structure into binaries, stores them in the GUI content module 250, reads the binaryized 3D data from the GUI content module 250, and transmits it to the GUI engine module ( 200) and;

   a GUI engine module 300 that generates a GUI class based on the binaryized 3D data received from the importer, stores the generated GUI class in the GUI content module 250, and transmits the generated GUI class to the OpenGL ES module;

   An OpenGL ES module 400 that receives and stores the GUI Class from the GUI Engine module, generates Command Parameters while traversing the Classes, and transmits the generated Command Parameters to the GPU;

   a GPU 500 that receives command parameters from the OpenGL ES module and controls them to be displayed on Display;

   And 3D data conversion and use system for 3D high-speed rendering, characterized in that consisting of a display (600) for expressing the received Command Parameters.
7. According to claim 6,

   The converter is

   For 3D high-speed rendering characterized by the creation and storage of instances of Mesh Class, Camera Class, Light Class, Texture Class, and Animation Class, which are 3D-related classes provided by the GUI engine and used by the GUI engine, the contents of 3D modeling data. 3D data conversion and use system.

Images