Cozy up.

State of dev, first and foremost.

And we are going to be talking about the...

You could call it a minor train wreck.

Quite literally.

That is EXP right now.

Because... We've done a lot of good chat.

But we also done fucked up.

And... Oh, yeah, indeed.

Nice Mona Lisa pose.

Is that what this is?

Isn't it?

Or is that also before your time?

Oh,

I mean... Kinda.

I think most people's time, right?

I mean, I suppose it's also before my time.

Yeah, yeah,

yeah.

See, I think of the Mr. Bean movie when I think of Mona Lisa, so... You're getting

distracted.

Stay on track.

Get it?

Oh!

That was unscripted.

Holy shit.

Nice.

Nice.

To get to the point, on the XP right now, if you are playing the experimental branch, if you dismantle a train, you may realize that 10 out of 10 times you will crash.

Like, the game will crash.

Which is...

Certainly not going to be there for live, I can tell you that much.

That's pretty bad,

actually.

That's pretty bad,

actually.

And there is a story behind why something so significant

could make it onto a patch, because this patch otherwise did fix a hell of a lot of stuff.

And the notes have been out for almost a week, because the patch has been out for almost a week.

So I'm not going to go through it super, super in depth, but we have fixed audio stuff, we have fixed crashes related to online and multiplayer and clients joining late game multiplayer sessions.

We have fixed custom map marker issues, we have fixed crashes due to path nodes, we have fixed performance overall, we have fixed...

Literally, the nodes are...

I'm gonna put them on the retweets, the restream, sorry.

Chat right there.

They are there, they are very chunky, not gonna read through all that, but there is a lot of stuff in here about performance, about game mechanics, fixes, bug fixes.

Um...

But we've talked about, so patch two was delayed.

It was supposed to be released, I believe, late or even like mid to late April, which is now two or three weeks ago.

Three weeks ago, yeah.

And when it wasn't released, because some key people got sick and a couple of other hiccups, people started scope creeping into just pushing more stuff into the patch, which is, you know, fine, fair, this stuff was going to make it into 1.2 live anyway.

So may as well push that in there too, with good intention.

This patch was being scope crept.

But that also meant that when QA was back on their feet, there would be even more stuff for them to bug test.

And I'm sure you've seen this.

If you play something like an MMO or even any huge game that gets regular updates, you're pretty aware of the weirdest interactions where

Just take MMOs for example.

You buff a random mob, an enemy, in some dungeon somewhere and all of a sudden a player's bags can break for no reason.

There are some strange interactions and intertwined messes of code, more, I guess, dependencies in the code, going on behind the scenes, and Satisfactory is no exception to that.

So, as a lot got shoved in in the scope creep in patch 2, that meant that some other things that you would suspect were completely unrelated

to say these fixes they started breaking and so qa has quite literally been playing whack-a-mole with this for a while

yeah

and we have a detailed or as detailed as we could go without boring you to death detailed summary from andrea our newest qa tester here at coffee stain for satisfactory

Where he's saying, so we had an issue, I'm gonna read this flat out because his words are the best words.

Basically, we had an issue for which you could fall out of the map inside a vehicle and fall indefinitely without dying.

That has now been fixed.

When that got fixed, the whack-a-mole started happening with where a bug came up that would cause players to be soft-locked and unable to move after respawning under certain conditions.

Not always, but under certain conditions, always.

Sometimes, yes.

so they fixed this bug where you could get stuck indefinitely and then the third bug finally reared its ugly head which was you crash whenever you dismantle any locomotive oh well and this was not realized internally until we were actually back on our feet and almost ready to send the patch 2 out

So the debate happened the delay has been three plus weeks now.

Do we delay even further or do we send this and Fix it as soon as possible Which felt like the better idea because one holding the patch

could mean that it was gonna be even more significantly delayed.

And two, because of this whack-a-mole timeline, you don't really know what would break if we did fix this train bug before we sent it out live.

If we did send it,

something even bigger or something even more annoying could happen and kind of in a fun twist of fate exp is actually a very good spot for this if we send this out live right now and uh just track the train crash bugs as they happen as you all crash as you dismantle trains

We have this out now.

If we hotfix this while the game is live on eXp, then whatever issue might crop up from that will be found much faster because we have a lot of players playing the game.

Not only our internal QA, but all of you.

If this had been the live version of the game, you could, one, definitely expect this to not go live until everything was fixed on our end, even if it would take some more time.

That is the one thing, yeah.

But because it is eXp,

Which, again, the point of eXp is not to just give you a fully functional game early for no reason.

It is for us to openly test everything going on with the upcoming content for a next major update in some cases.

Or it could also just be performance or back-end tests as well.

In this case it is tests for a major update.

We felt that, yeah, fuck it, it's EXP, so let's actually use it for what it's meant for, testing, large scale.

Do you think we're not clear enough about that?

Maybe.

Because, you know, I mean, I don't know if we've ever asked you guys to, like, back up your saves or anything like that.

But, yeah, EXP is certainly experimental.

Things are gonna break.

I think the team's usually pretty good about keeping even the experimental builds stable, but sometimes you just gotta send it.

I

just realized there's only one name tag.

It's pretty

implicit.

There we go.

There's only one name tag on that screen, I just realized.

Will the EXP patch go out if the train bug gets fixed before you peeps go on vacation?

I can already say, by the way, this bug is fixed internally, and Uzu is working on sending a hotfix out as soon as possible.

We have identified it, so funnily enough,

All of what I just said about something might break was a hypothesis.

Until it just got fixed internally this week, the train bug.

And funnily enough, yes, this hypothesis turned into concrete facts.

Something else did break.

Something else that in fact would actually maybe be even more annoying.

and that is that the bug is fixed right now and as far as i know we're gonna push a hot fix soon but only if we then squash the next bug in the whack-a-mole chain which is making it impossible for the players to cycle at hyper tube junctions and if you somehow would brute force that or try to the game might also the bed so i'm not sure if more people use hyper tubes than use trains but

At some point, we just gotta...

There's probably quite a bit of overlap there.

Yeah.

Maybe.

Because I'm definitely...

I've used hyper...

I use hyper tubes, but I've never touched a train.

Trains scare me a little bit.

I just don't know how the signals work.

That's really just the one thing.