15 réponses à ce sujet

[traveller_]

I was wandering if it is possible to open the main campaign (even readonly) with the toolset, at least to the extent of reading the dialogues. I rember doing that with NWN and NWN2 toolsets without much trouble, and it was pretty funny to see all the possibilities chosen and missed, but apparently it is harder (or impossible?) to do the same with DA.

I went into the single player and core directories, and found a designdiologue.erf files, and when opening them I found lots of .dlg files, so I exported them to another directory and proceeded to read them with the toolset. But while the toolset opens them, it does not give me dialogues as expected, but what seems to be a collection of variables. Am I doing something wrong? Or it is just not possible to read the content of the main campaign? I tried sifting between tutorials of various kind but couldn't find anything about opening the content of the main campaign.

Modifié par traveller_, 04 février 2010 - 09:26 .

[Avaraen]

.dlg files are the exported versions of the dialogue files, and can't be imported into the DA toolset in a meaningful format. To access the properly editable dialogue files, start the toolset, then go File -> Manage Modules -> Single Player. Now click the Conversation icon in the Palette Window area (looks like a speech bubble). From there, you can open any of the dialogue files, and you'll find the editing process to be similar to NWN2.

[traveller_]

Thanks for the reply. I tried that too, but when clicking the Conversation icon I get an empty set. From what you say I am starting to think that I may have screwed up during the toolset install (I had to do the manual install due to the "can't connect to DB" error), probably in the DB recovery.

More reinstall and bug-fixing for me, I am afraid... *groan*

Anyway, thanks for confirming that you CAN indeed open the main campaign dialogues and it's only my own problem. That helps a lot.

Modifié par traveller_, 04 février 2010 - 11:22 .

[Avaraen]

Ah, yeah, even if you are in the Demo Tutorial (default mode), you should still have some items displayed in the Palette Window. Hope you can get the database issue sorted; I've not run into that bug, so can't offer any suggestions on how to correct it.

[Eshme]

unable to connect to database is unpdated on the wiki , and restoring database ,if you want to reinstall and repeat



http://social.biowar...to_the_database



http://social.biowar...kup_and_restore

[traveller_]

Oh, I missed the second link, thanks for it, I will mess with it ASAP.

[traveller_]

I still have some problems with this issue. Currently I reinstalled everything, manually installing SQL and recovering the database. When during the installation I create an empty DB and immediately try to activate the toolset, the toolset rightfully tells me "Unable to connect to the DB". Then I restore the DB that comes with the toolset and the toolset starts, so it seems that the DB recovery has worked properly.

However when I select the Palette, EVERY voice, except Sounds and Models is completely empty. Opening the "Single Player" or the "Demo tutorial" modules does not change that (every voice except Sounds and Models stays empty) although the resources in Sounds are markedly different between the two modules. Refreshing does not help.

So I am basically stuck. What gives? Did I restore the wrong backup (Dragon Age/tools/dbbak/bw_dragonage_content.bak )? Do I need to restore other DBs? What is going on?

Modifié par traveller_, 04 février 2010 - 07:34 .

[Eshme]

Well i dont know.. the back up is right it is the 600mb file or so..



When you restore it, you get 2 big files mdf and ldf something like that somewhere. I suppose big means good. At least conversion takes a moment. And then i open toolset and everything is there.

Perhaps you check toolset configuration tool?



Its "ConfigureToolset.exe".. for me "default" is checked. But perhaps you can try to uncheck and customize? Server is .\\BWDATOOLSET

Database is bw_dragonage_content



dont know what else is important?

[traveller_]

When you restore it, you get 2 big files mdf and ldf something like that somewhere. I suppose big means good.

How big? I get one file of 84M and another of 688M.

Perhaps you check toolset configuration tool?

Yeha, I already tried everything with that. Also, if there was something wrong the toolset shouldn't boot at all. What I can't understand is why I can see the items in two palettes, while the others are empty...

[BryanDerksen]

The "sound" and "model" palettes don't show database resources, they show art assets. They're special that way - note how there's no "check out" option for them, for instance. So if there's something wrong with the database it's not unexpected to see stuff in those two palette filters but not in the other palettes.

However, I'm not sure why there's a problem with the database here (or if there's a problem with the database, for that matter). If you've got nice juicy mdf and ldf files in your database directory then that indicates the data got loaded up when you did the database restore.

One possibility that comes to mind is that you've wound up with multiple databases, with one being empty and the other having the correct resources in them, and the toolset's connecting to the wrong one. Do you have SQL Management Studio installed? That could be used to check up on which databases are present.

Oh, and if you're using Configuretoolset.exe to change databases or are installing the database in a non-default location, there's currently a bug in it that you might need to work around: http://social.biowar..._a_registry_key

[traveller_]

The "sound" and "model" palettes don't show database resources, they show art assets.

I see. So I cannot still rule out DB problems. Good to know.

However, I'm not sure why there's a problem with the database here (or if there's a problem with the database, for that matter). If you've got nice juicy mdf and ldf files in your database directory then that indicates the data got loaded up when you did the database restore.

Yep, my thought exactly.

One possibility that comes to mind is that you've wound up with multiple databases, with one being empty and the other having the correct resources in them, and the toolset's connecting to the wrong one. Do you have SQL Management Studio installed? That could be used to check up on which databases are present.

I have done lots of install/reinstall of both the toolkit and the SQL server, and had to wrestle with the default directories so theoretically I MIGHT have ended up with multiple copies of the DB scattared around the system no matter how much attention I have dedicated to cleaning up. However I have managed the DB recovery using the SQL management studio and it shows that there is only one DB (the usual bw_dragonage_content) into the SQL server (except for the system DB, of course). I also tried to manage backup recovery using the .bat script in the wiki, but to no avail, I got the same result. Besides, for comparison I tried to purposefully connect the toolset to an empty database and I got the "Unable to connect" error. Only after I restored the backup on that same DB (and touched nothing else) the toolset started. It seems the toolset won't start at all if connected to an empty DB, instead of behaving like it does.

Oh, and if you're using Configuretoolset.exe to change databases or are installing the database in a non-default location, there's currently a bug in it that you might need to work around: http://social.biowar..._a_registry_key

Yep, I already checked that page and at each installation manually modified the registry. To no avail though.

EDIT: Ah, I forgot to mention another odd behavior, though I have no idea whether it is related to this problem or not. When I install the toolset, even without installing the MSSQL, the toolset apparently installs, but when checking the installation icons I noticed that there is no "uninstall" icon in the start menu. I have to rerun the installer, thus performing a second install over the first one, to have the "uninstall" icon appear in the start menu.

Modifié par traveller_, 05 février 2010 - 10:12 .

[BryanDerksen]

Hm... So it sounds like the database has the information in it, but the toolset just isn't displaying anything in it. The closest I can think of as a way to get that to happen is to have some text in the palette's search field that doesn't match any resource name, or to have the "only show resources checked out to me" field selected and no resources are checked out to you. But both of these situations should make the sounds and models disappear too so it doesn't match up exactly with the symptoms you're describing, and I don't know how that situation would arise in a fresh installation.



One thing you can double-check that I didn't mention before: down in the lower right corner of the toolset, in the status bar, there's a line that reads "Database:<database you're connected to>". That line is sort of the final word on what database your toolset is really using, so you can confirm there that the toolset's connected to the one you're examining in management studio or whereever. The default installation should have ".\\BWDATOOLSET\\bw_dragonage_content" down there.



Another thing to check is to try creating a new resource of some kind and see what happens. Does it show up in the palette, can it be edited, and can you check it in? That way you'll know with certainty that there's at least _one_ resource in there that you should be able to see.

[traveller_]

Hm... So it sounds like the database has the information in it, but the toolset just isn't displaying anything in it. The closest I can think of as a way to get that to happen is to have some text in the palette's search field that doesn't match any resource name, or to have the "only show resources checked out to me" field selected and no resources are checked out to you. But both of these situations should make the sounds and models disappear too so it doesn't match up exactly with the symptoms you're describing, and I don't know how that situation would arise in a fresh installation.

Indeed. Besides I made sure that the "only show resources" field is unchecked, and that nothing is written in the palette search field.

One thing you can double-check that I didn't mention before: down in the lower right corner of the toolset, in the status bar, there's a line that reads "Database:".

I can confirm that it's the DB that I created and restored (just to be on the safe side I used the default names too, so it's BWDATOOLSET:bw_dragonage_content)

Another thing to check is to try creating a new resource of some kind and see what happens. Does it show up in the palette, can it be edited, and can you check it in? That way you'll know with certainty that there's at least _one_ resource in there that you should be able to see.

Excellent suggestion. I just tried to create a conversation resource "test2". The result is the following line in the log window:

"18:35:42 - test2.dlg - The resource "test2.dlg" has been added."

However in the palette nothing appears. I tried every possible refresh as well, to no avail. Then I tried to create the same resource again, and I get a "The resource name is already in use" error. So it seems that the resources are indeed created, maybe even managed, but the palette does not show them. What may be the cause I have no idea...

Now I am doing another test which requires me to uninstall everything again, since it seems that MSSQL may have some issues with MSXML6... I'll let you know if it works. In the meanwhile if you have other suggestions I am all ears.

[traveller_]

Ok, I made it work. What I did was to uninstall everything and then run again the whole installer, including the MSSQL. As it happened before the toolset wouldn't start ("Unable to connect..."). When this happened last time I installed the toolset and MSSQL separately as per wiki. Instead, this time I used the MSSQL studio, noticed that the DB was missing, so I created the DB, restored it, and now everything is working fine. Apparently there is soemthing amiss if I install MSSQL separately from the toolset. Some package maybe? I noticed that MSXML6 is installed if I do the full installation but is NOT installed if I install toolset and MSSQL separately.

[BryanDerksen]

For now I'm going to cross my fingers and hope that this mysterious problem gets mysteriously corrected by whatever it is you try next. Or that someone cleverer than I is able to figure it out and jumps in with the solution. This is a weird one.

Edit: Yayy! My strategy worked!

Modifié par BryanDerksen, 05 février 2010 - 06:41 .

[traveller_]

Edit: Yayy! My strategy worked!

Yep, but I think the wiki about separate installs needs updating. The MSSQL package pointed from the wiki installs les software than the MSSQL package installed by the toolset.