Echo Soft-lock (Watcher)

[dusty pine]

(Minimal spoilers)
I can play Watcher's campaign until a certain point, where it soft-locks.
Upon meeting the third echo in the first part of the campaign, it will 'teleport' me, and send me to a loading screen. The classic black screen with 'Loading...' in the bottom left. I basically load indefinitely after the third echo, all echoes beforehand create no issues. Note that it does not matter which order I go in. The only way I am able to exit the loading is to exit the game manually, via Task Manager or Alt-F4. This makes the campaign entirely unplayable past that certain point.

I have tried the following: Restarting save file, verifying file integrity, reinstalling the game entirely, etc. I have deleted my save on the Watcher's campaign multiple times, and the soft-lock persists.

I do not believe there are any mods causing this, as everything else works fine except in the Watcher. Hence why this isn't in any of the modding support channels. I'm only adding the MSC tag because I do have it enabled, if it provides any important information.

I don't know how to collect logs as a whole. If anyone is able to tell me how to get them I would appreciate it. Thank you.

[brazen thorn]

;exceptionlog

[charred moss]

The exception log contains details about where in the code the exception occurred, useful to debug an error. It may be found in the game's root folder, along with the executable. Launching the game clears the file; if you have done so after getting the exception, you will need to trigger the error again to regenerate the log. If, even after doing so, the exception log doesn't exist, it's useful to provide this.

Default Steam path on Windows:
C:\Program Files (x86)\Steam\steamapps\common\Rain World
In Steam, you may open the game's folder with Right Click -> Properties -> Installed Files -> Browse..

To send the file, drag and drop it into the Discord window. Do not copy and paste the contents of the file.

The file provides the function which threw the exception in the code, as well as all of its ancestors down to the main. If the exception is generated by a mod or combination, typically they will be near the top, marked as modifying the recently-called functions. Disabling them may fix the issue.

[dusty pine]

Going to try to do this, real quick. One moment.

Okay. So apparently it was one of my mods. I turned them off to prevent clutter in the log (If that's how it works, I don't know) and it loaded fine. I should have tried this earlier. Apologies.

[brazen thorn]

ah, do you know what mods it could've been?

[dusty pine]

Nope. I turned everything off except the Downpour and Watcher mods.