[ad_1]
This patch appears to follow the Photo Mode update, so there is always the chance that it resolves some minor issues with the Photo Mode, or fixes some of the problems that were reported since the last patch.
Some of the quest and progression bugs have been resolved in this patch while stability and performance have been improved as well.
God of War Ragnarok Update 3.01 Patch Notes:
Quests and Progression
Fixed a case where the central sword would not show properly if restarting from checkpoint during the challenges in Muspelheim.
Stability and Performance
Fixed two rare crashes that could occur randomly during gameplay.
The last major update that added Photo Mode was 3.0 and it added a lot more as seen in the patch notes.
If you are playing the game on PS5, the update size is just around 222 MB so it is not a large size by any means. We reckon that the PS4 version will also be a smaller update, under 500 MB at least.
God of War Ragnarok is one of the faster selling first-party games from Sony. It was released for the PS4 and PS5 this November and debuted with more than five million copies sold in its launch week, which is a record in itself.
God of War Ragnarok follows the story set up in the soft reboot of God of War in 2018. It brings the same protagonist, Kratos, and adds a new dynamic into his life by letting him take care of his son Atreus. The first game was a lengthy quest involving Kratos and his son on a mission to fulfill the wish of his wife, while the sequel is more action-packed delving deeper into Norse Mythology.
God of War series is developed by Sony Santa Monica Studio. The first God of War release, God of War 2018, is also available on PC while its sequel has yet to make a debut there.
// global variables
var Top40FullName=””;
var Top40FBid=”;
var Top40userid=”;
/*
// This is called with the results from from FB.getLoginStatus().
function statusChangeCallback(response) {
console.log(‘statusChangeCallback’);
console.log(response);
// The response object is returned with a status field that lets the
// app know the current login status of the person.
// Full docs on the response object can be found in the documentation
// for FB.getLoginStatus().
if (response.status === ‘connected’) {
// Logged into your app and Facebook.
fb_login_check();
} else {
// The person is not logged into your app or we are unable to tell.
document.getElementById(‘top40-login-status’).innerHTML = ‘Please log ‘ +
‘into this app.’;
}
}
function checkLoginState() {
FB.getLoginStatus(function(response) {
statusChangeCallback(response);
});
}
window.fbAsyncInit = function() {
FB.init({
appId : ‘160329538558’,
cookie : true, // enable cookies to allow the server to access the session
xfbml : true, // parse social plugins on this page
version : ‘v2.8’ // use graph api version 2.8
});
FB.getLoginStatus(function(response) {
statusChangeCallback(response);
});
};
// Load the SDK asynchronously
(function(d, s, id) {
var js, fjs = d.getElementsByTagName(s)[0];
if (d.getElementById(id)) return;
js = d.createElement(s); js.id = id;
js.src = “https://connect.facebook.net/en_US/sdk.js”;
fjs.parentNode.insertBefore(js, fjs);
}(document, ‘script’, ‘facebook-jssdk’));
// Here we run a very simple test of the Graph API after login is
// successful. See statusChangeCallback() for when this call is made.
function fb_login_check() {
console.log(‘Welcome! Fetching your information…. ‘);
FB.api(‘/me’, function(response) {
console.log(‘Successful login for: ‘ + response.name);
console.log(response);
Top40FullName=response.name;
Top40FBid=response.id;
Top40userid=’fb_’+response.id;
var metadata = {
user_id: Top40userid
};
Intercom(‘trackEvent’, ‘FB-login’, metadata);
document.getElementById(‘top40-login-status’).innerHTML =
‘Thanks for logging in, ‘ + response.name + ‘!’;
$(‘#top40-login-button’).css(‘display’,’none’);
});
}
*/
[ad_2]
Source link
Playlists