7.9 C
London
Sunday, November 17, 2024
No menu items!

‘The Witcher 3: Wild Hunt’ next-gen upgrade delayed indefinitely

April 13 (UPI) — CD Projekt Red announced Wednesday that it is delaying the next-gen version of The Witcher 3: Wild Hunt indefinitely.

In a post on the game’s official Twitter account, the developer said the port — which was expected to release during the second fiscal quarter of this year — was postponed “until further notice” after a development change.

Previously, the next-gen update was being developed externally by Saber Interactive. CD Projekt Red, however, has elected to handle the remainder of the game’s development.

“We have decided to have our in-house development team conduct the remaining work on the next-gen version of The Witcher 3: Wild Hunt,” CD Projekt Red wrote. “We are currently evaluating the scope of work to be done and thus have to postpone Q2 release until further notice.

“We’ll update you as soon as we can. Thank you for your understanding.”

The upcoming free optimization is expected to “visually and technically” enhance the PC, PlayStation 5 and Xbox Series X versions of the game, which was originally released in 2015 to widespread acclaim.

The upgrade was initially slated for a late 2021 release before being pushed back to early 2022.

CDPR’s latest Witcher update comes on the heels of its announcement that it is currently working on another entry in the popular franchise. The teaser image, posted to social media on March 21, displayed a Witcher medallion submerged in snow.

CD Projekt Red’s upcoming fourth Witcher game doesn’t have a release date yet.

Source

Latest news
Related news

LEAVE A REPLY

Please enter your comment!
Please enter your name here


Fatal error: Uncaught wfWAFStorageFileException: Unable to save temporary file for atomic writing. in /var/www/clients/client0/web1/web/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php:34 Stack trace: #0 /var/www/clients/client0/web1/web/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php(658): wfWAFStorageFile::atomicFilePutContents() #1 [internal function]: wfWAFStorageFile->saveConfig() #2 {main} thrown in /var/www/clients/client0/web1/web/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php on line 34