Mutagen-Modding / Synthesis

A patcher pipeline framework and GUI. Run collections of code-based mods to create content customized for your load order
GNU General Public License v3.0
245 stars 18 forks source link

Synthesis Error on any patch. Method Not Found: Mutagen.Bethesda.GameCategory #413

Closed DCDogWalks closed 1 year ago

DCDogWalks commented 1 year ago

Discussed in https://github.com/Mutagen-Modding/Synthesis/discussions/412

Originally posted by **DCDogWalks** August 12, 2023 I've run into a problem with Synthesis (latest version and previous version). Whenever I run it (I use MO2) it will error after a few seconds with the same error regardless of what patches I have added. Following is one of the error message (all seem to mention the bit in the subject line): `Running (""): "dotnet" "run --project \"C:\Users\david\AppData\Local\Temp\Synthesis\2bb878d8-510a-4adb-bb95-00e8a35c3d60\Git\e6a9f730-2033-4be2-9524-70ed61204b33\Runner\SpellAbsorbFix\SpellAbsorbFix.csproj\" --runtime win-x64 -c Release --no-build run-patcher --DataFolderPath \"C:\Steam\steamapps\common\Skyrim Special Edition\Data\" --ExtraDataFolder \"D:\Skyrim Tools\Synthesis\Data\Skyrim Special Edition\spellabsorbfix\" --GameRelease SkyrimSE --ModKey Synthesis.esp --LoadOrderFilePath C:\Users\david\AppData\Local\Temp\Synthesis\2bb878d8-510a-4adb-bb95-00e8a35c3d60\Workspace\Synthesis\Plugins.txt --LoadOrderIncludesCreationClub --OutputPath \"C:\Users\david\AppData\Local\Temp\Synthesis\2bb878d8-510a-4adb-bb95-00e8a35c3d60\Workspace\Synthesis\1 - spellabsorbfix\Synthesis.esp\" --PatcherName spellabsorbfix" System.MissingMethodException: Method not found: 'Mutagen.Bethesda.GameCategory Mutagen.Bethesda.GameReleaseExt.ToCategory(Mutagen.Bethesda.GameRelease)'. at Mutagen.Bethesda.Synthesis.SynthesisPipeline.Run(RunSynthesisMutagenPatcher args, Nullable`1 exportKey, IFileSystem fileSystem) at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[TStateMachine](TStateMachine& stateMachine) at Mutagen.Bethesda.Synthesis.SynthesisPipeline.Run(RunSynthesisMutagenPatcher args, Nullable`1 exportKey, IFileSystem fileSystem) at Mutagen.Bethesda.Synthesis.SynthesisPipeline.<>c__DisplayClass43_0.<b__0>d.MoveNext() in D:\a\Synthesis\Synthesis\Mutagen.Bethesda.Synthesis\Pipeline\SynthesisPipeline.cs:line 472 --- End of stack trace from previous location --- at Mutagen.Bethesda.Synthesis.SynthesisPipeline.HandleOnShutdown(Func`1 a) in D:\a\Synthesis\Synthesis\Mutagen.Bethesda.Synthesis\Pipeline\SynthesisPipeline.cs:line 833 at Mutagen.Bethesda.Synthesis.SynthesisPipeline.Run(RunSynthesisMutagenPatcher args, IFileSystem fileSystem) in D:\a\Synthesis\Synthesis\Mutagen.Bethesda.Synthesis\Pipeline\SynthesisPipeline.cs:line 460 at Mutagen.Bethesda.Synthesis.SynthesisPipeline.<>c__DisplayClass42_0.<b__1>d.MoveNext() in D:\a\Synthesis\Synthesis\Mutagen.Bethesda.Synthesis\Pipeline\SynthesisPipeline.cs:line 432`
HeilingerKrest commented 1 year ago

Same! i use Vortex.

Tycoonman500 commented 1 year ago

this is happening due to changes made with version 0.42 of mutagen, setting the version to 0.41 or earlier allows patches to compile.

DABalke7 commented 1 year ago

I had the same issue until I updated to the latest version of the .NET SDK 7.0 via the link provided in the installation instructions screen, apparently the latest version of Mutagen requires the latest released version of .NET SDK to work properly.

Noggog commented 1 year ago

Should be fixed. Was just missing a new Synthesis version to go with the new Mutagen version. It's out now, though, so if you pair Mutagen v0.42 with Synthesis v0.26, it should work again