CANNOT PROGRESS CAMPAIGN

I'm stuck in Act III where you put the medium soul cores into the generators. Every time I interact with a generator it says 'Unexpected Error'. I've tried updated my GPU driver and reverifying files. Also, tried just restarting the instance and what not but I'm still stuck. Any ideas?

I’m having this same issue, very frustrating. Disconnects every time I try to place the core. Corrupted a belt and it’s gone now also.

I'm trying to redownload the whole game now... let me know if you find a way around it.

I’ve reset the map, tried leaving the area and came back and it keeps doing it. I give up for the night and will hope for an update. Goodluck!

Uninstalled and reinstalled the game with the same issue...this is infuriating. I cannot progress at all now. No idea what to do.

On the character selection screen, there is a "home/house" button next to the character name that will allow you to respawn in town/hideout, in case the game instance is borked.

I tried the respawn at town and went back to the machinarium and now all soul core placements are causing the crash and not just the medium ones into the generator.

It almost seems to be a bug with all interactions now. I tried to revive someone and was instantly kicked with the same unexpected disconnection.

Yup, interacting with the levers in the waterways is disconnecting too 'An unexpected disconnection ocurred.'

Lovely...unplayable character now lol idk if it's even worth it to make another or if I'll get trapped again...

I am also experiencing this issue. Ive tried everything I can possibly think of.

ran in every mode (windowed, fullscreen, window fullscreen)
ran at many different resolutions
tried different monitors in case my ultra wide was causing an issue
cleared shader caches
reinstalled whole game
tried some other stuff i didnt think would work really like going back to earlier acts and doing stuff there then returning.

Problem initially occurred for me at jiquanis sanctum with the medium soul cores.
One of them worked fine but the second one started causing this issue.

no idea what else to try now.