JP2017148487A - Image processing method, and image processing program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To permit control of a highly operable character.SOLUTION: Before a moving body is related to a character, an image processing method determines whether a relationship between the moving body and the character satisfies a predetermined condition (401), determines whether predetermined input is performed (403), based on referenced touch input information by referring to the touch input information stored before the moving body is related to the character (402) when the predetermined condition is satisfied, and controls operation of the character (404), based on the touch input information stored before the moving body is related to the character when predetermined input is performed.SELECTED DRAWING: Figure 4

Description

  The present technology relates to an image processing method and an image processing program.

  Patent Document 1 discloses a technique for accepting a user's input operation (preceding input) before the player receives the ball and moving the ball in a direction corresponding to the input operation.

Japanese Patent Laid-Open No. 2001-321566

  In Patent Document 1, as a method for realizing the prior input, if there is a prior input, the candidate (character) state, the hit ball state, and the fielder (character) indicated by the prior input are covered. The state is recognized and it is determined whether the candidate can catch the ball. Therefore, the detection of the preceding input serves as a trigger for determining whether or not to cause the character to perform an action corresponding to the preceding input. In this case, since the program for detecting the operation input and the program for controlling the character are inseparable, the versatility of the program may be limited.

  An object of the present technology is to provide a method capable of improving the versatility of a program.

  In order to solve the above-described problem, an aspect of the present technology includes a step of displaying a moving object, an image including a character that can be operated by a user on a touch display, and a step of detecting a touch input to the touch display. A step of identifying touch input information based on the touch input; a step of storing the touch input information in a memory; and a position of the moving body and the character when the moving body is not associated with the character. Determining whether the relationship satisfies a predetermined condition; and when the predetermined condition is satisfied, refer to the preceding touch input information stored before the moving object is associated with the character, and the preceding touch input information is Determining whether to include a first input; and the preceding touch input information includes the first input The case, on the basis of the prior touch input information, including the steps of executing a first operation in the character, to a method.

  Another embodiment of the present technology is a program executed by a processor, which detects a touch input to a touch display and stores information on the touch input corresponding to a predetermined number of frames in a memory. When a predetermined condition is satisfied after the program and the information related to the touch input are stored in the memory, the movement of the character displayed on the touch display is controlled based on the information related to the touch input. And a character control program.

  According to the present technology, it is possible to control a character with high operability based on a touch input to the touch display.

FIG. 11 is a diagram illustrating a computer according to an embodiment of the present technology. It is a block diagram which shows the function of the process part by one Embodiment of this technique. It is an example of the game screen produced | generated by the game program of one Embodiment of this technique. 5 is a flowchart illustrating an operation example of a user interface unit according to an embodiment of the present technology. It is a schematic array figure of the touch position information acquired by one embodiment of this art. It is a schematic array figure of the touch position information acquired by one embodiment of this art. 4 illustrates an example configuration of touch input information according to an embodiment of the present technology. It is a flowchart which shows the operation example of the character control part by one Embodiment of this technique. It is a table | surface which shows the relationship of the action performed by the character control part by one Embodiment of this technique, the touch input information referred by the character control part, and the operation object character. It is a flow figure showing an example of detailed processing by one embodiment of this art. 6 is a graph example of flick operation information determined by an embodiment of the present technology.

  First, the contents of the embodiments of the present technology will be listed and described. An image processing method and an image processing program according to an embodiment of the present technology include the following configurations.

(Item 1)
Displaying a moving object and an image including a character operable by a user on a touch display;
Detecting touch input to the touch display;
Identifying touch input information based on the touch input;
Storing the touch input information in a memory;
Determining whether a positional relationship between the moving body and the character satisfies a predetermined condition when the moving body is not associated with the character;
Determining whether the preceding touch input information includes a first input by referring to the preceding touch input information stored before the moving body is associated with the character when the predetermined condition is satisfied;
Causing the character to perform a first action based on the preceding touch input information when the preceding touch input information includes the first input.

(Item 2)
When the preceding touch input information includes the first input and information for specifying a touch direction,
The method according to item 1, comprising a step of controlling a moving direction of the moving body based on information specifying the touch direction.

(Item 3)
The preceding touch input information further includes information specifying a touch distance;
Item 3. The method according to Item 2, wherein a trajectory of the moving body toward the moving direction is specified based on the touch distance.

(Item 4)
The method according to item 1 or 2, wherein the predetermined condition includes that a distance between the moving body and the character is equal to or less than a predetermined value.

(Item 5)
The method according to any one of Items 1 to 4, wherein the mode of the first action is specified based on a position of the moving body with respect to the character.

(Item 6)
Causing the character to execute a second action different from the first action when the preceding touch input information does not include the first input;
When subsequent touch input information including a second input is stored in a memory within a predetermined period after the character starts the second action, the character is transmitted to the character based on the subsequent touch input information. The method according to any one of items 1 to 5, further comprising: stopping the second operation and executing the first operation.

(Item 7)
A program for causing a computer to execute the method according to any one of items 1 to 6.

(Item 8)
A program executed by a processor,
A user interface program for detecting touch input to the touch display and storing information on the touch input corresponding to a predetermined number of frames in a memory;
Character control for controlling the action of the character displayed on the touch display based on the information on the touch input when a predetermined condition is satisfied after the information on the touch input is stored in the memory. A program comprising:

(Item 9)
Information about the touch input is:
Touch position coordinates of the touch input for each frame;
Touch direction between frames, touch distance, and touch speed,
Touch input type,
If the touch input type is flick or swipe input, their direction,
Item 9. The program according to Item 8, which includes a part or all of information regarding the length / shortness when the touch input type is a flick operation.

(Item 10)
The program according to item 8, wherein the predetermined condition is defined based on a positional relationship between the character displayed on the touch display and a moving object.

  Hereinafter, embodiments of the present technology will be described with reference to the drawings. In addition, this technique is not limited to these illustrations, is shown by the claims, and is intended to include all modifications within the meaning and scope equivalent to the claims. In the following description, the same reference numerals are given to the same elements in the description of the drawings, and redundant descriptions are omitted.

[Computer 100]
FIG. 1 is a hardware configuration diagram of a computer 100 according to an embodiment of the present technology.
The present embodiment relates to controlling the movement of a character in a computer game space in accordance with a user instruction.

  As shown in FIG. 1, the computer 100 includes a processing unit 102, a storage unit 104, and a touch display 110. The computer 100 may further include a network interface (not shown) for communicating with other computers and smartphones via a network. The computer 100 is a device including a touch display 110 such as a smartphone or a tablet terminal.

  The processing unit 102 is configured to read a program stored in the storage unit 104 and execute processing according to the program. When the processing unit 102 executes various programs stored in the storage unit 104, each function described later is realized. The processing unit 102 includes a CPU (Central Processing Unit) and a GPU (Graphics Processing Unit).

  The storage unit 104 stores at least an operating system. The operating system is a computer program for controlling the overall operation of the computer 100. The storage unit 104 can also store data generated by the operation of the computer 100 temporarily or permanently. The storage unit 104 includes a main storage device such as a ROM (Read Only Memory) and a RAM (Random Access Memory), and an auxiliary storage device such as a hard disk, a flash memory, and an optical disk.

  The touch display 110 includes a display unit 112 that provides visual information to the user, and a contact detection unit 114 that receives an input for operating the computer 100 from the user.

  The display unit 112 displays the image generated by the processing unit 102. For example, the display unit 112 displays an image generated as a result of image processing on the computer game screen. As an example, a liquid crystal display or organic EL (organic electroluminescence) is used for the display unit 112.

  When touching the surface with a finger, stick, stylus pen, or the like, the contact detection unit 114 detects the contact position at a predetermined cycle (for example, a frame rate of 30 fps), and outputs coordinate data corresponding to the contact position. It has a function. The contact detection unit 114 may be disposed on the upper layer of the display unit 112. As an example, a pressure detection method, a resistance film method, a capacitance method, or an electromagnetic induction method is adopted for the contact detection unit 114.

  FIG. 2 is a block diagram illustrating a functional configuration of the processing unit 102 according to an embodiment of the present technology. The processing unit 102 includes a user interface unit 210, a character control unit 220, and an image generation unit 230. The character control unit 220 includes a shooting condition determination unit 221, a UI reference unit 222, an input determination unit 223, a character action control unit 224, and an object control unit 225.

  The user interface unit 210 executes a process common to operations of various computer games (for example, a soccer game and a tennis game) using the touch display 110. A specific operation example of the user interface unit 210 will be described in detail with reference to FIG.

  The character control unit 220 refers to the touch input information 241 as necessary, and controls character movements specific to various computer games based on the reference information. A specific configuration and operation example of the character control unit 220 will be described in detail with reference to FIG.

  The user interface unit 210 executes processes common to various computer game operations using the touch display 110 regardless of the processes performed by the character control unit 220. Therefore, the user interface unit 210 can be applied to various other computer games without changing its configuration.

  The image generation unit 230 acquires predetermined data from the storage unit 104, generates a game image based on the acquired data, and causes the display unit 112 to display the game image. As an example, the game image is a soccer game image, for example, a soccer game field, a character appearing in the soccer game, and an image including a ball.

  The storage unit 104 stores game information 240 and a game program 250. The game information 240 includes, for example, touch input information 241 specified by the user interface unit 210. The game program 250 includes, for example, a UI program 251 that causes the user interface unit 210 to function, and a character control program that causes the character control unit 220 to function. 252.

  FIG. 3 is a game screen 300 when the game program 250 of one embodiment is applied to a soccer game. The touch display 110 displays a soccer field FD captured by a virtual camera (not shown) arranged in the game space. Further, on the upper part of the touch display 110, the score “1-0” and the elapsed time “second half 01:12” are displayed as additional information. In the soccer field FD, various game objects that can be operated by the user are arranged. Examples of game objects include a moving body (for example, soccer ball) MB, own characters CH11 and CH12 of the own team, opponent characters CH21 to CH23 of the opponent team, and the like. Each character is displayed with a position such as “FW”. In the center of the display, the moving object MB is associated with the player character CH12, and an active mark MK marked with ▽ is displayed on the player character CH11. The own character CH12 on which the active mark MK is displayed is an operation target character that can be operated through a user's touch operation. Examples of the action of the player character include dribbling and kicking the ball, and movement in the field (positioning). The kick includes various operations such as pass, clear, centering, and chute. Field coordinates are defined in the field FD. Each of the objects such as the moving body MB, the own characters CH11 to 12, the opponent characters CH21 to 23 of the opponent team, and the goal GL have field coordinate information. A user interface image (hereinafter referred to as “UI image”) corresponding to the touch operation by the user is displayed at the bottom of the screen. The UI image is associated with a motion command to the player character CH12. According to one embodiment, the UI image may relate the sliding direction to the moving direction of the character in the game space and the sliding distance to the moving speed of the character in the slide operation. Thereby, it is possible to provide a UI image that can provide the user with intuitive operability.

  FIG. 4 is a flowchart illustrating an operation example of the user interface unit 210. This flowchart represents processing performed by the user interface unit 210 during one frame. When the process from the beginning (step S401) to the end (step S405) of the flowchart is completed, a game image is generated for one frame, and then the same from the beginning of the flowchart again to generate the next frame of the game image. The process is repeated.

In step S401, the user interface unit 210 detects whether or not there is a touch input by the user to the contact detection unit 114.
When the touch input is detected, in step S402, the user interface unit 210 acquires the touch position coordinates (x, y) on the touch display 110 of the touch input by the user on the contact detection unit 114, and the storage unit 104. ("Yes" in step S401). If no touch input is detected, nothing is stored in the storage unit 104, and the process returns to step S401.

  In step S403, the user interface unit 210 obtains a difference between the touch position coordinate of the touch input in the latest frame and the touch position coordinate of the touch input in the immediately previous frame, and based on the difference, updates the latest touch input coordinate from the previous touch input. The touch direction and the touch distance until the touch input is calculated. Furthermore, the user interface unit 210 calculates the touch speed from the previous touch input to the latest touch input based on the difference and the elapsed time between frames (for example, 33 milliseconds at a frame rate of 30 fps).

  In step S404, the user interface unit 210 uses the touch position coordinates, the touch direction, the touch distance, and the touch speed for the latest predetermined number of frames (for example, 10 frames) as touch input information 241 (information related to touch input). Each time it is stored in the storage unit 104. Touch input information 241 in frames prior to the latest predetermined number of frames is sequentially deleted from the storage unit 104.

  In step S405, the user interface unit 210 determines the type of touch input (eg, tap, flick, swipe operation) based on the latest predetermined number of frames of touch input information stored in the storage unit 104. The type of touch input is further stored in the storage unit 104 as touch input information 241. When the touch input information 241 corresponding to the number of valid frames for determining the touch input type does not exist, the touch input type is not determined.

  The user interface unit 210 may further specify the flick and swipe directions and store them in the storage unit 104 as touch input information 241. For example, the direction of the flick may be specified based on the touch direction of the latest frame in all the frames used for the determination of the flick operation, or may be specified based on the touch direction of the oldest frame. . Further, the flick direction may be specified based on the average of the touch directions in all the frames used for the determination of the flick operation.

  The user interface unit 210 may further specify a strong flick and a weak flick and store the strength / weakness of the flick in the storage unit 104 as touch input information 241. For example, the strength / weakness of the flick is specified based on the maximum touch distance in all frames used for the determination of the flick operation. The determination method of the flick operation will be described in detail in the description related to FIGS.

  FIG. 5A and FIG. 5B show a storage example when the touch position coordinates acquired by the user interface unit 210 are stored. Through the touch operation, a predetermined number of pieces of touch position information are stored in the array table fp in the storage unit 104 for each predetermined frame rate (for example, 30 fps). The initial position coordinates are stored in the table for each touch operation. The touch position information may be acquired as xy position coordinates of the touch area on the touch display 110. The xy position coordinates are adjusted so that, for example, the center of the touch area is the origin (0, 0), the upper end in the vertical direction is +1.0, and the lower end in the vertical direction is −1.0. Based on the touch position information, a tap, flick, or swipe operation is determined in S405.

  In the storage example of FIG. 5A, as the array table fp, a storage area for storing an arbitrary number (for example, 11 pieces) of touch position information for each frame rate from fp [0] to fp [10] is provided. In this specification, the term “touch-on” refers to a state in which the user touches the touch display 110 with an object such as a finger, and the term “touch now” refers to a state in which the user contacts with an object such as a finger while changing the position. The state of maintaining contact, the term “touch-off”, respectively refers to the state of subsequently releasing the object.

  In the first touch-on state, the position coordinates (x0, y0) when touched on the touch area are stored in fp [0]. In the touch-on state, fp [1] to fp [10] are still null (empty) values, but touch position coordinates are sequentially stored for each frame rate as the touch now state progresses. For example, in the touch now state 1, five position coordinates are sequentially stored from fp [1] to fp [5], and in the touch now state 2, five position coordinates are sequentially stored from fp [6] to fp [10]. Stored. Since the array table fp stores only 11 data, old data is sequentially deleted as soon as the capacity becomes full. Note that touch-on coordinate information (x0, y0) is separately stored as initial position coordinates so that the touch direction can always be detected. It is preferable that the initial position coordinates are not deleted through the slide operation until the touch-off state is reached.

  From the touch now state 2 to the next touch-off determination until the next touch-off determination, the position coordinate data for each frame rate is sequentially overwritten again from fp [0], and the old position coordinate data is sequentially deleted. . The touch-off determination is performed when a position value is not physically acquired and a null value is stored. In FIG. 5A, at least fp [5] has been overwritten and updated with the null value, so the touch-off determination is performed. If it is determined as touch-off, the acquisition of touch position information for a series of slide operations is completed. In the touch-off determination, when the touch position information cannot be acquired only once (one null value), but cannot be continuously acquired over a plurality of frame rate units (the null value is continuously two or more), Determination logic may be configured to determine touch-off. The reason for this configuration is that it is sufficiently assumed that the finger is separated from the touch display for a moment when the touch operation is complicated.

  FIG. 5B shows the result of the touch-off determination shown in FIG. 5A. (1) When the touch-off determination is made and then the touch-on state is entered again. An example of storing two patterns in the case of In both (1) and (2), null values are stored in fp [5] and fp [6] instead of (x16, y16) and (x17, y17). When the next touch position coordinate (x18, y18) is received, the (x18, y18) is stored in fp [7]. Thereafter, the position coordinates are sequentially stored from fp [8] for each frame rate (arrow). On the other hand, in the case of (1), the initial position coordinates are newly overwritten and updated with (x18, y18), whereas in the case of (2), the initial position coordinates are maintained as (x0, y0). In addition to (2), it is preferable that the arrangement table fp is not initialized even after the touch-off determination is made in (1). That is, in order to make the most recent touch position information (x14, y14) and (x15, y15) in the previous slide operation usable in the advance input process described later, these pieces of information are maintained. Is preferred.

  FIG. 6 shows an example of touch input information 241 stored in the storage unit 104. The touch input information 241 includes information related to touch input from fp [0] to fp [3]. Touch position coordinates of touch input for each frame, touch operation information (touch direction, touch distance, touch speed) between frames, operation determination information (determined touch input type, touch input type is flick, swipe input In the case, the direction and information on strength / weakness when the touch input type is a flick operation) are included.

  The touch position coordinates in the frame fp [0] are initial position coordinates. In the frame fp [0], there are no touch position coordinates of two or more immediately adjacent frames, so that the touch operation information and the operation input determination information are not stored in the storage unit 104. When the touch distance (touch speed in the frame) of fp [0] is not equal to or greater than the threshold value TH, it is determined that the flick operation is not established, and the swipe process is determined in the frame fp [1]. The swipe direction is obtained, for example, from the initial position coordinate to the current (fp [1]) touch position coordinate. When the touch distance (touch speed in the frame) of fp [2] is equal to or greater than the threshold value TH, it is determined that the flick operation has been established in frame fp [3]. The flick direction is obtained, for example, by the touch direction of the frame having the fastest touch speed among the touch operation information used for the flick determination. In the frame fp [3], no touch input is detected, and the touch position coordinates are overwritten and updated with a null value.

  FIG. 7 is a flowchart showing an operation example of the character control unit 220. In the present embodiment, the character control unit 220 controls the movement of the operation target character existing in the soccer game space.

  The operation target character is specified by, for example, a user tap operation performed on one character among a plurality of characters existing in the game space. When the character is associated with the moving object, for example, when receiving and keeping the moving object, the character can control the moving object.

  First, in step S <b> 701, when the character is not associated with the moving body, the bullet firing condition determining unit 221 determines whether the positional relationship between the moving body and the character satisfies a predetermined condition. In the present embodiment, for example, when the character does not keep the moving object, it is determined whether the distance between the moving object and the character is equal to or less than a certain value (for example, 1 m or less in the game space). The distance between the moving object and the character is calculated based on the position of the moving object specified by the xyz space coordinates in the three-dimensional game space and the position of the operation target character specified by the xy plane coordinates in the three-dimensional game space. .

  If it is determined that the relationship between the moving object and the character satisfies the predetermined condition, the process proceeds to step S702. On the other hand, if it is determined in step S701 that the relationship between the moving object and the character does not satisfy the predetermined condition, the process returns to step S701.

In step S702, the UI reference unit 222 refers to the touch input information 241 stored in the user interface unit 210 (“Yes” in step S701).
In step S703, the input determination unit 223 refers to previous touch input information (hereinafter referred to as previous touch input information) stored before the moving object and the character are associated with each other, and determines whether there is a previous touch input. judge. If there is a previous touch input in step S703, the process proceeds to step S704.

  In step S704, the input determination unit 223 determines whether the preceding touch input information includes the first input. The first input is an operation for causing the character to execute the first action, for example, a flick operation or a tap operation. The preceding touch input information may further include information for specifying the touch direction and information for specifying the touch distance. If the preceding touch input information includes the first input in step S704, the process proceeds to step S705.

In step S705, the input determination unit 223 specifies the touch direction of the preceding touch input based on the information specifying the touch direction of the preceding touch input information.
In step S706, the character motion control unit 224 causes the character when receiving the moving body to execute the first motion (for example, volley or heading motion) based on the touch input information 241. When there is a preceding input, the touch input information 241 is the preceding touch input information stored before the moving object is associated with the character.

  Specifically, when the touch input type is flick or tap, the character motion control unit 224 obtains the height of the moving body relative to the operation target character when receiving the moving body. When the character receives the moving object, the character action control unit 224 associates the character with the moving object. Then, the character action control unit 224 causes the operation target character to execute the first action based on the height of the moving object with respect to the operation target character when receiving the moving object. The image generation unit 230 generates a game image including an operation target character that performs a volley or a heading action and a moving object.

  The character has information about height. For example, the height of the moving body relative to the character is about the height of the character's feet (0 to 0.5 times the height), the body is about 0.5 to 0.9 times the height, and the height is about ( Height of 0.9 to 1.05 times the height), slightly higher than the height (1.05 to 1.2 times the height), considerably higher than the height (1.2 times the height) It is divided into five stages. Then, when the height of the moving body with respect to the character is about the height of the foot, the character is caused to perform a volley operation. When the height of the moving body is about the height of the torso of the character to be operated, the character is caused to perform a trapping action and then to perform a volleying action. Further, when the height of the moving body is slightly higher than the height of the character and about the height, the character is caused to perform a heading operation. As described above, the mode of the first action is specified based on the position of the moving body with respect to the character.

  In step S707, the moving body control unit 225 controls the moving direction of the moving body based on the information specifying the touch direction of the touch input information 241. Specifically, when the touch input type is flick, the moving body control unit 225 controls the moving body in the direction of the game space corresponding to the flick direction. Furthermore, the moving body control unit 225 may change the trajectory and moving distance of the moving body based on the touch distance (flick strength / weakness). For example, in the case of a strong flick, a high trajectory (flyball, liner ball) is used, and in the case of a weak flick, a low trajectory (goro) is selected.

  When the touch input type is tap, the moving body control unit 225 controls the moving body so that the moving body moves from the plane coordinates of the game space where the moving body is currently located toward the tap coordinates on the display unit 112. To do. Note that the tap coordinates on the display unit 112 may be converted into a position in the game space, and the moving body may be controlled toward the converted position in the game space.

  Furthermore, in step S707, the moving body control unit 225 may identify the trajectory of the moving body that moves in the moving direction based on the touch distance. And the image generation part 230 produces | generates the game image containing the controlled mobile body.

  On the other hand, if it is determined in step S703 that there is no preceding input with reference to the preceding touch input information stored before the moving object and the character are associated with each other, the process proceeds to step S708. If the preceding touch input information does not include the first input in step S704, the process proceeds to step S708.

  In step S <b> 708, when the character motion control unit 224 receives a moving object that moves, the character associates the character with the moving object. Then, the character action control unit 224 causes the operation target character to execute a predetermined second action different from the first action, for example, an action for trapping a moving body. Since there is no preceding input, the operation of the operation target character is not controlled based on the touch input information 241. Then, the image generation unit 230 generates a game image including the operation target character that performs the trapping action.

In step S709, the UI reference unit 222 refers to the touch input information 241 for a predetermined period (for example, 0.4 seconds) after the operation target character starts the second action.
In step S710, the input determination unit 223 determines whether there is a subsequent touch input based on the touch input information 241 within a predetermined period.

  In step S711, the input determination unit 223 determines whether the subsequent touch input information includes the first input. If subsequent touch input information including the first input is stored in the storage unit 104 in step S711, the second action of the operation target character is stopped, and the process proceeds to step S706. In this case, the touch input information 241 used in step S706 is information stored after the moving object is associated with the character.

  On the other hand, when there is no subsequent touch input (“No” in Step S710) and when the subsequent touch input information does not include the first input (“No” in Step S711), the character motion control unit 224 The operation target character is caused to continue the second action (step S712).

  In an actual soccer game, the player predicts where the ball falls based on the trajectory of the moving ball. Based on such prediction, the player proceeds with the play while immediately determining the next action to be performed. In the present embodiment, the action to be performed by the operation target character is determined based on information before the moving body is associated with the character, that is, before the character enters a state where the character can operate the moving body. Therefore, according to the present technology, it is possible to develop a more interesting game that matches the situation played in an actual soccer game. Further, according to the present technology, the user can instruct an action on the operation target character without strictly timing when the character receives the moving body. Therefore, a game with higher operability is developed.

  FIG. 8 is a table showing the relationship between the character control unit 220 according to an embodiment of the present technology, the touch input information 241 referred to by the character control unit, and the actions to be performed by the character. As shown in FIG. 8, the character control unit 220 determines whether the character is based on the character state (normal state, falling state) or the moving body state (whether the moving body is associated with the operation target character). The action to be performed can be determined. The state of the character in the predetermined frame fp is associated with the touch input type, touch direction, touch distance, and touch speed in the predetermined frame fp of the touch input information 241 to be referred to.

  The character state is specified based on information from the game program 250 being executed by the processing unit 102. The normal state is a state in which the character can be controlled based on the touch input information 241. In the fall state, the character is not controlled based on the touch input information 241 but is controlled by a predetermined action (an action to get up after falling). That is, the character control unit 220 refers to the touch input information 241 in the normal state, but does not refer to it in the fall state. By not referring to the touch input information 241 in the fall state, it is possible to prevent an unnatural motion such as the operation target character from running by a user input in the fall state. The state of the moving object is specified based on information from the game program 250 being executed by the processing unit 102.

  When the moving body is associated with the character, the movement of the character is controlled based on the touch input information 241 stored in the storage unit 104. For example, in FIG. 8, when the character control unit 220 corresponds to the frames fp [a] to fp [c], the information of the frames fp [a] to fp [c] of the touch input information 241 is referred to. On the other hand, the character control unit 220 is stored in the storage unit 104 when the character is in a normal state and the positional relationship between the moving object and the character satisfies a predetermined condition and the moving object is not associated with the character. Based on the touch input information 241, the movement of the associated character is controlled. For example, in FIG. 8, when the character control unit 220 corresponds to the frames fp [e] and fp [f], information on the frames fp [em] and fp [fm] of the touch input information 241, that is, the preceding Based on the touch input information, the movement of the character is controlled.

  Also, as shown in FIG. 8, even if the same touch input information 241 is referred to, the action to be performed by the character differs depending on whether or not the moving object is associated with the character. For example, when the character control unit corresponds to fp [a], the moving object is not associated with the character. At this time, the touch input type is identified as a swipe by referring to the frame fp “a” of the touch input information 241. The character is controlled to run based on the swipe direction and the swipe distance that exist in the frame fp “a” of the touch input information 241. On the other hand, when the character control unit corresponds to fp [b], the moving object is associated with the character. The touch input type is identified as a swipe by referring to the frame fp [b] of the touch input information 241. The character is controlled to dribble the moving body based on the swipe direction and the swipe distance existing in the frame fp “b” of the touch input information 241.

  FIG. 9 illustrates a flow of touch operation determination processing (S405) by the user interface unit 210. FIG. 10 illustrates a flick operation information graph. The horizontal axis of the graph indicates the frame F in a predetermined frame rate unit, and the vertical axis indicates the slide distance (swipe distance or flick distance). The touch-on state is detected in the first frame F [1], and the slide (swipe) distance is plotted as the touch now state up to the (n-1) th frame F [n-1]. Since the touch position information is not specified in the nth frame F [n], the slide distance cannot be calculated (N / A). As a result, the distance touch-off is detected.

  In response to the determination of the flick operation information in at least one immediately preceding frame, it is determined whether the slide distance in the flick operation information is greater than or equal to the threshold value TH1 (S901). Specifically, it is determined whether the slide (flick) distance plotted in the immediately preceding n-1 frame F [n-1] or the immediately preceding n-2 frame F [n-2] is greater than or equal to the threshold value TH1. Is done. In the case of “Yes”, it is determined that the flick operation has been established, and the operation on the object is executed through the subsequent processing. On the other hand, in the case of “No”, it is determined that the flick operation is not established, and the operation on the object is not executed, and the process ends with the swipe process. When two flick distances of F [n−1] and F [n−2] are used, it is preferable to determine whether the flick operation is established when both are equal to or greater than the threshold value TH1. That is, even if only the flick distance for one frame of F [n−1] is greater than or equal to the threshold value TH1, the establishment of the flick operation is not determined. The plurality of immediately preceding frames used for the determination may be any number up to 2 and up to a number that can be used (10 in the example of FIGS. 5A and 5B). The reason for using a plurality of immediately preceding frames is to distinguish them from tap operations in which only the operation information of only the immediately preceding frame is determined. Note that not only the flick distance but also the flick direction may be determined using the frame used in the above determination. The direction in the latest frame may be determined as the flick direction, and when a plurality of frames are used for determination, the direction of the oldest frame may be determined as the flick direction. In addition, the average direction of each frame may be calculated and determined as the flick direction.

  If it is determined in step S901 that the flick operation is established, the flick operation type is further determined based on the flick distance. The flick operation type includes a “strong” flick operation and a “weak” flick operation. That is, it is determined whether the flick distance is greater than or equal to a further threshold value T2 (> T1) (S902). If “yes”, the flick operation type is set to “strong” flick operation (S903), and if “no”, the flick operation type is set to “weak” flick operation (S904). When the flick distances of a plurality of consecutive frames are used, it is preferable that the maximum value among them is compared with the threshold value T2. That is, in FIG. 9, the flick distance of F [n−1] is the maximum value and is greater than TH2, and therefore, the flick operation type is set to “strong” flick operation. The flick operation type is associated with the operation to be performed.

  As mentioned above, although embodiment of this technique was described, this technique is not limited to the said embodiment. Those skilled in the art will appreciate that various modifications of the embodiments can be made without departing from the spirit and scope of the invention as set forth in the appended claims.

DESCRIPTION OF SYMBOLS 100 ... Computer, 102 ... Processing part, 104 ... Memory | storage part, 110 ... Touch display, 112 ... Display part, 114 ... Contact detection part, 210 ... User interface part, 220 ... Character control part, 230 ... Image generation part, 240 ... Game information, 241 ... Touch input information, 250 ... Game program, 251 ... UI program, 252 ... Character control program

Claims (10)

Displaying a moving object and an image including a character operable by a user on a touch display;
Detecting touch input to the touch display;
Identifying touch input information based on the touch input;
Storing the touch input information in a memory;
Determining whether a positional relationship between the moving body and the character satisfies a predetermined condition when the moving body is not associated with the character;
Determining whether the preceding touch input information includes a first input by referring to the preceding touch input information stored before the moving body is associated with the character when the predetermined condition is satisfied;
Causing the character to perform a first action based on the preceding touch input information when the preceding touch input information includes the first input. When the preceding touch input information includes the first input and information for specifying a touch direction,
The method according to claim 1, comprising controlling a moving direction of the moving body based on information specifying the touch direction. The preceding touch input information further includes information specifying a touch distance;
The method according to claim 2, wherein a trajectory of the moving body toward the moving direction is specified based on the touch distance.   The method according to claim 1, wherein the predetermined condition includes that a distance between the moving body and the character is equal to or less than a predetermined value.   The method according to claim 1, wherein the mode of the first action is specified based on a position of the moving body with respect to the character. Causing the character to execute a second action different from the first action when the preceding touch input information does not include the first input;
When subsequent touch input information including a second input is stored in a memory within a predetermined period after the character starts the second action, the character is transmitted to the character based on the subsequent touch input information. The method according to claim 1, further comprising: stopping the second operation and executing the first operation.   The program for making a computer perform the method of any one of Claims 1-6. A program executed by a processor,
A user interface program for detecting touch input to the touch display and storing information on the touch input corresponding to a predetermined number of frames in a memory;
Character control for controlling the action of the character displayed on the touch display based on the information on the touch input when a predetermined condition is satisfied after the information on the touch input is stored in the memory. A program comprising: Information about the touch input is:
Touch position coordinates of the touch input for each frame;
Touch direction between frames, touch distance, and touch speed,
Touch input type,
If the touch input type is flick or swipe input, their direction,
The program according to claim 8, wherein when the touch input type is a flick operation, part or all of the information on the length / shortness is included. The program according to claim 8, wherein the predetermined condition is defined based on a positional relationship between the character displayed on the touch display and a moving object.