
Hey everyone,
We have been reading your discussions, reviews, bug reports, and feedback. A few issues are coming up more often than anything else, so we wanted to share what we are currently working on and our present order of priority.
We know that “we hear you” only means something when fixes follow. This is not an exhaustive patch list, and priorities may move if we find something more critical, but this is where the team’s attention is currently going as head into the weekend.
We are working to safely raise the default Simulation Thread Count while investigating the root causes of the performance issue within our multiplayer engine. Until that work is complete, players experiencing extremely low FPS after entering a mission should continue setting Simulation Thread Count to 2 under Options > Settings.
We have also implemented a fallback for players who encounter this issue last patch: The game will automatically adjust the relevant settings, although you will need to restart the client for the change to take effect. If the mission is cancelled because of this issue, you should not receive any penalty. If the issues remain, we still recommend players manually setting the Simulation Thread Count to 2.
We are still investigating cases where a disconnect can leave players stuck during the transition to Mission Results. While we work on the proper fix, rejoining the previous session can preserve your mission rewards in most cases, so please try to rejoin before abandoning the session entirely - if you are playing with a friend, ask them to wait for you to rejoin before they leave the mission result screen.
Our immediate goal is to remove unintended losses caused by deaths or mission failures outside the player’s control. You should not be punished because the game crashed or disconnected. We are also investigating whether we can release an earlier version of our intended weapon repair system, giving players a way to deal with existing Scars sooner.
Until that time, we recommend holding on to your favorite scarred weapons until we can implement the Repair functionality.
Manual keybinding is coming, with keyboard controls as our first priority. This requires extensive testing before we can safely release it, but implementation is actively being pursued.
Some devices continue to experience stuttering even after changing Simulation Thread Count. This appears to be a separate performance issue, and we are profiling affected systems while investigating the hardware, driver, and gameplay conditions involved. Your continued efforts in reporting this and sharing your player.logs with us help a lot.
We are investigating crates that fail to appear correctly, as well as cases where players become trapped inside Purple Encounter Zones because enemies remain outside the barrier or cannot be eliminated.
Testing these issues is taking time because we need to reproduce and validate them across individual mission maps. Both remain under active investigation.
Switching between online and offline states can sometimes trigger an alarming save-data warning. In most cases, our save-load system already resolves the problem by reverting to a back-up save in the system and players do not need to reset their progression.
The current error reporting does not communicate this clearly, and we will be updating that messaging.
For now, if you encounter this warning, do not delete your local files or perform a full reset. Load into the game first and check whether the reverted save loads correctly. If the problem remains, then you can resort to a full reset.
We hear that Credits currently accumulate too slowly compared with the cost of progression and Armory purchases. We are reviewing mission payouts, progression costs, and the broader game economy as part of an overall balance pass and we agree.
We hope to get these fixes ready for a patch soon, until then please keep your feedback coming. Fandry, Valent, and I will continue to check the Discussions and Discord to compile all your thoughts as we go.
For everyone on Discord, please bear with us as we're just moonlighting as community managers so we're still figuring out the flow of things and we can't adjust some of the very strict bot settings. Don't worry if the bot yells at you for something silly, we can remove any warnings and or timeouts.
Thank you for being understanding and direct with us and for continuing to send detailed reports. We are excited to keep improving RIFTSTORM with you, one fix and one increasingly difficult build at a time.
Cheers!
Fandry, Valent, Igor & The RIFTSTORM Team