I fixed the issue by disabling the 60 FPS cinematic unlock fix. So for people who use the 60 FPS cinematic unlocker and can't get past the opening cutscene world, disable it again and you should be able to play.
2018 and still having this problem. I'll be running around and then my character freezes. I'm currently in the Hinterlands and for the first quest there I couldn't get to the Crossroads from the nearest access point. I had to climb up a cliff to the lake campsite then slide down the cliff, go through the ruined area with all the Templars and Mages, then I was able to get to the Crossroads. I'm now trying to get to Solas's quest regarding the veil measurement devices, the first one that activates the continuation of the quest. I can't get near the area because it's like my character is stuck in a wall. I rotate between the characters and all have the same issue. I tried fast traveling to get out of there and then my game stopped loading and froze on the "TRAVELING" screen.
Here's my computer info:
Windows 10
Processor: Intel Core i5-4460 CPU 3.20 Ghz
RAM: 8 GB
System Type: 64-bit system, x64-based processor
BIOS: A13
DirectX Version: DirectX 12
NVIDIA: GeForce GTX 745
Okay, so I got the game for PC today after playing for years on PS4. I knew being in the Fade like that wasn't normal, so I looked around the entire area, and I found a path on the far side. If you face the stairs when you first end up there, go behind it and a little to the left, and you'll see a pretty wide gap in the mountains that is climbable. Follow it, and keep going until you get over the next hill of the mountain. You'll find yourself overlooking the second broken bridge of the tutorial path(the one after the one you fall through with Cassandra). Go left and follow the path back to the first bridge. It will take some Skyrim-style mountain climbing, but you can do it. Once you go far enough back to the start, the screen will go black, and the game will begin as normal(though the opening cut scene you were supposed to get earlier WILL be a little glitchy until your first choice). This is obviously not a proper FIX to the problem, since you still have to trek back, and it does take a bit, but if you spent hours on your character and don't want to lose them, this will at least save you from having to remake them, and give you a chance to save them.
2020, and the bug is still in the game. Reactivated the game last week (from STEAM) because "lockdown", created some characters to get a a feel. Now 8 days later, after a "new "origin launcher game will not let me create new characters, failing to load the cutscene after selecting race etc. No Old (previous game) saves loaded
funnily enough the games runs normally and without fault in all the existing saves, so I doubt it is my system or drivers ( or even the mods) , but this still quite dysfunctional piece of Software
which means I have the luxury of being able to play, but cannot create .....say a new male dwarf character or a Qunari which i have not tried at all.
Windows 10, 64bit
16GB RAM
Ryzen5 3600
Gforce GT1060 6GB, newest directX, Win 10 updated, newest graphics driver
2,5 GB HDD space still free
ran the repair tool, uninstalled/reinstalled already, erased cache data, erased program data (bothe for the origin launcher, uninstalled origin launcher, erased its %appdata% etc
there is also a secondary bug that after crashing the game cannot be restarted because "it is still running" (not according to windows but according to itself) ...Because windows has no idea what is running, and only Origin does. sooo yes, full reboot of the system
and before the reply goes into "We need DxDiagnosis" blather... here you go
Mods often cause this, always first step is to remove all mods repair game and retest. Also make sure you don't have any launch overrides such as 60fps cutscens set up. Since the game runs it isn't likely machine issue.
Done that, of course nothing happened and the mods work fine.
Plus the mods do not show up in the cutscene, just teh default dwarf/elf/human/qun because this is pre creation, so I doubt there would be any interaction. Nevermind them not affecting the game "running" (for purposes of restart) while it is not running at all
Just wanted to say that, after 10 years and with an absolute garbage "sequel", this bug still happens.
I started a new run with dozens of mods, but the culprit is still the FPS unlocker.
Remember, it's the "-GameTime.MaxSimFps 60 -GameTime.ForceSimRate 60+" in the properties that needs to be removed.
Start new game without it, reach the bridge in-game, save and exit, put the code back, continue playing the 2nd best Dragon Age (Origins being the unbeatable champion, of course)
