Advertisement
Australia markets closed
  • ALL ORDS

    8,153.70
    +80.10 (+0.99%)
     
  • ASX 200

    7,896.90
    +77.30 (+0.99%)
     
  • AUD/USD

    0.6518
    -0.0018 (-0.28%)
     
  • OIL

    83.11
    -0.06 (-0.07%)
     
  • GOLD

    2,254.80
    +16.40 (+0.73%)
     
  • Bitcoin AUD

    108,982.59
    +2,734.66 (+2.57%)
     
  • CMC Crypto 200

    885.54
    0.00 (0.00%)
     
  • AUD/EUR

    0.6036
    +0.0005 (+0.09%)
     
  • AUD/NZD

    1.0901
    +0.0021 (+0.19%)
     
  • NZX 50

    12,105.29
    +94.63 (+0.79%)
     
  • NASDAQ

    18,254.69
    -26.15 (-0.14%)
     
  • FTSE

    7,952.62
    +20.64 (+0.26%)
     
  • Dow Jones

    39,807.37
    +47.29 (+0.12%)
     
  • DAX

    18,492.49
    +15.40 (+0.08%)
     
  • Hang Seng

    16,541.42
    +148.58 (+0.91%)
     
  • NIKKEI 225

    40,168.07
    -594.66 (-1.46%)
     

'God of War' gets a 60 fps and 4K patch for PS5 tomorrow

The upgrade is free.

Santa Monica Studio / Sony

One of the PlayStation 4’s best exclusives is finally getting a next-gen upgrade. Sony will release a free PS5 optimization patch for 2018’s God of War tomorrow, giving you an excuse to replay the game before its sequel comes out later this year. With the update, the console will render the title at 60 frames per second and 4K by default. If you played God of War on a PS4 Pro, you might remember you could set the game to either target a 4K resolution or a smoother frame rate. The PS5 gives you the best of both those options. If for whatever reason you want to play the game at 30 frames per second, you can do so by selecting the new Original Performance Experience option.

The interesting side note to all this is that you could technically already run the game at 60 frames per second and 4K if you owned it on a disc and stopped your PlayStation 5 from downloading any updates for it. God of War shipped with an unlocked frame rate, which developer Santa Monica Studio later changed in a patch to smooth out inconsistent performance on the PS4. Now there’s no need for that workaround.