Larian Studios Forums Baldur's Gate III Baldur's Gate III - Technical & Gameplay Problems Hotfix #7 [Blocker] Act 1: Voss cutscene causes crash when changing zones

In Act 1 Mountain Pass:

I resolved the Creche quest in the Mountain Pass so when I attempt to leave the map, either by clicking on the zone lines or by fast traveling to another map, the game teleports me to the nighttime Mountain Pass Camp so I can have the Voss cutscene.

Upon finishing Voss' cutscene, the party wakes up the next morning and any attempts to leave the camp will crash the game consistently (at 33~66% load screen usually).

It does not seem to matter where I originally tried to leave the Mountain Pass from, or what waypoint I was trying to teleport too - it consistently crashes each time.
It feels like after the cutscene ends it forgets where I was trying to go.
This cutscene cannot be avoided when attempting to leave the zone, so I'm effectively trapped in the Mountain Pass.

___

I already submitted this bug with a save file, but I'm hoping to find someone else experiencing this so I can narrow down what might be causing it?

I'm playing Dark Urge and had recently rested several times to get the owlbear before my planned return to the underdark, but I tried loading before those rests and attempted to leave the mountain pass and it would still force the Voss cutscene and its crashes.

Edit: Still blocking progress in Hotfix #7 Version: 4.1.1.3735951
Submitted a new bug report for new game version:
https://larian.com/support/faqs/how-to-submit-a-bug-report_85

I'm having the exact same issue as a Paladin Oathbreaker Dark Urge, except that I load up to 67% before the game crashes.

I can still get the Voss cutscene going back everywhere else in Act 1, but then going in Act 2 through the Mountainpass or through the Grymforge area both crashes the game.
Additional Long Rests do not fix the issue.

I had a save right before the end of the Crèche, , and managed to leave the crèche and load Act 2 properly without triggering Voss' cutscene.
My thought process was to load it in and hope having it saved in the cache would help, and reached the closest waypoint so I can go back and finish the Crèche and fast travel to it instead.
But instead, the game now crashes when loading the Mountainpass area but not any other part of Act 1, which seems to be a similar issue other people are experiencing currently when trying to go back to a previous act or area.

TLDR: Voss' cutscene or something in the very last room of the Crèche is preventing going in Act 2, and going in Act 2 preemptively currently prevents going back in the Mountainpass area, making it impossible to finish the Crèche and keep playing.

To note: Unsure if related, but when traveling back to any other area of Act 1, or when approaching one of the possible paths back from Act 2 to Act 1, I'm also getting a Backpack with a Goodberry in it which I believe might be the belongings of Halsin as he doesn't show up in my camp anymore.

A small comfort knowing I'm not the only one then, but concerning that this happens even after you were able to load far enough back to enter Act 2 though...

I think I'll try loading a save just before meeting Vlaakith too, which should let me work on finishing the Grymforge while I wait for a fix to whatever is bugging the creche and Mountain Pass route.

I was hopeful that Hotfix #7 today would fix this when I saw that it addressed some misc issues when changing regions, but I've tried loading my save again and it still crashes same as before the hotfix.

Hotfix #7 Notes:
https://store.steampowered.com/news/app/1086940/view/3656415107310390368?l=english

No changes for this bug on my end - it's still blocking progress.

I am having the same issue also on Durge Oathbreaker. Finished the Creche and attempted to leave back to either the EG or the Myconid Colony and it triggers the Voss Cutscene in the mountain pass camp, then any attempts to leave camp or fast travel cause a game crash on load ~33% through.

Really bumming me out as I can't seem to continue my Durge playthrough until this is fixed