I was playing normally then saved and quit but when I came back to my world it returned to me with this error. Is there any way to recover it or fix it? This was the main save that I was playing on along with a few other autosaves. Have you ever seen this before and is there any way to prevent it?
[1.0.0] Corrupted FliudBoxIndex: no system 3825205248/24
[1.0.0] Corrupted FliudBoxIndex: no system 3825205248/24
Last edited by Froodys on Fri Nov 13, 2020 7:30 am, edited 1 time in total.
- NotRexButCaesar
- Smart Inserter
- Posts: 1133
- Joined: Sun Feb 16, 2020 12:47 am
- Contact:
Re: Corrupted FliudBoxIndex: no system 3825205248/24 [1.0.0(build 54889, linux64, steam]
What are those parentheses?
Ⅲ—Crevez, chiens, si vous n'étes pas contents!
Re: Corrupted FliudBoxIndex: no system 3825205248/24 [1.0.0(build 54889, linux64, steam]
It’s my signature on other forums websites but it didn’t work on this one
Re: Corrupted FliudBoxIndex: no system 3825205248/24 [1.0.0(build 54889, linux64, steam]
Is this still a bug report or an text-to-ascii showcase using FIre Font-k?
Code: Select all
) ) (
( /( ( /( ( )\ )
)\()) ( ( )\()))\ (()/(
((_)\ )\ )\ ((_)\((_) ((_))
| |(_) ((_)((_)| |(_)(_) _| |
| '_ \/ _ \(_-<| / / | |/ _` |
|_.__/\___//__/|_\_\ |_|\__,_|
Re: Corrupted FliudBoxIndex: no system 3825205248/24 [1.0.0(build 54889, linux64, steam]
Alright I’m just removing it lmfaoboskid wrote: Fri Nov 13, 2020 7:28 am Is this still a bug report or an text-to-ascii showcase using FIre Font-k?Code: Select all
) ) ( ( /( ( /( ( )\ ) )\()) ( ( )\()))\ (()/( ((_)\ )\ )\ ((_)\((_) ((_)) | |(_) ((_)((_)| |(_)(_) _| | | '_ \/ _ \(_-<| / / | |/ _` | |_.__/\___//__/|_\_\ |_|\__,_|
Re: [1.0.0] Corrupted FliudBoxIndex: no system 3825205248/24
I see all 3 save files failing to load when loading them in 1.0 but all of them are loading fine in 1.1. I was trying to narrow which change fixed it but it appears it was somewhere before 1.0 on a branch and i have no way to load that save file in older branches. For now i am moving this to resolved for next release, but if it would happen it was not fixed when 1.1 goes out then let me know and i will move topic back to bug reports.