Laveillon Posted October 13 Report Posted October 13 Greetings and also a quick apology not wanting to make a github account for a singular bug report, a few minutes ago, my Single Player world crashed because of lack of free space in my C drive (random crap always fills it up, always an uphill battle). I was glad to see that the world itself did not get corrupted, nor damaged, but the boat i was in completely disappeared. Hit /gm2 to scout the area quick, hoping it just sailed away, but nope. Like it never existed before. Nothing that i can't re-create, but i'm stranded ~11kms away from my home and the trek there will grind my soles away. Cheers, Laveillon
Laveillon Posted October 13 Author Report Posted October 13 Damn it, lost The Lantern... the one with the electrum lining.
Kreeate Posted October 13 Report Posted October 13 Best suggestion would be to go into creative mode, add the items required and jump back into survival. Always make sure that you have enough space for your world saves. 1
Laveillon Posted October 14 Author Report Posted October 14 I know the miss on the clean-up is my fault, but not the boat disappearing. I'd say that's quite a problem, but the subject of this post is that i don't want to create another account just to make a bug report. A boat you are currently sitting in should not disappear, just because the game has a failsafe built in. Band-aid proposals, while appreciated, won't help future cases like mine and i intend to bring awareness of this slim, yet possible outcome.
Kreeate Posted October 14 Report Posted October 14 If you want to use a different drive than C for your world saves, you can try the below: Vintage Story stores worlds inside its user-data folder, in the Saves subfolder. To move the default location, launch the game with a custom data path. On Windows: Create the folder you want to use, such as D:\VintageStoryData. Make a shortcut to Vintagestory.exe. Right-click the shortcut → Properties. In Target, add this after the executable path (outside the closing quote): --dataPath "D:\VintageStoryData" For example: "C:\Games\Vintage Story\Vintagestory.exe" --dataPath "D:\VintageStoryData" Start the game using that shortcut. It will create/use the new data folder; worlds will be saved in D:\VintageStoryData\Saves. To keep existing worlds, close the game and copy the contents of your current VintagestoryData\Saves folder into the new folder’s Saves folder. The default Windows data folder is %APPDATA%\VintagestoryData On Linux or macOS, the data folder can also be changed with the --dataPath startup argument; how you add it depends on how you launch the game.
Kreeate Posted October 14 Report Posted October 14 1 minute ago, Laveillon said: I know the miss on the clean-up is my fault, but not the boat disappearing. I'd say that's quite a problem, but the subject of this post is that i don't want to create another account just to make a bug report. A boat you are currently sitting in should not disappear, just because the game has a failsafe built in. Band-aid proposals, while appreciated, won't help future cases like mine and i intend to bring awareness of this slim, yet possible outcome. It's not a bug. Your boat disappeared because the game crashed due to not enough hard drive space. How is this a bug in the game?
Laveillon Posted October 14 Author Report Posted October 14 Okay, let me rephrase my point. Every entity in the world is intact, except the boat that disappeared. That shouldn't be the case. If every entity, animals and other targed dummies also disappeared, then i'd understand, but Just the boat? Why? I'll admit i'm not well versed in programming, but if everything else could be restored, why not the boat? Was that part of my character's entity and got lost during relog? If so, why can't be the boat it's own entity? I'll look into moving my save folder, that advice is nice, thanks for that!
Teh Pizza Lady Posted October 14 Report Posted October 14 You'll get generic responses because this is a public forum. The proper channel to reporting issues like this is to create an issue on the github, which is the one task you said you were initially unwilling to make. Unfortunately, that is the proper way to do it as that is the only method of reporting bugs now if you do not wish to join their Discord server either. See here:
MKMoose Posted October 14 Report Posted October 14 14 minutes ago, Laveillon said: Every entity in the world is intact, except the boat that disappeared. That shouldn't be the case. If every entity, animals and other targed dummies also disappeared, then i'd understand, but Just the boat? Why? I'm failing to find the technical explanation for it now, but if I recall correctly the issue was that newly-generated chunks were saved immediately with the entity and older chunks were only updated on autosave, which causes the same entity to be saved multiple times in the same world if the game crashes, which in turn causes conflicts when the game tries to load the same entity twice. Take it with a grain of salt, because I might be misremembering that from one of Zaldaryon's comments. Other entities are fine because they've been saved to disk earlier so the crash cannot affect them. The issue is tracked by GitHub Issue #7298 and should be fixed for 1.23. 1
Laveillon Posted October 14 Author Report Posted October 14 I see that this is already known, thanks for linking the issue. And i'm also glad i didn't open a duplicate ticket.
Zaldaryon Posted October 14 Report Posted October 14 7 hours ago, Laveillon said: I know the miss on the clean-up is my fault, but not the boat disappearing. I'd say that's quite a problem, but the subject of this post is that i don't want to create another account just to make a bug report. A boat you are currently sitting in should not disappear, just because the game has a failsafe built in. Band-aid proposals, while appreciated, won't help future cases like mine and i intend to bring awareness of this slim, yet possible outcome. This is a known bug with lots of info in the github from anego studios issue tracker. They said it will be fixed in 1.23. The bug occurs when the boat/entity/elk changes chunks but the engine didn't have the time to update it in the world file and some crash happens. It happened in several servers. There is no mitigation to bypass that for now. For reference: https://github.com/anegostudios/VintageStory-Issues/issues/9697 1
Zaldaryon Posted October 14 Report Posted October 14 6 hours ago, MKMoose said: I'm failing to find the technical explanation for it now, but if I recall correctly the issue was that newly-generated chunks were saved immediately with the entity and older chunks were only updated on autosave, which causes the same entity to be saved multiple times in the same world if the game crashes, which in turn causes conflicts when the game tries to load the same entity twice. Take it with a grain of salt, because I might be misremembering that from one of Zaldaryon's comments. Other entities are fine because they've been saved to disk earlier so the crash cannot affect them. The issue is tracked by GitHub Issue #7298 and should be fixed for 1.23. Oopsie, I missed this post. Yes, you were right, besides the issue number. But not all entities are fine. Boats and elks are the ones affected (basically, any entity you can mount on - I guess that could happen with modded mounts/boats as well). 1
Laveillon Posted October 14 Author Report Posted October 14 Many thanks for the reply, i've added the issue number in the tags field for better clarity. Nice to see that the peeps here are this friendly.
Recommended Posts