KONAMI have warned of a new save file glitch that could ruin Metal Gear Solid 5: The Phantom Pains for fans on Xbox, PlayStation and PC platforms.
The Big Boss title has been out since September 1 and so far my game has been bug free for the most part.
But players have been warned that a glitch found in the game could corrupt save files and leave fans having to start the game again.
That means more prologue up-close butt shots and staggering about in a hospital that some users would be hoping to avoid.
It seems the issues can be triggered when choosing Quiet as your companion on either Mission 29 or Mission 42.
Konami say they are currently working on a fix but have told fans it's best to avoid using the sniper for those missions until further notice.
The bug reportedly affects the PS4, PS3, Xbox One, Xbox 360 and PC platforms.
An official post on the game publisher's website confirms: "In "In Metal Gear Solid V: The Phantom Pain, which was released on September 1st 2015, there is a possibility that save data may get corrupted and becomes unusable if having Quiet as a buddy while playing "Mission 29" or "Mission 42".
Sneaky peak at how our stands at #LOGLive looked before the doors opened! If you're here then let us know! pic.twitter.com/YJdr1UjcrY
— Konami UK (@KonamiUK) September 5, 2015
"This situation can be avoided by not using Quiet as a buddy while playing either "Mission 29" or "Mission 42".
"We deeply apologise, and appreciate your patience for further announcements regarding this issue."
A Konami community manager explained how the bug affects the game and let fans know on Twitter that the dev team were looking into the problem, writing: "The game loop in loading screen; the team is still working on a cause and resolution, as reported for now avoid Mission 29 & 42 using Quiet."
The game's release was also affected by server issues, resulting in Metal Gear Solid 5 being taken offline for maintenance while the FOB Online Mode being limited to keep stability for fans on all platforms.
Post a Comment Blogger Facebook Disqus