[PS4] The Loadout version provided to the Battleborn Open Beta server is out of date

Battleborn Open Beta Bug Reporting
#3

So I think this is where I need to post this, but this is an issue I arrived at, and I am sorry but I am not tech savy and have screenshots, but maybe someone else ran into this issue.

Preface: Played game a ton last two days, logged on 11 AM Est today, first thing I did was go into command - gear.

Joined on a friend (he was party leader) was making a character specific loadout. When I was done I went to save the loudout (by hitting the save loudout button, the center button on PS4 controller, it has worked before). It wouldn’t save, gave me a message like… could not save loudout because battleborn open beta server is out of date. I didn’t know what this was about. But also, I could not exit this screen. I was stuck with the option to “Save loudout?” “Yes” “No” it didn’t matter which option I chose, it didn’t let me get out of the gear in command menu (hit yes, could not save message popped up again, hit no, it would try to leave gear but fail, bringing me back to the same option to save loudout). Luckily my friend was party leader and he was able to matchmake and we started a PvE.

Played game, got more gear, tried to get back into my gear, did not work, got stuck in the paradox of not being able to save but cannot leave. Tried closing app, opening again, did not do anything. So we did another PvE. After final boss kill, saw final score, but not anything else (such as unlocked gear, character progression, etc.) game kicked me out to title screen, now I cannot play again. My friend did not have any issues so I assumed that it wasn’t the servers were down.

Also, the original gear loadout I went to save (the one which started the whole issue) actually did save because I used it in PvE right after the first time I got stuck, even though the game said it “could not save because battleborn open beta is out of date”

Pretty sure it said date and not data, because I remember it sounding wierd. I am assuming my account may be screwed up at this point but I will try again later today and give an update, if anyone actually reads this.

Sorry for the long post, I wanted to tell the story of my fateful journey.

1 Like
#4

Sorry moderators, I just now realized that someone else had posted on this, I appologize, but I am going to leave this here if you wish to delete or move.

1 Like
#5

That’s fine, I’ll just merge it into another thread. All feedback is useful, thanks!

1 Like
#6

I hope they fix this bug soon cause its hard to compete with people with full epic gear while im stuck with all un-commons

1 Like
#7

I also have this problem, i hope they adress this problem soon because its game braking. It makes me not wanne play the beta. Wich is sad because im loving it so much.

1 Like
#8

As an update, I was able to play last night, but still am getting stuck in the paradox of not being able to leave the gear screen once I enter it, and it automatically requests a save as soon as I do.

1 Like
#9

After they did their “fix” earlier today i figured i’d be back playing without any hitches, but i was disapointed when i realized it wasn’t resolved and my gear menu is still locked out.

1 Like
#10

Same here. I created a new loadout and when i tried to save it got the “Loadout version” message.
I’m then stuck and have to close the game.
So no Loadout change until launch, I guess. :fearful:

Other than that I really enjoy the game.

Edit: I tried deleting the savegame from the PS4. No luck. Still the same issue.

1 Like
#12

I too have this error and definately won’t be buying the launch version until i’m certain that it has been resolved.

1 Like
#13

Yeah some sign of life from the devs would be great.
It has been a couple of days and one update since it was reported.
Truly hope it sorts out. If it will be post the Beta we at least do not see what we missed out on :wink:

1 Like
#14

Ya this is a really annoying problem and when i see bug fixes on the patch about phoebe jumping to high i get mad that they can not fix something that is hurting my play experience that they new about since day 1. I want to buy this game but i feel i should not do it unless this bug gets fixed before the beta is done because if they can not fix a bug like this then what faith should i put fourth in buying a game that could have bugs that are not addressed.

1 Like
#15

I know they are hesitant to patch the beta due to it not being the release candidate; rendering some fixes useless, but they really need to address this issue. The problem is not a client issue its most certainly a server connection bug on their side. Well i hope the figure it out soon, or at least acknowledge the issue…

1 Like
#16

Got the same problem on Steam.

Happened after I created and named a second loadout, followed by a game crash, followed by the repetitive messages.

I have tried so far:

  • Verifying game files
  • Reinstalling the whole game
  • Deleting my game profile
  • Selling all my gear (no loadouts = no erros) nope, doesn’t work (bye bye legendary )

I already contacted the support about this but they are limited in their possibilities to help and couldn’t resolve the issue.

I’d too be glad to hear if this is actively being tracked by the devs, or any other form of response.

1 Like
#17

Woops!
Just created a new topic concerning this issue on PC bc. I thought this one here was only reports from PS4 incidents.
Idk … guess mine can be closed, merged or whatever? :open_mouth:

( Don´t know if it did cause the bug, but here´s my story: When I last changed and saved my gear I created 5 very similar loadouts on slots 1-4 and 6th … leaving the 5th loadout slot empty. It´s been bugged since then … )

1 Like
#18

Yea mine happened instantly when i created a second loadout without having anything in the first. This creation order might be the issue and i hope they can fix it soon

1 Like
#19

same error for me… i was gonna pre-purchased but now i’ll wait… character balancing isn’t what u should priorise when u launch a beta… now we can’t test the loadout and can’t send u feedback about it cause it just don’t work since a week…

1 Like
#20

My workaround right now is a second account. This way I can test Loadouts. Works on PS4. I do not know about Steam though.
I’m still going to preorder since this seems to be easy to fix. Balancing seems to have priority - for good reason I think.
With a week of Beta on the clock and only very few people having the problem it does not seem to be much of an issue…

And after all: Beta is Beta. Not Release Candidate - just Beta.
The often seen instrumentalization of Betas for plain marketing does not seem to be the case here. The marketing team is rather, well, lets say it politely: “slow”. Or on vacation…

#21

I am also experiencing this GAME BREAKING glitch.

I would HIGHLY advise someone to IMMEDIATELY look into this, as the GEAR tab has become nothing but a force close button.

EDIT: OP please edit the title to say PS4+PC as the issue is confirmed on both. Thank you.

#22

While this bug may appear to happen in a low % of the population it is in fact a game breaking bug. Not having the ability to use a gear loadout is downright debilitating and is something that needs to be fixed going into launch. Fixes also need to be tested themselves in large numbers so that small occurrences such as this can be observed and delt with.

I would agree that bugs in the beta release candidate are not normally representative of the final version, but the thing is that this is not a client side bug seeing how reinstall does nothing and different accounts on the same machine work.

I love this game and i only hope this problem is fixed so i can continue to dutifully test for bugs and balancing. :grin:

#23

I have had this error since day one and nobody from Gearbox has acknowledged it other the a moderator saying that the developers do check the forums and bug reports. Yet the patch they did put out only fixed mostly minor bugs and did not mention any of the bigger game braking bugs that a few dozens of people have. It makes me wonder if i buy the game and get a similar bug if they would even do anything about it. I feel like their attitude on the matter is; to bad for you, 99% of the game’s population does not have this problem.