V2.2 b3 Stable

I wouldn't have thought so, but people without mods installed are having the same issue. Verifying can help restore files that may have been missed during the initial update, however I am not 100% certain if it will work.
Thanks. I may have missed something someone said about these. All the posts I've seen have started out saying they had no mods installed, only to find out that they do and removing them solved the problem with the red Xs, which is why I lean towards it being a mod problem and the person doesn't realize they have mods installed. A lot of people think reinstalling the game, even uninstalling and reinstalling it, will remove mods. It does not.
 
Thanks. I may have missed something someone said about these. All the posts I've seen have started out saying they had no mods installed, only to find out that they do and removing them solved the problem with the red Xs, which is why I lean towards it being a mod problem and the person doesn't realize they have mods installed. A lot of people think reinstalling the game, even uninstalling and reinstalling it, will remove mods. It does not.
Getting my info from the Technical Support channel on the discord (you should totally join it by the way). Could very well be mods still, but verifying shouldn't hurt anything.
 
Any solution for the RED X's Other then uninstalling the mod?

WHAT is causing the red X's to appear when there is a backpack mod ??

@DEVS? @MODDERS?
 
I think it’s been pretty well stated that the mod needs to be updated to be compatible with 2.2. Just remove the mod and wait for the mod Der to update it before you put it back.
I realized as much but looking for a bit more then "reboot your computer Tech help"
I mod and I was wondering what CAUSED the issue so we can understand what has changed to cause it and what might be done to repair it. ;)
 
I realized as much but looking for a bit more then "reboot your computer Tech help"
I mod and I was wondering what CAUSED the issue so we can understand what has changed to cause it and what might be done to repair it. ;)
I would back up saves, maps & settings completely delete the game using the Game Launcher, then reinstall it.Screenshot 2024-07-26 184549.pngScreenshot 2024-07-26 184326.png
 
Last edited:
Thanks. I may have missed something someone said about these. All the posts I've seen have started out saying they had no mods installed, only to find out that they do and removing them solved the problem with the red Xs, which is why I lean towards it being a mod problem and the person doesn't realize they have mods installed. A lot of people think reinstalling the game, even uninstalling and reinstalling it, will remove mods. It does not.
I can understand your thinking this is to do with mods but I have independently confirmed it is not the case, at least not the entire case. I had mods on a dedicated server, if I connected to the dedicated server running the 2.2 update with the mods I got the X's; however if I was to launch a standalone 2.2 game the mods worked just fine so this doesn't really get us to a full gone conclusion but it does seem to indicate that the mods are not the whole of the problem, it seems there may be something with dedicated servers and mods, rather than just saying it is the mods.

Additionally, just making blanket statements to disable/remove mods can harm the game save. These mods may add new craftable items that should the mod(s) be removed will remove the game assets that depend upon them. These can be weapons, structures, and so on.

Rather than telling folks to remove the mods they have installed, the CORRECT instruction should be to roll back their game version to the last workable version, in this case v2.1 until all of the mods which you can't play without have been updated to the latest version.

EVERYONE, PLEASE STOP TELLING PEOPLE TO JUST REMOVE THE MODS!

They are coming here to ask for help, and they possibly have no idea what the consequences of removing the mods will do to their game, and every post I have seen here suggesting such action either indicates that those proposing the mods be removed either do not understand the implications themselves or simply don't mind giving bad advice to those seeking their help and guidance.

Same, no option for 2.2 stable yet in Steam. I don't think I've ever seen it take this long. Maybe tomorrow then.
Close down your Steam client, this includes the background (run minimized) processes; you may need to expand the caret symbol near your clock in the bottom right and exit steam. Once it is all fully closed reopen Steam and it will poll the update catalogs and should start any game updates.
 
And now we are at a point where the update drops without announcement on steam. And even one that breaks a popular backpack mod. Also breaks the quick stack mod.

Why no announcement on steam before the update drops? We would have stayed on V2.1 until the mods were updated.
 
This was to be expected. The update affects the fixation of items in the inventory, which means the mod needs to be updated.

Mods break, that´s expected, no worries with that. The no announcement part is what is bad. It was a 45MB update, not announced so people will assume it´s just a hotfix and not a mod breaking update. You can´t go back once you loaded your save in the new version and with a bit of bad luck it could have been breaking saves with certain mods making them unplayable after loading the new version.
 
Steam users:

On the Betas list, choose "None" to always remain on the current stable version. This will auto-update.

For long-term play, always lock into the numbered version on which your save was created. This will NOT auto-update.

This is not new stuff. It has always been this way on Steam, at least for the 8-9 years I have been around.

If your save was lost due to auto-update, that is on you.

I am surprised to see some vets just learning this well-known fact.
 
Last edited:
Back
Top