49 réponses à ce sujet

[seacow42]

 I installed a bunch of mods recently then started a new game with them. I finished Lothering but now I can't leave. I keep right clicking the Bannorn but nothing happens. I went back and did all the quests but still nothing. Please help!

[Nwalya42]

what do you mean right clicking the bannorn?

[Titius.Vibius]

Its possible that a mod may have caused this problem. Try disabling it.

[seacow42]

I tried disabling all but the officially bioware ones but there are still many in my override folder. as for Nwalya's question, I mean right clicking the zone-change area

[Nwalya42]

huh. try using WASD to walk into the zone change area. Do you get a message saying something like "gather your party and venture forth"?

[Titius.Vibius]

On the override folder? Save the folder and rename it, create a new override folder.

[seacow42]

I got no message like that- thus being why I can't continue. If I moved by override folder, played to the camp, then put it back, would that still cause problems later?

[Titius.Vibius]

I guess it will because the game happens to look for changes on the override folder.

[seacow42]

Will mess up the game or will allow me to pass lothering??

[Fleapants]

Is your game downloading any DLCs in the background? I had the same issue, and I think that that was the cause of it.

Otherwise, save and reboot your computer.

[seacow42]

I'll reboot tomorrow and see if that helps- if it doesn't I'll come back here and maybe try taking out my override folder temporarily. Thanks guys!

[Herethos]

Hmm well the save might already contain the error if you've saved in lothering, I'd say disable the mods, rename override folder and load a save just before you entered lothering and see if there still is a problem. But this issue could also be tied the toolset if you've recently installed that, there should be a topic somewhere in the forums on what empty foldiers to delete.

[seacow42]

tried to do lothering again with a save from before lothering and that didn't work. moved my override full of mods and disabled all but the bioware addins then rebooted and that didn't work either. this is rather distressing, please help.

[Xetrill]

Do you have the toolset installed? And if so used it?
Then look into your documents (BioWare\\Dragon Age\\packages\\core\\override\\toolsetexport) and if there is anything at all, delete it.

I had some weird problems, because of that. I actually wrote an small app to help with that, and other override problems.
(I haven't released it, since its only tested on my computer. But if there is actual demand for something like it, I will)

Still, I might be totally wrong here...

edit: why doesn't the post look like it did when I wrote it...

Modifié par Xetrill, 11 décembre 2009 - 10:57 .

[seacow42]

nope no toolset for me. I'm no modder. 

Modifié par seacow42, 11 décembre 2009 - 11:06 .

[Cathedron]

Same problem here. Lothering exit seems to be broken after installing the 1.02 patch.

Tried loading a save from a pre 1.02 no mod playthrough and still couldn't exit the area (obviously worked fine before).

[Madd Bomber 83]

I'm in the same boat. It worked before and now it doesn't. Rebooted comp, removed all mods, tried from a prior save game. Nothing can get me past Lothering now.

[Teyrn Seraphim]

Ok I had this problem too...

If you are using daorigins.exe to enter the game,then just try to start game through DAOriginsLauncher.exe...or if you use DAOriginsLauncher.exe then try through daorigins.exe..

Helped for me

[Vizkos]

It is possible that a mod made in an older version of dragon age may conflict with a patched version of dragon age. I'd suggest temporarily moving any mods that are in your override folder to a different location and trying that. If that doesn't work, best thing I can say is to reference when each of the mods you activated were made.

[Neriana]

Teyrn Seraphim wrote...

Ok I had this problem too...
If you are using daorigins.exe to enter the game,then just try to start game through DAOriginsLauncher.exe...or if you use DAOriginsLauncher.exe then try through daorigins.exe..
Helped for me

I tried that, it didn't work. I've tried disabling all mods, removing everything from override, and various combinations thereof  -- didn't work. I loaded up both my characters who were able to get through Lothering pre-1.02, and they couldn't leave either. And I thought not being able to name the dog was bad...

One odd thing: once I did three Chanter's Board quests in Lothering this time, I wasn't able to see any more. (Civil War, Refugees, etc.) This did not happen the first two times I played. Maybe it's related?

Edit: I uninstalled the toolset, but that didn't fix it. So I uninstalled the game, reinstalled the game, and loaded the Lothering save without enabling any mods. That fixed it. I did not patch the game. I'm most likely not going to patch the game to 1.02, in fact, since it didn't fix anything I had problems with, introduced a gamebreaker and made me unable to name the dog.

Modifié par Neriana, 14 décembre 2009 - 09:57 .

[Orange_Section]

same problem here.... I guess i have to re-install aswell then....?

[JironGhrad]

Neriana wrote...

Teyrn Seraphim wrote...

Ok I had this problem too...
If you are using daorigins.exe to enter the game,then just try to start game through DAOriginsLauncher.exe...or if you use DAOriginsLauncher.exe then try through daorigins.exe..
Helped for me

I tried that, it didn't work. I've tried disabling all mods, removing everything from override, and various combinations thereof  -- didn't work. I loaded up both my characters who were able to get through Lothering pre-1.02, and they couldn't leave either. And I thought not being able to name the dog was bad...

One odd thing: once I did three Chanter's Board quests in Lothering this time, I wasn't able to see any more. (Civil War, Refugees, etc.) This did not happen the first two times I played. Maybe it's related?

Edit: I uninstalled the toolset, but that didn't fix it. So I uninstalled the game, reinstalled the game, and loaded the Lothering save without enabling any mods. That fixed it. I did not patch the game. I'm most likely not going to patch the game to 1.02, in fact, since it didn't fix anything I had problems with, introduced a gamebreaker and made me unable to name the dog.

Your problem is that the toolset corrupted your saves.  There's a fix for that listed in the thread in my signature. It's not patch related at all.

[Orange_Section]

and if i have the same problem, BUT i have never installed the toolset? What then?

[Neriana]

JironGhrad wrote...

Neriana wrote...

Teyrn Seraphim wrote...

Ok I had this problem too...
If you are using daorigins.exe to enter the game,then just try to start game through DAOriginsLauncher.exe...or if you use DAOriginsLauncher.exe then try through daorigins.exe..
Helped for me

I tried that, it didn't work. I've tried disabling all mods, removing everything from override, and various combinations thereof  -- didn't work. I loaded up both my characters who were able to get through Lothering pre-1.02, and they couldn't leave either. And I thought not being able to name the dog was bad...

One odd thing: once I did three Chanter's Board quests in Lothering this time, I wasn't able to see any more. (Civil War, Refugees, etc.) This did not happen the first two times I played. Maybe it's related?

Edit: I uninstalled the toolset, but that didn't fix it. So I uninstalled the game, reinstalled the game, and loaded the Lothering save without enabling any mods. That fixed it. I did not patch the game. I'm most likely not going to patch the game to 1.02, in fact, since it didn't fix anything I had problems with, introduced a gamebreaker and made me unable to name the dog.

Your problem is that the toolset corrupted your saves.  There's a fix for that listed in the thread in my signature. It's not patch related at all.

No, that was not my problem. I performed the listed fixes in your thread, and others around the forum related to the toolset and anything else that was listed as likely to fix script or area transition bugs as well, and they did not help. My saves worked perfectly well as soon as I removed the 1.02 patch, and the 1.02 patch was the ONLY difference between my game working and it not working.

I've been doing this kind of thing with computer games for a very long time. It's entirely possible that there's something else weird going on here, and maybe it was my installation that was corrupt and not the 1.02 patch in particular. But it was not a known and fixable toolset error, and I'm not taking my chances with a patch that I didn't need anyway. I've had too much experience with EA patches breaking more than they fix.

Orange_Section: Have you tried uninstalling the game and re-installing it without the 1.02 patch, then loading your save and seeing if you can escape Lothering?

Modifié par Neriana, 14 décembre 2009 - 09:36 .

[JironGhrad]

Neriana wrote...

JironGhrad wrote...

Neriana wrote...

Teyrn Seraphim wrote...

Ok I had this problem too...
If you are using daorigins.exe to enter the game,then just try to start game through DAOriginsLauncher.exe...or if you use DAOriginsLauncher.exe then try through daorigins.exe..
Helped for me

I tried that, it didn't work. I've tried disabling all mods, removing everything from override, and various combinations thereof  -- didn't work. I loaded up both my characters who were able to get through Lothering pre-1.02, and they couldn't leave either. And I thought not being able to name the dog was bad...

One odd thing: once I did three Chanter's Board quests in Lothering this time, I wasn't able to see any more. (Civil War, Refugees, etc.) This did not happen the first two times I played. Maybe it's related?

Edit: I uninstalled the toolset, but that didn't fix it. So I uninstalled the game, reinstalled the game, and loaded the Lothering save without enabling any mods. That fixed it. I did not patch the game. I'm most likely not going to patch the game to 1.02, in fact, since it didn't fix anything I had problems with, introduced a gamebreaker and made me unable to name the dog.

Your problem is that the toolset corrupted your saves.  There's a fix for that listed in the thread in my signature. It's not patch related at all.

No, that was not my problem. I performed the listed fixes in your thread, and others around the forum related to the toolset and anything else that was listed as likely to fix script or area transition bugs as well, and they did not help. My saves worked perfectly well as soon as I removed the 1.02 patch, and the 1.02 patch was the ONLY difference between my game working and it not working.

I've been doing this kind of thing with computer games for a very long time. It's entirely possible that there's something else weird going on here, and maybe it was my installation that was corrupt and not the 1.02 patch in particular. But it was not a known and fixable toolset error, and I'm not taking my chances with a patch that I didn't need anyway. I've had too much experience with EA patches breaking more than they fix.

Orange_Section: Have you tried uninstalling the game and re-installing it without the 1.02 patch, then loading your save and seeing if you can escape Lothering?

There's a link located in the same section as the removal of files which points to a post by Brian from Bioware who explains how the toolset can corrupt the saves and how to resolve it.  I suggest that because, according to the guys who created the 1.01v Toolset, they had to renumber a variety of the components to sync them up with the 1.02 patch and prevent the breakages that have been occurring from re-occuring. That suggests to me that the corruption with the saved games is being triggered by the changes related to 1.02.