JPWO2015093108A1 - CAPTURE CONTROL DEVICE, CAPTURE CONTROL METHOD, PROGRAM, AND INFORMATION STORAGE MEDIUM - Google Patents

Abstract

Provided are a capture control device, a capture control method, a program, and an information storage medium that can accurately capture a play image at a timing according to an event that occurs during game play. In response to detection of an event that occurs during game play, the capture timing specifying unit (32) generates timing relationship data that indicates the relationship between the occurrence timing of the event and the capture timing of the play image indicating the play content of the game. Based on this, the capture timing corresponding to the detection is specified. The capture control unit (34) performs control so that a play image at the specified capture timing is captured.

Description

  The present invention relates to a capture control device, a capture control method, a program, and an information storage medium.

  There is a technique for capturing a play image indicating the play content of a game. As an example of such a technique, Patent Document 1 discloses a technique in which an image of a game screen is captured when a predetermined screen shot operation is performed during execution of a game program.

US Patent Application Publication No. 2009/0118008

  A user who plays a game may want to capture a timing at which an event occurs during play of the game or a play image before or after a predetermined time. However, in the technique described in Patent Document 1, it is necessary to perform a screen shot operation in order to capture a play image, and it is possible to accurately capture a play image at a timing according to an event that occurs during game play. There wasn't.

  The present invention has been made in view of the above problems, and one of its purposes is a capture control device capable of accurately capturing a play image at a timing according to an event that occurs during game play, and capture A control method, a program, and an information storage medium are provided.

  In order to solve the above-described problem, the capture control device according to the present invention, in response to detection of an event that occurs during game play, capture timing of the event and capture timing of a play image indicating the play content of the game, A capture timing identifying unit that identifies the capture timing according to the detection based on timing relationship data indicating the relationship, and a capture control unit that controls the play image at the identified capture timing to be captured, It is characterized by including.

  Further, the capture control method according to the present invention provides a timing relationship indicating a relationship between an occurrence timing of the event and a capture timing of a play image indicating the play content of the game in response to detection of an event occurring during the game play. The step of specifying the capture timing according to the detection based on the data and the step of controlling the play image at the specified capture timing to be captured are included.

  Further, the program according to the present invention includes timing relationship data indicating a relationship between an occurrence timing of the event and a capture timing of a play image indicating the play content of the game in response to detection of an event occurring during the game play. Based on this, the computer is caused to execute a procedure for specifying the capture timing according to the occurrence timing of the detected event and a procedure for controlling the play image at the specified capture timing to be captured. .

  Further, the information storage medium according to the present invention provides a timing relationship indicating a relationship between an occurrence timing of the event and a capture timing of a play image indicating the play content of the game in response to detection of an event occurring during the game play. A procedure for causing the computer to execute a procedure for specifying the capture timing according to the occurrence timing of the detected event based on data and a procedure for controlling the play image at the specified capture timing to be captured. Is a computer-readable information storage medium storing the program.

  In the present invention, control is performed so that a play image at a capture timing specified based on timing relationship data is captured in response to detection of an event that occurs during game play. Therefore, according to this invention, the play image of the timing according to the event which generate | occur | produces during the play of a game can be captured exactly.

  In one aspect of the present invention, the capture timing specifying unit performs the detection based on the timing relationship data indicating a relationship between an occurrence timing of the event and a start timing of capturing a play image indicating the play content of the game. The corresponding start timing is specified, and the capture control unit performs control so that the play image from the specified start timing is captured.

  In this aspect, the start timing may be a timing before the generation timing.

  Moreover, in one aspect of the present invention, the capture timing specifying unit is based on the timing relationship data indicating a relationship between an occurrence timing of the event and an end timing of capture of a play image indicating the play content of the game. The end timing corresponding to the detection is specified, and the capture control unit performs control so that the play image up to the specified end timing is captured.

  Moreover, in one aspect of the present invention, it further includes a timing related data receiving unit that receives the timing related data from a user different from the user who plays the game, and the capture timing specifying unit includes the timing related data received Based on this, the capture timing corresponding to the detection is specified.

  In the aspect of the invention, the capture timing specifying unit may perform the detection based on the timing relationship data indicating a relationship between an occurrence timing of the event and a capture period of a play image indicating the play content of the game. A capture period corresponding to the detected capture period, wherein the capture control unit identifies a plurality of identified capture periods when at least a part of the capture period according to the detection identified for each of a plurality of different event detections overlaps. Control is performed so that the play image from the earliest timing in the start of the capture period to the latest timing in the end of the plurality of capture periods is captured as one moving image.

It is a figure which shows an example of the whole structure of the game system which concerns on one Embodiment of this invention. It is a figure which shows an example of capture condition data. It is a figure which shows an example of a list display screen. It is a figure which shows an example of a registration screen. It is a figure which shows an example of an edit screen. It is a figure which shows an example of an edit screen. It is explanatory drawing which shows typically an example of the relationship between the generation timing of each of several events, and the capture timing of a play image. It is explanatory drawing which shows typically an example of the relationship between the generation timing of each of several events, and the capture timing of a play image. It is explanatory drawing which shows typically an example of the relationship between the generation timing of each of several events, and the capture timing of a play image. It is explanatory drawing which shows typically an example of the relationship between the generation timing of each of several events, and the capture timing of a play image. It is explanatory drawing which shows typically an example of the relationship between the generation timing of each of several events, and the capture timing of a play image. It is a figure which shows an example of a capture list screen. It is a functional block diagram which shows an example of the function implement | achieved by the client which concerns on one Embodiment of this invention.

  Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a diagram showing an example of the overall configuration of a game system 1 according to an embodiment of the present invention. As shown in FIG. 1, a game system 1 according to the present embodiment includes a server 10 and clients 12 (12-1 to 12-n), each of which is configured with a computer at the center. The server 10 and the client 12 are connected to a computer network 14 such as the Internet. The server 10 and the client 12 can communicate with each other.

  The server 10 is a server computer that relays data exchange between the clients 12. As illustrated in FIG. 1, the server 10 includes, for example, a control unit 10a, a storage unit 10b, and a communication unit 10c. The control unit 10a is a program control device such as a CPU, for example, and executes various types of information processing according to programs stored in the storage unit 10b. The storage unit 10b is, for example, a storage element such as a ROM or a RAM, a hard disk drive, or the like. The communication unit 10c is a communication interface such as a network board for exchanging data with the client 12 via the computer network 14, for example. The server 10 transmits / receives information to / from the client 12 via the communication unit 10c.

  The client 12 is a computer used by a user, such as a personal computer, a game console, a television receiver, a portable game device, or a portable information terminal. In the present embodiment, a game program played by the user is installed in the client 12. Then, the user of the client 12 plays the game as a player of the game. The client 12 includes, for example, a control unit 12a, a storage unit 12b, a communication unit 12c, an output unit 12d, and an input unit 12e. The control unit 12a is a program control device such as a CPU, for example, and executes various types of information processing according to programs stored in the storage unit 12b. The control unit 12a according to the present embodiment also includes a GPU (Graphics Processing Unit) that draws an image in a frame buffer based on graphics commands and data supplied from the CPU. The storage unit 12b is, for example, a storage element such as a ROM or a RAM, a hard disk drive, or the like. The storage unit 12b stores a program executed by the control unit 12a. In the storage unit 12b according to the present embodiment, a frame buffer area in which an image is rendered by the GPU is secured. The communication unit 12c is a communication interface for exchanging data with the server 10 via the computer network 14, for example. The client 12 transmits / receives information to / from the server 10 and other clients 12 via the communication unit 12c. The output unit 12d is, for example, a display unit such as a display that displays and outputs information according to an instruction input from the control unit 12a, and an audio output unit such as a speaker that outputs audio. The input unit 12e is, for example, a game controller, a touch pad, a mouse, a keyboard, a microphone, a camera, or the like that outputs the content of an operation performed by the user to the control unit 12a.

  In this embodiment, while playing a game in which the user of the client 12 participates as a player, a play image indicating the play content of the game is displayed on the display of the client 12 at a predetermined frame rate. A copy of the play image displayed on the display, that is, a copy of the play image drawn in the frame buffer is provided in a ring buffer area provided in the storage unit of the client 12 and capable of storing a maximum of 15 minutes of moving images. Written sequentially.

  In the present embodiment, when an event set in the capture condition data illustrated in FIG. 2 occurs during play of the game, a moving image composed of a play image or a series of play images corresponding to the event is generated. Captured. In the present embodiment, a moving image composed of a play image or a series of play images is captured even when a capture operation is performed by the user. When a play image is captured, the captured play image is stored in the storage unit 12b as a captured image. When a moving image is captured, the moving image is encoded and stored in the storage unit 12b as a captured moving image. The captured moving image is composed of a plurality of frame images. The frame rate when a series of play images are displayed on the display and the frame rate of the captured moving image stored in the storage unit 12b may be the same or different. The captured image or captured moving image stored in the storage unit 12b of the client 12 in this way can be uploaded to various sites on the Internet such as an image posting site. The captured image or captured moving image uploaded in this way is made public.

  The capture condition data is data for managing an event serving as a condition for capturing a play image, and a relationship between the occurrence timing of the event and the capture timing of the play image. The capture condition data is stored in the storage unit 12b of the client 12.

  FIG. 2 is a diagram illustrating an example of capture condition data stored in the storage unit of the client 12 used by the player A. As shown in FIG. 2, the capture condition data includes a capture condition ID, a set player ID, editability data, occurrence status data, title data, event data, captured image type data, and timing relationship data.

  The capture condition ID is identification information of capture condition data.

  The set player ID is identification information of the player who set the capture condition data.

  The editability data is data indicating whether the capture condition data can be updated or deleted by the user of the client 12 in which the capture condition data is stored. If it is possible, “possible” is set as the value of the editability data, and “impossible” is set as the value of the editability data if it is not possible.

  The occurrence status data is data indicating whether or not an event set in the capture condition data has occurred. If it has occurred, “occurred” is set as the value of the occurrence status data, and “not generated” is set as the value of the occurrence status data if it has not occurred.

  The title data is data indicating the title of the game for which the play image is captured.

  The event data is data indicating an event set in the capture condition data. In the present embodiment, the event data indicates an event that occurs in the title game indicated by the title data associated with the event data in the capture condition data.

  The captured image type data is data indicating the type of image to be captured. In the present embodiment, “moving image” or “still image” is set as the value of the captured image type data. When the value of the captured image type data is “moving image”, the captured moving image that is a moving image is stored in the storage unit 12b, and when it is “still image”, the captured image that is a still image is stored in the storage unit 12b. Is done.

  The timing relationship data is data indicating the relationship between the occurrence timing of the event indicated by the event data included in the capture condition data and the capture timing of the play image. The timing relation data indicates, for example, the difference between the occurrence timing of the event indicated by the event data included in the capture condition data and the capture timing of the play image.

  For example, for the capture condition data whose capture condition ID is “0001”, the timing related data indicates that the play image capture start timing is three minutes before the event occurrence timing. Regarding the capture condition data, the timing related data indicates that 3 minutes after the timing of the event is the capture end timing of the play image.

  For example, for capture condition data with a capture condition ID “0002”, the timing related data indicates that the timing at which the event occurred is the start timing of capture of the play image. As for the capture condition data, the timing related data indicates that the play image capture end timing is five minutes after the event occurrence timing.

  For example, for capture condition data with a capture condition ID “0003”, the timing related data indicates that the play image capture start timing is five minutes before the event occurrence timing. As for the capture condition data, the timing related data indicates that the play image capture end timing is five minutes after the event occurrence timing.

  For example, for capture condition data with a capture condition ID “0004”, the timing related data indicates that the timing at which the event occurred is the capture timing of the play image.

  As in the example of the capture condition data whose capture condition ID is “0001”, “0002”, or “0003”, the timing relationship data includes the event occurrence timing and the play image capture start timing or end timing. It may indicate a relationship. For example, the timing relation data may indicate the difference between the event occurrence timing and the play image capture start timing, or the difference between the event occurrence timing and the play image capture end timing. In these cases, the captured moving image is stored in the storage unit 12b.

  Further, as in the example of the capture condition data whose capture condition ID is “0001” or “0003”, the play image capture start timing may be earlier than the event occurrence timing. . In the present embodiment, as described above, a copy of the play image is written in the ring buffer area provided in the storage unit 12b of the client 12. Therefore, a copy of the play image displayed before the occurrence of the event stored in the ring buffer area can be stored in the storage unit 12b of the client 12 as a captured image. In this way, in the present embodiment, a play image can be captured from a timing before the event occurrence timing.

  Hereinafter, display and setting of values set in the capture condition data will be further described. FIG. 3 is a diagram illustrating an example of a list display screen displayed on the display of the client 12 used by the player A. A value set in the capture condition data is displayed on the list display screen. The list display screen is displayed on the display when the user performs a predetermined operation while the system screen is displayed or during game play. In this embodiment, a list display screen generated based on the capture condition data stored in the storage unit 12 b of the client 12 is displayed on the display of the client 12.

  On the list display screen, the capture condition information CCI associated with the capture condition data is arranged vertically. The user can change the arrangement order of the capture condition information CCI by operating a pull-down menu arranged on the list display screen. The capture condition information CCI illustrated in FIG. 3 is associated with capture condition data having capture condition IDs “0001”, “0002”, “0003”, and “0004” in order from the top. The capture condition information CCI includes a player icon PI, a title character string TS, and an event character string IS. The player icon PI is an icon associated with the set player ID included in the capture condition data. In FIG. 3, a player icon PIa associated with the player A and a player icon PIb associated with the player B are arranged. The title character string TS is a character string representing the title indicated by the title data included in the capture condition data. The event character string IS is a character string representing an event indicated by event data included in the capture condition data.

  In the present embodiment, the display mode of elements included in the capture condition information CCI, here, for example, the display mode of the player icon PI, the title character string TS, and the event character string IS is the occurrence status included in the capture condition data. It depends on the data value. Specifically, for example, the brightness of the element associated with the capture condition data whose occurrence status data value is “not generated” is the element associated with the capture condition data whose occurrence status data value is “occurred” It is higher than the brightness.

  A lock icon LI is arranged in the capture condition information CCI associated with the capture condition data whose editability data value is “impossible”.

  A newly created link NL is arranged on the list display screen. When the user performs an operation of selecting the newly created link NL, a registration screen shown in FIG. 4 is displayed on the display. In the registration screen shown in FIG. 4, the user can set the title data value, event data value, captured image type data value, and timing related data value included in the capture condition data by operating a pull-down menu. It has become.

  Here, it is assumed that the user performs an operation of selecting the registration button RB arranged on the registration screen. Then, new capture condition data including a value of title data, a value of event data, a value of captured image type data, and a value of timing related data set on the registration screen is generated, and the storage unit 12b of the client 12 is created. Is remembered. In this embodiment, a unique value that does not overlap with any capture condition ID included in any capture condition data stored in the storage unit 12b of the client 12 is set as the capture condition ID included in the capture condition data. . Further, identification information of the user of the client 12 is set as the setting player ID included in the capture condition data. Also, “OK” is set as the value of the editability data included in the capture condition data. Then, “not generated” is set as the value of the occurrence status data included in the capture condition data.

  Also, assume that when the registration screen shown in FIG. 4 is displayed, the user performs an operation of selecting the upload button ULB arranged on the registration screen. Then, as described above, new capture condition data is generated and stored in the storage unit 12b of the client 12, and the capture condition data is transmitted to the server 10. The server 10 that has received the capture condition data reassigns the capture condition ID included in the capture condition data. Here, for example, the capture condition ID is reassigned to a unique value that does not overlap with any capture condition ID included in any capture condition data stored in the storage unit 10b of the server 10. Then, the server 10 stores the capture condition data in which the capture condition ID is reassigned in the storage unit 10b of the server 10.

  In this way, the capture condition data stored in the server 10 is transmitted to a client 12 other than the client 12 that is the transmission source of the capture condition data.

  In the present embodiment, an administrator of the server 10 can store capture condition data in the server 10. The capture condition data stored in the server 10 in this way is transmitted to the client 12 that can communicate with the server 10.

  The client 12 that has received the capture condition data from the server 10 reassigns the capture condition ID included in the capture condition data. Here, for example, the capture condition ID is reassigned to a unique value that does not overlap with the capture condition ID included in any capture condition data stored in the storage unit 12b of the client 12. Further, the value of the editability data included in the capture condition data is changed to “impossible”. Then, the client 12 stores the capture condition data in which the capture condition ID is reassigned in the storage unit 12b of the client. In this way, in the present embodiment, the capture condition data registered by the player different from the player who is the user of the client 12 and stored in the storage unit 12b of the client 12 is “ “Not possible” is set.

  Further, when the user performs an operation of selecting the cancel button CB arranged on the registration screen while the registration screen shown in FIG. 4 is displayed, the list display screen shown in FIG. 3 is displayed on the display. .

  In the present embodiment, the capture condition information CCI arranged on the list display screen is a link. Then, when the user performs an operation of selecting the capture condition information CCI, an edit screen of capture condition data associated with the capture condition information CCI illustrated in FIGS. 5 and 6 is displayed on the display.

  FIG. 5 is a diagram illustrating an example of an edit screen displayed on the display when the user performs an operation of selecting the second capture condition information CCI from the top on the list display screen illustrated in FIG. 3. On the editing screen, a player icon PI associated with the set player ID included in the capture condition data associated with the selected capture condition information CCI is arranged. In the example of FIG. 5, a player icon PIa is arranged. Here, when the user performs an operation of selecting the update button UB after changing the set value, the value of event data or the like included in the capture condition data stored in the storage unit 12b of the client 12 Is changed to the value set in the editing screen.

  Further, when the user performs an operation of selecting the delete button DB arranged on the edit screen while the edit screen shown in FIG. 5 is displayed, the capture stored in the storage unit 12b of the client 12 is performed. The condition data is deleted from the storage unit 12b. Further, when the user performs an operation of selecting the cancel button CB arranged on the editing screen while the editing screen shown in FIG. 5 is displayed, the list display screen shown in FIG. 3 is displayed on the display. .

  FIG. 6 is a diagram illustrating an example of an edit screen displayed on the display when the user performs an operation of selecting the fourth capture condition information CCI from the top on the list display screen illustrated in FIG. 3. Also on the editing screen, a player icon PI associated with the set player ID included in the capture condition data associated with the selected capture condition information CCI is arranged. In the example of FIG. 6, a player icon PIb is arranged. Further, a lock icon LI is arranged on the editing screen. In the present embodiment, the user cannot change the value of the capture condition data whose editability data value is “impossible”. For this reason, on the editing screen shown in FIG. 6, the player A cannot edit the capture condition data associated with the selected capture condition information CCI. Here, when the user performs an operation of selecting the OK button OB arranged on the editing screen, a list display screen shown in FIG. 3 is displayed on the display.

  In the present embodiment, it is assumed that an event indicated by the event data included in the capture condition data occurs during the play of the game having the title indicated by the title data included in the capture condition data. Then, the play image of the capture timing specified based on the occurrence timing of the event and the value of the timing relation data included in the capture condition data is captured. When the value of the occurrence status data included in the capture condition data stored in the storage unit 12b of the client 12 is “not generated”, it is updated to “occurred”. In the present embodiment, an image of the type indicated by the captured image type data included in the capture condition data, here, a still image or a moving image is captured. For example, it is assumed that the player A defeats the dragon on the map 1 while the game A is played. In this case, a moving image composed of a series of play images from 3 minutes before to 3 minutes after the occurrence timing of the dragon-defeating event is stored in the storage unit 12b of the client 12 used by the player A as a captured moving image. Will be. The capture is based on capture condition data whose capture condition ID is “0001”.

  Here, when the event indicated by the event data included in the capture condition data occurs, the play image is captured when the value of the occurrence status data included in the capture condition data is “not generated”. Also good. On the other hand, if the value of the occurrence status data included in the capture condition data is “generated”, the play image may not be captured. In this way, once the event indicated by the event data included in the capture condition data occurs, the play image is not captured. Note that for the capture condition data whose occurrence status data value is “occurred”, the occurrence status data value may be changed from “occurred” to “not occurred” in response to a request from the user. In this case, when the event indicated by the event data included in the capture condition data including the occurrence status data occurs, the play image is captured again. In this way, for example, when the user is dissatisfied with the captured image, the play image can be captured again.

  In addition, every time an event indicated by the event data included in the capture condition data occurs, regardless of whether the value of the occurrence state data included in the capture condition data is “not generated” or “occurred” A play image may be captured. Alternatively, the play image may be captured when the number of occurrences of the event indicated by the event data included in the capture condition data reaches a predetermined number.

  Thus, in this embodiment, if capture condition data is stored in the storage unit 12b, a play image is captured based on the capture condition data. Therefore, according to the present embodiment, it is possible to accurately capture a play image at a timing according to an event that occurs during game play.

  In this embodiment, the user can set the value of capture condition data, particularly the value of event data and the value of timing related data. Therefore, when an event occurs, the user can capture a play image that has a desired temporal relationship with the occurrence timing of the event.

  Further, in the present embodiment, it is possible to capture a moving image composed of a series of play images starting from the timing before the occurrence of an event as described above. Therefore, according to the occurrence of an event, the process leading to the occurrence of the event can be recorded as a captured moving image.

  In this embodiment, as described above, it is possible to capture a play image based on the relationship between the occurrence timing of an event set by another player and the capture timing of the play image. Therefore, according to this embodiment, it is possible to request another player to capture the play image that the player wants.

  In the present embodiment, a plurality of capture condition data is stored in the storage unit 12b of the client 12 as described above. Therefore, in some cases, at least a part of a period during which a play image is captured, which is specified in response to the occurrence of an event for a plurality of capture condition data, may overlap. Hereinafter, a period during which a play image is captured is referred to as a capture period. In this case, a play image from the earliest timing among the start times of the plurality of specified capture periods to the latest timing among the end times of the plurality of capture periods is captured as one capture moving image.

  For example, as shown in FIG. 7A, it is assumed that an event indicated by event data included in each of the two capture condition data occurs at the date and time t1. The capture period set in one capture condition data is from before P1 / 2 to after P1 / 2 of the event occurrence timing. It is assumed that the capture period set in the other capture condition data is from P2 / 2 before the event occurrence timing to after P2 / 2. Here, it is assumed that P1 <P2. In this case, a captured moving image composed of play images displayed in a period P from date / time t1−P2 / 2 to date / time t1 + P2 / 2 is stored.

  In this case, for example, as shown in FIG. 7B, it is assumed that the capture period set in one capture condition data is from the event occurrence timing to after P1. The capture period set in the other capture condition data is from the event occurrence timing to P2. In this case, a captured moving image composed of play images displayed in a period P from date / time t1 to date / time t1 + P2 is stored.

  The occurrence timing of two events may be different. For example, as shown in FIG. 7C, it is assumed that the events indicated by the event data included in the two capture condition data occur at the date and time t1 and the date and time t2, respectively. The capture period set in the capture condition data including the event data indicating the event that occurred at the date and time t1 is from before P1 / 2 to after P1 / 2 of the event occurrence timing. The capture period set in the capture condition data including event data indicating the event that occurred at the date and time t2 is from P2 / 2 before the event occurrence timing to after P2 / 2. Here, it is assumed that P1 <P2. In this case, a captured moving image composed of play images displayed in a period P from date / time t1−P1 / 2 to date / time t2 + P2 / 2 is stored.

  In this case, for example, as shown in FIG. 7D, it is assumed that the capture period set in the capture condition data including event data indicating the event that occurred at the date and time t1 is from the event occurrence timing to after P1. Further, it is assumed that the capture period set in the capture condition data indicating the event that occurred at the date and time t2 is from the event occurrence timing to P2. In this case, a captured moving image composed of play images displayed in a period P from date / time t1 to date / time t2 + P2 is stored.

  Similarly, as shown in FIG. 7E, for example, it is assumed that the capture period set in the capture condition data including event data indicating the event that occurred at the date and time t1 is from the event occurrence timing to after P1. Further, it is assumed that the capture period set in the capture condition data indicating the event that occurred at the date and time t2 is from before P2 / 2 to after P2 / 2 of the event occurrence timing. In this case, a captured moving image composed of a play image displayed in a period P from date / time t1 to date / time t2 + P2 / 2 is stored.

  In the present embodiment, the captured moving image or the captured image is stored in the storage unit 12b in association with the metadata. Here, the metadata includes, for example, a file name, a value of event data included in the capture condition data, a date and time indicating an event occurrence timing, and the like.

  Further, in the present embodiment, when one captured moving image associated with a plurality of events is stored as described above, metadata associated with each of the plurality of events is associated with the captured moving image. . In this case, each metadata includes the value of event data included in the associated capture condition data, and the date and time indicating the event occurrence timing. The metadata may further include data indicating the position in the capture moving image corresponding to the start and end of the capture period associated with the associated capture condition data. The position in the capture moving image is expressed by, for example, the frame number of the image constituting the capture moving image. In this way, in the present embodiment, even if one captured moving image associated with a plurality of generated events is stored, the portion associated with each event is cut from the captured moving image based on the metadata. It can be put out. As described above, when a play image is captured every time an event indicated by event data included in the capture condition data occurs, data indicating how many times the event has occurred is included in the metadata. It may be.

  Further, in response to a request received from the user, a capture moving image or a capture list screen that is a list of captured images as shown in FIG. 8 may be displayed. On the capture list screen illustrated in FIG. 8, four capture information CIs each associated with a capture moving image or a capture image are arranged. In this embodiment, when the user performs an operation of selecting the capture information CI, the captured moving image associated with the capture information CI is reproduced or the captured image associated with the capture information CI is displayed.

  In the capture information CI, for example, information related to the captured moving image or captured image such as the captured moving image or the file name of the captured image, the stage name where the event occurred, the capture reason, and the capture date and time are arranged. The capture information CI is generated based on the above-described metadata, for example. In the present embodiment, for example, the value of the event data included in the metadata is arranged on the capture list screen as a capture reason. Further, for example, the date and time indicating the occurrence timing of the above-described event included in the metadata is arranged on the capture list screen as the capture date and time. Further, as shown in FIG. 8, information indicating how many times an event has occurred may be arranged as a capture reason. In the example of FIG. 8, for capture based on the capture condition data, a character string indicating the capture reason is enclosed in parentheses. On the other hand, for the capture according to the user's capture operation, a character string “user photographed” is arranged as the capture reason.

  Hereinafter, setting of capture condition data and capture of a play image will be further described.

  FIG. 9 is a functional block diagram illustrating an example of functions implemented by the client 12 according to the present embodiment. Note that it is not necessary for the client 12 according to the present embodiment to realize all the functions illustrated in FIG. 9, and functions other than the functions illustrated in FIG. 9 may be realized.

  Functionally, the client 12 according to the present embodiment functionally includes, for example, a capture condition data storage unit 20, a capture condition data reception unit 22, a capture condition data management unit 24, a capture condition data transmission unit 26, a game process execution unit 28, and a detection. Section 30, a capture timing specifying section 32, a capture control section 34, a captured image storage section 36, and a capture notification section 38. The capture condition data storage unit 20 and the captured image storage unit 36 are mainly implemented by the storage unit 12b. The capture condition data receiving unit 22 is mainly implemented by the communication unit 12c. The capture condition data transmission unit 26 is mainly implemented by the communication unit 12c. The capture control unit 34 is mainly implemented by the control unit 12a and the storage unit 12b. The capture notification unit 38 is mainly implemented by the communication unit 12c and the output unit 12d. Other functions are mainly implemented by the control unit 12a.

  The above functions are implemented by executing a program installed in the client 12 that is a computer and including a command corresponding to the above functions by the control unit of the client 12. This program is supplied to the client 12 via a computer-readable information storage medium such as an optical disk, a magnetic disk, a magnetic tape, a magneto-optical disk, or a flash memory, or via a computer network such as the Internet.

  The capture condition data storage unit 20 stores the above-described capture condition data illustrated in FIG. In the present embodiment, the capture condition data stored in the capture condition data storage unit 20 of the client 12 is associated with the client 12. In this embodiment, the capture condition data stored in the capture condition data storage unit 20 by the client 12 is different from each other.

  The capture condition data receiving unit 22 receives capture condition data from a user different from the user who plays the game. In this embodiment, the capture condition data receiving unit 22 of the client 12 receives from the server 10 capture condition data registered in the server 10 by a user different from the user who uses the client 12 or an administrator of the server 10. . Note that the capture condition data reception unit 22 may inquire whether new capture condition data is registered in the storage unit 10b of the server 10 at predetermined time intervals, for example. In this case, the server 10 transmits the newly registered capture condition data to the client 12.

  The capture condition data management unit 24 causes the capture condition data storage unit 20 to store the capture condition data received by the capture condition data reception unit 22. In the present embodiment, the capture condition data management unit 24 generates capture condition data based on, for example, the input content on the registration screen illustrated in FIG. 4 and stores the capture condition data in the capture condition data storage unit 20. . When receiving the capture condition data from the server 10, the capture condition data management unit 24 stores the capture condition data in which the capture condition ID is reassigned as described above in the capture condition data storage unit 20. When the capture condition data update operation is performed, the capture condition data management unit 24 updates the capture condition data stored in the capture condition data storage unit 20. When the capture condition data deletion operation is performed, the capture condition data management unit 24 deletes the capture condition data stored in the capture condition data storage unit 20.

  The capture condition data transmission unit 26 transmits capture condition data to the server 10. In the present embodiment, for example, when the user performs an operation of selecting the upload button ULB arranged on the registration screen illustrated in FIG. 4, the capture condition data management unit 24 generates new capture condition data. The data is stored in the storage unit 12b of the client 12. Then, the capture condition data transmission unit 26 transmits the capture condition data to the server 10. The server 10 registers the capture condition data by causing the server 10 to store the capture condition data in which the capture condition ID is reassigned as described above. As described above, the registered capture condition data is received by the capture condition data receiving unit 22 of the client 12 different from the client 12 that is the transmission source of the capture condition data.

  Note that when the capture condition data is updated via the editing screen, the capture condition data transmission unit 26 may transmit the updated capture condition data to the server 10. Then, the capture condition data receiving unit 22 of the client 12 different from the client 12 that has transmitted the capture condition data may receive the capture condition data. When the capture condition data management unit 24 of the client 12 that has received the capture condition data updates the value of the capture condition data stored in the capture condition data storage unit 20 to the value of the received capture condition data. Good.

  Further, when the capture condition data is deleted via the editing screen, the capture condition data transmission unit 26 may transmit the capture condition ID of the deleted capture condition data to the server 10. Then, the capture condition data receiving unit 22 of the client 12 different from the client 12 that has transmitted the capture condition ID may receive the capture condition ID. Then, the capture condition data management unit 24 of the client 12 that has received the capture condition ID may delete the capture condition data including the capture condition ID stored in the capture condition data storage unit 20.

  The game process execution unit 28 executes a game program installed in the client 12. As described above, the game process execution unit 28 generates a play image at a predetermined frame rate and displays it on the display. In addition, the game process execution unit 28 writes a copy of the play image displayed as described above in the ring buffer area.

  The detection unit 30 detects an event that occurs during game play. In the present embodiment, the detection unit 30 detects an event that has occurred in the game as the game process execution unit 28 executes the game program. The detection unit 30 may detect the event by accepting that the event has occurred, which is notified by the game process execution unit 28 when the event occurs. The detection unit 30 may detect the event by confirming whether or not the event has occurred at a predetermined frame rate.

  The capture timing specifying unit 32 specifies the capture timing corresponding to the detection based on the timing relation data in response to the detection of the event by the detection unit 30. In the present embodiment, the capture timing specifying unit 32, for example, captures timing relationship data associated with event data indicating an event detected by the detection unit 30 in the capture condition data stored in the capture condition data storage unit 20. Identify. And the capture timing specific | specification part 32 specifies the capture timing according to the said detection based on the timing related data specified and the timing at which an event is detected. Note that the capture timing specifying unit 32 may specify the capture start timing and end timing of the play image according to the detection as described above. The capture timing specifying unit 32 may specify the capture timing corresponding to the detection based on timing relation data received from a user different from the user who plays the game. The capture timing specifying unit 32 may specify a capture period corresponding to the detection.

  The capture control unit 34 performs control so that the play image at the capture timing specified by the capture timing specifying unit 32 is captured. In the present embodiment, for example, the capture control unit 34 captures a play image displayed at the specified capture timing or a play image displayed at the specified capture timing and stores the captured image in the captured image storage unit 36. Here, as described above, when the value of the captured image type data included in the capture condition data is “moving image”, the captured moving image is stored, and when it is “still image”, the captured image is stored. Let In addition, the capture control unit 34 associates metadata with the captured moving image or the captured image as described above, and stores the captured image in the captured image storage unit 36. In addition, as illustrated in FIGS. 7A to 7E, at least a part of the capture periods corresponding to the detections specified for the detection of a plurality of different events may overlap. In this case, the capture control unit 34 captures a play image from the earliest timing among the start periods of the plurality of specified capture periods to the latest timing among the end periods of the plurality of capture periods as one moving image. You may control so that. Further, the capture control unit 34 may integrate the captured moving images for each of the plurality of capture periods in the above-described case.

  The captured image storage unit 36 stores the image captured by the capture control unit 34. In this embodiment, a capture moving image and a capture image associated with metadata are stored.

  The capture notification unit 38 displays that effect on the display when the play image is captured. In addition, when the play image is captured based on the capture condition data received from another user, the capture notification unit 38 may transmit that fact to the client 12 used by the other user. In this case, the capture notification unit 38 may transmit an e-mail describing that the play image has been captured to the e-mail address of the other user. Moreover, the application which can receive the notification that the play image was captured may be installed in the smart phone which the said other user owns. Then, when the play image is captured, the capture notification unit 38 may notify the other user that the play image has been captured via the network service to which the application is connected. In this case, the capture notification unit 38 may transmit the captured image or the captured moving image to the client 12 used by the other user. In the present embodiment, the capture notification unit 38 generates a capture list screen illustrated in FIG. 8 and displays it on the display.

  Also, when a captured image or captured moving image stored based on the capture condition data is uploaded to various sites such as an image posting site, the URL of the site is transmitted to the user who sets the value of the capture condition data May be.

  In addition, this invention is not limited to the above-mentioned embodiment.

  For example, the relationship between the event and the capture timing may be determined in advance. Specifically, for example, data in which event data and timing relation data are associated with each other may be stored in the capture condition data storage unit 20 in advance. Then, the capture condition data management unit 24 may generate capture condition data including event data indicating the event and timing relationship data associated with the event data in response to receiving the designation of the event. Good. The capture condition data management unit 24 may store the capture condition data in the capture condition data storage unit 20. In this way, the user captures the play image according to the preset relationship without designating the relationship between the event occurrence timing and the play image capture timing.

  Further, the captured moving image may be distributed live. For example, the captured moving image may not be stored in the storage unit 12b of the client 12, but may be uploaded to a site that provides a live streaming service after being buffered. The URL of the site may be transmitted to the client 12 of the user who has set the capture condition data.

  Moreover, the server 10 may be comprised from the some housing | casing. Further, the division of roles between the server 10 and the client 12 is not limited to the above. Further, the server 10 and the client 12 may be integrated.

  For example, the present embodiment may be applied to capture of a play image in a game program executed on the server side in which a play image is displayed via a browser installed on the client 12. For example, when a game program is executed on the server 10, the server 10 may detect an event that occurs during play of the game, specify a capture timing according to the detection, and capture a play image. . Alternatively, the server 10 may notify the client 12 of a play image capture instruction in association with the specified capture timing. Then, the client 12 may capture a play image in response to the capture instruction. In this case, the server 10 does not capture, but controls the play image to be captured at the specified capture timing.

  For example, the server 10 may notify the client 12 of an event that has been detected. Then, the client 12 may specify the capture timing corresponding to the detection and capture the play image.

  Further, for example, the capture condition data is a combination of parameters used by the system program installed in the client 12 and parameters used in the game to be played, in addition to those described above. Also good.

  Examples of parameters used by the system program include a user ID, a user's affiliation region, a user's gamer rank (trophy rank / gamer score), and a game title name possessed. Other examples of parameters managed in the system include play time of a specific game, shooting time (play image capture time), and the like.

  Examples of parameters used in a game to be played include the number of acquired trophies for a specific game, the number of killed opponents, the number of combos, the score, and the best time. Other examples of parameters managed in the game to be played include a map ID, a location ID, an enemy object ID, an item object ID, an event ID, and a trophy ID in the game. Other examples of parameters managed in the game being played include the number of acquired item objects in the game, the number of clears, the acquisition timing of the trophy, the activation time, the number of defeated attackers and the number of scores It is done. Other examples of parameters managed in the game to be played include fluctuations in transactions between the client 12 and the server 10, fluctuations in volume and number of speakers in voice chat, and the like.

  The specific character strings described above and the specific character strings in the drawings are examples, and are not limited to these character strings.

Claims (9)

In response to detection of an event that occurs during game play, the timing according to the detection is based on timing relationship data that indicates the relationship between the occurrence timing of the event and the capture timing of the play image indicating the play content of the game. A capture timing specifying unit for specifying the capture timing;
A capture control unit for controlling the play image at the specified capture timing to be captured;
A capture control apparatus comprising: The capture timing specifying unit specifies the start timing according to the detection based on the timing relationship data indicating a relationship between the occurrence timing of the event and the start timing of capturing the play image indicating the play content of the game. And
The capture control unit controls to capture the play image from the specified start timing;
The capture control apparatus according to claim 1. The start timing is a timing before the generation timing.
The capture control apparatus according to claim 2. The capture timing specifying unit specifies the end timing according to the detection based on the timing relation data indicating a relationship between the occurrence timing of the event and the end timing of capturing the play image indicating the play content of the game. And
The capture control unit controls to capture the play image until the end timing specified;
The capture control apparatus according to any one of claims 1 to 3, wherein the capture control apparatus includes: A timing relationship data receiving unit that receives the timing relationship data from a user different from the user who plays the game;
The capture timing specifying unit specifies the capture timing according to the detection based on the received timing relationship data;
The capture device according to claim 1, wherein The capture timing specifying unit specifies a capture period according to the detection based on the timing relation data indicating a relation between an occurrence timing of the event and a capture period of a play image indicating the play content of the game,
The capture control unit, when at least a part of the capture period corresponding to the detection specified for each of the detection of a plurality of different events overlaps, the most of the start of the specified plurality of capture periods The play image from the early timing to the latest timing among the end of the plurality of capture periods is controlled to be captured as one moving image.
The capture control apparatus according to claim 1. In response to detection of an event that occurs during game play, the timing according to the detection is based on timing relationship data that indicates the relationship between the occurrence timing of the event and the capture timing of the play image that indicates the play content of the game. Identifying the capture timing;
Controlling the play image at the specified capture timing to be captured;
A capture control method comprising: Occurrence of an event detected based on timing relationship data indicating a relationship between an occurrence timing of the event and a capture timing of a play image indicating the play content of the game in response to detection of an event occurring during game play A procedure for identifying the capture timing according to the timing;
A procedure for controlling the play image at the specified capture timing to be captured;
A program that causes a computer to execute. Occurrence of an event detected based on timing relationship data indicating a relationship between an occurrence timing of the event and a capture timing of a play image indicating the play content of the game in response to detection of an event occurring during game play A procedure for identifying the capture timing according to the timing;
A procedure for controlling the play image at the specified capture timing to be captured;
A computer-readable information storage medium storing a program characterized by causing a computer to execute.

Images