[0.9.048-BACKER-ELECTRON#3207] Imagepack check fails

KignOhzar

New Member
Apr 7, 2023
1
0
"Determining Image Pack Status" never changes, tested up to 30 minutes, restarting does not change this. This also prevents using the uninstall option in settings to clear the download cache. On start "Image pack installed and available" does still pop-up in the top right corner. This did not occur while moving to 0.9.046, where new images were installed successfully.


1680829740356.png
 

Gedan

BUTTS BUTTS BUTTS
Staff member
Aug 26, 2015
8,008,906
8,008,325
There's probably an error happening somewhere in the electron process; the best bet to get me some useful information will be to start the game executable through the command line, which will then capture the messages being spat out as part of the downloading process.
 

Shade177

New Member
Jun 3, 2023
2
3
23
I had this exact issue for the most recent backer version, 0.9.065 Electron #3675, and I think I found a work around. I just found where the imagepack was located and deleted the entire folder. Of corse it means reinstalling the entire imagepack but it does seem to work properly. For me it was located in C:\users\{username}\AppData\Roaming\tits if that helps any.
 

Oblivion9873

Member
Nov 4, 2019
7
0
27
I had this exact issue for the most recent backer version, 0.9.065 Electron #3675, and I think I found a work around. I just found where the imagepack was located and deleted the entire folder. Of corse it means reinstalling the entire imagepack but it does seem to work properly. For me it was located in C:\users\{username}\AppData\Roaming\tits if that helps any.
thanks, this solved it for me, I'm tempted to just do this every update in the future because the check can be so slow anyway
 

fiduciam

New Member
Dec 14, 2017
1
0
27
Hi, currently on version backer-0.9.082-linux/0.9.082-BACKER-ELECTRON#4204, can confirm it still happen.

Since I'm on Linux, I had to delete the ~/.configs/tits/ImagePack folder to "fix" that bug.

This seem to happen when launching a tits instance that is not the one that installed the image pack.

Here are a few pastes to help debug this issue :