[0.29.2] Issues with Skyrim SE

[suamor]

Windows 11 Pro was updated today. C:>dotnet --list-sdks 6.0.424 [C:\Program Files\dotnet\sdk] 8.0.206 [C:\Program Files\dotnet\sdk]

Synthesis was updated from 0.27 today.

Generally I was able to use Synthesis (no crashes or general issues with patching), but I encountered several issues while using it:

• Having multiple patches, I had reproducable hangs either on preparing or network. Fixed when the patcher SynBookSmart was removed. This happened even when patchers where not active.
• Plugins that are not active are patched (SPERG-SSE.esp causes issue with one patcher). I need to fully uninstall and reinstall) (generally will cause missing master issues with mods that are temporarily deactivated) Workaround with MO2 is to remove the ESP in the mod settings
• Hangs when ending the program. Waited around 30min then killed synthesis and dotnet (does not happen always)
• No patcher was updated until I removed "Auto", switched between branch, tag and back. Update seemed to hang
• Sometimes from MO2 synthesis is not starting at all and I need to kill MO2 2.5.1rc2 (never had such a problem before). -> no synthesis logs, need to check MO2 logs as well

Logs: Everything.txt Everything.txt Everything.txt

Settings PipelineSettings.json (without SynBookSmart).

[Noggog]

Having multiple patches, I had reproducable hangs either on preparing or network.
Hangs when ending the program. Waited around 30min then killed synthesis and dotnet (does not happen always)

Feels like some dotnet jobs are getting stuck in the pipes, from the sound of it. I can see if i can add some more logging around certain operations to detect when this is happening better, but I think that'd just be an informational change -> not a fix.

Have you purged your synthesis temp folder at all? Might be good to do after a major update if you're having problems. %temp%/Synthesis

Plugins that are not active are patched (SPERG-SSE.esp causes issue with one patcher).

Disabling a patcher group A to run doesn't remove it from the LO. So if a later patcher group B is run solo, and patcher A's file is listed on the LO before it, it'll still consider the stale contents from A. A is just another mod on the LO, like any other.

https://github.com/Mutagen-Modding/Synthesis/wiki/Load-Order-and-Previous-Patchers https://github.com/Mutagen-Modding/Synthesis/wiki/Multiple-Output-Targets#running-with-multiple-groups

Generally I recommend running all your patchers at once in a single run. There's usually very little reason to only run half/some, and doing so can lead to staleness issues

[Noggog]

470