KR20090092522A - 3 dimensional landering engine, system, and method using eXtensible Markup Language - Google Patents

Abstract

A 3D rendering engine using the XML(Extensible Markup Language), a system thereof and a method therefor are provided to define a 3D space by using the XML having an opened data structure, and execute an event. An attribute processor(220) recognizes space information and event information from XML-data about space configuration, and then outputs the recognized space information and event information. An event registering unit(260) sequentially registers events generated based on the event information in an event queue. An event interpreter(240) interprets the registered events, and then executes the events. A screen processor(250) displays the 3D space on a screen.

Description

3D landering engine, system, and method using eXtensible Markup Language

The present invention relates to a three-dimensional rendering technology, and more particularly, to a three-dimensional rendering engine, a three-dimensional rendering system, and a method using an XML (eXtensible Markup Language) which is an open data structure.

Tools for general game development only support creating spaces or objects. Therefore, when developing a game, all the source code of the configuration of the three-dimensional space and the execution of various events must be source coded, and a lot of time is spent on development, and the probability of error is increased.

XML stands for Extensible Markup Language and can be seen as a consistent standard of open data structures for data and documents on the Internet. In game development, game development can be facilitated by defining three-dimensional space and executing events using XML that supports an open data structure.

Therefore, the technical problem to be achieved by the present invention is a three-dimensional rendering engine, three-dimensional rendering system that can reduce the game development time and the possibility of error by defining a three-dimensional space and executing events using XML having an open data structure And to provide a method thereof.

The three-dimensional rendering engine for achieving the technical problem includes an attribute processor, an event queue, an event interpreter, a screen processor and an event register. The attribute processor recognizes the spatial information and the event information from the XML (eXtensible Markup Language) data for the spatial configuration, and outputs the recognized spatial information and the event information.

The XML data may be received from a game server in the case of an online game, or may be defined by a client developer in the case of a single game. The event register sequentially registers an event generated based on the event information in the event queue. The event interpreter interprets the event registered in the event queue and executes the interpreted event. The screen processor displays on the screen a three-dimensional space constructed based on the spatial information and event information.

The event register may register asynchronous events directly to the event queue, generated by a client developer, requiring no response from the server, and requiring immediate response. The event register monitors whether the event has occurred, and if the event occurs, classifies the generated event to determine an event target, configures an event based on the determined event target, and configures the configured event in the event queue. Register.

The 3D rendering engine may further include a message processor configured to receive the XML data and mesh data and to process a message received from a data storage unit or a server storing the received XML data and mesh data. .

A 3D rendering system for achieving the technical problem includes a game client including the 3D rendering engine and a game server connected to the game client through an information communication network. Since the features of the 3D rendering engine are as described above, a detailed description of the game client including the same is omitted, and only the game server will be described in detail.

The game server includes an attribute handler and an event handler. The attribute processor recognizes spatial information and event information from the XML data received from the game client, and outputs the recognized spatial information and event information. The event processor determines a response event based on event information received from the attribute processor of the game server, and notifies the game client of the determined response event.

The game server may further include a data storage unit for receiving XML data and mesh data from the game client and storing the received XML data and mesh data or a message processor for processing a message received from the game client. .

The 3D rendering method for solving the technical problem is to recognize the spatial information and event information from the XML (eXtensible Markup Language) data for the spatial configuration, and outputting the recognized spatial information and event information, the event information Sequentially registering the generated event in the event queue, interpreting the registered event, executing the interpreted event, and displaying a three-dimensional space configured based on the spatial information and the event information on the screen. Displaying.

The 3D rendering method may further include directly registering an asynchronous event generated by a client developer, requiring no response from the game server, and requiring an immediate response to the event queue. The registering of the event in the event queue may include monitoring the occurrence of the event, determining, when the event occurs, classifying the generated event to determine an event target, and based on the determined event target. And registering the configured event with the event queue.

The 3D rendering method may further include receiving the XML data and the mesh data, storing the received XML data and the mesh data, or receiving a message from a game server and processing the received message. It may include.

As described above, the three-dimensional rendering engine, the three-dimensional rendering system, and the three-dimensional rendering method according to the embodiment of the present invention require three-dimensional game development because three-dimensional spaces and events are defined using XML, which is an open data structure. It can reduce the time required and reduce the possibility of error in game development process.

1 is a block diagram showing a three-dimensional rendering engine according to an embodiment of the present invention.

2 is a flowchart illustrating an event processing operation of a 3D rendering engine according to an exemplary embodiment of the present invention.

3 is a flowchart illustrating an operation of an event register illustrated in FIG. 1 when a window-related event occurs.

In order to fully understand the present invention, the operational advantages of the present invention, and the objects attained by the practice of the present invention, reference should be made to the accompanying drawings which illustrate preferred embodiments of the present invention and the contents described in the accompanying drawings.

In the present specification, when one component 'transmits' data or a signal to another component, the component may directly transmit the data or signal to the other component, and at least one other component. Through this means that the data or signal can be transmitted to the other component.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. Like reference numerals in the drawings denote like elements.

1 is a block diagram showing a three-dimensional rendering system 100 according to an embodiment of the present invention. Referring to FIG. 1, the 3D rendering system 100 includes a game client 200 and a game server 300. The game client 200 includes a three-dimensional rendering engine 210.

The 3D rendering engine 210 includes an attribute processor 220, an event queue 230, an event interpreter 240, a screen processor 250, and an event register 260. The attribute processor 220 recognizes the spatial information and the event information from the XML (eXtensible Markup Language) data about the spatial configuration, and outputs the recognized spatial information and the event information. The XML data may be received from a game server in the case of an online game, may be defined by a client developer in the case of a single game, and may include the spatial information and event information.

XML is the next-generation standard for open data structures that allows you to create information on the Web or intranet, and share both the data itself and its format. XML is compatible with various documents in different systems and working environments. Recently, many companies have introduced XML-based solutions one after another.

The spatial information includes map information including a name of a map of the game and a mesh file, race information including a race name and a mesh file registered in the game, a name of the character actually located on the map, a race, and Character information including the position of the character on the map, NPC information including the position of the NPC (Non-Player Character) registered in the game and the position of the NPC actually located on the map, the type and the actual object registered in the game Object information indicating the location of an object present in the map, and definitions for effects that occur on the map. The mesh file refers to a file containing mesh data generated by the 3D model data production tool.

For example, suppose a game has an event that hits an NPC. The XML data should include definitions of animations and effects to be applied when clicking on the NPC, and definitions of event messages sent to the game client by the rendering engine. do.

The event register 260 sequentially registers an event generated based on the event information in the event queue 230, and the event interpreter 240 analyzes an event registered in the event queue 230. Run the interpreted event.

The screen processor 250 displays a three-dimensional space configured on the screen based on the spatial information and the event information. The screen processor 250 displays a three-dimensional space on a screen by using directX 3D or Open Grapnics Library (OpenGL).

DirectX is an application programming interface (API) for working on the Microsoft platform in multimedia, especially game programming.OpenGL is an industry standard graphics library created by Silicon Graphics. Is bisecting.

The event register 260 may directly register an asynchronous event generated by a client developer, a response from a game server, and requiring an immediate response to the event queue 230. That is, the event register 260 may directly register an asynchronous event that does not need to be synchronized with the game server 300 to the event queue 230. For example, the asynchronous event may include a window related event such as a button click.

The event register 260 monitors whether the event has occurred, and when the event occurs, classifies the generated event to determine an event target, configures an event based on the determined event target, and configures the configured event. The event queue 230 may be registered.

The 3D rendering engine 210 may further include a data storage unit 270 which receives the XML data and mesh data from the game server 300 and stores the received XML data and mesh data. Can be. In addition, the 3D rendering engine 210 may further include a message processor 280 for processing a message received from the game server. The message may be a message extracted by the attribute processor 220 from the XML data.

The game server 300 is connected to the game client 200 through an information communication network, and includes an attribute processor 310 and an event processor 320. The attribute processor 310 recognizes spatial information and event information from the XML data received from the game client 200, and outputs the recognized spatial information and event information. The event processor 320 determines a response event based on the event information received from the attribute processor 310 of the game server 300, and notifies the game client 200 of the determined response event.

The game server 300 may further include a data storage unit 340 and a message processor 330. The data storage unit 340 may receive XML data and mesh data from the game client 200 and store the received XML data and mesh data. The message processor 330 processes a message received from the game client 200. The message may be a message extracted from the XML data received from the game client 200 by the property processor 310 of the game server 300.

2 is a flowchart illustrating an event processing operation of the 3D rendering engine 210 according to an exemplary embodiment of the present invention. Referring to Figures 1 and 2, the process will be described in detail.

The 3D rendering engine 210 initializes the event queue 230 (S100). The attribute processor 220 of the 3D rendering engine 210 receives XML data (S101), determines whether event information is received from the received XML data, and outputs event information if event information is received. The system continuously checks whether event information is received (S102).

The event register 260 registers an event generated based on the event information output from the attribute processor 220 in the event queue 230 (S103). The event interpreter 240 analyzes the event registered in the event queue 230 and checks whether the interpreted event has occurred (S104). When an event occurs, the event interpreter 240 checks whether the generated event is a space movement event (S105).

If the generated event is a spatial movement event, the 3D rendering engine 210 causes the attribute processor 220 to receive XML data again to obtain new spatial information (S101), otherwise, the generated event is terminated. Check whether the event (S106). If the generated event is an end event, the event queue 230 deletes the registered event, and the event processing process is terminated (S107).

If the generated event is not an end event, the event interpreter 240 classifies the object of the event into an NPC, an object, and a space (S108), applies an effect or animation corresponding to the generated event, and outputs the result. Create an event message to inform the application (S109).

The event interpreter 240 determines whether an event corresponding to the generated event is required (S110), and if a corresponding event is required, configures a corresponding event message (S111), and then the event message is a synchronization event. It is determined whether the message (S112). If the corresponding event is unnecessary, the event interpreter 240 immediately determines whether the event message is a synchronization event message (S112).

If the event message is a synchronization event message, the 3D rendering engine 210 transmits the synchronization event message to the game server (S113). If the event message is not a synchronization event message, the property processor 220 checks whether event information is received (S102).

3 is a flowchart illustrating an operation of the event register 260 illustrated in FIG. 1 when a window-related event occurs. Hereinafter, the process will be described in detail with reference to FIGS. 1 and 3.

The event register 260 monitors whether a window-related event, which is an asynchronous event, occurs (S200). When a window related event occurs, the event register 260 classifies the generated window related event (S202) to determine an event target (S203), and configures a window related event based on the determined event target (S204). In operation S205, the configured window-related event is registered in the event queue 230.

Although the invention has been described with reference to one embodiment shown in the drawings, this is merely exemplary, and it will be understood by those skilled in the art that various modifications and equivalent other embodiments are possible. Therefore, the true technical protection scope of the present invention will be defined by the technical spirit of the appended claims.

Claims (14)

An attribute processor that recognizes spatial information and event information from eXtensible Markup Language (XML) data for spatial configuration, and outputs the recognized spatial information and event information; An event register that sequentially registers events generated based on the event information in an event queue; An event interpreter for interpreting an event registered in the event queue and executing the interpreted event; And And a screen processor configured to display a three-dimensional space configured on the screen based on the spatial information and the event information. The method of claim 1, wherein the event register, A three-dimensional rendering engine capable of registering an asynchronous event directly in the event queue that does not require a server response. The method of claim 1, wherein the event register, 3D for monitoring whether the event occurs, classifying the generated event to determine an event target, configuring an event based on the determined event target, and registering the configured event in the event queue. Rendering engine. The method of claim 1, wherein the XML data, 3D rendering engine, which may be received from a game server in the case of an online game, or defined by a client developer in the case of a single game. The method of claim 1, wherein the three-dimensional rendering engine, And a data storage unit configured to receive the XML data and the mesh data and to store the received XML data and the mesh data. The method of claim 1, wherein the three-dimensional rendering engine, And a message handler for processing messages received from the server. A game client comprising the three-dimensional rendering engine according to any one of claims 1 to 6; And A game server connected to the game client through an information communication network; The game server, An attribute processor for recognizing spatial information and event information from XML (eXtensible Markup Language) data received from the game client and outputting the recognized spatial information and event information; And And an event processor to determine a response event based on event information received from the property processor of the game server, and to notify the game client of the determined response event. The method of claim 7, wherein the game server, And a data storage unit configured to receive XML data and mesh data from the game client and store the received XML data and mesh data. The method of claim 7, wherein the game server, And a message processor for processing a message received from the game client. Recognizing spatial information and event information from eXtensible Markup Language (XML) data for spatial configuration, and outputting the recognized spatial information and event information; Sequentially registering events generated based on the event information in an event queue; Interpreting the registered event and executing the interpreted event; And And displaying a three-dimensional space configured on the screen based on the spatial information and the event information. The method of claim 10, wherein the three-dimensional rendering method, And registering an asynchronous event that does not require a response of a server directly in the event queue. The method of claim 10, wherein registering the event to the event queue comprises: Monitoring whether the event occurs; When the event occurs, classifying the generated event to determine an event target; And Configuring an event based on the determined event target, and registering the configured event in the event queue. The method of claim 10, wherein the three-dimensional rendering method, Receiving the XML data and mesh data and storing the received XML data and mesh data. The method of claim 10, wherein the three-dimensional rendering method, And processing the message received from the game server.