March 31st, 2026 - State of Dev

March 31st, 2026

State of Dev

State of Dev (Part 1)

https://www.youtube.com/watch?v=5SUMibgYAvM&t=0

Suggested Wiki Reference Code

EXP Updates

https://www.youtube.com/watch?v=5SUMibgYAvMt=0

Suggested Wiki Reference Code
Topics
  1. Mikael

    Alright chat, here we are Satisfactory, we had a patch last week for experimental and we are having a patch this week as well.

    It should be out today If not, it might be out tomorrow.

    I thought it was gonna be out yesterday.

    I thought wrong They were always planning on doing that today

    and uh let me get my little cheat sheet going so i don't say the wrong things now oh my pocket sound my side my pocket is buzzing which means i might be getting scolded by uzu no you can't talk about the patch okay no that was not uzu it was actually macro factor funnily uh patch today or tomorrow

    And whereas last week's patch was aiming at fixing, I mean, crashes and errors that were a bit more visible, on the XP specifically, this is a patch for Experimental, this patch is aiming to fix a couple of visible things, most, if not all of them, pertaining to weather.

    and also work even more on quite a lot of technical crashes behind the scenes.

    Because, honestly, pound for pound, I mean, most of us have been lurking in chats or in streams, just watching you guys play 1.2 or, you know, testing it ourselves.

    And content-wise, like gameplay-wise, the EXP is stable.

    Like, it's across all of the huge update EXPs we've done since even before 1.0.

    This is on the more stable side, which is nice.

    in terms of like actual game bugs and obvious gameplay issues.

    So the focus is more on the crash, the technical, why is the game just randomly shutting down on occasion side.

    So this patch is heavy on crashes, crash fixes, sorry, and weather fixes specifically.

State of Dev (Part 2)

https://www.youtube.com/watch?v=5SUMibgYAvM&t=110

Suggested Wiki Reference Code

Leaving most of the update to the written Patch Notes (Part 1)

https://www.youtube.com/watch?v=5SUMibgYAvM&t=110

Suggested Wiki Reference Code
Topics
  1. Mikael

    So...

    The, I'm not sure how worthwhile, like, Uzo is going to post the patch notes later today or tomorrow, again, when the patch is out, whenever that is.

    And since it is more technical, I don't think, like, rambling about gameplay is fun, rambling about crashes is just ultimately going to go in one ear and go out the other.

    So I'm going to leave that to the written patch notes for the most part.

Nasty crash when joining a Multiplayer session

https://www.youtube.com/watch?v=5SUMibgYAvM&t=136

Suggested Wiki Reference Code
Topics
  1. Mikael

    But we had an especially nasty crash that was happening when you joined a multiplayer session that had been going on for a while.

    Something, something, not quite memory leak, but something, something, overloading memory, running out of whatever the bandwidth hell,

    when a session had been going on for too long and enough memory or enough I don't know run time Had happened enough.

    Let's just call it memory had been occupied and when a new player Hopped into this session and loaded every single recipe available including the alternative alternates those could eventually

    Run past the maximum use for that specific memory and just cause a crash the specific little block of a lot of memory for that but you see that this is like this kind of this is a very easy crash to explain and

Leaving most of the update to the written Patch Notes (Part 2)

https://www.youtube.com/watch?v=5SUMibgYAvM&t=190

Suggested Wiki Reference Code
Topics
  1. Mikael

    Run past the maximum use for that specific memory and just cause a crash the specific little block of a lot of memory for that but you see that this is like this kind of this is a very easy crash to explain and

    mind you, and I'm doing a terrible job, and this kind of technical, like, mumbo is basically what's going to happen in this patch, so that's why it's not really worth for me to ramble them, because I would have to find my own words, first and foremost, and then you would have to remember the details, and they are not gigafun, or interesting, to be fair.

    But it's a very performance and crash heavy patch.

Weather-related Fixes

https://www.youtube.com/watch?v=5SUMibgYAvM&t=216

Suggested Wiki Reference Code
Client Issues

https://www.youtube.com/watch?v=5SUMibgYAvM&t=216

Suggested Wiki Reference Code
Client thunder audio stacking

https://www.youtube.com/watch?v=5SUMibgYAvM&t=216

Suggested Wiki Reference Code
Topics
  1. Mikael

    But it's a very performance and crash heavy patch.

    The few weather, rain and thunder connected phenomena we are fixing are that thunder sometimes does not stop for clients when playing and can sometimes even stack on top of each other.

    This can be very fucking loud if you've heard it.

    So mambo, technical mambo jambo.

    I mean, besides, you know, eating at performance and besides being very just strange as a phenomenon, it's also geek allowed.

    So, thunder stacking on top of each other, yeah, we're sorting that.

    If anyone was being bothered by that.

Client experiences distorted game audio due to rain

https://www.youtube.com/watch?v=5SUMibgYAvM&t=260

Suggested Wiki Reference Code
Topics
  1. Mikael

    If anyone was being bothered by that.

    And client experiences distorted game audio due to rain when joining sessions.

    So if you have had distorted audio from everything in the game, or mostly everything in the game, rain specifically was at the fault of that.

    Go figure, of course it's something that 1.2 introduced and something that would be constant if it is raining.

    That then caused this new distorted audio everywhere.

Outro

https://www.youtube.com/watch?v=5SUMibgYAvM&t=285

Suggested Wiki Reference Code
Topics
  1. Mikael

    That then caused this new distorted audio everywhere.

    Those are, I think, the only two visible or audible weather fixes that were nasty and not uncanny, but unpleasant that we are fixing.

Rain Rendering & Community Resources

https://www.youtube.com/watch?v=5SUMibgYAvM&t=299

Suggested Wiki Reference Code
Topics
  1. Mikael

    As well as rain rendering.

    I mentioned this last week, but it's happening this week, I think, instead.

    Rain rendering plugin files are missing from community resources.

    If you need that, if you're a modder or whatever, then you're welcome.

State of Dev (Part 3)

https://www.youtube.com/watch?v=5SUMibgYAvM&t=313

Suggested Wiki Reference Code

Escalations (Part 1)

https://www.youtube.com/watch?v=5SUMibgYAvM&t=313

Suggested Wiki Reference Code
Intro

https://www.youtube.com/watch?v=5SUMibgYAvM&t=313

Suggested Wiki Reference Code
Topics
  1. Mikael

    We also had a couple of escalations.

    I talked a little bit about escalations last week and what an escalation is in this context is that we plan content, we ship content and

    both before and after shipping content, in this case to eXp, we have our own internal plan or map of, okay, we want to fix this, we want to do this.

    And then escalation is if we notice that either internally, oh shit, an issue is a lot more pressing than we gave it credit for, we need to bump this up the list, which essentially is what that is, escalation.

    You bump an issue that existed with a certain priority on the list up higher on the list.

    And escalation can happen, again, because we realize this is way more important and heavy than we thought it would be, or because you guys are like, dude, how can you ignore this for so long?

    Like, this is clearly an issue.

    Either for bugs or, you know, gameplay experience, or just for what you guys could consider fun.

    Even though it is working, as intended by us, you guys are like, it would be a lot better if it's like this instead.

    And so we're like, okay, we hear you, and community especially, and QA in this case, are usually the ones to escalate stuff that you keep repeating, because we both, we hear you, and we might even agree with you.

Daisy-Chaining

https://www.youtube.com/watch?v=5SUMibgYAvM&t=395

Suggested Wiki Reference Code
Topics
  1. Mikael

    And so we're like, okay, we hear you, and community especially, and QA in this case, are usually the ones to escalate stuff that you keep repeating, because we both, we hear you, and we might even agree with you.

    And in this case, I am agreeing with you.

    And you might already know, realize from last week, that I am about to mention daisy chaining on EXP again.

    Because I agree.

    Making a new save file would be nicer, even nicer, than it already is.

    If you could daisy chain much earlier in the game.

    People... Mark 2 power poles and Mark 3 power poles and chaining now being below Mark 3 on the Catherian tree.

    Power poles...

    don't really lose all of their use cases.

    They do have niche use cases.

    I forget, god, what are they called?

    Power switches?

    Whatever.

    Power poles, they do have use cases, even if we were to move daisy chaining up from below the MK3 power pole to above the MK3 power pole.

    Maybe even, maybe even above the MK2 power pole.

    so we wouldn't like outright delete power posts it would also just crush factories left right and center if we did that so don't worry they are not going anywhere um direction and production has agreed and promised that they are looking into looking into the merits of moving data chaining most likely higher than mark 3 probably not above mark 2 which is okay okay

    As far as I could get for now, Jack.

    And even then, that may also not happen.

    It has been promised, it has been the single feedback point, specifically pertaining to 1.2.

    Of course, there are more general game-wide feedback or issues.

    Stuff like architecture, walls, foundations, circles, triangles, that we always keep bickering about.

    But for 1.2 content in particular, in this case, daisy chaining is what they have agreed to give a closer look, because we kind of want to, we kind of need to, lock in on exactly what will make it in for the final version of 1.2.

    Down the line because it is I mean in the context of the pipeline of content coming out 1.2 live is soon soon enough So we don't have infinite time to address every issue or every point of feedback that we would like to or you would like to for this estimation that we have in house at the moment and

    But daisy chaining is the one thing that they have promised to try to cram in with a bunch of other mostly internal stuff that we want in as well.

    So, below Mark II is a good trade-off?

    Honestly, personally, I would like it to be baseline, but I can also see the argument for that being...

    I don't want to say broken chat, because...

    Again, power poles, they still have their niche use cases.

    Yes, maybe it should not be, like, available before the Mark I power pole, so, like, basically from the moment you step out of the drop pod or as close as.

    But I don't know, like...

    Satisfactory, like...

    Yeah, logistics challenges.

    Yeah, design challenges.

    Yeah, options with wall or roof placed power nodes.

    But like, this one is so, so overwhelmingly more comfortable to play with, dayshading that is, that it's worth the trade-off of making the game quote-unquote easier to manage or easier to play, like,

    Yeah, if the game becomes easier, if the game becomes a bit more braindead, in this context, who cares?

    Like, if you do, all the power to you.

    I don't know, I feel like this trade-off is, to me specifically, like, definitely worth pushing all the way, whenever.

    I don't, again, it's not gonna be even above Mark II, most likely.

    um for live and heck again maybe not even above mark 3 but but why debates we can have eternally in the office

    Because we have that and a million other things going on.

Outro

https://www.youtube.com/watch?v=5SUMibgYAvM&t=677

Suggested Wiki Reference Code
Topics
  1. Mikael

    And honestly, that is mostly it for State of Dev.

    We are very happy with how 1.2 is unfolding, both out in the public, on streams and shit.

    For EXP.

    Thank you for all the content created in its wake.

    We are seeing all the videos, I think.

    We are following streams.

    Oh my god.

    Oh my god.

    How?

    How could we?

    How could Coffee City Studios create a vehicle with an actual booty?

    It happened.

State of Dev (Part 4)

https://www.youtube.com/watch?v=5SUMibgYAvM&t=706

Suggested Wiki Reference Code

Escalations (Part 2)

https://www.youtube.com/watch?v=5SUMibgYAvM&t=706

Suggested Wiki Reference Code
Q&A: FOV fix for super-wide monitors?

https://www.youtube.com/watch?v=5SUMibgYAvM&t=706

Suggested Wiki Reference Code
Topics
  1. Mikael

    a very pretty man thank you thank you i'm sure you are too can we make a semi truck a pretty man or woman by the way fov fix for super ultra wide monitors has been escalated has been uh actually that's a good shot where is that in the i'm not gonna check it now but that may have moved in the bug prior list ah i should i should have checked in about that today

    But they took it.

    They took it.

    I mean, that's the biggest thing that I shouted last week.

    So, it has gone somewhere.

    I just don't know where.

    We'll see.

    We shall see.

Q&A: Is 1.2 being released today?

https://www.youtube.com/watch?v=5SUMibgYAvM&t=740

Suggested Wiki Reference Code
Topics
  1. Mikael

    Is 1.2 being released today?

    No, the EXP branch is getting an update, mostly a technical and crash fixing one, and any weather effects, any effects on gameplay or like visible updates you will see will be weather related.

    I might be missing small stuff, both technical and gameplay, but again, patch notes written will be out by UZU, and they are always, always way more comprehensive.

    On Reddit, Discord, Steam, all the good places, so you'll see them the second the patch is out.

    We'll push 1.2 to the main branch if we can send him a pile of Pepsi Max.

    If it staves off my hunger.

    No.

Community FYI: Apart from some crashes I got with pathing etc., I have to say 1.2 is amazing

https://www.youtube.com/watch?v=5SUMibgYAvM&t=781

Suggested Wiki Reference Code
Topics

    Outro

    https://www.youtube.com/watch?v=5SUMibgYAvM&t=787

    Suggested Wiki Reference Code
    Don't expect anything related to 1.3 / DLC / future plans any time soon

    https://www.youtube.com/watch?v=5SUMibgYAvM&t=787

    Suggested Wiki Reference Code
    Topics
    1. Mikael

      Apart from some crashes I got with tractor pathing etc, but I have to say that 1.2 is amazing Chat we are like I'll just also say right now before we move into highlights that It's gonna be a little of a it's gonna be a bit of a like boring boring drop for all of April

      for all of April, at least for all of April, upcoming month now, if you are tuning into these streams hoping to get even a sliver, a little hint of a supposed 1.3 or bigger update,

      Unless I'm feeling very mad at Emmet for whatever particular reason, and right now I have no reason to be, nothing is gonna be even shadowdropped or anything on these streams.

      I'm not going to crack anything about 1.3, supposedly, or the DLC, supposedly, or this bigger special update, supposedly, in April at the very least, so...

      If you tune in for that, I'll just save you your precious time, and you can go watch the Race to World first in WoW instead.

      I really hope they start pulling Beloran, and even, I mean, if they reach Lura tonight, then please pull her too.

      Because I am dying to see how hard or easy that boss will be.

      Midnight's being very interesting to watch so far.

      Still not playing.

    But maybe... (Part 1)

    https://www.youtube.com/watch?v=5SUMibgYAvM&t=870

    Suggested Wiki Reference Code
    Topics
    1. Mikael

      The one thing I will say, chat.

      The one thing...

      I will maybe giga, giga breathe, giga whimper breathe about what's coming next.

      Don't run with this, chat.

      Don't run with this.

      And it's nothing that the devs themselves are deciding on, okay?

      It's not like they are sitting down and are like, this is next.

      This is next.

      This is purely, purely a community thing right now.

      This is purely Jason and Linus and I going to the meetings and being like, yo, it's about fucking time.

      That they get some new architecture.

      Again, that doesn't confirm you're getting it.

      That doesn't mean anything.

      But it is what we're fighting for.

      So I am hoping, hoping to the high heavens, that we can move that car somewhere soon.

      I'm fighting on your behalf, chat.

      Like, I always have been.

      But I've been, I've been, bluntly...

      Huh.

      It's not like I feel like I have slacked in bringing feedback from you guys to the devs, because I haven't.

      But I do think I have, just looking back on old logs, listening in, talking a lot with Uzu and Guru lately, a lot with QA lately, just listening in on the times for when Jace and Snoot were here.

      Jace and Snoot were apparently very...

      very persistent on your behalf.

      Like, they didn't immediately walk away after a single no.

      And I feel like, maybe not after one no, but two or three, I could have been like, you know what, maybe I shouldn't make anyone mad about this and whimpering away.

      I think it's time for me to start tanking a few more no's before I die.

      So, that's kind of where I will fight for you guys.

      I'm speaking slowly to make sure that I don't actually overspeak.

      I have nothing to always speak on, again, nothing is clear in terms of what's coming beyond 1.2 for you guys in what order.

      But depending on how I form myself or word myself, people are going to start taking my word as gospel.

      Anyway, I should probably leave it there.

      That's all I dare tell you today, chat.

    Outro

    https://www.youtube.com/watch?v=5SUMibgYAvM&t=787

    Suggested Wiki Reference Code

    Transcription omitted.