zhongjiedong / Tsukiro

MIT License
25 stars 6 forks source link

Unable to download KS Hairdo SSE BSA #152

Closed dnash90 closed 2 years ago

dnash90 commented 2 years ago

What happened?

tried with network workaround as well!

--- End of stack trace from previous location --- at Wabbajack.Lib.Downloaders.WabbajackCDNDownloader.State.<>cDisplayClass9_0.<b0>d.MoveNext() in C:\Wabbajack\splitwork\wabbajack\Wabbajack.Lib\Downloaders\WabbajackCDNDownloader.cs:line 123 184.03 - Loading for alternative to faA/BCit+M8= 184.03 - No alternative for faA/BCit+M8= could be found 184.14 - Hashing Remaining Archives 184.14 - Looking for files to hash 184.35 - Found 2280 total files, 1290 matching filesize 196.8 - Unable to download KS Hairdos SSE BSA.7z (WabbajackCDNDownloader+State|https://authored-files.wabbajack.org/KS Hairdos SSE BSA.7z_82a1ab0e-5618-4751-8a51-7d2192d953b6) 196.8 - Cannot continue, was unable to download one or more archives 196.8 - Encountered error, can't continue - System.Exception: Cannot continue, was unable to download one or more archives at Wabbajack.Lib.AInstaller.Error(String msg) in C:\Wabbajack\splitwork\wabbajack\Wabbajack.Lib\AInstaller.cs:line 71 at Wabbajack.Lib.MO2Installer._Begin(CancellationToken cancel) in C:\Wabbajack\splitwork\wabbajack\Wabbajack.Lib\MO2Installer.cs:line 161 at Wabbajack.Lib.ABatchProcessor.b66_0() in C:\Wabbajack\splitwork\wabbajack\Wabbajack.Lib\ABatchProcessor.cs:line 177 at Wabbajack.MO2InstallerVM.<>cDisplayClass31_0.<b0>d.MoveNext() in C:\Wabbajack\splitwork\wabbajack\Wabbajack\View Models\Installers\MO2InstallerVM.cs:line 181 --- End of stack trace from previous location --- at Wabbajack.MO2InstallerVM.Install() in C:\Wabbajack\splitwork\wabbajack\Wabbajack\View Models\Installers\MO2InstallerVM.cs:line 175 at Wabbajack.InstallerVM.<>cDisplayClass88_0.<<-ctor>b__78>d.MoveNext() in C:\Wabbajack\splitwork\wabbajack\Wabbajack\View Models\Installers\InstallerVM.cs:line 391

Modlist version

Current

dnash90 commented 2 years ago

Got this working, now realizing many of the executable paths are looking for a "modding" folder in drive D: We can probably establish this ourselves - is that the intent?

zhongjiedong commented 2 years ago

yes they are not included and are because of that