Needed for a relatively large project I’m progressing on, an un-uploaded place file I’m using as a sort of asset storage “workshop” has become unopenable, despite seeming to have been saved properly before I last closed it.
I had both it, and another, twice as big file open at the same time (taking up most my 4GB of RAM), and had tried to save the larger file (About 80k kb) before saving the smaller (now broken) one and closing them both.
If it is of any relevance, now the larger file still opens correctly, but the smaller “workshop” file returns this error when opened;
"We could not open the place “C:/Users/(Me)/Documents/SPH_R15 v1.3.1 AnimConv.rbxl”. readData error: "OK 0 bad 0 fail 1 gcount 33554384 readsize 39634882 offset -1 flength -1 freeKB 524308.000000 << compressed data << chunk#0 data
If you continue to encounter this error, please report it on the Developer Forum.
Incident ID: 8370966517588803688
"
even though the smaller file returned the regular “(filepath).here.rbxl has been saved” message in the output window before I closed it.
Is there any reference for what these error values mean, could the context in which it was saved have anything to do with it,
and is it possible to fix said rbxl file so that it can be opened again?
Any further clarification of the error output would be something I’m hoping to resolve, and if I end up corrupting my main file as well, I’m done for.
Thanks,
SpudJTB
Expected behavior
Had this not happened, the rbxl file would load as normal when opened
Hey, I’m sorry for the late followup! That error message means essentially that the file is truncated or otherwise corrupted. Can you give more context on what you were doing with the file when you started seeing this issue? Did you download it from anywhere, or do anything in particular the last time you saved it?
Hi, thanks anyway-
If I remember right, it was the smaller of 2 files which were being saved at the same time. Both files, and their previous iterations, originated only from my machine; the larger one (~80kb) saved successfully, and the smaller one (per this report) didn’t open afterwards even though they both printed as having saved successfully (so I know I didn’t kill the window early).
I’ve since found a recent enough autorecovery file, but what would cause this?
I’m glad to hear you found an autorecovery file! Unfortunately it’s difficult to speculate what might cause these issues, but we haven’t found any concrete evidence that points to it being a bug with Studio itself.
If you have a chance, could you send me the autorecovery file as well? Looking through it, and comparing the differences, might help me understand what happened.
I could send it, but I don’t think it’d be of much use as the autorecovery was 2 weeks and several versions behind the broken file. They’re too far removed to begin with
There are a number of reasons why the file might have been truncated, and it’s hard to speculate without more information. Because we can’t reproduce the issue, and we have no indication this is a Studio or engine bug (as opposed to a generic issue with a file being truncated), I’m going to close this report as “Cannot Reproduce”. I’m sorry for the unsatisfying conclusion, but thank you for the report.
I would always suggest backing up important work, and if you see this happen again, or find some way to consistently reproduce the issue, please let us know, and we will take another look!