Patch 1.5 update
Giants blog post about what’s in the up coming patch.
One of the most requested features is a performance mode on consoles to increase framerate and fix crashes under certain circumstances. Both of these things will be addressed in 1.5, among other things.
Increased performance on PS5 Pro by default. Increased performance via optional performance mode on PS5 and Xbox Series X. General improvements, bug fixes, crash fixes, and more on all systems. More details in the upcoming changelog alongside 1.5!
From the outside, creating a patch probably looks like a simple thing: You tell us what's wrong, we fix it, and upload it somewhere for you to download. In reality, there are several steps, many factors, dependencies, and rules that we have to take into account. This is how it usually works:
Identifying Issues: We gather bug reports, feedback, and other data to identify what needs fixing or improving. You can report bugs via our Bug Tracker.
Planning: Goals for the patch are defined and priorities set. What fixes are the most crucial? How complex are they and how many resources are needed? What is possible in a timely-manner? Which dependencies need to be kept in mind?
Development: Programmers create fixes and improvements, and sometimes new functionalities if required. This includes testing individual changes locally to ensure they generally work as intended before they enter a broader testing phase.
Internal Testing: The patch undergoes quality assurance (QA) testing to identify bugs, compatibility issues, or unintended side effects.
Iterative fixes & testing: Things not working or colliding with other changes get back into the development phase so they can be adjusted. The puzzle pieces must fit. They get tested again.
Platform-specific adjustments: Since PC and console platforms differ in architecture, controls, and requirements, the patch is adjusted for each platform. Each version of the game is its own entity requiring attention.
Certification: Console patches must pass platform-holder (e.g., Sony, Microsoft) certification. This process checks for technical compliance with platform guidelines.
Approval: Once certification is passed, the patch is approved for release. Only at this phase, we can discuss a potential release date, as certification times can vary, and we need to release the patch simultaneously for all platforms to guarantee multiplayer functionality.
Release: The patch is deployed to the respective platforms via digital distribution systems (e.g., Steam, PlayStation Store) and the rollout can take a couple of hours across regions until the download is available for everyone.
Post-Release Monitoring: We monitor player feedback and start the process again for the following patch.