11 réponses à ce sujet

[JasonNH]

I have been reading the forums and I am seeing a very disturbing trend and I am experiencing it myself personally. After playing around with the toolset for a while and doing some local posts, my game is now very broken!!

New party members will not join, the world map is broken, and I can't start a new game or I get "Unable to Load Module" errors!

*Edit* - As noted below, renaming the "Single Player" directory in your My Documents/Bioware/Dragon Age/Modules path fixes these problems.

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

[BryanDerksen]

The toolset allows people to modify the main campaign, so unfortunately that also means the toolset allows people to break the main campaign. There's a command under the "Tools" menu called "Empty Export Directories" that might be useful for un-breaking it without having to manually delete directories, it removes exported things from the override directories. It doesn't handle modified art resources, though, and I don't think it'll reverse changes done to module properties so it's still useful to keep those directory locations in mind for manual intervention.

[BryanDerksen]

The reinstall may not have deleted any broken resources that were exported by the toolset. It's the files that were added to the override directories that are likely causing problems, not anything missing from the install.



I should also note that modified core resources will affect the main campaign too, BTW. So check the core/override directories for stray exports as well.

[BryanDerksen]

Smakit wrote...
All I saw on the wiki was:
Certain types of file are not packaged into ERFs and may be omitted
from the DAZIP file by the current builder-to-player packaging process.
Known examples include TGA files and BIK files. If you're using these
sorts of resources you can manually insert them into the DAZIP file
using any standard ZIP-editing program.


Anyhow, now that I have a bit - not a lot, but a bit  - of free time, I planned on jumping back and messing with the toolset, so just thought I would confirm.

That's an old bug that's been fixed now, actually. I'll go remove that from the wiki.

[BryanDerksen]

As for the plot flag issue, I'm going to have to follow up on that with people more knowledgeable than I about how plot flags work. The version of the core resources included with the toolset was taken out of our database some time after the version that shipped on disk but I don't see why those particular flags would be different.

[BryanDerksen]

Proleric1 wrote...

I'm pleased to see this has been made a sticky.

However, I'd suggest that Bioware needs to make a high-profile statement about this, to restore confidence in the toolset (assuming a fix isn't likely in the next 24 hours).

There's been an unfortunate confluence of people being sick, me being handed other assignments, and BioWare being shut for Remembrance Day that took me away from this at a bad time. But this does seem quite serious indeed, and I don't fully understand what's gone wrong to cause this problem, so I'm going to be doing a bunch of emailing now to try to catch up.

[BryanDerksen]

I wish. So far everyone I've talked to have been "plots have GUIDs? Didn't know that." And I'm completely out of my league on it myself. But I'm spamming the issue around and hopefully it'll hit someone that'll figure it out soon. The workarounds you guys have been coming up with in the meantime are likely going to be invaluable in giving us a leg up.

Modifié par BryanDerksen, 12 novembre 2009 - 05:58 .

[Allan Smith]

Sorry for the long absence here. Swine Flu took me right out of the picture for since Sunday Evening. I think I got more hours of sleep in the last 4 days than I usually get in a month. I have literally been sleeping for 18 hours a day, with very little energy to do anything. Feeling significantly better today (i.e. I have been awake for about 3 hours and don't feel like I need another nap!) but staying home so as not to take down my fellow workers.



We have one of BioWare's finest digging deep into this issue now. When we have something substantial to tell you about, we will let you know.

[BryanDerksen]

I've been told that the root cause of the problem has been found, something to do with the builder-to-builder process (which was used when making the database that was included with the toolset). I don't know what the exact details are or just how quickly to expect a fix, but I figured I should post that progress is being made on this now.

[BryanDerksen]

New version of the toolset and its core resources is coming along. In the meantime I put together a quick page on the wiki summarizing what's known about this bug: http://social.biowar...p/Plot_GUID_bug

[BryanDerksen]

Did you delete the contents of My Documents\\BioWare\\Dragon Age\\packages\\core\\override? That's where the toolset exports core resources to, so if you exported plots from the old database and they're still in that directory they'll continue to mess with your game. I don't know whether uninstalling Dragon Age wipes those directories but I'm guessing it might not.

[BryanDerksen]

It should be fixed in 1.01, though old resources left over from 1.00 (including savegames) may still be broken.



If you've removed all of the exported resources, and are not using old savegames with possibly corrupt GUIDs, I'm not sure how the old install of the toolset could be causing problems with a fresh install of the game. All of the methods by which the toolset might influence the game seem like they should be removed at that point.



The specific "poison" files that the old toolset would have emitted would end in a .plo extension, perhaps do a search of your computer to see if any were missed by your cleanup?