I just bought an Elegoo Saturn S and used ChituBox for slicing. I had sliced a couple of models but for some reason the printer stopped recognizing the .ctb files the other day. I sliced a model and started the print, but it failed. Then when I tweaked the settings and sliced again, the printer said that the file was an unrecognized file type. The file shows up and I can see the name and .ctb, but the image is a folder instead of the actual model. I sliced directly to the USB as well as sliced to the PC and copied the file over to the jump drive.
I looked online and saw that I should to downgrade from ChituBox 1.9.0 down to 1.8.something. Since I was using 1.9.2, I assumed that the former advice was out of date and didn't want to deal with downgrading since there's a whole process with log files and directories or something.
Another commenter said that the firmware may be out of date so I ensured that my firmware is up to date.
Another recommendation was to try a new USB stick since the one with the printer is garbage, but the problem persisted. I formatted both drives a couple of times and nothing worked. I've switched to Lychee which sliced files that the printer actually recognized as files.
While the blaring answer is "Just use Lychee, duh!" I am curious if there is a fix/workaround for ChituBox in case this pops up again.
Update: Well, this seems to happen with Lychee now too. I slice a file and the printer still recognizes that the file exists including the .ctb filetype and it shows a folder instead of a preview of the model. When I go to print, the printer says "Unrecognized file extension." This happens with the jump drive that came with the printer. The second jump drive I use doesn't even get recognized by the printer. Everything is blank when I plug it in. From my limited research, allegedly the Saturn doesn't do well with USB 3.0 for some reason.
Resliced files and sliced new files using both Lychee and ChituBox on two brand new, USB 2.0 16 GB jump drives of differing brands. I was informed that perhaps the size of the jump drive may be a problem. Both jump drives are using FAT32, as recommended on an Elegoo forum. Problem persists.