We're currently finalizing the next patch for Farming Simulator 25 - version number 1.5. You can expect it to be released soon for all platforms. We're currently aiming for a release next week.
But to give you a little more information before the weekend, here are some details about the patch, as well as an explanation of how patches are made, in case you want to know. Stay tuned, we'll update you as soon as the patch is released!
What will Patch 1.5 include?
Just a short outlook...
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!
How are patches created?
Some info on the process...
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.
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.
FAQ
Having more questions?
Why aren’t patches coming quicker?
As described above, the process of patch creation takes time, as there are many variables and dependencies - internally and externally. As software development, especially for a variety of systems, is complex, it takes some time.
Why don’t you name specific release-dates?
We don’t talk about specific release-dates because they might not be held due to unforeseen occurrences and external processes, e.g. certification on platforms etc. We don’t like to name a date we can’t guarantee. The farther away from release, the more uncertain any prediction would be.
Why haven’t I received a reply to my bug report?
Don’t worry, your bug report is important and was received! Answering every single report is not possible, especially since you will not be the only one to report a specific problem. That doesn’t mean your report is in vain - it’s the opposite: receiving multiple reports on a issue sends us the signal that it must be important to fix.
Our dedicated support team will answer individual issues, e.g. key activation difficulties, and take care of your specific needs.
When it comes to bug reports, the support team is dedicated to work efficient with the goal of helping our programmers to create fixes. Meaning: they will use their resources for collecting, categorizing, prioritizing and internally reporting and discussing what you report instead of creating individual responses.
The patch did not fix X for me.
Please note that certain issues may arise due to specific conditions, e.g. installation of mods, corrupted save games, individual hardware configurations etc.
The game is stuttering after installing the patch.
After installation of a new patch, shaders need to be recompiled. This can take a few minutes and will solve itself after a bit of playing or simply waiting after starting up the game.
How do I report bugs?
You can report bugs via our Bug Tracker. This way, we can collect, prioritize, and plan what the next patch needs to address.
Much explain, but patch when?
Patch very soon! More patches after - promise!
