KR100847754B1 - Method for detecting collision of objects in game engine - Google Patents

Abstract

The present invention relates to a method for performing collision checking between objects in a game engine. More specifically, when the game engine receives a collision check request from a first object, the second object information is collected and collected by a second object. And transmit the collected second collider information to the first object, wherein the first object collides the second collider information and the first collider information through a class of a collision collision function. The main purpose is to return to the game engine after performing. According to the present invention, by delegating a collision check to an object and returning a result of the collision check from the object, it is possible to minimize the coding to be modified when the shape of the collision in the game engine. In addition, the game engine can provide a generalized game engine by performing a collision check regardless of the shape of the object.

Collision Checking, Game Engines, Objects, Views, Object Orientation, Abstraction

Description

How to check for collision in objects in game engines {METHOD FOR DETECTING COLLISION OF OBJECTS IN GAME ENGINE}

1 is a diagram showing an example of performing a collision test of a person and a bullet in a game engine according to the present invention.

FIG. 2 is a flowchart illustrating steps for performing the collision test of FIG. 1.

3 is a diagram illustrating a collision checking function maintained in a function class according to the present invention.

4 is an internal block diagram of a general purpose computer system that may be employed to perform the collision detection method in the game engine according to the present invention.

<Explanation of symbols for the main parts of the drawings>

201: Step for sending a query 202: Step for receiving a query

203: Receiving collider information 204: Transmitting collider information

205: Collision check request step 206: Collision check perform step

207: Return of collision check operation result step 208: Return of collision check operation result

209: Collision check processing step

The present invention relates to a method for performing collision checking between objects in a game engine. More specifically, when the game engine receives a collision check request from a first object, the second object information is collected and collected by a second object. And transfer the collected second collider information to the first object, and the first object determines whether the second collider information and the first collider information collide through a predetermined collision check function class. The point is to return to the game engine.

Today, with the development of computers, the 3D game industry related to computers is developing day by day. Accordingly, the types of games have also changed in various ways. For such various changes in game types, collision tests for determining whether or not collisions between objects in a game are being changed in various ways. As a representative method of the current collision check, the game engine performs the collision check as a predetermined collider instead of the object in order to perform the collision check of the object in the game. The collider has at least one of a rectangle shape, an axis aligned bounding box shape, a sphere shape, a cylinder shape, a cone shape, a frustum shape, a ray shape and a mesh shape. It is a unit of figure that includes one shape and performs collision check on behalf of the object represented by complex shape. For example, in order to perform a collision test between a bullet and a person, the bullet may perform a collision test on behalf of a spherical collider, and the person may perform a collision test on behalf of a collider in the form of a bounding box.

Looking at an example of the conventional coding of the game engine (Before) side that needs a collision determination in order to perform the collision check, as follows.

Implement methods (1) and (2) for obtaining collider information of the first object to collect collider information of the first object.

Before vCenter = A-> GetSphereCollisionCenter (); - (One)

Float fRad = A-> GetSphereCollisionRadus (); - (2)

In addition, by implementing methods (3) and (4) for obtaining collider information of the second object, collider information of the second object is collected.

Before vMin = B-> GetAABBCollisionMin (); -(3)

Before vMax = B-> GetAABBCollisionMax (); - (4)

When collection of collider information from the first object and the second object is completed, collision checking of the first object and the second object is performed for each type of the first object and the second object. At this time, the game engine generates a specialized function according to the shape of the first object and the second object to perform the collision check.

The function includes a function of performing a collision check in the form of a sphere in the form of a first object and a bounding box in the form of a second object, and performing a collision test in the form of the sphere and the bounding box. ) Is as follows.

bool bCollide CollisionQuerySphereAndAABB (& vCenter, fRad, & vMin, &vMax); -(5)

That is, collision inspection is performed by applying the collider information collected from the first object and the second object to the function 5 as a factor.

However, in the case of an example in which a collision collimator represented by a spherical shape on the first object side is changed to a collider represented by a cylindrical form in the conventional collision inspection as described above, the method corresponding to the cylindrical form is implemented to implement the modified first We need to collect new collider information from the object. In other words, the methods ((1), (2)) used in the game engine should be changed to the new methods. In addition, the newly collected collider information cannot be applied to the function 5 to perform a collision check. This function (5) performs a collision check of the new cylindrical shape and the bounding box because the collision check should be performed by applying the factor used in the cylindrical shape instead of the & vCenter and fRad arguments. Should be changed. An example of a function for performing collision checking between the changed first object and the second object is as follows.

bool bCollide CollisionQueryCylinderAndAABB (Cylinderinfo, & vMin, &vMax); -(6)

Function 6 performs a collision check by applying an argument of "Cylinderinfo" on behalf of "& vCenter" and "fRad". At this time, "Cylinderinfo" is a factor expressing the cylindrical shape in the three-dimensional space. In addition, the function that performs the collision check should use the function that compares the cylindrical shape and the bounding box. This changes the function that performs the collision check.

That is, in the conventional game engine, the collision checking between objects should significantly change the overall coding such as a method for receiving argument values and a function for performing collision checking when the type of collider representing the object is changed. This massive change in coding is not only a fundamental cause of the problem of slowing down the game engine, but also acts as a decisive factor that hinders the generalization of the game engine.

In addition, a significant change in coding on the game engine side requires a large amount of coding work when modifying or maintaining a game, and at this time, a high cost is consumed.

SUMMARY OF THE INVENTION The present invention has been made to improve the prior art as described above, which delegates collision checking to an object and returns the results of the collision checking from the object to minimize coding that is modified when the shape of the collision is changed in the game engine. .

An object of the present invention is to provide a generalized game engine by performing a collision check regardless of the shape of the object in the game engine.

In order to achieve the above object and solve the above-mentioned problems of the prior art, the collision inspection method in the game engine according to the present invention is the second collider information of the second object from the first object-the second object Receiving a query requesting-location information for the collider of the request, sending the second collider information request command to the second object according to the query, and transmitting the second collision from the second object. Receiving child information, transmitting the second collider information to the first object in response to the query, and receiving a collision check result with the second object from the first object. The first object transmits the second collider information and the first collider information of the first object to a predetermined collision check function class. The collision check function class transmits a collision check operation result for the first collider information and the second collider information to the first object, and the first object receives a collision check result corresponding to the collision check operation result. Characterized in that the transmission to the collision detection function class.

Hereinafter, with reference to the accompanying drawings will be described in detail a collision detection method according to the present invention.

1 is a diagram showing an example of performing a collision test of a person and a bullet in a game engine according to the present invention.

1 illustrates a person 111 as an example of the first object 110 and a bullet as an example of the second object 120. The person 111 and the bullet 121 move according to a predetermined change rate in the game, and the person 111 determines whether the bullet 121 has collided with itself. In general, since the person 111 is represented by a smaller change rate of distance over time than the bullet 121, the person 111 is the target collider and the bullet 121 is the collider. Therefore, it is determined whether the person 111 who is the target collider collides with the bullet 121 that is the collider. The target collider and the collider may be variously changed according to a predetermined rule of a game application providing a game.

In one example, the person 111 may be replaced with a quadrangular form 112 as a collider, and the bullet may be replaced with a sphere 122 as a collider. In general, in order to check whether the bullet 121 has collided with the person 111, the collision test is performed through the collider roughly without grasping the current coordinates of the complex object. Such colliders are at least one of a rectangle, an axis aligned bounding box, a sphere, a cylinder, a cone, a ray, and a mesh. Represents the current coordinates of the object, including one form. That is, the game engine 130 of FIG. 1 uses a collider instead of the person 111 and the bullet 121 instead of the person 111 to process the result of the collision test between the person 111 and the bullet 121. Position information of the collider in form 122 is used. Since the collision test using such a collider is a well-known conventional technique, detailed description thereof will be omitted.

In order to perform the collision check, the first object 110 collects the second collider information of the spherical form 122 which is the collider of the second object 120. At this time, in order to collect the second collider information, the first object 110 requests the game engine 130 to collect the second collider information. The first object 110 that collects the second collider information is a collision check function class 140 that maintains a predetermined collider test function. The first collider information and the second object 120 of the first object 110 are maintained. Request collision check by transmitting second collider information The collision check function Clarsu 140 performs a collision check by searching for a collision check function according to the type of collider included in the first collider information and the second collider information, and generates a collision check result. Is returned to the first object 110. The first object 110 returns the collision check result to the game engine 130 and the game engine 130 performs a predetermined collision result process according to the collision check result. The collision result processing is a function previously coded by the creator associated with the production of the game.

That is, according to FIG. 1, in order to perform a collision check, a game engine directly collects argument values of collider information of objects and minimizes a problem of coding modification that occurs when a predetermined subroutine is performed. .

FIG. 2 is a flowchart illustrating steps for performing the collision test of FIG. 1.

In step 201, the first object transmits a query for requesting second collider information of the second object to the game engine according to the present invention. The second collider information is positional information about the collider of the second object. For example, when the second collider is a sphere collider, the second collider information may include center point and radius length information capable of expressing the sphere form in three dimensions. As another example, when the collider is in the form of a cylinder, the center point and radius length information of two faces may be included, and the cylinder may further include a height to express the shape of the cylinder in three dimensions. In addition, the query may request the game engine to the game engine at a predetermined period, and when the change rate of movement with respect to the time of the first object is greater than the rate of change with movement with time of the second object, the query is sent to the game engine. May be required.

In step 202, the game engine receives the query from a first object and sends the second collider information request command to the second object according to the query. The second object having received the second collider information request command transmits second collider information, which is its own location information, to the game engine, and the game engine receives the second collider information (step ( 203)). The game engine receiving the second collider information transmits the second collider information to the first object (204).

In step 205, the first object transmits the second collider information received from the game engine and the first collider information which is its own position information to the collision check function class to request collision check. The collision check function class that receives the first collider information and the second collider information grasps the form of the first object and the second object from the first collider information and the second collider information, and A collision check is performed from the collision check function defined at (step 206). The collision checking function is a set of predetermined numbers of functions associated with the number N of collisions of each of the first object and the second object. Collision Check Function The collision check function maintained in the class will be described in detail with reference to FIG. 3.

3 is a diagram illustrating a collision checking function maintained in a function class according to the present invention.

The collision check function class maintains a number of collision check functions 302, depending on the collider type 301. As shown in FIG. 3, the collision check function 302 is rectangular when the collider type 301 includes a rectangular shape, a bounding box shape, a spherical shape, a cylindrical shape, a cone shape, a ray shape, and a mesh shape. Compares square and square shapes, compares square and bounding box shapes, compares square and sphere shapes,… We maintain 6 + 5 + 4 + 3 + 2 + 1 = 21 functions that compare the mesh form with the mesh form.

In the example of FIG. 1, in order to perform a collision check between the first collider 112 having the square shape 112 of the first object 110 and the second collider having the spherical shape 122 of the second object 120, the identification number <303 See>. In this case, the collision check function used is as follows.

Collision (GoRectangleCollider * GoSphereCollider)

In step 207 of FIG. 2, the collision check function class that has performed the collision check returns the collision check operation result to the first object, and in step 208, the first object returns the collision check operation result to the game engine. do. The game engine receiving the collision check calculation result performs a predetermined collision result processing according to the collision check calculation result. The collision result processing operates based on a program previously created by the creator of the game or the like.

As a result, the game engine according to the present invention performs collision checks on various types of collisions, and can minimize coding modifications according to the collision checks. The game engine performs a collision check including coding information that does not change regardless of a property change of the first object or the second object. That is, the game engine according to the present invention provides a generalized collision checking method that is not shaken by the change of the collision.

As a result, coding written in an object-oriented language due to a collision between a person and a bullet mentioned in the prior art may be generalized as follows.

First, a method for collecting second collider information of a bullet, which is a second object, is generated.

class Bullet

{

public:

      GoCollider * GetCollider () {return &m_collider; }

protected:

      GoVisual m_BulletVisual; // bullet visual

      GoSphere Collider m_collider; // collider

};

Next, a method for collecting first collider information of a person who is a first object is generated.

class Man

{

public:

      GoCollider * GetCollider () {return &m_collider; }

protected:

      GoVisual m_ManVisual; // human visual

      GoAABBCollider m_collider; // collider

};

Next, the game engine calls a function to handle the collision between the bullet and the person. We assume that bullets and people are instantiated with m_pBullet and m_pMan, respectively.

bool CheckManHitByBullet () {

      GoCollider * pBulletCollider = m_pBullet-> GetCollider (); -(7)

      GoCollider * pManCollider = m_pMan-> GetCollider (); -(8)

return pBulletCollider-> Query (pManCollider); -(9)

}

The second collider information is collected from the second object (bullet) at the identification number 7, and the first collider information is collected from the first object (person) at the identification number 8. At identification number 9 the game engine sends a query requesting collision checking to the first object (person) and waits for a return value. This delegates to each object a collision check that was previously performed on a game engine. In this case, within the Query function of pBulletCollider, the collision detection function for each type may be called by determining the shape of the first object and the shape of the first object. That is, if the game engine delegates collision checking to an object through an abstract GoCollider without knowing the specific collider type (GoSphereCollider or GoAABBCollider) for the first object and the second object, The test can be performed.

4 is an internal block diagram of a general purpose computer system that may be employed to perform the collision detection method in the game engine according to the present invention.

Referring to FIG. 4, the computer system 400 may include one or more processors 410 connected to a main memory including a random access memory (RAM) 420 and a read only memory (ROM) 430. Include. The processor 410 is also called a central processing unit (CPU). As is well known in the art, the ROM 430 serves to transfer data and instructions to the CPU unidirectionally, and the RAM 420 typically transfers data and instructions bidirectionally. Used to. RAM 420 and ROM 430 may include any suitable form of computer readable media. Mass storage 440 is bidirectionally coupled to processor 410 to provide additional data storage capabilities, and may be any of the computer readable recording media described above. The mass storage device 440 is used to store programs, data, and the like, and is a secondary memory device such as a hard disk which is generally slower than the main memory device. Certain mass storage devices such as CD ROM 460 may be used. The processor 410 may include one or more input / output interfaces, such as a video monitor, trackball, mouse, keyboard, microphone, touchscreen display, card reader, magnetic or paper tape reader, voice or handwriting reader, joystick, or other known computer input / output device. Connected with 450. Finally, the processor 410 may be connected to a wired or wireless communication network through the network interface 470. Through this network connection, the procedure of the method described above can be performed. The apparatus and tools described above are well known to those skilled in the computer hardware and software arts.

The hardware device described above may be configured to operate as one or more software modules to perform the operations of the present invention.

As described above, the present invention has been described by way of limited embodiments and drawings, but the present invention is not limited to the above-described embodiments, which can be variously modified and modified by those skilled in the art to which the present invention pertains. Modifications are possible. Accordingly, the spirit of the present invention should be understood only by the claims set forth below, and all equivalent or equivalent modifications thereof will belong to the scope of the present invention.

According to the present invention, by delegating the collision check to the object and returning the result of the collision check from the object it is possible to minimize the coding to be modified when the shape change of the collision in the game engine.

According to the present invention, a general-purpose game engine can be provided by performing a collision check regardless of the shape of an object in the game engine.

Claims (7)

At the game engine, receiving a query from the first object; Receiving, at the game engine, second collider information about the location of the second object from a second object colliding with the first object according to the query; Sending, at the game engine, the received second collider information to the first object; Transmitting, at the first object, a second collision information and a first collision information about its location in a collision checking function class; In the collision checking function class, (1) the first object and the second object based on the first collider information and the second collider information are formed in the form of a rectangle and an axis aligned bounding. identify at least one of a box form, a sphere form, a cylinder form, a cone form, a frustum form, a ray form, and a mesh form, and (2) the identified forms are the same Or receiving the collision check result from the collision check function class at the first object, as the collision check result is generated through collision comparison with respect to two different types; And Returning, from the first object, the collision check result to the game engine; The game engine, And a game process for collision between the first object and the second object during a game by using the collision check result received from the first object. delete delete delete The method of claim 1, The game engine is a collision detection method, characterized in that implemented in the Object Oriented Program Language. The method of claim 1, The first collider information or the second collider information, And at least one of a center point, a height, and a radius according to the shape of the first object and the second object. A computer-readable recording medium for recording a program for executing the method of any one of claims 1, 5 and 6 on a computer.

Images