Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(+1)

Hey! Sorry for the trouble. 

Just making sure, what version of Sai2 are some of these files made on? It looks like there were some recent updates to Sai2 that might have changed how the file format works a bit, which I am still looking into at the moment and wanna be precise about what version you might be on. Do you see thumbnails for an Sai1 files you happen to have? Otherwise, are you installing the correct 64-bit version of SaiThumbs Particularly the one from the SaiThumbs-x64.zip file? Be sure to uninstall the previous version if you end up switching to the correct version to make sure there is no additional complexity. Generally the location of your Sai installation should not matter much, I personally have Sai2 installed on a separate drive as well, so that shouldn't impact the thumbnail generation. Though, it might matter what drive the SaiThumbs installation is on, and it will likely need to be located on a stable system-folder of some kind and not on an external drive.

It's alright, that one's on me—I forgot to mention I recently updated to the latest SAI 2 build (2026.07.04), which no longer supports exporting to the legacy .sai format. It does seem the update changed a few things here and there, nothing to do with your work.. Since regsvr32 completes successfully and returns DllRegisterServer succeeded, the issue likely isn't with the DLL itself or its registration, but rather with how the new file format is being written or interpreted by the thumbnail handler

 It's likely that my Sai2 code was not considering an edge-case in the file format that the latest version of Sai2 utilizes that I'll have to reverse-engineer. I notice some people on the GitHub page are running into similar issues, though with larger documents. Do your issues seem similar?
https://github.com/Wunkolo/SaiThumbs/issues/12

Either way, this may take a bit of time to reverse engineer!

(1 edit)

So the file type has actually stayed largely the same and shouldn't be effected by the new version. I've tested both Alpha.2026.09.02 and the 2026.07.04 build. I did fix this bug and updated the latest build to address that but it probably doesn't address the bug you're describing in particular. Are you still seeing this issue on the new version? Have you tried any other attempts to resolve it?