Closed chisps427 closed 1 year ago
Ah, sorry - looks like you have a corrupted berry bush in your save game. For unknown reasons there is a remnant of a bery bush (its block entity, BlockEntityBerryBush) at a position where there is actually no berry bush. The issue was almost certainly already present before 1.18.4, but masked - previously it didn't cause any problems. It's now causing problems.
We will be fixing this as a priority, next build, and the team is working on getting that ready ASAP.
In the meanwhile, if you're playing single player, re-downloading game version 1.18.3 should solve the problem for now. 1.18.3 and 1.18.4 savegames are fully compatible with each other. For mulltiplayer, however, your options will depend on what the server does.
Some other things to try:
At the main menu screen, in Settings, Graphics, turn down your view distance a lot, to something like 96 blocks, maybe even less than that if 96 blocks is still crashing. Now join the game. Don't move. Hopefully no crash. Assuming you didn't crash already, turn around and move away from the direction you were headed, retrace your steps instead. You may need to try 2 or 3 times to figure out which direction to move in, we don't know the coordinates of this corrupted berry bush.
Similar to (1) above, but try a teleport command as soon as you join the game, to teleport yourself far from this spot. e.g. /tp 0 160 0
will normally take you to some point in the air above (or close to) the original spawn. /gm 2
to put yourself into Creative Mode temporarily so you don't die from fall damage.
(Use with caution, may make things worse!) If you're in a part of the map where you didn't build anything anywhere nearby (to be safe I suggest you need to be more than 300-500 blocks away from anything you built) then you may be able to fix the corrupted berry bush by running a /wgen regen 5
command, assuming you can successfully join the game for long enough to run a command. I don't know the correct number there, you might start small like 3, then if that doesn't fix it try 5, then try 7 etc. More than 7 starts to get very slow, you may have to be patient. I don't recommend using numbers much higher than 7, it might take forever or cause other issues. At least one person has said, however, that this didn't help as the newly worldgenned chunks also had a corrupted berry bush.
Hope one of these things helps most people
This happens to me too, but happens as soon as I load in, so I actually can't play on that world at all.
Just want to make clear that this also happens in brand new 1.18.4 worlds. for me at least.
We are working on a solution urgently
I've got this problem too... my friends playing some 100 blocks away from my plot don't have this problem. please help.
can confirm berry bush chunks are instantly crashing our base, but seems like the rest of the world is alright
can confirm berry bush chunks are instantly crashing our base, but seems like the rest of the world is alright
i've placed a lot of berry bushes in my base, does this problem only occur with naturally generated bushes or the ones placed by players?
I know it can occur with naturally generated berry bushes. I do not know if it also happens with player-placed ones. I'm going to guess whether or not a player places it is probably not directly related to the issue.
i've placed a lot of berry bushes in my base, does this problem only occur with naturally generated bushes or the ones placed by players?
both, new worlds where naturally generated ones are, and hand placed ones on old worlds are both crashing it
If you're swimming in a part of the map where you didn't build anything anywhere nearby (to be safe I suggest you need to be more than 300-500 blocks away from anything you built) then you may be able to fix the corrupted chunk by running a /wgen regen 5 command, assuming you can successfully join the game for long enough to run a command. I don't know the correct number there, you might start small like 3, then if that doesn't fix it try 5, then try 7 etc. More than 7 starts to get very slow, you may have to be patient. I don't recommend using numbers much higher than 7, it might take forever or cause out of memory issues etc.
Following these instructions on another world where I encountered the error while running around, doing the re-gen, actually caused the client to crash and now I can't load in to that world either. So I'm guessing a corrupted berry bush was generated when running the regen command.
- u didn't crash already, turn around and swim away from land, and just avoid that land area for now. You may need to tr
Following these instructions on another world where I encountered the error while running around, doing the re-gen, actually caused the client to crash and now I can't load in to that world either. So I'm guessing a corrupted berry bush was generated when running the regen command.
uh oh! I'll edit the instructions to say use with caution!
The team's intention is that we will be putting up a new game version ASAP to fix this - I hope this evening. Until then, if the suggestions 1, 2, 3 above don't already help, I'm afraid it's just a question of being patient, or else trying a different save.
The team's intention is that we will be putting up a new game version ASAP to fix this - I hope this evening. Until then, if the suggestions 1, 2, 3 above don't already help, I'm afraid it's just a question of being patient, or else trying a different save.
I'm out of spare saves now though! lol. Will just have to wait until it's fixed now.
If you're playing single player a downgrade to 1.18.3 will fix it for today, I should have said that at the beginning.
I am, so I'll try that out. Thanks!
We will have a Vintage Story version 1.18.5 fixing this, in the next few minutes. Look out for an announcement in #news on Discord
Game Version
v1.18.4
Platform
Windows
Modded
Modded
SP/MP
Singleplayer
Description
Updated to 1.18.4 and now I'm getting a repeated client thread crash when approaching a certain place on the map. It takes a few seconds after loading back into the game, but the game crashes without fail with no interaction now that I'm in the location. My world save is effectively softlocked at the moment.
The only mod that I'm using is Plains and Valleys v1.02: https://mods.vintagestory.at/show/mod/4522
The log also appears to reference a memory leak issue on certain textures. The texture id is incrementing by 1 each crash (???) starting at id 48, then 49 and 50.
Crashes at timestamps 7:11:40, 7:13:05, and 7:23:47 in client-main.txt log attached
How to reproduce
Screenshots
No response
Logs