‘Fallout 4’ Updates: New Patch Imminent For PC First, Then Consoles (Photo : YouTube)
A lot of players are enjoying the exploration component in "Fallout 4' even though it appears that not everyone has stepped out of the Vault 111 yet. However, this is not to say that the game is perfect as it is, as several players have also reported encountering a game-breaking bug.
The glitch that was seen is bigger than the usual inconvenience, as players are not able to go beyond the point in the game after encountering the bug, DualShockers reported. According to the report, players usually find the game crashing upon reaching the Monsignor Plaza. All versions of the game have been reported to experience this bug.
PC players are redirected to their desktops, while crashes are reported for the Xbox One and PS4 versions of "Fallout 4." Fans have pointed out a few areas that may be the touch point for the bug.
Some of the speculated triggers for the game-breaking bug include passing the location, since any direction that the player enters the area will still result in a crash. In another instance, it is also possible that those who do not crash at the expected location will crash sometime later in the game, especially if a player tries to access a save version from the crash. What is interesting is how other people appear to have gotten over the area without crashing, considering the mentioned speculated triggers.
Bethesda has yet to acknowledge the existence of the bug. There is also no word yet on whether Bethesda will release a patch to target the different issues seen in "Fallout 4."
Another bug that is currently plaguing "Fallout 4"users is the Terminal Stuck bug. As the name implies, players are forcibly stuck in the Terminal, as they cannot be exit despite being finished with the mission, Gamepur reported.
The good thing about this is that a fix has already been found. All that needs to be done is to change the parameters in the program files. Specifically, the "Fallout4Prefs" file parameter should be changed from "iPresentInterval=1" to "iPresentInterval=0" to get rid of the bug. There are still a couple of other issues with the game, though Bethesda has yet to announce the release of an encompassing fix to resolve issues.
