Game program, game system, game device, and game processing method

Abstract

To provide a game program, a game system, a game device and a game processing method capable of achieving deformation with a high degree of freedom with high operability in a game using voxels, by suppressing a residue of small chips due to deformation such as destruction of an object.SOLUTION: With regard to at least part of voxels included in a first scope that is set on the basis of a position where an event related to a geography occurs on the basis of an input of a player's operation, voxel data is updated so that it becomes voxel data indicating that such a geography does not exist. In addition, if there is an independent small region where voxels having voxel data indicating that the geography exists are continuous, and whose size is smaller than a prescribed standard, within a second scope that at least includes the first scope, the voxel data of the voxels included in the small region is updated so that it becomes voxel data indicating that the geography does not exist.SELECTED DRAWING: Figure 21

Description

[Technical Field]

[0001] The present invention relates to a game program, a game system, a game device, and a game processing method that are capable of processing to generate an image using voxel data. [Background technology]

[0002] BACKGROUND ART Conventionally, there is an image generation system that displays game images by creating character voxels and generating polygon mesh information based on imaging information (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2008-33521 Summary of the Invention [Problem to be solved by the invention]

[0004] However, the image generation system disclosed in Patent Document 1 uses voxels in a game to utilize imaging information, and does not assume that objects generated from the voxels will be freely destroyed. If it were assumed that objects generated from voxels in a game would be freely destroyed, it is conceivable that small pieces (fragments) of the object would remain as a result of the destruction, which would result in a poor appearance after destruction and would be time-consuming for the user to dispose of the fragments.

[0005] Therefore, an object of the present invention is to provide a game program, a game system, a game device, and a game processing method that can realize highly flexible deformations with high operability in games using voxels by suppressing the leaving behind small fragments due to deformations such as destruction of objects. [Means for solving the problem]

[0006] In order to achieve the above object, the present invention may employ the following configurations, for example.

[0007] One configuration example of a game program of the present invention is executed on a computer of an information processing device. The game program causes the computer to store, in a storage medium, terrain volume data representing a terrain in a virtual space, the data holding voxel data indicating the presence of the terrain for each voxel included in a voxel space defined in the virtual space. When an event occurs on the terrain based on a player's operation input, the game program updates the terrain volume data so that at least some of the voxels included in a first range defined based on the location where the event occurred have voxel data indicating the absence of the terrain. Furthermore, when there is an independent small area within a second range that includes at least the first range, where voxels having voxel data indicating the presence of the terrain are contiguous and the size of the area is smaller than a predetermined standard, the game program updates the voxel data of the voxels included in the small area to indicate the absence of the terrain. The game program then generates an image of the virtual space by rendering at least a polygon mesh representing the surface of the terrain based on the terrain volume data.

[0008] According to the above, by generating events on the terrain based on the player's operational input, it is possible to deform the terrain generated from voxels, and by preventing fragments of the terrain from remaining due to the deformation of the terrain, it is possible to achieve highly flexible deformation with high operability.

[0009] The voxel data may be a value indicating the degree to which a terrain occupies a space defined by the voxels. The game program may cause the computer to update the voxel data when an event occurs so that the degree of a terrain occupancy for voxels included in a first range decreases and the voxel data indicates that no terrain exists for at least some of the voxels included in the first range.

[0010] According to the above, the value indicating the degree can easily change the state of a voxel to one in which no terrain exists.

[0011] Furthermore, if the sum of the values ​​indicating the degree of each voxel in a region where voxels having voxel data indicating the presence of the above-mentioned terrain are consecutive is smaller than a threshold, the region may be determined to be a small region.

[0012] According to the above, even if the size is less than one voxel, it is possible to prevent fragments from remaining.

[0013] The first range may be a range within a first distance from a reference position set based on the position where an event occurred in the virtual space. The game program may cause the computer to update the voxel data when an event occurred so that the degree of occurrence decreases according to the distance from the reference position and voxels within a second distance from the reference position that is shorter than the first distance indicate that no terrain exists.

[0014] Based on the above, the closer the location is to a reference position that is set based on the location where the event occurred, the more the terrain can be deformed.

[0015] The voxel data may further include material data indicating a material of the terrain. The game program may cause the computer to, when an event occurs, update the voxel data for a voxel included in the first range so that the degree of the voxel is reduced further based on the type of material indicated by the material data of the voxel.

[0016] According to the above, it is possible to provide a wide variety of deformations of the terrain due to the occurrence of events depending on the geology of the terrain.

[0017] The game program may also cause the computer to generate a polygon mesh using an algorithm that determines the vertex positions of polygons based on voxel data between voxels where no terrain exists and voxels where terrain exists. The game program may also cause the computer to recalculate the vertices of the polygon mesh in a range that includes at least voxels whose voxel data has been updated, based on the occurrence of an event.

[0018] According to the above, the recalculation of the vertices of the polygon mesh is limited to the range including the voxels whose voxel data has been updated, thereby reducing the processing load. Furthermore, even if a small region is generated by recalculating the vertices of such a polygon mesh, the fragments caused by the small region can be eliminated.

[0019] The game program may further cause the computer to have the player character perform a destructive action that can destroy the terrain based on an operation input by the player. The event may be the player character hitting the terrain with the destructive action.

[0020] Based on the above, a process for deforming the terrain in accordance with the destruction action of the player character and a process for erasing fragments resulting from the transformation occur, so that the sense of incongruity caused by the erasure can be reduced.

[0021] Furthermore, the game program may cause the computer to update the voxel data of the voxels included in a small area, if the small area is in the air within the virtual space, so that the voxel data indicates that no terrain exists.

[0022] According to the above, the fragments remaining in the air can be eliminated by transforming the terrain due to the occurrence of an event.

[0023] The present invention may also be embodied in the form of a game system, a game device, and a game processing method. [Effects of the Invention]

[0024] According to the present invention, it is possible to deform the terrain generated from voxels by generating events on the terrain based on the player's operational input, and by preventing fragments of the terrain from remaining due to the deformation of the terrain, it is possible to achieve highly flexible deformation with high operability. [Brief explanation of the drawings]

[0025] [Figure 1] FIG. 1 shows an example of a state in which the left controller 3 and the right controller 4 are attached to the main unit 2. [Figure 2] FIG. 10 shows an example of a state in which the left controller 3 and the right controller 4 are detached from the main unit 2. [Figure 3] Six-sided views showing an example of the main unit 2 [Figure 4] Six-sided diagram showing an example of the left controller 3 [Figure 5] Six-sided diagram showing an example of the right controller 4 [Figure 6] A block diagram showing an example of the internal configuration of the main unit 2. [Figure 7] A block diagram showing an example of the internal configuration of the main unit 2, the left controller 3, and the right controller 4. [Figure 8] FIG. 1 is a diagram showing an example of a terrain object that is a voxel object. [Figure 9]FIG. 9 is a diagram showing an example of a state before a part of the terrain object shown in FIG. 8 is deleted. [Figure 10] FIG. 9 is a diagram showing an example of a state after a part of the terrain object shown in FIG. 8 has been deleted. [Figure 11] A diagram showing an example of the contents of voxel data. [Figure 12] A diagram showing an example of property information indicating the properties of a material [Figure 13] A diagram showing an example of texture information indicating the texture of a material. [Figure 14] A diagram showing an example of a mesh generation method [Figure 15] FIG. 10 is a diagram showing an example of a game image including a terrain object. [Figure 16] FIG. 10 shows an example of a game image displayed on the display 12 in which the player character PC performs an action to destroy a terrain object TO. [Figure 17] FIG. 10 shows an example of a game image in which the player character PC destroys a terrain object TO. [Figure 18] FIG. 10 shows an example of a game image in which the player character PC destroys a terrain object TO and the resulting fragments are erased. [Figure 19] FIG. 10 is a diagram showing an example of a destruction range of a voxel to be destroyed in a terrain object TO and a voxel fragment determination range for determining fragments of the terrain object TO. [Figure 20] FIG. 10 is a diagram showing an example of various data used in information processing in the game system 1. [Figure 21] A flowchart showing an example of the flow of game processing executed by the game system 1. DETAILED DESCRIPTION OF THE INVENTION

[0026] A game system according to an example of this embodiment will be described below. An example of the game system 1 according to this embodiment includes a main unit (information processing device; in this embodiment, it functions as a game device main unit) 2, a left controller 3, and a right controller 4. The left controller 3 and the right controller 4 are each detachable from the main unit 2. In other words, the game system 1 can be used as an integrated device by attaching the left controller 3 and the right controller 4 to the main unit 2. The game system 1 can also be used by separating the main unit 2 from the left controller 3 and the right controller 4 (see FIG. 2). Below, the hardware configuration of the game system 1 according to this embodiment will be described, followed by a description of the control of the game system 1 according to this embodiment.

[0027] FIG. 1 is a diagram showing an example of a state in which a left controller 3 and a right controller 4 are attached to a main unit 2. As shown in FIG. 1, the left controller 3 and the right controller 4 are each attached to and integrated with the main unit 2. The main unit 2 is a device that executes various processes (e.g., game processes) in the game system 1. The main unit 2 is equipped with a display 12. The left controller 3 and the right controller 4 are devices that have operation units that allow the user to perform inputs.

[0028] Fig. 2 is a diagram showing an example of the state in which the left controller 3 and the right controller 4 are detached from the main unit 2. As shown in Figs. 1 and 2, the left controller 3 and the right controller 4 are detachable from the main unit 2. Note that, below, the left controller 3 and the right controller 4 may be collectively referred to as "controllers."

[0029] Fig. 3 is a six-sided view showing an example of the main unit 2. As shown in Fig. 3, the main unit 2 includes a substantially plate-shaped housing 11. In this embodiment, the main surface of the housing 11 (in other words, the front surface, i.e., the surface on which the display 12 is provided) is generally rectangular.

[0030] The shape and size of the housing 11 are arbitrary. As an example, the housing 11 may be of a portable size. Furthermore, the main unit 2 alone or an integrated device in which the left controller 3 and right controller 4 are attached to the main unit 2 may be a portable device. Furthermore, the main unit 2 or the integrated device may be a handheld device. Furthermore, the main unit 2 or the integrated device may be a portable device.

[0031] 3, the main unit 2 includes a display 12 provided on the main surface of the housing 11. The display 12 displays images generated by the main unit 2. In this embodiment, the display 12 is a liquid crystal display (LCD). However, the display 12 may be any type of display device.

[0032] The main device 2 also includes a touch panel 13 on the screen of the display 12. In this embodiment, the touch panel 13 is of a type that allows multi-touch input (for example, a capacitance type). However, the touch panel 13 may be of any type, and may be of a type that allows single-touch input (for example, a resistive type).

[0033] The main unit 2 is provided with a speaker (i.e., speaker 88 shown in FIG. 6) inside the housing 11. As shown in FIG. 3, speaker holes 11a and 11b are formed on the main surface of the housing 11. The output sound of the speaker 88 is output from these speaker holes 11a and 11b, respectively.

[0034] The main unit 2 also has a left terminal 17, which is a terminal for the main unit 2 to communicate with the left controller 3 via a wired connection, and a right terminal 21, which is a terminal for the main unit 2 to communicate with the right controller 4 via a wired connection.

[0035] As shown in FIG. 3, the main unit 2 includes a slot 23. The slot 23 is provided on the upper side of the housing 11. The slot 23 has a shape that allows a predetermined type of storage medium to be inserted therein. The predetermined type of storage medium is, for example, a storage medium (e.g., a dedicated memory card) dedicated to the game system 1 and the same type of information processing device. The predetermined type of storage medium is used, for example, to store data used by the main unit 2 (e.g., application save data, etc.) and / or programs executed by the main unit 2 (e.g., application programs, etc.). The main unit 2 also includes a power button 28.

[0036] The main unit 2 has a lower terminal 27. The lower terminal 27 is a terminal through which the main unit 2 communicates with the cradle. In this embodiment, the lower terminal 27 is a USB connector (more specifically, a female connector). When the all-in-one device or the main unit 2 alone is placed on the cradle, the game system 1 can display images generated and output by the main unit 2 on a stationary monitor. In this embodiment, the cradle also has the function of charging the all-in-one device or the main unit 2 alone that is placed on it. The cradle also has the function of a hub device (specifically, a USB hub).

[0037] FIG. 4 is a six-sided view showing an example of the left controller 3. As shown in FIG. 4, the left controller 3 includes a housing 31. In this embodiment, the housing 31 has a vertically long shape, that is, a shape that is long in the up-down direction (i.e., the y-axis direction shown in FIGS. 1 and 4). The left controller 3 can also be held in a vertically long orientation when detached from the main unit 2. The housing 31 has a shape and size that allows it to be held in one hand, particularly the left hand, when held in a vertically long orientation. The left controller 3 can also be held in a horizontally long orientation. When the left controller 3 is held in a horizontally long orientation, it may be held with both hands.

[0038] The left controller 3 includes an analog stick 32. As shown in FIG. 4, the analog stick 32 is provided on the main surface of the housing 31. The analog stick 32 can be used as a direction input unit that can input directions. By tilting the analog stick 32, the user can input a direction corresponding to the tilt direction (and input a magnitude corresponding to the tilt angle). Note that instead of an analog stick, the left controller 3 may be equipped with a cross key or a slide stick that can perform slide inputs as a direction input unit. In this embodiment, input can be made by pressing the analog stick 32.

[0039] The left controller 3 is equipped with various operation buttons. The left controller 3 is equipped with four operation buttons 33 to 36 (specifically, a right button 33, a down button 34, an up button 35, and a left button 36) on the main surface of the housing 31. The left controller 3 also is equipped with a record button 37 and a - (minus) button 47. The left controller 3 is equipped with a first L button 38 and a ZL button 39 on the upper left of the side of the housing 31. The left controller 3 is also equipped with a second L button 43 and a second R button 44 on the side of the housing 31 that is attached to the main unit 2. These operation buttons are used to issue instructions according to various programs (for example, OS programs and application programs) executed on the main unit 2.

[0040] The left controller 3 also includes a terminal 42 for wired communication between the left controller 3 and the main unit 2.

[0041] FIG. 5 is a six-sided view showing an example of the right controller 4. As shown in FIG. 5, the right controller 4 includes a housing 51. In this embodiment, the housing 51 has a vertically long shape, that is, a shape that is long in the up-down direction. The right controller 4 can also be held in a vertically long orientation when detached from the main unit 2. The housing 51 has a shape and size that allows it to be held in one hand, particularly the right hand, when held in a vertically long orientation. The right controller 4 can also be held in a horizontally long orientation. When the right controller 4 is held in a horizontally long orientation, it may be held with both hands.

[0042] Like the left controller 3, the right controller 4 is equipped with an analog stick 52 as a directional input unit. In this embodiment, the analog stick 52 has the same configuration as the analog stick 32 of the left controller 3. The right controller 4 may also be equipped with a cross key or a slide stick that allows slide input, instead of an analog stick. Like the left controller 3, the right controller 4 is equipped with four operation buttons 53 to 56 (specifically, an A button 53, a B button 54, an X button 55, and a Y button 56) on the main surface of the housing 51. The right controller 4 is also equipped with a + (plus) button 57 and a home button 58. The right controller 4 is also equipped with a first R button 60 and a ZR button 61 on the upper right side of the housing 51. Like the left controller 3, the right controller 4 is also equipped with a second L button 65 and a second R button 66.

[0043] The right controller 4 also includes a terminal 64 for wired communication between the right controller 4 and the main unit 2.

[0044] Fig. 6 is a block diagram showing an example of the internal configuration of main unit 2. In addition to the configuration shown in Fig. 3, main unit 2 includes components 81-91, 97, and 98 shown in Fig. 6. Some of these components 81-91, 97, and 98 may be mounted on an electronic circuit board as electronic components and housed in housing 11.

[0045] The main unit 2 includes a processor 81. The processor 81 is an information processing unit that executes various types of information processing executed in the main unit 2, and may be composed of, for example, only a CPU (Central Processing Unit), or may be composed of an SoC (System-on-a-chip) that includes multiple functions such as a CPU function and a GPU (Graphics Processing Unit) function. The processor 81 executes various types of information processing by executing an information processing program (for example, a game program) stored in a storage unit (specifically, an internal storage medium such as flash memory 84, or an external storage medium inserted into slot 23, etc.).

[0046] The main device 2 includes a flash memory 84 and a DRAM (Dynamic Random Access Memory) 85 as examples of internal storage media built into the main device 2. The flash memory 84 and the DRAM 85 are connected to the processor 81. The flash memory 84 is a memory used primarily to store various types of data (which may be programs) saved in the main device 2. The DRAM 85 is a memory used to temporarily store various types of data used in information processing.

[0047] The main device 2 includes a slot interface (hereinafter abbreviated as "I / F") 91. The slot I / F 91 is connected to the processor 81. The slot I / F 91 is connected to the slot 23, and reads and writes data from and to a predetermined type of storage medium (e.g., a dedicated memory card) inserted into the slot 23 in accordance with instructions from the processor 81.

[0048] The processor 81 reads and writes data from and to the flash memory 84, DRAM 85, and the above-mentioned storage media as appropriate, to execute the above-mentioned information processing.

[0049] The main unit 2 includes a network communication unit 82. The network communication unit 82 is connected to the processor 81. The network communication unit 82 communicates with external devices via a network (specifically, wireless communication). In this embodiment, the network communication unit 82 connects to a wireless LAN and communicates with external devices using a method conforming to the Wi-Fi standard as a first communication mode. The network communication unit 82 also performs wireless communication with other main units 2 of the same type using a predetermined communication method (e.g., communication using a proprietary protocol or infrared communication) as a second communication mode. Note that wireless communication using the second communication mode enables wireless communication with other main units 2 located within a closed local network area, and realizes a function that enables so-called "local communication," in which data is transmitted and received by direct communication between multiple main units 2.

[0050] The main unit 2 is equipped with a controller communication unit 83. The controller communication unit 83 is connected to the processor 81. The controller communication unit 83 performs wireless communication with the left controller 3 and / or right controller 4. Any communication method may be used between the main unit 2 and the left controller 3 and right controller 4, but in this embodiment, the controller communication unit 83 performs communication with the left controller 3 and right controller 4 in accordance with the Bluetooth (registered trademark) standard.

[0051] The processor 81 is connected to the left terminal 17, right terminal 21, and lower terminal 27. When performing wired communication with the left controller 3, the processor 81 transmits data to the left controller 3 via the left terminal 17 and receives operation data from the left controller 3 via the left terminal 17. When performing wired communication with the right controller 4, the processor 81 transmits data to the right controller 4 via the right terminal 21 and receives operation data from the right controller 4 via the right terminal 21. When performing wired communication with the right controller 4, the processor 81 transmits data to the cradle via the lower terminal 27. As described above, in this embodiment, the main unit 2 can perform both wired and wireless communication with the left controller 3 and the right controller 4. When an integrated device in which the left controller 3 and the right controller 4 are attached to the main unit 2 or the main unit 2 alone is attached to the cradle, the main unit 2 can output data (e.g., image data and audio data) to a stationary monitor or the like via the cradle.

[0052] Here, the main unit 2 can communicate simultaneously (in other words, in parallel) with multiple left controllers 3. The main unit 2 can also communicate simultaneously (in other words, in parallel) with multiple right controllers 4. Therefore, multiple users can simultaneously input to the main unit 2 using their own sets of left controllers 3 and right controllers 4. For example, a first user can input to the main unit 2 using a first set of left controllers 3 and right controllers 4, while a second user can simultaneously input to the main unit 2 using a second set of left controllers 3 and right controllers 4.

[0053] The display 12 is also connected to the processor 81. The processor 81 displays on the display 12 an image generated (for example, by executing the above-described information processing) and / or an image acquired from the outside.

[0054] The main unit 2 includes a codec circuit 87 and speakers (specifically, a left speaker and a right speaker) 88. The codec circuit 87 is connected to the speakers 88 and the audio input / output terminal 25, and is also connected to the processor 81. The codec circuit 87 is a circuit that controls the input and output of audio data to and from the speakers 88 and the audio input / output terminal 25.

[0055] The main device 2 includes a power control unit 97 and a battery 98. The power control unit 97 is connected to the battery 98 and the processor 81. Although not shown, the power control unit 97 is also connected to each part of the main device 2 (specifically, each part that receives power from the battery 98, the left terminal 17, and the right terminal 21). The power control unit 97 controls the power supply from the battery 98 to each of the above parts based on instructions from the processor 81.

[0056] Furthermore, battery 98 is connected to lower terminal 27. When an external charging device (for example, a cradle) is connected to lower terminal 27 and power is supplied to main device 2 via lower terminal 27, battery 98 is charged with the supplied power.

[0057] Figure 7 is a block diagram showing an example of the internal configuration of the main unit 2, the left controller 3, and the right controller 4. Note that details of the internal configuration of the main unit 2 are omitted in Figure 7 because they are shown in Figure 6.

[0058] The left controller 3 is equipped with a communication control unit 101 that communicates with the main unit 2. As shown in FIG. 7 , the communication control unit 101 is connected to each component, including the terminal 42. In this embodiment, the communication control unit 101 can communicate with the main unit 2 both via wired communication via the terminal 42 and via wireless communication without using the terminal 42. The communication control unit 101 controls the method of communication between the left controller 3 and the main unit 2. That is, when the left controller 3 is attached to the main unit 2, the communication control unit 101 communicates with the main unit 2 via the terminal 42. When the left controller 3 is detached from the main unit 2, the communication control unit 101 communicates wirelessly with the main unit 2 (specifically, with the controller communication unit 83). Wireless communication between the controller communication unit 83 and the communication control unit 101 is performed in accordance with, for example, the Bluetooth (registered trademark) standard.

[0059] The left controller 3 also includes a memory 102, such as a flash memory. The communication control unit 101 is configured, for example, by a microcomputer (also called a microprocessor), and executes firmware stored in the memory 102 to perform various processes.

[0060] The left controller 3 includes buttons 103 (specifically, buttons 33 to 39, 43, 44, and 47). The left controller 3 also includes an analog stick (referred to as "stick" in FIG. 7) 32. Each button 103 and analog stick 32 repeatedly outputs information related to operations performed on the button 103 and analog stick 32 to the communication control unit 101 at appropriate timing.

[0061] The communication control unit 101 acquires information related to the input (specifically, information related to the operation or the detection results from the sensor) from each input unit (specifically, each button 103 and analog stick 32). The communication control unit 101 transmits operation data including the acquired information (or information obtained by performing a predetermined process on the acquired information) to the main unit 2. The operation data is repeatedly transmitted once every predetermined time. The interval at which the information related to the input is transmitted to the main unit 2 may or may not be the same for each input unit.

[0062] By transmitting the above operation data to the main unit 2, the main unit 2 can obtain the input made to the left controller 3. In other words, the main unit 2 can determine the operation of each button 103 and analog stick 32 based on the operation data.

[0063] The left controller 3 is equipped with a power supply unit 108. In this embodiment, the power supply unit 108 has a battery and a power control circuit. Although not shown, the power control circuit is connected to the battery and to each part of the left controller 3 (specifically, each part that receives power from the battery).

[0064] As shown in FIG. 7, the right controller 4 is equipped with a communication control unit 111 that communicates with the main unit 2. The right controller 4 also has a memory 112 that is connected to the communication control unit 111. The communication control unit 111 is connected to each component, including the terminal 64. The communication control unit 111 and memory 112 have the same functions as the communication control unit 101 and memory 102 of the left controller 3. Therefore, the communication control unit 111 can communicate with the main unit 2 both via wired communication via the terminal 64 and via wireless communication that does not use the terminal 64 (specifically, communication in accordance with the Bluetooth (registered trademark) standard), and controls the method of communication between the right controller 4 and the main unit 2.

[0065] The right controller 4 has input units similar to those of the left controller 3. Specifically, it has buttons 113 and an analog stick 52. These input units have the same functions as those of the left controller 3 and operate in the same manner.

[0066] The right controller 4 is equipped with a power supply unit 118. The power supply unit 118 has the same functions as the power supply unit 108 of the left controller 3 and operates in the same manner.

[0067] Next, an overview of the processing executed in the game system 1 will be described with reference to Figs. 8 to 15. In this embodiment, the game system 1 generates a game image in which terrain objects and characters (for example, a player character operated by a player) are arranged in a game space, which is a three-dimensional virtual space, and displays the game image on a display device. Note that in this embodiment, the display device on which the game image is displayed may be the above-mentioned display 12 or a stationary monitor.

[0068] In this embodiment, the shapes of some objects in the game space are defined by voxel data. Here, a voxel is a rectangular parallelepiped (more specifically, cubic) region arranged in a grid pattern in the game space, and voxel data is data set for each voxel. Hereinafter, an object whose shape is defined by voxel data will be referred to as a "voxel object." In this embodiment, the game system 1 stores voxel data for each of a plurality of voxels set in the game space as data for generating voxel objects in the game space.

[0069] Fig. 8 is a diagram showing an example of a terrain object that is a voxel object. As shown in Fig. 8, in this embodiment, the shape of a terrain object that represents terrain such as the ground is defined by voxel data (i.e., it is a voxel object). Each cube shown in Fig. 8 represents a terrain object. Note that in Fig. 8, the edges of the terrain object are shown with thick lines, but these thick lines are added to make the drawing easier to read, and in reality, the edges of the terrain object do not need to be displayed thick.

[0070] The terrain object shown in FIG. 8 is generated according to a rule that, for example, "if a parameter included in the voxel data set for a voxel is greater than a predetermined value, a cube is placed at the position of the voxel, and if the parameter is equal to or less than the predetermined value, nothing is placed at the position of the voxel." The terrain object shown in FIG. 8 is shown for the purpose of clearly illustrating the relationship between voxels and voxel objects. In this embodiment, a voxel object is actually generated (based on voxel data) according to a rule that results in a shape that is complex compared to the length of one side of a voxel, such as the terrain object shown in FIG. 15 (described later). Note that the rule for determining the shape of a voxel object based on voxel data is arbitrary. In other embodiments, the game system 1 may generate a voxel object as shown in FIG. 8 or a voxel object as shown in FIG. 15 based on object data.

[0071] The shape of a voxel object can be changed by changing the voxel data of each voxel. FIGS. 9 and 10 are diagrams showing an example of the state before and after a portion of the terrain object shown in FIG. 8 is deleted. That is, when the hatched portion of the terrain object shown in FIG. 9 is destroyed, the terrain object changes to a shape as shown in FIG. 10. At this time, the game system 1 can easily erase the terrain object by rewriting the voxel data (described later) for the voxels in the hatched portion so that they indicate that the terrain object does not exist. Note that when adding a terrain object, the game system 1 can easily change the shape of the terrain object by changing the voxel data of each voxel, just as when erasing a terrain object.

[0072] In this way, the game system 1 can freely change the shape of a voxel object by rewriting the voxel data. For example, when a terrain object is destroyed in a game for some reason (for example, when a player character hits the terrain object), resulting in a change in the shape of the terrain object, the game system 1 can freely change the shape of the terrain object by changing the voxel data used to generate the terrain object, rather than directly changing the data indicating the outer shape of the terrain object (i.e., a mesh, which will be described later).

[0073] 11 is a diagram showing an example of the contents of voxel data. In this embodiment, the game space can be divided into a plurality of voxels arranged in a grid pattern. The game system 1 associates and stores voxel data for each voxel in the game space. The voxel data indicates, for example, whether a voxel object exists in the voxel corresponding to the voxel data.

[0074] As shown in Fig. 11, the voxel data includes density data. The density data is data of density that indicates the degree to which an object is contained within the area in which each voxel is defined. As will be described in detail later, the position and shape of the surface of the voxel object (i.e., the mesh described later) are determined based on the density. In other words, in this embodiment, the density is also data used to create a mesh that defines the surface of the voxel object.

[0075] In this embodiment, density can take an integer value ranging from a lower limit (e.g., 0) to an upper limit (e.g., 255). In this embodiment, the game system 1 assumes that when the density value set for a voxel is high, the proportion of the volume occupied by the voxel object in that voxel is likely to be large, and when the density value is low, the proportion of the volume occupied by the voxel object in that voxel is small. For example, when the density is 0, no object is present in that voxel; when the density is 255, the entire voxel is occupied by the object; and when the density is between these values, the voxel is occupied by the object at a proportion corresponding to the value. The shape of the voxel mesh, i.e., the shape of the voxel object, is then determined based on the density. However, the shape of the voxel object generated based on the density does not necessarily have a volume that exactly matches the proportion indicated by the density. For example, a method for generating a voxel object such as that shown in FIG. 8 and a method for generating a voxel object such as that shown in FIG. 15 may result in different volumes even if they are based on the same density.

[0076] In other embodiments, the density may indicate either a state in which the entire area of ​​the voxel is occupied by voxel objects, or a state in which the area of ​​the voxel does not contain any voxel objects. For example, the density data may be data that can take only 0 or 1.

[0077] As shown in Fig. 11, the voxel data includes material data. The material data indicates the material (in other words, the substance) of a voxel object generated from the voxel data. In this embodiment, materials such as sand, rock, and soil are set for the voxel object. That is, in this embodiment, multiple types of materials are prepared as materials that can be set for the voxel object, and one of the multiple types of materials is set for the voxel object.

[0078] As shown in FIG. 11, in this embodiment, the material data indicates identification information of the material (referred to as a "material ID"). Furthermore, in this embodiment, the game system 1 stores material information indicating the properties and texture of the material for each material provided in the game. In this embodiment, the material information associates the material ID with the properties of the material and the appearance of the material (specifically, the texture). Specifically, the material information associates the material ID with identification information of the properties of the material (referred to as a "property ID") and identification information of the texture of the material (referred to as a "texture ID") (see FIG. 11).

[0079] Fig. 12 is a diagram showing an example of property information indicating the properties of a material. As shown in Fig. 12, the game system 1 stores property information that associates the above property ID with information indicating the content of the property indicated by the property ID. The property of a material is a property that a voxel object to which the material is set has in the game, and is, for example, information such as weight and slipperiness shown in Fig. 12. Note that the specific content of the property is arbitrary, and for example, the following information may be set as the property of a material: ·temperature Breakability (for example, the number of times a voxel object can be impacted before it breaks) Whether other objects are glued to the voxel object - The amount of health recovered by the player character when the player character destroys a voxel object The amount of in-game currency the player character will acquire when they destroy a voxel object. The specific content of the properties set for the material is arbitrary. In other embodiments, information different from the above may be set as information indicating the properties of the material.

[0080] 13 is a diagram showing an example of texture information indicating the texture of a material. As shown in Fig. 13, the game system 1 stores texture information that associates the above texture ID with the texture indicated by the texture ID.

[0081] In addition to texture information, any information related to color and / or pattern may be set as data defining the appearance of a voxel object. For example, a crack pattern may be set as information related to the appearance of a voxel object. By using such a pattern, the game system 1 can generate an image of a voxel object that appears cracked.

[0082] As described above, in this embodiment, the material data defines the properties of a voxel object and the texture to be used for the voxel object by the material ID. For example, if the material ID indicated by the material data included in the voxel data is "002," the property indicated by the property ID "001" associated with that material ID in the material information is set as the property of the voxel object corresponding to that voxel data (see the arrow in FIG. 11). Also, in the above case, the texture indicated by the texture ID "002" associated with that material ID in the material information is applied to the voxel object corresponding to that voxel data (see the arrow in FIG. 11).

[0083] As described above, in this embodiment, the game system 1 manages the properties and textures of materials separately. Therefore, in this embodiment, it is possible to easily set multiple types of materials that have the same properties but different appearances (i.e., textures), or multiple types of materials that have different properties but the same appearance.

[0084] Note that the material data may be any data that can identify the properties and / or texture of a material. For example, in other embodiments, the material data may indicate the property ID and texture ID, or may have a data structure that actually includes data indicating the properties and texture of the material.

[0085] Furthermore, the material data may be information about a material that further indicates information other than the properties and textures described above. For example, the material data may include effect data that indicates an effect that is generated when an effect generation condition set for a voxel object (e.g., a part of the voxel object is destroyed, or a character steps on the voxel object) is satisfied. The effect data may be data that indicates an effect image (e.g., an effect image that expresses that a voxel object has been destroyed) or data that indicates an effect sound (footsteps when a character walks on a voxel object).

[0086] As shown in FIG. 11 , the voxel data includes state data that indicates the state of a voxel object. The specific content of the state data is arbitrary. For example, the state data may be data that indicates whether a voxel object is wet or not, or data that indicates the amount of damage that has been inflicted on the voxel object. The content of the state data may be updated during the game.

[0087] In this embodiment, the surface of a voxel object is represented by a mesh. A mesh is a collection of multiple faces (specifically, polygons) arranged in a game space. In this embodiment, the game system 1 generates a mesh of a voxel object based on voxel data of each voxel set in the game space. An example of generating a mesh based on voxel data will be described below.

[0088] Fig. 14 is a diagram showing an example of a method for generating a mesh. In Fig. 14, voxels and meshes are expressed in two dimensions for the purpose of making the drawing easier to see and the explanation easier to understand, but in reality, a three-dimensional mesh is generated based on voxels in a three-dimensional space.

[0089] As described above, in this embodiment, the density set for a voxel is set in the range of 0 to 255. Furthermore, in this embodiment, voxels with a density equal to or greater than a reference value are considered to be inside the object, and voxels with a density less than the reference value are considered to be outside the object. It is not necessary to define only voxels with a density of 0 as outside the object (i.e., reference value = 1); the reference value may be, for example, 128. In the example shown in FIG. 14, the density of voxel 201 and the other voxels outside is set to 0, the density of voxel 202 is set to 100, which is less than the reference value, and the densities of voxels 203 and 204 are set to 150 and 200, which are equal to or greater than the reference value. In this embodiment, the game system 1 generates vertices between voxels with densities equal to or greater than the reference value and voxels with densities less than the reference value. Specifically, a determination is made as to whether to generate a vertex for each area spanning eight adjacent voxels (four in the drawing) (areas surrounded by dotted lines in the drawing). In other words, vertices are generated in areas that span both voxels with densities above the reference value and voxels with densities below the reference value. Furthermore, if adjacent vertices (the boundaries of the above-mentioned areas that include each vertex) pass between voxels with densities above the reference value and voxels with densities below the reference value, a polygon mesh is generated by connecting those vertices.

[0090] The coordinates of the vertices are determined by comparing the densities of adjacent voxels along each of the X, Y, and Z axes and interpolating based on the density difference. At this time, coordinate calculations can also be performed based on normal information. However, normal information may be stored in advance for at least some of the voxels. If normal information is not stored, normal information may also be calculated based on the densities of adjacent voxels. Note that in FIG. 14, the density of voxel 202 is less than the reference value, so voxel 202 is treated as outside the object when determining whether or not a vertex exists. However, the density value of voxel 202 itself is used to calculate the coordinates of the vertices to be generated. If the reference value were set to a value lower than the density of voxel 202, additional vertices would be added to the upper right and upper left corners of voxel 202 in FIG. 14.

[0091] By generating a polygon mesh as described above, it is possible to generate a shape whose volume reflects the density of each voxel to some extent. However, depending on the relationship with adjacent voxels, it is possible that a voxel with a density of 0 may include a portion of an area within the object, or that a voxel with a density of 255 may include a portion of an area outside the object. Furthermore, in this embodiment, voxels with a density less than the reference value are processed as being outside the object, so that the number of vertices is reduced compared to when voxels are processed as being inside the object, resulting in a smaller volume. In other words, it is not necessary to calculate a polygon mesh so that the volume strictly corresponds to the density value.

[0092] 15 is a diagram showing an example of a game image including a terrain object. In this embodiment, by generating a mesh as described above, it is possible to make a voxel object have a shape with complex irregularities compared to the length of one side of a voxel, for example.

[0093] Note that any method may be used to generate a mesh based on voxel data. For example, in another embodiment, if the density of voxel data is greater than a predetermined value, a mesh may be generated such that cubes are placed in the voxels (see FIG. 8).

[0094] The game system 1 determines the appearance (i.e., color and / or pattern) of each face of the mesh generated as described above, depending on the material specified by the voxel data. Specifically, the game system 1 determines the texture to be used for drawing each face of the mesh based on the voxel data, and generates an image of the voxel object by mapping the determined texture to each face. The texture to be mapped to each face of the mesh is determined based on voxel data of voxels (referred to as target voxels) used to generate the face, among the voxels in which the voxel object exists. The target voxels may be, for example, one or more voxels arranged around the face, depending on the mesh generation method. In other words, the texture to be mapped to a face of the mesh is determined to be a texture corresponding to the material set for one or more voxels arranged around the face.

[0095] In another embodiment, one voxel data may include multiple types (e.g., two types) of material data. In this case, the voxel data includes ratio data relating to the multiple types of material data. The ratio data is data for determining a texture to be used for a voxel object, and indicates the ratio of influence that each material (specifically, the texture corresponding to the material) indicated by the multiple types of material data has on the appearance (specifically, the color and / or pattern) of the voxel object. When determining a texture to be mapped to each face of a mesh, the texture is determined based on various data (specifically, density data, multiple types of material data, and ratio data) included in the voxel data of the target voxel. For example, when multiple types of materials are set for a target voxel corresponding to one face, the texture corresponding to the material (one type) with the greatest influence may be used in consideration of the ratio, or each texture corresponding to the multiple types of materials may be used in consideration of the ratio.

[0096] In other embodiments, there may be both voxel objects that use voxel data including one type of material data and voxel objects that use voxel data including two types of material data.

[0097] 16 to 19, an example of gameplay in which a player character moves within a game space in response to user operations on the game system 1 will be described. For example, in this embodiment, the player character PC appearing in the game space displayed on the display 12 moves in response to operations of the operation buttons and sticks on the left controller 3 and / or right controller 4 in the all-in-one game system 1, touch operations on the touch panel 13 of the main unit 2, operations to move the entire game system 1, operations to change the posture, etc.

[0098] FIG. 16 is a diagram showing an example of a game image displayed on the display 12 in which the player character PC performs an action to destroy a terrain object TO. In FIG. 16, the player character PC performs a destruction action, such as punching the terrain object TO provided on the game field F, in response to a user operation. Here, the terrain object TO is an example of a voxel object generated based on the voxel data described above, and its surface is represented by a mesh. In the example shown in FIG. 16, one voxel space defining voxels is set on the game field F in the game space, and a terrain object TO is generated on the game field F by defining multiple voxels in the voxel space. Here, at least one voxel space is set in at least a part of the game space to define multiple voxels, and the length of one side of the voxel (resolution), a vector (direction) in global coordinates of the x, y, and z axes in the vector space, the lengths of the x, y, and z directions of the voxel space, the position of the voxel space in the game space, etc. are defined for each voxel space. Note that, for the sake of explanation, Figures 16 to 18 show an example of drawing using a block-shaped mesh, but in reality, drawing may be performed using mesh generation that results in an appearance like that of Figure 15 using the method described in Figure 14.

[0099] In this embodiment, the player character PC can destroy the terrain object TO and cause at least a part of it to disappear by performing an action to destroy the terrain object TO. As an example, as shown in Fig. 16, the player character PC can destroy the terrain object TO and cause a part of the terrain object TO to deform and disappear by performing an action to hit a part of the terrain object TO.

[0100] Figure 17 is a diagram showing an example of a game image displaying a state in which the player character PC has destroyed a terrain object TO. As shown in Figure 17, a part of the terrain object TO is destroyed, deformed, and erased from the game space by the destruction action of the player character PC. Specifically, a circular defect is formed in part of the flat terrain object TO by the destruction action of the player character PC, and the terrain object TO is deformed in a state in which it is divided into a terrain object TOa and a terrain object TOb by the defect.

[0101] The terrain object TOa is relatively large compared to the size of the terrain object TOb, and remains in the game space in a state where it is placed on the game field F. In contrast, the terrain object TOb is a relatively small fragment (piece) and remains in the game space in a state where it is separated from the game field F. In other words, the terrain object TOb remains floating in the air in the game space, which looks bad and gives the user an uncomfortable feeling. Furthermore, it is considered to be time-consuming for the user to dispose of such a fragment. In this embodiment, the fragments resulting from destroying the terrain object TO are automatically erased.

[0102] FIG. 18 is a diagram showing an example of a game image in which a fragment resulting from the player character PC's destruction of a terrain object TO has been erased. As shown in FIG. 18, the terrain object TOb displayed in the game image shown in FIG. 17 has been erased from the game space, and only a portion of it, the terrain object TOa, remains on the game field F due to the player character PC's destruction action. Note that to facilitate understanding of the fragment of the terrain object TO remaining due to the destruction action, the description of the state in which the terrain object TOb remains and the example game image shown in FIG. 17 are provided. However, in actual game processing, the user may not be able to recognize that the terrain object TOb remains. As an example, the destruction process of the terrain object TO and the erasure process of the fragment, the terrain object TOb, may be performed at the same processing timing as the destruction action of the player character PC. As another example, the terrain object TO may be destroyed in response to the player character PC's destruction action, and the fragment may be erased after an effect image, such as an effect image of the fragment, the terrain object TOb, flying through the air in the game space, is displayed.

[0103] In this embodiment, among the pieces of the terrain object TO remaining in the game space after the player character PC destroys the terrain object TO, the removal process is performed on pieces whose size is smaller than a predetermined standard. Furthermore, among the pieces of the terrain object TO, pieces that further satisfy at least one of the following conditions may be subject to the removal process. The first condition is that pieces at least a portion of which is contained within a predetermined range that includes the area in which the terrain object TO is destroyed are subject to the removal process. The second condition is that pieces that are not in contact with other objects or the game field are subject to the removal process. Typically, pieces that remain alone in the air are subject to the removal process. Note that by setting the condition that a piece does not come into contact with an object of the same material, it is possible to remove not only pieces that remain in the air but also pieces made of a single material that remain within an object of another material.

[0104] In this embodiment, the terrain object TO is expressed as being destroyed and deformed / erased by changing the voxel data of each voxel constituting the terrain object TO. FIG. 19 is a diagram showing an example of the destruction range of voxels to be destroyed in the terrain object TO and the voxel fragment determination range for determining fragments of the terrain object TO. The left diagram in FIG. 19 shows the front of the terrain object TO (the surface to be destroyed) as seen from the player character PC destroying the terrain object TO. The right diagram in FIG. 19 shows the right side of the terrain object TO shown in the left diagram.

[0105] The destruction range of the terrain object TO destroyed by the player character PC's destruction action is set based on the position, strength, and ability of the player character PC at which the terrain object TO is destroyed, as well as the strength (material) of the terrain object TO. For example, the destruction range is set to a range within a predetermined distance from a reference position set based on the position in the game space where the destruction action by the player character PC occurs. In the example of FIG. 19, a bell-shaped destruction range is formed on the terrain object TO, with the position where the player character PC performed the destruction action as its center and the innermost part missing due to the destruction becoming a hemisphere. Note that the shape of the destruction range may be other shapes, such as a sphere, an oval sphere, a cube, a cylinder, a wedge, a shape generated by 3D software, or a shape with a portion missing from any of these shapes. Furthermore, the position of the destruction range may be set to be centered on the position in the game space where the destruction action by the player character PC occurred (for example, the position where the player character PC's punch reached), or may be set to be centered a predetermined distance forward from that position as seen from the player character PC. The destruction range corresponds to an example of a first range that is set for the terrain volume data based on the position where an event occurs when the event occurs on the terrain based on the player's operation input.

[0106] The voxels to be erased / deformed based on the above-mentioned destruction range are determined using a signed distance field (SDF). The SDF indicates the distance from each voxel to the nearest destruction range surface, with the destruction range surface being considered 0, and the distance outside the destruction range being considered positive, and the distance outside the destruction range being considered negative. Then, the erasure / deformation process for each voxel is set according to the SDF for that voxel. For example, for a voxel to be erased, the voxel data for that voxel is rewritten to indicate that no terrain object exists, and the part of that voxel is erased from the terrain object TO.

[0107] For example, in this embodiment, the erasure / deformation of each voxel is controlled by changing the density included in the voxel data. For example, density is an index that indicates the degree of volume occupied by a voxel object within a region defined by the voxel. The density value can take an integer value ranging from a lower limit (e.g., 0) to an upper limit (e.g., 255). A higher density value set for a voxel indicates a greater degree of the above-mentioned phenomenon within the voxel, while a lower density value indicates a smaller degree of the above-mentioned phenomenon within the voxel. Furthermore, a voxel whose density is set to the lower limit (i.e., 0) is considered to contain no voxel object within the voxel, while a voxel whose density is set to the upper limit (i.e., 255) is considered to contain a voxel object throughout the voxel. In other words, when the density is set to a value greater than the lower limit, it becomes voxel data indicating the presence of a terrain object, and when it is set to the lower limit, it functions as voxel data indicating the absence of a terrain object. However, the shape of the voxel mesh generated based on the density does not need to have a volume that strictly corresponds to the density value.

[0108] In this embodiment, the erasure / deformation of each voxel is controlled by rewriting the density of each voxel based on the SDF of each voxel. Specifically, by lowering the density of at least voxels whose SDF is a negative distance, at least some voxels within the destruction range are placed in a state where no terrain object exists. As a first example, by rewriting the density of voxels whose SDF is a negative distance to a lower limit, voxels within the destruction range are placed in a state where no terrain object exists, and by maintaining the density of voxels whose SDF is a positive distance as it is, voxels outside the destruction range are placed in a state where a terrain object exists. As a second example, by rewriting the density of voxels whose SDF is a negative distance to a lower value as the absolute value of the distance increases, and by rewriting the density of voxels whose absolute value is greater than a predetermined value to a lower limit, some voxels within the destruction range are placed in a state where no terrain object exists, and by maintaining the density of voxels whose SDF is a positive distance as it is, voxels outside the destruction range are placed in a state where a terrain object exists. As a third example, by rewriting the density of voxels where the SDF is a negative distance to the lower limit value, the voxels within the destruction range are set to a state where no terrain objects exist, and by rewriting the density of voxels where the SDF is a positive distance to a lower value the smaller the absolute value of the distance, the voxel objects do not exist anywhere within the voxels, even in some of the voxels outside the destruction range.

[0109] Note that the density of the voxel data may be rewritten by adjusting the amount of change in density according to the type or state of the material indicated by the material data included in the voxel data. For example, the amount of change in density may be adjusted according to the properties of the material indicated by the material data (e.g., fragility, temperature) (e.g., the more fragile the material, the greater the amount of change in density to be rewritten).

[0110] Furthermore, when rewriting the density in the voxel data, the amount of change in the density may be adjusted according to status data included in the voxel data. For example, the status data may indicate the amount of damage inflicted on the terrain object TO by the player character PC. As an example, whether to reduce the density in the voxel data or increase the amount of damage may be determined based on the relationship between the attacking power of the player character PC and the defensive power of the terrain object TO. Specifically, in terms of the relationship between the hardness of the attacking side (e.g., the hardness of the fist used by the player character PC to punch the terrain object TO) and the hardness of the attacked side (the hardness of the material of the terrain object TO), if the hardness of the attacking side is greater, the density in the destruction range is rewritten. If the hardness of the attacked side is greater, neither the density nor the amount of damage in the destruction range is rewritten. If the hardness of the attacking side and the hardness of the attacked side are equal, the amount of damage to the voxels in the destruction range is increased. If the amount of damage exceeds the voxel's tolerance (damage resistance value due to its material), the density of the voxel is rewritten. In addition, if the amount of damage to a voxel exceeds the capacity of the voxel, the density of the voxel may be set to 0 and the voxel may be erased, and the amount of damage to the voxel can also function as voxel data indicating that no terrain exists.

[0111] Then, after the density of the terrain object TO has been rewritten as described above (specifically, the surface newly exposed to the outside due to the destruction), a new mesh is generated to update the display. For example, based on the occurrence of an event in which the terrain object TO is destroyed, a new mesh is generated by recalculating the vertices of the mesh in a range including at least the voxels whose voxel data has been rewritten due to the destruction. As an example, as shown in FIG. 14, each vertex of the mesh is generated. In this way, after the voxels are erased, a new mesh is generated based on an algorithm that recalculates the vertices of the mesh based on the density of each voxel, resulting in fragments of the terrain object TO. However, in this embodiment, even if fragments remain due to the generation of such a new mesh, these fragments are also erased. Then, a texture to be used to draw each face of the mesh is determined based on the voxel data, and an image of the destroyed terrain object TO is generated by mapping the determined texture to each face. Note that the range in which the mesh is recalculated as described above may be a chunk (a group of voxels serving as a processing unit consisting of a predetermined number of voxels) including the voxels whose voxel data has been rewritten. For example, if 16x16x16 voxels are treated as one chunk and recalculation is performed on the chunk containing the voxel whose voxel data has been rewritten, the processing load can be reduced compared to recalculating the mesh of the entire game space. The range in question may be the voxel space in which the voxel whose voxel data has been rewritten is located, or the entire terrain object TO containing the voxel whose voxel data has been rewritten. Alternatively, if there is no problem with the processing load, the mesh may be recalculated for the entire game space.

[0112] The fragment determination range for determining whether a fragment of a terrain object TO created by a destruction action of the player character PC is to be subject to erasure processing is set based on the location where the destruction action was performed. For example, the fragment determination range is set to encompass at least the destruction range set for the terrain object TO. In the example of FIG. 19, the fragment determination range is set for the terrain object TO a predetermined distance outside the destruction range where the player character PC performed the destruction action, so as to encompass the destruction range. The fragment determination range may be set based on other criteria. For example, as a first example, the fragment determination range may be a range where the SDF is a predetermined positive distance. As a second example, the fragment determination range may be the entire terrain object TO where the destruction range was created by the player character PC's destruction action, or the entire voxel space in which the terrain object TO is defined. As a third example, the fragment determination range may be the chunk described above, which includes voxels whose voxel data has been rewritten by the player character PC's destruction action. The fragment determination range corresponds to an example of a second range that encompasses at least the first range.

[0113] Then, if there is an independent small area within the fragment determination range where voxels having voxel data indicating the presence of a terrain object are adjacently connected and the size of the area is smaller than a predetermined standard, the voxel data of the voxels included in the small area is rewritten to have voxel data indicating the absence of a terrain object. As a first example, if the sum of the density values ​​of the voxels belonging to an area within the fragment determination range where voxels having voxel data indicating the presence of a terrain object are adjacently connected is smaller than a predetermined threshold, the area is determined to be the small area. In this case, even an area smaller than the size of a single voxel can be determined to be the small area. As a second example, if the number of voxels belonging to an area within the fragment determination range where voxels having voxel data indicating the presence of a terrain object are adjacently connected is smaller than a predetermined threshold, the area is determined to be the small area. Through this processing, fragments of the terrain object TO belonging to the small area resulting from the destruction of the terrain object TO are erased. Any method may be used to detect small regions within the fragment determination range, and for example, small regions may be detected using a clustering process based on a three-dimensional filling process.

[0114] Note that the fragment of the terrain object TO that is the target of the above-mentioned erasure process may be at least partially included within the fragment determination range, or may be at least entirely included within the fragment determination range. Typically, the fragment of the terrain object TO that is the target of the above-mentioned erasure process exists alone in the air in the game space and is not connected to the terrain object or other objects, not only within the fragment determination range but also outside the fragment determination area. However, fragments that are in contact with the game field (ground) or other objects, fragments held by characters, etc. may also be targeted for the above-mentioned erasure process. Furthermore, the fragment of the terrain object TO that is the target of the above-mentioned erasure process is considered to be stationary in the air in the game space. However, as another example, fragments that are moving in the air in the game space may also be targeted for the above-mentioned erasure process.

[0115] In the above description, an example of an event in which the terrain object TO is erased is given in which the player character PC hits the terrain object TO with a destruction action, destroying, deforming, or erasing a portion of the terrain object TO. However, the terrain object TO may be erased by other events. For example, the terrain object TO may be destroyed by the player character PC hitting the terrain object TO with his / her entire body or another part such as a leg, or by the player character PC hitting the terrain object TO with an item such as a weapon. The terrain object TO may also be erased (deformed) by an event in which the player character PC throws or kicks another object, causing the other object to hit and destroy the terrain object TO, or by an event in which the player character PC shoots or fires a gun, causing the terrain object TO to be hit and destroyed by a bullet object fired by the gunfire or gunfire.

[0116] Furthermore, in the above explanation, a terrain object TO is used as an example of an object whose part is to be erased from the game space, but it goes without saying that similar processing is possible even when other voxel objects are erased from the game space. For example, similar erasure processing can be performed on other voxel objects, such as buildings and trees placed in the game space, moving objects such as vehicles that move through the game space, other characters such as enemy characters that exist in the game space, items placed in the game space, and objects such as food and tools placed in the game space.

[0117] In the above explanation, an example was used in which the fragment determination range was set so as to include at least the destruction range set for the terrain object TO, but part of the destruction range may be set outside the fragment determination range, or the fragment determination range may be set within the destruction range. As an example of the former, the fragment determination range may be set only on the player character PC side of the destruction range set for the terrain object TO. In this case, the area in the destruction range farthest from the player character PC may be set outside the fragment determination range.

[0118] Next, a specific example of information processing in the game system 1 will be described with reference to FIGS.

[0119] FIG. 20 is a diagram showing an example of various data used in information processing in the game system 1. As shown in FIG. 20, the game system 1 stores a game program, voxel space data, voxel object data, mesh data, operation data, player character data, destruction range data, fragment determination range data, size data, and the like. The game program and voxel space data are data stored in the game system 1 before execution of game processing. The game program and voxel space data are stored, for example, in a storage medium inserted in the slot 23 of the main unit 2. The voxel object data, mesh data, operation data, player character data, destruction range data, fragment determination range data, and size data are data generated during execution of game processing. The voxel object data, mesh data, operation data, player character data, destruction range data, fragment determination range data, and size data are stored, for example, in the DRAM 85 of the main unit 2.

[0120] The game program is a game program for executing the game processing in this embodiment (specifically, the game processing shown in FIG. 21).

[0121] Voxel space data is data that defines voxels set in the game space. Specifically, the voxel space data indicates the length of one side of a voxel and the direction of each side of the voxel in the game space. Furthermore, when voxels are set in only a partial area of ​​the game space, the voxel space data may include data indicating the position and size of the space in which the voxels are set (i.e., voxel space) (i.e., data indicating the range in the game space in which the voxels are set).

[0122] The voxel object data is data that indicates a voxel object to be placed in the game space. Specifically, the voxel object data includes voxel data for each unit area within a part or the entire range of the game space.

[0123] The mesh data is data that indicates a mesh that is set for a voxel object placed in the game space, and includes, for example, data that indicates the position of each vertex in the mesh.

[0124] The operation data is data appropriately acquired from the left controller 3 and / or right controller 4 and the main unit 2. As described above, the data acquired from the left controller 3 and / or right controller 4 and the main unit 2 includes information about inputs (specifically, information about operations) from the input units (specifically, the buttons, analog sticks, and touch panels). In this embodiment, data is acquired from the left controller 3 and / or right controller 4 and the main unit 2, and the acquired data is used to appropriately update the operation data. The update cycle of the operation data may be every frame, which is the cycle of processing executed by the game system 1, which will be described later, or may be every cycle in which the above data is acquired.

[0125] The player character data is data that indicates the position and posture of the player character PC placed in the game space, as well as the movement and state in the game space.

[0126] The destruction range data is data indicating a destruction range that is set when the terrain object TO is destroyed by the player character PC. The fragment determination range data is data indicating a fragment determination range that is set when the terrain object TO is destroyed by the player character PC. The size data is data indicating the size of the fragment of the terrain object TO that is included in the fragment determination range.

[0127] In addition to the data shown in FIG. 20, the game system 1 stores the above-mentioned property information and texture information data as data that is stored in advance in the game system 1 before the game process is executed.

[0128] Fig. 21 is a flowchart showing an example of the flow of game processing executed by the game system 1. In this embodiment, the series of processes shown in Fig. 21 are performed by the processor 81 executing a game program. The game processing shown in Fig. 21 can be started at any timing, but as an example, the game processing is started in response to a command to start the game being given by the player while the game program is being executed.

[0129] In the present embodiment, the processor 81 of the main unit 2 executes the game program stored in the game system 1 to perform the processing of each step shown in FIG. 21 . However, in other embodiments, some of the processing of each step may be performed by a processor (e.g., a dedicated circuit) other than the processor 81. Furthermore, if the game system 1 is capable of communicating with another information processing device (e.g., a server), some of the processing of each step shown in FIG. 21 may be performed by the other information processing device. In other words, each process shown in FIG. 21 may be performed by multiple information processing devices including the main unit 2 working together. Furthermore, the processing of each step shown in FIG. 21 is merely an example, and the order of the processing of each step may be reversed, or other processing may be performed in addition to (or instead of) the processing of each step, as long as similar results are obtained.

[0130] 21 using a memory (for example, DRAM 85). That is, the processor 81 stores information (in other words, data) obtained by each processing step in the memory, and when using the information in a subsequent processing step, reads the information from the memory and uses it.

[0131] 21, processor 81 sets voxel objects in an initial state in the game space (step S1) and proceeds to the next step. Specifically, processor 81 acquires voxel data indicating the arrangement of voxel objects in the initial state and stores (in other words, writes) some or all of the acquired voxel data in DRAM 85 as voxel object data. Note that the voxel data indicating the arrangement of voxel objects in the initial state is stored, for example, in a storage medium attached to slot 23 of main unit 2. Note that a processor that stores, in a storage medium, terrain volume data that represents the terrain in a virtual space and holds voxel data indicating the existence of terrain for each voxel included in a voxel space set in the virtual space, corresponds to processor 81, for example, that performs the processing of step S1.

[0132] Note that the voxel data written to DRAM 85 as voxel object data may be voxel data for a partial range of the voxel data for the entire range of the game space, which is used to generate a game image. For example, processor 81 may generate an image of an object using voxel data for only a partial range of the game space (for example, a range within a predetermined distance from the position of the virtual camera). In this case, the voxel object data may include voxel data for that range. Furthermore, when voxel data for a partial range of the game space is written, a process similar to step S1 is executed at an appropriate timing during execution of a series of processes in steps S3 to S11 (described later) (for example, when the position of the virtual camera has moved by more than a predetermined distance).

[0133] Next, processor 81 generates a mesh for the voxel object (step S2), proceeds to the next step to start the game, and repeatedly executes the processes of steps S3 to S11 during the game. The mesh is generated according to the method described above. Here, processor 81 generates the mesh based on voxel object data stored in DRAM 85. By the process of step S2, voxel objects such as terrain objects are constructed in the game space.

[0134] Next, the processor 81 acquires data corresponding to the user operation from the left controller 3, the right controller 4, and / or the main unit 2, updates the operation data (step S3), and proceeds to the next step.

[0135] Next, processor 81 controls the movements of various objects (e.g., player characters and enemy characters) that appear in the game space (step S4), and proceeds to the next step. For example, processor 81 controls the movements of the player character based on the operation data acquired in step S3 above, and updates the player character data. Processor 81 also controls the movements of enemy characters based on an algorithm defined in the game program.

[0136] Next, the processor 81 determines whether or not an erasure condition for erasing at least a portion of the voxel object is satisfied (step S5). For example, when the player character PC strikes the terrain object TO, the processor 81 sets the position of the strike and its surrounding area as a destruction area, updates the destruction area data, destroys the terrain object TO (voxel object) present in the destruction area, and erases the destroyed portion. As an example, to represent that the destruction area is destroyed, the density values ​​indicated by the voxel data of at least some voxels within the destruction area are set to 0, thereby erasing the objects within the destruction area. Therefore, the processor 81 makes a positive determination in step S5 if the voxels of the voxel object are included in the destruction area caused by the player character's strike. Then, if the erasure condition is satisfied, the processor 81 proceeds to step S6. On the other hand, if the erasure condition is not satisfied, the processor 81 proceeds to step S10.

[0137] In step S6, processor 81 updates the voxel data for the voxel object that satisfies the deletion condition and proceeds to the next step. For example, processor 81 changes the voxel density for the voxels in the portion struck by the player character and the voxels in the surrounding portion so that at least a portion of the voxel object that satisfies the deletion condition is deleted, and updates the voxel data corresponding to each voxel. Processor 81 also deforms the voxel object in the voxels surrounding the destruction range (e.g., the range of the strike) by reducing the density of the voxels (however, to 0 or greater) around the deleted destruction range. Specifically, processor 81 updates the voxel object data stored in DRAM 85 so as to change the density data for the voxel data for the voxels in the deleted range and its surrounding voxels. Processor 81 may also update the density data so that the density indicates a value less than the above-mentioned reference value. For example, processor 81 may set the density of voxels in the area struck by the player character (destruction area) to 0, and reduce the density of voxels in the surrounding area by a predetermined value. When an event occurs on the terrain based on the player's operation input, the processor that updates the voxel data of the terrain volume data so that at least some of the voxels included in the first area set based on the position where the event occurred become voxel data indicating that the terrain does not exist corresponds to processor 81 that performs the processing of step S6, for example.

[0138] Next, processor 81 determines whether or not there are any fragments to be removed in the game space (step S7). For example, processor 81 sets a fragment determination range that includes at least the destruction range set in step S5 and updates the fragment determination range data. Processor 81 then calculates the size of each area within the fragment determination range where voxels having voxel data indicating the presence of a voxel object (e.g., voxel data with a density other than 0) are adjacent and continuous, and updates the size data. If there is an independent small area whose size is smaller than a predetermined standard, processor 81 makes a positive determination in step S7. Here, the independent small area refers to an area not only within the fragment determination range but also outside the fragment determination range that is not connected to other objects. As described above, the fragment determination range may be set a predetermined distance outside the destruction range, or may be set to a range where the SDF is a predetermined positive distance, or may be set to the entire voxel object or the entire voxel space for which the destruction range is set, or may be set to a predetermined chunk that includes the destruction range. If there are any pieces to be erased, processor 81 proceeds to step S8. On the other hand, if there are no pieces to be erased, processor 81 proceeds to step S9.

[0139] In step S8, processor 81 updates the voxel data for the fragment determined to be deleted in step S7, and proceeds to step S9. For example, processor 81 changes the voxel density of the voxels of the fragment so that the fragment determined to be deleted is deleted, and updates the voxel data corresponding to each voxel. Specifically, processor 81 updates the voxel object data stored in DRAM 85 (e.g., updates the density to 0) so as to change the density data for the voxel data of the voxels of the fragment to be deleted. Note that, if there is an independent small area within a second range that includes at least the first range, where voxels having voxel data indicating the presence of a terrain are contiguous and the size of the area is smaller than a predetermined standard, the processor that updates the voxel data of the voxels included in the small area to voxel data indicating the absence of the terrain corresponds to processor 81, for example, that performs the processing of step S8.

[0140] In step S9, processor 81 updates the mesh of the voxel object whose voxel data was changed in steps S6 and S8, and proceeds to step S10. That is, processor 81 generates a mesh of the voxel object for which the erasure condition is satisfied and from which the fragments to be erased have been erased, based on the voxel object data updated in steps S6 and S8. This allows the mesh of the terrain object to be dynamically changed during the game and the fragments remaining in the air to be erased. Processor 81 updates the mesh data stored in DRAM 85 to content indicating the newly generated mesh. Note that the mesh update process in step S9 may be executed after step S6.

[0141] In step S10, processor 81 generates a game image representing the game space, displays it on the display device, and proceeds to the next step. Specifically, processor 81 generates a game image representing the game space including voxel objects and other objects (e.g., a player character and an enemy character). The image of the voxel object is generated according to the method described above using voxel object data and mesh data stored in DRAM 85. The image of the player character is generated using player character data stored in DRAM 85. Processor 81 then displays the generated game image on the display device. During the game, the processing of step S10 is repeatedly executed once per predetermined time (e.g., one frame time). The processor that generates an image of the virtual space by drawing at least a polygon mesh representing the surface of the terrain based on the terrain volume data corresponds to processor 81 that performs the processing of steps S9 and / or S10, for example.

[0142] Next, processor 81 determines whether or not to end the game (step S11). Conditions for ending the game processing in step S11 above include, for example, a condition for ending the game processing being satisfied, or the user performing an operation to end the game processing. If processor 81 does not end the game processing, it returns to step S3 above and repeats the processing, and if it ends the game processing, it ends the processing according to this flowchart. Thereafter, the series of processing from step S3 to step S11 is repeatedly executed until it is determined in step S11 that the processing should end.

[0143] In this way, in this embodiment, by preventing small fragments from remaining when terrain objects generated from voxels are deformed by destruction actions such as those of the player character PC, highly flexible deformation can be achieved with high operability.

[0144] As is clear from the above-described flowchart, when an event occurs in which the player character PC destroys a terrain object TO, the process of erasing voxels due to the destruction in step S6 is executed, and the process of erasing fragments remaining due to the destruction in step S8 is also executed, and by performing these two voxel data update processes, it becomes possible to quickly erase the fragments remaining due to the destruction. Furthermore, because the above-described two voxel data update processes are executed while the player character PC is performing the action of destroying the terrain object TO, even if more voxels than those that would have been erased due to the destruction are erased, the game image appears to show that the destruction has been carried out successfully, and it is possible to prevent the user from feeling uncomfortable.

[0145] The game system 1 may be any device, such as a portable game device or any portable electronic device (PDA (Personal Digital Assistant), mobile phone, personal computer, camera, tablet, etc.). In this case, the input device for performing operations to move the player object PO does not have to be the left controller 3, the right controller 4, or the touch panel 13, but may be another controller, a mouse, a touchpad, a touch panel, a trackball, a keyboard, a cross key, a slide pad, etc.

[0146] Furthermore, although the above description uses an example in which information processing is performed by the game system 1, at least some of the above processing steps may be performed by another device. For example, if the game system 1 is configured to be able to communicate with yet another device (e.g., another server, another image display device, another game device, or another mobile terminal), the above processing steps may be executed by cooperation with the other device. In this way, by performing at least some of the above processing steps in another device, processing similar to the above-described processing becomes possible. Furthermore, the above-described information processing may be executed by one processor or cooperation between multiple processors included in an information processing system composed of at least one information processing device. Furthermore, in the above embodiment, information processing can be performed by the processor 81 of the game system 1 executing a predetermined program, but some or all of the above processing may be performed by a dedicated circuit provided in the game system 1.

[0147] According to the above-described modified example, the present invention can also be realized in a so-called cloud computing system configuration, or in a distributed wide area network or local network system configuration. For example, in a distributed local network system configuration, the above processing can be performed cooperatively between a stationary information processing device (stationary game device) and a portable information processing device (portable game device). Note that in these system configurations, there is no particular limitation on which device performs the above processing, and it goes without saying that the present invention can be realized regardless of the processing division.

[0148] Furthermore, the processing order, setting values, conditions used for judgment, etc. used in the information processing described above are merely examples, and it goes without saying that this embodiment can be realized even with other orders, values, and conditions.

[0149] The program may be supplied to the game system 1 not only through an external storage medium such as an external memory, but also through a wired or wireless communication line. The program may be pre-recorded in a nonvolatile storage device within the device. The information storage medium for storing the program may be a nonvolatile memory, a CD-ROM, a DVD, or similar optical disk-shaped storage media, a flexible disk, a hard disk, a magneto-optical disk, or a magnetic tape. The information storage medium for storing the program may also be a volatile memory for storing the program. Such a storage medium may be a recording medium readable by a computer or the like. For example, the various functions described above can be provided by having a computer or the like read and execute the program from such a recording medium.

[0150] Although the present invention has been described in detail above, the above description is merely illustrative of the present invention in all respects and is not intended to limit its scope. It goes without saying that various improvements and modifications can be made without departing from the scope of the present invention. Furthermore, those skilled in the art will understand that, from the description of specific embodiments of the present invention, they will be able to implement equivalents based on the description of the present invention and common technical knowledge. Furthermore, unless otherwise specified, it should be understood that the terms used in this specification are used in the same sense as commonly used in the art. Therefore, unless otherwise defined, all technical and technical terms used in this specification have the same meaning as commonly understood by those skilled in the art to which this invention belongs. In the event of any conflict, the present specification (including definitions) will prevail. [Industrial Applicability]

[0151] As described above, the present invention can be used as a game program, game system, game device, game processing method, etc. in games using voxels, which allows objects to be destroyed or otherwise deformed with a high degree of freedom through user operation, and which can prevent small fragments from remaining as a result of such destruction or deformation. [Explanation of symbols]

[0152] 1. Information processing system 2...Main unit 3...Left controller 4...Right controller 11. Housing 12...Display 13...Touch panel 32, 52...Analog stick 42, 64...Terminals 81...Processor 82...Network Communication Department 83...Controller communication section 85...DRAM 101, 111...Communication control unit

Claims

1. A game program executed on a computer of an information processing device, The computer, storing, in a storage medium, terrain volume data that is data representing terrain within a virtual space and holds voxel data that indicates the existence of terrain for each voxel included in a voxel space set within the virtual space; When an event occurs on the terrain based on an operational input by the player, updating the voxel data of the terrain volume data so that at least some of the voxels included in a first range set based on the position where the event occurred become voxel data indicating that the terrain does not exist; and If there is an independent small area within a second range that includes at least the first range, where voxels having voxel data indicating the presence of the terrain are continuous and the size of the area is smaller than a predetermined standard, updating the voxel data of the voxels included in the small area so that the voxel data indicates the absence of the terrain, A game program that generates an image of the virtual space by drawing at least a polygon mesh that represents the surface of the terrain based on the terrain volume data.

2. the voxel data is a value indicating the degree to which the topography occupies a space defined by the voxels; 2. The game program of claim 1, wherein the computer updates the voxel data so that, when the event occurs, the degree decreases for voxels included in the first range and voxel data indicates that no terrain exists for at least some voxels included in the first range.

3. 3. The game program according to claim 2, wherein the area is determined to be the small area if the sum of the values ​​indicating the degree at each voxel within the area where voxels having voxel data indicating the presence of the terrain are consecutive is smaller than a threshold value.

4. the first range is a range in which a distance from a reference position set based on a position where the event occurred in the virtual space is within a first distance, 3. The game program according to claim 2, wherein the computer updates the voxel data so that, when the event occurs, the degree decreases according to the distance from the reference position, and voxels within a second distance from the reference position that is shorter than the first distance become voxel data indicating that no terrain exists.

5. the voxel data further includes material data indicating a material of the terrain; 3. The game program according to claim 2, wherein when the event occurs, the computer updates the voxel data for voxels included in the first range so that the degree is reduced further based on the type of material indicated by the material data of the voxels.

6. The computer, generating the polygon mesh between the voxels where the terrain does not exist and the voxels where the terrain exists by an algorithm that determines vertex positions of polygons based on the voxel data; 6. The game program according to claim 1, further comprising: a step of recalculating, based on the occurrence of the event, vertices of the polygon mesh in a range including at least the voxel whose voxel data has been updated.

7. the computer further causes a player character to perform a destruction action capable of destroying the terrain based on an operation input by a player; 6. The game program according to claim 1, wherein the event is a destructive action by the player character hitting the terrain.

8. A game program according to any one of claims 1 to 5, wherein the computer updates the voxel data of voxels contained in a small area so that the voxel data indicates that no terrain exists when the small area is in the air within the virtual space.

9. a storage medium for storing terrain volume data representing a terrain in a virtual space, the data holding voxel data indicating the existence of a terrain for each voxel included in a voxel space set in the virtual space; When an event occurs on the terrain based on an operational input by the player, updating the voxel data of the terrain volume data so that at least some of the voxels included in a first range set based on the position where the event occurred become voxel data indicating that the terrain does not exist; and If there is an independent small area within a second range that includes at least the first range, where voxels having voxel data indicating the presence of the terrain are continuous and the size of the area is smaller than a predetermined standard, updating the voxel data of the voxels included in the small area so that the voxel data indicates the absence of the terrain, a computer that generates an image of the virtual space by drawing at least a polygon mesh that represents the surface of the terrain based on the terrain volume data.

10. the voxel data is a value indicating the degree to which the topography occupies a space defined by the voxels; 10. The game system of claim 9, wherein when the event occurs, the computer updates the voxel data so that the degree decreases for voxels included in the first range and voxel data indicating that no terrain is present for at least some voxels included in the first range.

11. The game system of claim 10, wherein the area is determined to be a small area if the sum of the values ​​indicating the degree at each voxel within the area, where voxels having voxel data indicating the presence of the terrain are continuous, is smaller than a threshold value.

12. the first range is a range in which a distance from a reference position set based on a position where the event occurred in the virtual space is within a first distance, 11. The game system of claim 10, wherein the computer updates the voxel data so that, when the event occurs, the degree decreases according to the distance from the reference position, and voxels within a second distance from the reference position that is shorter than the first distance become voxel data indicating that no terrain is present.

13. the voxel data further includes material data indicating a material of the terrain; The game system of claim 10, wherein when the event occurs, the computer updates the voxel data for voxels included in the first range so that the degree is reduced further based on the type of material indicated by the material data of the voxels.

14. The computer generating the polygon mesh between the voxels where the terrain does not exist and the voxels where the terrain exists by an algorithm that determines vertex positions of polygons based on the voxel data; 14. The game system according to claim 9, wherein, based on the occurrence of the event, vertices of the polygon mesh in a range including at least the voxels whose voxel data has been updated are recalculated.

15. the computer further causes the player character to perform a destruction action capable of destroying the terrain, based on an operation input by the player; 14. The game system according to claim 9, wherein the event is a destructive action by the player character hitting the terrain.

16. 14. A game system according to claim 9, wherein the computer updates the voxel data of the voxels included in the small area so that the voxel data indicates that no terrain exists when the small area is in the air within the virtual space.

17. a storage medium for storing terrain volume data representing a terrain in a virtual space, the data holding voxel data indicating the existence of a terrain for each voxel included in a voxel space set in the virtual space; When an event occurs on the terrain based on an operational input by the player, updating the voxel data of the terrain volume data so that at least some of the voxels included in a first range set based on the position where the event occurred become voxel data indicating that the terrain does not exist; and If there is an independent small area within a second range that includes at least the first range, where voxels having voxel data indicating the presence of the terrain are continuous and the size of the area is smaller than a predetermined standard, updating the voxel data of the voxels included in the small area so that the voxel data indicates the absence of the terrain, a computer that generates an image of the virtual space by drawing at least a polygon mesh that represents the surface of the terrain based on the terrain volume data.

18. the voxel data is a value indicating the degree to which the topography occupies a space defined by the voxels; 18. The game device according to claim 17, wherein, when the event occurs, the computer updates the voxel data so that the degree decreases for voxels included in the first range and voxel data indicating that no terrain exists for at least some voxels included in the first range.

19. The game device according to claim 18, wherein the area is determined to be the small area when the sum of the values ​​indicating the degree of each voxel in the area where voxels having voxel data indicating the presence of the terrain are consecutive is smaller than a threshold value.

20. the first range is a range in which a distance from a reference position set based on a position where the event occurred in the virtual space is within a first distance, 19. The game device according to claim 18, wherein the computer updates the voxel data so that, when the event occurs, the degree decreases according to the distance from the reference position, and voxels that are within a second distance from the reference position that is shorter than the first distance become voxel data indicating that no terrain is present.

21. the voxel data further includes material data indicating a material of the terrain; 19. The game device according to claim 18, wherein when the event occurs, the computer updates the voxel data for voxels included in the first range so that the degree is reduced further based on the type of material indicated by the material data of the voxels.

22. The computer generating the polygon mesh between the voxels where the terrain does not exist and the voxels where the terrain exists by an algorithm that determines vertex positions of polygons based on the voxel data; 22. The game device according to claim 17, wherein, based on the occurrence of the event, vertices of the polygon mesh in a range including at least the voxels whose voxel data has been updated are recalculated.

23. The processor of the information processing device storing, in a storage medium, terrain volume data that is data representing terrain within a virtual space and holds voxel data that indicates the existence of terrain for each voxel included in a voxel space set within the virtual space; When an event occurs on the terrain based on an operational input by the player, updating the voxel data of the terrain volume data so that at least some of the voxels included in a first range set based on the position where the event occurred become voxel data indicating that the terrain does not exist; and If there is an independent small area within a second range that includes at least the first range, where voxels having voxel data indicating the presence of the terrain are continuous and the size of the area is smaller than a predetermined standard, updating the voxel data of the voxels included in the small area so that the voxel data indicates the absence of the terrain, A game processing method that generates an image of the virtual space by drawing at least a polygon mesh that represents the surface of the terrain based on the terrain volume data.

24. the voxel data is a value indicating the degree to which the topography occupies a space defined by the voxels; 24. The game processing method according to claim 23, wherein, when the event occurs, the processor updates the voxel data so that the degree decreases for voxels included in the first range and voxel data indicating that no terrain exists for at least some voxels included in the first range.

25. 25. The game processing method according to claim 24, wherein the small region is determined to be a small region when the sum of the values ​​indicating the degree in each voxel within the region where voxels having voxel data indicating the presence of the terrain are consecutive is smaller than a threshold value.

26. the first range is a range in which a distance from a reference position set based on a position where the event occurred in the virtual space is within a first distance, 25. The game processing method according to claim 24, wherein the processor updates the voxel data so that, when the event occurs, the degree decreases according to the distance from the reference position, and voxels within a second distance from the reference position that is shorter than the first distance become voxel data indicating that no terrain is present.

27. the voxel data further includes material data indicating a material of the terrain; 25. The game processing method according to claim 24, wherein, when the event occurs, the processor updates the voxel data for voxels included in the first range so that the degree is reduced further based on the type of material indicated by the material data of the voxels.

28. the processor, generating the polygon mesh between the voxels where the terrain does not exist and the voxels where the terrain exists by an algorithm that determines vertex positions of polygons based on the voxel data; 28. The game processing method according to claim 23, further comprising: recalculating, based on the occurrence of the event, vertices of the polygon mesh in a range including at least the voxel whose voxel data has been updated.

Images