FANDOM


Image Fight II: Operation Deepstriker is a sequel for the PC Engine Super CD-ROM in 1992 exclusively in Japan. Like the TurboGrafx-16 version of the first Image Fight, Image Fight II was re-released for the Virtual Console only in Japan.

The OF-1 Daedalus is the first ship which the player must pilot. Later, it was replaced by the OF-3 Garuda.

This game is a lost jewel of Irem, and they really put love in this game. It features a good storyline, new enemies, upgrades of past ones and a few new arsenal. The only bad thing in this game is Irem reusing the old soundtracks from Image Fight.

Game's Intro

"On July 18, 2048. Mariko, the mother computer on the moon base, gave a silent cry and went silent.

Peace was then restored to the Earth and people tried hard on reconstruction on the devasted planet.

Three years after, a Space probe placed between Saturn and Uranus detected the change in Deep Space for the first time.

In the direction of Sagitarius, a cluster of objects emerged, warping the space around it and emiting light shifting to blue intro the spectrum.

The analysis of the spectrum revealed the most fearful data about the unidentified objects.

Distance: 0.15 Years Light, Direction: Straight forward to the Earth, Conclusion: An Enemy Armada approaching.

It now came home to the human race that the last space war had been nothing more than a preliminary skirmish."

Trivia

  • The unknown enemies may be previous versions of the Bydo or allies of the Bydo.
  • In the game's intro, there's an OF-1 debris floating in space. It may allude that the other 2 pilots sent in the previous mission were destroyed.
  • In the game's ending, the OF-3 Garuda ejects the canopy to save its pilot. This is the only OF Fighter seen to be able to do this, since multiple Daedalus units were shot down in that game.

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.