Today we have the Outriders News Update for 7/13/21. Today we were supposed to get the latest patch for Outriders, but it ran into a snag. In today’s News Update we hear what the current problem is and what the developers are looking to do. Also, the devs want to know your opinion. We discuss this and more in today’s News Update!
LEEROY GAMING SOCIAL MEDIA:
🌳 LinkTree – All-In-One Social @Leeroy_Gaming https://linktr.ee/Leeroy_Gaming
🎮Twitch: https://www.twitch.tv/leeroygamingstream
🐣Twitter: https://twitter.com/GamingLeeroy
🏪 Merch Store: https://streamlabs.com/leeroygaming/merch
🟣Discord: https://discord.gg/7StQkDxKYE
🔵Facebook: https://www.facebook.com/leeroy.gaming.7
📷Instagram @ Leeroy_gaming https://www.instagram.com/leeroy_gaming/
Interact with me when I stream on Twitch (#LeeroyGamingStream) by
checking out my current Twitch Stream Schedule: https://www.twitch.tv/leeroygamingstream/schedule
News Update Highlights:
Hi everyone,
As you know we were hoping to release our latest patch today. We have, however, made the difficult decision to push the patch back to Thursday. We’ve explained this decision below – please do take the time to read it as it contains important information.
During our final tests of this latest patch, our team encountered two different crash scenarios, as described below:
Issue 1:
A rare issue that, after installing the patch, appeared to cause the game to crash on launch for a small number of testers. After a certain number of these launch crashes, the game launched without any issues and the crashes did not reappear.
Issue 2:
An issue that can cause the game to crash for players when returning to the lobby from a multiplayer session.
Theory: This crash may only occur when one of the party members is a Pyromancer and has specific skills (e.g Heatwave or Overheat?) and mods (e.g Tidal Wave?) equipped.
Throughout our ongoing work on Outriders, we only encountered these issues for the first time when testing the latest patch. Using specific reproduction steps, we are able to trigger these crashes between 20% to 40% of the time.
However, our recent community research indicates that both of these crashes may already be present in the game but have never been formally diagnosed until now (because testing didn’t encounter them). If this is the case, then this patch wouldn’t actually introduce any new issues and could be considered “safe”.
So here’s where we ended up today:
Option A:
Release the patch today, having only partial information about these encountered crashes and running the risk of introducing new issues, including crash on launches, into the game for an unknown number of players.
The fixes for these issues would be rolled into the next available patch once we’ve identified and resolved the root cause.
Option B:
Push back the entire patch to fully understand these issues, fix them, retest the patch for a number of days and then release the patch sometime next week at the earliest. This in turn could also delay the next patch thereafter.
Given the already long wait in-between our last and this current patch, we want to avoid delays as much as possible.
Option C:
Delay the current patch till this Thursday to gather more information about whether these issues (and how often they occur) are already prevalent in the game and how often they may occur.
The fixes for these issues would be rolled into the next available patch once we’ve identified and resolved the root cause.
We have opted for Option C and we need your help to determine whether this is the best move to make.
Please let us know in this thread if you feel that you have recently (in the past few weeks) encountered either Issue 1 (Crash on Launch Subthread) or Issue 2 (Crash on Return to Lobby Subthread). As usual, the more information you can provide, the more likely it is that we will be able to identify and resolve them.
What happens next?
If we, alongside the community, are able to determine that both of these issues are already present in the game, we will go ahead and aim to release the patch this Thursday.
With community data about under which circumstances these issues appear, it will also be easier for us to identify and fix these issues in a future patch.
RISK: It is possible that something within the patch has increased the frequency at which these crashes appear, but this will be very difficult to determine in the time we have.
If we are unable to determine that both of these crashes are already present in the game, this would indicate that one (or both) of them would have been introduced as part of this patch. The patch would therefore need to be reworked.
ORIGINAL NEWS POST LINK:
https://www.reddit.com/r/outriders/comments/ojhq7g/outriders_interim_dev_update_july_13th/
#Outriders #outridersnews #leeroygaming
source
Keepin us informed.
I've had it happen twice in the last week buti can't say if I was on my Pyro or not my Pyro does have those skills and mods but I thick ihad the issue while on my trickster to so I can't pin point the root cause of it
Heya leeroy hope all is well. I haven't been feeling outriders recently logged in and ran two expeditions in a row archway and scorched lands and got same 3 guns each run.
I have never encountered that pyro issue in multiplayer, and i have played with many pyros both as a devastator and as a pyro myself, so having 2 or 3 pyros in a team and not encouraging that issue makes it highly unlikely that it was an existing issue. Close to 500hrs in game, and we all use those mods.
I wonder if they will pay me for helping with crash testing smh.
A majority of the crashes I have experienced in the game usually take place in the first 30 minutes of a game session. Usually, if I get by the first 30 minutes without a crash, then I don't crash.
I don't experience the crash of returning to the lobby after multiplayer sessions. I often go to the lobby because I don't usually run as lead and whenever the leader leaves, you end up in the lobby.
I do play Pyromancer a lot. I also run Heatwave / Overheat with the mod Tidal Wave. So I do not believe it is an existing issue. I have almost 600 hours playing with a majority of the time as a Pyromancer.
I will admit that many of my crashes are related to playing on PC. Sometimes when my game crashes I think about being upset at the developers but then I see in the bottom right corner of my computer screen that my antivirus is doing an unexpected update or something like that.
People can't always blame crashes on PCF.
I say just take the week. The game is in a decent place. Releasing a broken patch will just set them back even more.
Dam I was hopeing for the skill buff patch been pretty bored of the game as of lately because got all the legendary gear and been playing the same expedition getting super bored been playing other games now. I’ll boot up outriders as soon as the skill patch is put in otherwise they need dlc some new game mode some new legendary armor idk
Honestly, I know a lot of people want to talk poorly about the team at PCF, but the communication they are doing now is amazing. If we want to see what actually happens when a team listens to fans, then now is the time. This could end up be revolutionary in all honesty. If this becomes a positive story and the game does a complete turn around, other companies may start doing the same thing. Maybe it won't be about making the most amount of money with the minimal work.
They released the game with mixed and bad info why stop now
Release the dragon ???…wtf was that…lmfao
No crashes, for me…
How can you call the people that are upset trolls? We paid 60 dollars for a game that was still in early Beta. Don't get me wrong, it's has potential to be a great game but let's call a spade a spade. The game was not a finished game when it was released. He'll it was so unfinished they had to turn it into a biweekly life update game when it wasn't supposed to be.
Lets be honest, we knew it wasn't gonna be released today