16 réponses à ce sujet

[Bahlsa]

 made some really bad modules, and
want to not see them in the toolset anymore, but when I delete
the folders, the toolset brings them back.

How do I get
rid of them completely ?

[ixobelle]

they're not folder, they're database entries.



we've had a dev posting here to 'just ignore them for the time being'.

[Bahlsa]

Hmmm.... Thank you for the response, I should have searched first.

[Arumite]

I just posted a topic asking this same question. Because I couldn't find this one. because search don't work. thanks for the answer. Wait, the answer is that you can't delete them? and to ignore them?

\\/\\/  Thank you for quick response, and for the warning.  It's bugging me to the point where I was just about to do that.  I'm a compulsive perfectionist like that...

Modifié par Arumite, 11 novembre 2009 - 11:20 .

[ixobelle]

yes, just ignore them for now. They may update it to be removable (or you can probably remove it if you're a SQL whiz), but for now just make a new one, and ignore the ones you don't want anymore. Whatever you do don't reinstall the toolset from scratch, as that creates a new database (overwriting the old one), and you just screw stuff up royally. I speak from experience on that last note.

[Arumite]

^^^ Thank you for quick response, and for the warning. It's bugging me to the point where I was just about to do that. I'm a compulsive perfectionist like that...

this site bugs me.  lol.

Modifié par Arumite, 11 novembre 2009 - 11:21 .

[Bronyaux]

There are Backup and Restore batch files in the dbbak folder. If you have all the default settings, you should be able to run them as is. Using that, you can Backup your database before you add modules, and restore it later if you want to revert back.

[Bahlsa]

Would uninstalling the toolset, for me hte 5th time, work to remove the database, and clear all modules ?

[Allan Smith]

Bahlsa wrote...

Would uninstalling the toolset, for me hte 5th time, work to remove the database, and clear all modules ?

Yes it would.  However, you have a bunch of options here:
(I am at home, sick working by memory,I will try and describe things without seeing the actual directories and such)

A FULL uninstall of the toolset followed by a re-install would work. You would lose any work you had done in the database, and end up with a clean database again.

A quicker alternative is to just restore to a backup of your database before you made the stuff you want to get rid of if you have one.  If you don't, you could use the clean one the toolset restores from when it installs.  It  is found in Dragon Age\\\\Tools\\\\DBBack\\\\  (some path like that, it will have a .bak file in it)
Backup/restore can be accomplished by a command line (if you are comfortable with that sort of thing) see instructions at http://social.biowar...kup_and_restore
or, you can download Microsoft SQL Server 2005 Management Studio Express (free) which has an interface for backing up  and restoring databases.  You'll have to search thier help on how to do it, I usually just use the command line.
Alternately, you can just leave the modules in, they don't really do any harm.  If you delete the resources from them, they take up almost no space at all.
If you have already installed/unistalled 5 times, you probably have this down to a science, and it may be the easiest path for you , just make sure that when you uninstall you select the option where you remove the database engine and  files, or you will just end up back in the same place you are right now.

Modifié par Allan Smith, 12 novembre 2009 - 08:59 .

[Languard]

Just made a blog post about this actually. In short, what everyone above me said. If having it visible in the list really bugs you, you can rip it out rather easily, but you will leave invisible junk in the database. Looking into writing a tool to clean out the database.

[Tasker]

Hang on a sec, so basically, the toolest is just going to get more and more cluttered with junk untill Bioware or a third party can be bothered to make it deletable?

[Bronyaux]

Well why not? It doesn't hurt anything. Usually cosmetic bugs like that are a lower priority to function-breaking bugs. Or enhancements in some cases.

In fact this isn't even a bug, so it's a cosmetic enhancement.

Modifié par Bronyaux, 13 novembre 2009 - 12:47 .

[Tsunami]

Actually there is another option, it is fairly complex, but non the less effective. Remember to delete any areas, creatures, palceables, etc. that you created for that module prior to deleting it, or you will have a mess. the entire process is outlined here. From my point of view, some more descriptive steps would have improved this wiki entry.
http://social.biowar...emoving_Modules
I just tried the steps listed to remove the module from the database, like most articles written in regards to this type of thing, they are never using the tools currently avaialble. Evidently, they must be using SQL Server Management Studio 2005, because this does not work for SQL Server Managment Studio 2008. When I find the steps that do, I will edit this post or add another with the "updated" information. I agree, that to not have the ability to merely delete a failed to load module, is rediculous, it should have been a "primary" feature. This is precisly what happens when you get only game programmers to do beta testing. 
 

Modifié par Tsunami, 01 décembre 2009 - 03:27 .

[Aslend]

I am expereincing and error when trying to delete the module from the database, using SQL Server Management Studio 2005.

The DELETE statement conflicted with the Reference constraint "FK_t_ModuleResRef_t_Module."The conflict occured in the database "bw_dragonage_content", table "dbo.t_ModuleResRef" column "ModuleID"

The statement has been terminated. correct the error and attempt to delete the row again or press ESC to cancel the changes(s).

[BryanDerksen]

Can't help with that error specifically, but I figured I should link to http://social.biowar...eting_a_module where the feature request for module-deletion is being tracked. Feel free to expand the page with any tricks or ideas that come up.

[Aslend]

Thanks for the link Bryan, I had looked at this previously and was utilizing that exact method when this error occured. Since updating the toolset and replacing the database as instructed for the toolset update to allow for the new database type file extention. When I have tried to open the new database, bw_dragonage_content, with SQL Server Management Studio Express 2005 , I am presented with this error The database bw_dragonage_content is not accessible. (Microsoft.SqlServer.Express.ObjectExplorer)
I get the feeling that a connection to the database cannot be established, probably due to changes in location or authentication. Any assistance on this would be appreciated, I would like to assist in getting all of this resolved so we can stream line the process of module removal. I feel the level of frustration with this will cause many to abandon work in the toolset.
I discovered you must use the SQL Surface Area Configuration in Windows Vista to enable "Administrative" rights to the data base, then connection to it works fine.

Modifié par Aslend, 18 mars 2010 - 07:45 .

[Sleeplessone]

Below is an alternative way which is part of the SQL tools when you first install the Toolset.  

The reason why i found out how to do it below is because I failed to create an administrator for the SWL DB hence I had an error where the Management GUI would not open the 
bw_dragonage_content.

Or if you cannot install and use SQL Server Management Studio Express 2005  

you can via command line in CMD at administrator

The first is to connect using SQLCMD tool 

SQLCMD -S .\\SQLEXPRESS

Now you want to select the DB instance 

use bw_dragonage_content
go

To list the modules in the editor

select +[NAME]+,',' from t_module
go

To delete a module from the editor , where your_module_name is the name of your module

delete from t_module where [NAME] = "your_module_name"
go

Modifié par Sleeplessone, 15 juin 2012 - 11:45 .