35 réponses à ce sujet

[Fudzie]

 So I can't seem to make any new modules, and I refuse to tamper with anything any further until I can get at least one "test" module made to mess with. Is there any reason for this to occur?

This is a step-by-step that happens;

Load up Toolset
Manage Modules
New Module
Change Name to "Test"
Change UID to "test"
Click Ok
"Unable to save module"

I am using the Steam version of DA if that might help figure out what's going on, I know it causes problems with the MSSQL2K5 installation but I'm not sure if there are any other issues involving it.

Modifié par Fudzie, 14 novembre 2009 - 01:06 .

[RavenNightsight]

What were you trying to make? A new face or...?

[Fudzie]

Just a new module. That's it.

[Fudzie]

Does anyone have any idea what might be causing this inability to make a new module? Nobody else seems to have a problem doing it, so this must be an isolated bug issue.

[Captain Lovestar]

I'm having the same problem. I'm following WeriKK's guide(http://social.biowar.../5339/blog/576/) and I can't save the module I'm making. If I try to modify anything in the manage modules window it says it can't save any of my associations, either.

[Captain Lovestar]

I still don't have a clue.

[Fudzie]

In lieu of any advice for this (as I have decided to wait for my new computer before attempting anything with the toolset anymore), has there been anyone else other than Captain Lovestar and I who have experienced this problem?

[Shieara]

I'm having the same issue here. I tried a reinstall on the toolset but it didn't help.

[Lejontass]

Had the same problem myself, got response from Scott Meadows, but only advise he had was to reinstall, which didn't help ofcourse.

[Meihem808]

Just adding that I also have experienced this same error. Uninstalled, patched, restarted, reinstalled and it still didn't help. If anyone gets any additional advice, please post.

[DeathTyrant]

Got the same problem here, even after a new install. I am at a loss, and as I have yet to find an answer, I guess everyone is.

 edited to add:
I am running the Retail UK Collector's Edition DVD game
Windows 7 Ultimate x64
Intel i7 920
6GB DDR-3

Modifié par DeathTyrant, 28 novembre 2009 - 12:58 .

[giskard44]

I may be able to help.

First Aliens put the save option there to confuse you, its primary use is to save individual files but outside of that role it appears available at random times, exactly why, I do not know so I recommend not worrying about it too much.

Instead do this.

Right click on anything with a green tick next to it to that you made and select check in to save that individual item when your done. Check an item out again to edit it. This makes sure the item your working on is actually saved. A checked in item has no green tick, an editable item does have a green tick.

Some items are auto saved as work.... that just adds to the confusion.

Also if you want to save the whole mod instead of using save as any normal folk would naturally thin of doing first, think like an Bioware Alien and start looking in the last place you would look for the last menu item you would expect it to be.

Go to the tools menu in the toolset and select export with dependances (if nessessary, it might not even appear as available some times) then generate module xml and generate manifest xml. That will save your mod.

Also post to local exports things under specific conditions for use in the game the Tools/Builder menus also have uses too.

Why is the save option fragmented in this way ?
Its the aliens

(For those taking the aliens thing too seriously, its my way of saying the toolkits design is insane and had to designed by beings from a different planet).

Tip

If you reinstall the toolkit, it blanks the database and removes any mods you might have made whether you wish to remove them or not. Once gone, youve lost them for good. So do not reinstall the toolkit unless you want to lose all your work.

Modifié par giskard44, 28 novembre 2009 - 05:44 .

[mpstringfellow]

I am getting the same error. The log reports



Sun Nov 29 16:36:16 2009, ERROR, "d:\\DASecuROMBuild\\main\\dev\\tools\\sdk\\include\\toolsoledb.h", 226, "String or binary data would be truncated."

Sun Nov 29 16:36:16 2009, ERROR, ".\\dbmodule.cpp", 338, "CDBModule::Add caught an exception: Bad HRESULT: 80040e57"

[Ruken_Dracun]

I am having the same problem. I cant seem to find a fix either

[mihlena]

I have exactly the same problem. If all possible one has already tried, but nothing has helped .

[Ruken_Dracun]

Just like everyone else, I tried a fresh re install and it did not fix the problem. I really hope the issue is resolved with the next toolset update.



EDIT: I checked my logs after trying to create a new module and this is what it showed

Sun Nov 29 21:22:25 2009, ERROR, "d:\\DASecuROMBuild\\main\\dev\\tools\\sdk\\include\\toolsoledb.h", 226, "String or binary data would be truncated."

Sun Nov 29 21:22:25 2009, ERROR, ".\\dbmodule.cpp", 338, "CDBModule::Add caught an exception: Bad HRESULT: 80040e57"


Thing is, I have my game and Toolset installed on the F: Drive. Not sure why its throwing up ERROR D:   It starting to ****** me off

Modifié par Ruken_Dracun, 30 novembre 2009 - 04:25 .

[Elizabeth Sterling]

Just to add I'm also having this issue when I try to create a module, can't find anything to help.

(Retail version, 1.02 game, 1.0.982 toolset)

Modifié par Elizabeth Sterling, 10 décembre 2009 - 11:15 .

[Elizabeth Sterling]

Same issue with 1.1... out of curiosity what drives do you guys have Windows and Dragon Age installed to? On my system DA is on C:\\ and Windows is on D:\\ and I'm wondering if this is part of the issue.... oh, and my My Documents folder is also on C:\\

Modifié par Elizabeth Sterling, 11 décembre 2009 - 04:15 .

[Lejontass]

I've got it all on C:\\ so, that probably not the problem. And my version of the toolset is 1.0.982.0. The game is installed on C:\\Program Files\\Dragon Age. I got the advice to try it out with a different language setting, but I haven't tried that exactly, instead I used AppLocale(a program which simulates other language settings), it didn't work so I kinda gave up on that idea. But perhaps someone else want to try it.

[Allan Smith]

We have never encountered this issue with our internal testing. Really don't even know what would be causing this. Any of you that are having this issues, would you please do the following so that we can take a look at what is going on and see if we can find any clues.



1. Go to My Documents\\BioWare\\Dragon Age\\Toolset\\logs\\ and delete all of the log files that exist in there. (We want a clean slate to look at)

2. Open the toolset and do your steps to try and create a new module (i.e. recreate the problem)

3. Go back to My Documents\\BioWare\\Dragon Age\\Toolset\\logs\\. Zip up all the log files found in there.

4. Send an email to toolsetsupport@bioware.com with the following subject line: Unable to Save Module. Attention Allan Smith. Attach the zipped up log files to the email along with any other description or comments that you think might be helpful.



I will take a look at the logs that are being created and see if they give us any clues into this issue.

[Allan Smith]

Can anyone who is having this problem chime in and let me know what language their windows operating system is running? I suspect this may be the issue, but need some data to back up the suspicion.



Thanks

[iw4o]

[malicious content removed]

[Lejontass]

As in language settings? Well, Im using swedish language. Still want me to send you that e-mail? Could send you a dxdiag aswell if that would help you.

Modifié par Lejontass, 15 décembre 2009 - 08:51 .

[Allan Smith]

Lejontass wrote...

As in language settings? Well, Im using swedish language. Still want me to send you that e-mail? Could send you a dxdiag aswell if that would help you.

Go ahead and send the email and dxdiag as well.

[mihlena]

I have send you an e-mail with my logs.The language of my windows operating system is german.