wabbajack
wabbajack copied to clipboard
wabbajack-cli vfs-index command crashes when indexing Fallout 4 GoG release
I brought Fallout 4 GOTY on GoG. It is not quite the same as the Steam edition for a variety of reasons.
I ran the following command
.\wabbajack-cli.exe vfs-index -f "F:\gog games\Fallout 4 GOTY\"
It crashed with following output.
at Wabbajack.RateLimiter.Resource`1.Begin(String jobTitle, Int64 size, CancellationToken token) in c:\oss\Wabbajack\Wabbajack.RateLimiter\Resource.cs:line 66
at Wabbajack.VFS.Context.<>c__DisplayClass20_0.<<AddRoots>b__4>d.MoveNext() in c:\oss\Wabbajack\Wabbajack.VFS\Context.cs:line 77
--- End of stack trace from previous location ---
at Wabbajack.Common.AsyncParallelExtensions.<>c__DisplayClass2_0`2.<<PMapAll>b__0>d.MoveNext() in c:\oss\Wabbajack\Wabbajack.Common\AsyncParallelExtensions.cs:line 34
--- End of stack trace from previous location ---
at Wabbajack.Common.AsyncParallelExtensions.PMapAll[TIn,TOut](IEnumerable`1 coll, Func`2 mapFn)+MoveNext() in c:\oss\Wabbajack\Wabbajack.Common\AsyncParallelExtensions.cs:line 36
at Wabbajack.Common.AsyncParallelExtensions.PMapAll[TIn,TOut](IEnumerable`1 coll, Func`2 mapFn)+System.Threading.Tasks.Sources.IValueTaskSource<System.Boolean>.GetResult()
at Wabbajack.Common.AsyncParallelExtensions.ToList[T](IAsyncEnumerable`1 coll) in c:\oss\Wabbajack\Wabbajack.Common\AsyncParallelExtensions.cs:line 198
at Wabbajack.Common.AsyncParallelExtensions.ToList[T](IAsyncEnumerable`1 coll) in c:\oss\Wabbajack\Wabbajack.Common\AsyncParallelExtensions.cs:line 198
at Wabbajack.VFS.Context.AddRoots(IEnumerable`1 roots, CancellationToken token, Func`3 updateFunction) in c:\oss\Wabbajack\Wabbajack.VFS\Context.cs:line 74
at Wabbajack.VFS.Context.AddRoot(AbsolutePath root, CancellationToken token) in c:\oss\Wabbajack\Wabbajack.VFS\Context.cs:line 62
at Wabbajack.CLI.Verbs.VFSIndex.Run(AbsolutePath folder) in c:\oss\Wabbajack\Wabbajack.CLI\Verbs\VFSIndex.cs:line 29
at System.CommandLine.NamingConventionBinder.CommandHandler.GetExitCodeAsync(Object returnValue, InvocationContext context)
at System.CommandLine.NamingConventionBinder.ModelBindingCommandHandler.InvokeAsync(InvocationContext context)
at System.CommandLine.Invocation.InvocationPipeline.<>c__DisplayClass4_0.<<BuildInvocationChain>b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass17_0.<<UseParseErrorReporting>b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass12_0.<<UseHelp>b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass22_0.<<UseVersionOption>b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass19_0.<<UseTypoCorrections>b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<<UseSuggestDirective>b__18_0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass16_0.<<UseParseDirective>b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<<RegisterWithDotnetSuggest>b__5_0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass8_0.<<UseExceptionHandler>b__0>d.MoveNext()
This is on Windows 11 Version 22H2
Wabbajack Version 3.2.0.1
A log file was not produced for this crash, so I generated one asking for wabbajack to tell me what games it finds. You can see it detects both Steam and GoG installs of Fallout 4.
Marked as stale due to no interactions in the last 90 days. If the issue still exists, please provide any possibly still needed information or excuse the devs for not getting around to addressing this issue yet. If this issue is still considered unsolved a dev will soon remove the stale tag from this issue.
Marked as stale due to no interactions in the last 90 days. If the issue still exists, please provide any possibly still needed information or excuse the devs for not getting around to addressing this issue yet. If this issue is still considered unsolved a dev will soon remove the stale tag from this issue.
Closed due to inactivity. Please create a new issue if this problem has come up again and no dev has reopened this issue after a week of it being marked as closed.