8 réponses à ce sujet

[Orihime]

heres the question if youve made a module and its in the toolset how do you delete it

 

 

ive never known this for the past 1 and half years ive used the toolset.

 

 

let me know if you know what to do about it.

 

 

much thanks

[DahliaLynn]

To the best of my knowledge, there are no conventional methods to delete a module once you've created one within the DA database. (There are probably alternatives that require knowledge of using SQL software which is beyond me)

If you want to start with a clean database, an easy way to do so would be to back up the current database using the backup utility (\ProgramFiles\Dragon Age\tools\DatabaseUtilities) and restoring to a fresh new database.

You could of course create a uniquely named database and switch between the two using the configuration utility, but again, not something I could personally offer advice on.

[Orihime]

To the best of my knowledge, there are no conventional methods to delete a module once you've created one within the DA database. (There are probably alternatives that require knowledge of using SQL software which is beyond me)

If you want to start with a clean database, an easy way to do so would be to back up the current database using the backup utility (\ProgramFiles\Dragon Age\tools\DatabaseUtilities) and restoring to a fresh new database.

You could of course create a uniquely named database and switch between the two using the configuration utility, but again, not something I could personally offer advice on.

oh thank you very much dahlialynn ill try that out

[MerAnne]

As far as I know, there is no way to delete the module, there IS a way to delete the contents of a module and then rename the empty module to something else.  This is potentially 'dangerous' so it is something that I've only done on some small test modules that I created early on.

[luna1124]

Do you mean an item/morph/weapon/armor etc in the toolset you've created or altered, or an actual module (Add-In)?

[Orihime]

yes exactly basicly i have so many of them idk how to get rid of them in toolset itself when you create a new module name o-o i hope that explains what i mean and thank you all for helping

[Sunjammer]

The toolset doesn't provide a way to delete a module but if you have a little SQL Server knowledge (or know someone that does) you have a few options. For example you can:

• Delete a modules entry from the modules table in the database: this will effectively remove that module from your "Manage Modules" window however it doesn't actually remove the module's contents from your database. Probably easiest but least advisable option (in my opinion). If all you want to do is reduce the size of you module list this might work.

• Completely delete a module and all of its resources (including any checked out resources) from a database: this would be a delete function in the purest sense. Unfortunately this would require a very involved procedure (and a lot of testing) and I don't recall anyone in the community actually writing it. I think there were a couple of attempts in years gone by which might provide a good starting point for anyone willing to pursue this.

• Backup your existing database and restore default database backup: this effectively remove all your modules and gives you a clean database with just the core, demo and Single Player resources installed. The reason for backing up is that if you ever need anything from your old database them you just back up the new database, restore the old one, B2B the resources you need, restore the new database and ingest the B2B file. Obviously if there are some modules or resources you know you will want in the new database you can always B2B them in advance. Note that if you want to transfer a whole module you'll have to manually note its properties as they are not included in the B2B file.

• Create an additional database; restore the default database backup and use the toolset configuration utility to switch between them whenever you need to: this allows you to create as many clean databases as you need.  You can have multiple database running in parallel and switching between them is simplicity itself (i.e. close the toolset, run the configuration tool, open the toolset). Personally this is my preferred option (I have a different database for each person I collaborate with) but it does require a bit of discipline when doing backup/restores and if you collaborate you may have to use my B2B reconfiguration tool.

[Sunjammer]

For completeness and because I didn't have time to find the link before I boarded my plane yesterday ...

 

Anyone uses the default database (bw_dragonage_content) and who shares design resources with someone that doesn't (or vice versa) you may find Sunjammer's Dadbdata Database Switcher helpful (well essential really because otherwise you can't load each other's B2B files).

[Orihime]

thank you all of you for replying to my noobish knowledge x]

 

and ill look at your link and see what i can learn

 

thans on that sunjammer