Game machine for development, and program execution method
A game machine for development is connected to a host computer, reads out a file requested by a game program under development from a storage device, and executes the game program. In the game machine for development, a file confirmation section confirms whether or not the file requested by the game program is stored in the storage device, a file request section requests the host computer to transmit the file in a case where the file is not stored, and a storage processor acquires the file from the host computer and stores the file in the storage device.
1. A game machine for development that is connected to a host computer and to a storage device not connected to the host computer, and configured to read out a file requested by a game program under development, and execute the game program, the game machine for development comprising:
a file confirmation section that is configured to confirm whether or not the file requested by the game program is stored in the storage device;
a file request section that is configured to request the host computer to transmit the file to the game machine in a case where the file is not stored in the storage device; and
a storage processor that is configured to acquire the file from the host computer and stores the file in the storage device; wherein
synchronization is not established between the storage device and the host computer;
a plurality of game developer computers are connected to the host computer, and each game developer computer uploads a respective game file to the host computer;
a file tree of the host computer has an include definition file describing a list of files to be transferred to the game machine that includes at least one uploaded game file, and an ignore definition file describing a list of files not to be transferred to the game machine that includes at least one other uploaded game file;
when the file requested by the game machine is included in the include definition file, the host computer determines that the file is allowed to be transmitted to the game machine;
when the file requested by the game machine is included in the ignore definition file, the host computer determines that the file is not allowed to be transmitted to the game machine; and
both definition files may be used for determination as to whether or not the file is allowed to be transmitted to the game machine, while only one of the definition files may be used.
2. The game machine for development according to claim 1 , further comprising an update management section that acquires update information indicating that the file stored in the storage device is updated in the host computer.
3. The game machine for development according to claim 2 , wherein in a case where the update management section retains the update information of the file requested by the game program, the file request section requests the host computer to transmit the file.
4. The game machine for development according to claim 2 , wherein when a predetermined condition is satisfied, the file request section requests the host computer to transmit a file identified by the update information retained by the update management section.
5. The game machine for development according to claim 3 , wherein the storage processor stores an updated file in the storage device together with a pre-update file.
6. The game machine for development according to claim 5 , wherein the game program is capable of using the pre-update file, and the storage processor deletes the pre-update file from the storage device in a case where the game program is terminated.
7. A program execution method that executes a game program under development in a game machine for development connected to a host computer and to a storage device not connected to the host computer, the program execution method comprising:
confirming whether or not a file requested by the game program is stored in the storage device;
requesting the host computer to transmit the file to the game machine in a case where the file is not stored in the storage device; and
acquiring the file from the host computer and storing the file in the storage device; wherein
synchronization is not established between the storage device and the host computer;
a plurality of game developer computers are connected to the host computer, and each game developer computer uploads a respective game file to the host computer;
a file tree of the host computer has an include definition file describing a list of files to be transferred to the game machine that includes at least one uploaded game file, and an ignore definition file describing a list of files not to be transferred to the game machine that includes at least one other uploaded game file;
when the file requested by the game machine is included in the include definition file, the host computer determines that the file is allowed to be transmitted to the game machine;
when the file requested by the game machine is included in the ignore definition file, the host computer determines that the file is not allowed to be transmitted to the game machine; and
both definition files may be used for determination as to whether or not the file is allowed to be transmitted to the game machine, while only one of the definition files may be used.
8. A non-transitory, computer readable storage medium containing a computer program, which when executed by a computer in a game machine for development connected to a host computer and to a storage device not connected to the host computer, causes the computer to carry out actions, comprising:
confirming whether or not a file requested by a game program is stored in the storage device;
requesting the host computer to transmit the file to the game machine in a case where the file is not stored in the storage device; and
acquiring the file from the host computer and storing the file in the storage device; wherein
synchronization is not established between the storage device and the host computer;
a plurality of game developer computers are connected to the host computer, and each game developer computer uploads a respective game file to the host computer;
a file tree of the host computer has an include definition file describing a list of files to be transferred to the game machine that includes at least one uploaded game file, and an ignore definition file describing a list of files not to be transferred to the game machine that includes at least one other uploaded game file;
when the file requested by the game machine is included in the include definition file, the host computer determines that the file is allowed to be transmitted to the game machine;
when the file requested by the game machine is included in the ignore definition file, the host computer determines that the file is not allowed to be transmitted to the game machine; and
both definition files may be used for determination as to whether or not the file is allowed to be transmitted to the game machine, while only one of the definition files may be used.