dudi4155

Damn, that would have come in handy. I just used a 4GB patch on the toolsets executable, but it still crashed sometimes due to running out of memory. Guess I'll have to remember about pyGFF for the future. Thanks!

It took me a while but I've been poking around it every now and then for the past month and I found the solution. It was probably caused by the fixpack. It seems that something kept stacking more and more effects on my character, and these effects never went away. In the toolset, when I opened my save game and navigated to the following key: Top Level Struct -> SAVEGAME_PLAYERCHAR -> SAVEGAME_PLAYERCHAR_CHAR -> SAVEGAME_EFFECT_LIST I found out that there were almost 5000 effects on the list, while my last working save had about 18. The bug appears after the number of effects there surpasses 1022. I guess someone might find it helpful in the future, so the solution is as follows: 1. Disable ALL sustainable abilities on your character (and your party members just in case), unequip all your items then save and close the game.2. Install the toolset. This is a bit tricky, since it requires SQL Server 2005 Express which doesn't support newer versions of Windows. There are some hacks available online to make it work on Windows 10, or you could use a virtual machine with Windows XP.3. Open your save file with the toolset. The save is located at: C:\Users\YourUserName\Documents\Bioware\Dragon Age\Characters\YourCharacter\Saves\YourSaveSlot\YourSaveGame.das4. Clear all entries under Top Level Struct -> SAVEGAME_PLAYERCHAR -> SAVEGAME_PLAYERCHAR_CHAR -> SAVEGAME_EFFECT_LIST and overwrite your save file. After that it should work. I guess it could probably be done without the toolset and by using a hex editor,

If there is no script to force the cutscene to play, I'll just play around with the toolset. Seems like I need to use a Virtual Machine to install it, since newer version of Windows don't support SQL Server 2005, but I'm determined to get it fixed. Thanks for the help anyway :)

I haven't even installed the toolset before and this is my first playthrough. I also tried not skipping anything with ESC key. I just re-enabled all mods, loaded the oldest save file that is unaffected by this bug, traveled to Denerim and triggered the Landsmeet via console. The duel worked properly and I noticed a difference - there is an additional cutscene right before the duel where the crowd disperses and the characters get ready to fight - that cutscene doesn't play in the corrupted save files. This must be some plot choice that I made that affects this issue. While searching for the issue on Google I noticed that someone mentioned that saving the Arl of Redcliffe is what triggers this bug, but there must be something else that needs to be done in order to make it happen...

I've tried removing all mods and loading a save I made before doing any quests in Denerim (though it is possible that I had briefly visited the market district at that point), but the bug still occurred. I also tried to copy the save file to my girlfriends laptop who has a different edition of the game, but it didn't help. Guess my only option is to try and mess around with the Dragon Age Toolset, if I can get it to work. Thanks for the advice anyway :)

I ran into a bug during Landsmeet duel with Loghain. Whenever I choose any character to fight him I always end up with my whole party fighting him, and when he reaches 0 HP he becomes invincible. I tried restoring earlier saves, removing mods and using console cheats to kill him or move around various plot points, but nothing helps. The only thing that helps is to restore a very old save game (from before the Urn of Sacred Ashed quest) and using console commands to move to the Landsmeet plot point. The mods that I had installed are: - Dragon Age Redesigned - Leliana -- Realistic DAO Project - Alistair-- Realistic DAO Project - Dragon Age Rules Fixpack Removing ALL mods did not fix the problem. After I encountered the bug I installed Qwinn's Ultimate DAO Fixpack but it didn't help either. I've found numerous mentions of this bug via Google, but no way to fix this. Is there any way to fix this or just skip the fight with Loghain? Any help will be appreciated!