313 réponses à ce sujet

[LokiHades]

Allan Smith wrote...
For those wondering about the "Can't connect to Database" issue.  This is just another symptom/manifestation of a failure somewhere in the installation of SQL Server 2005 and the populating of the database with data.  This is almost always an issue with the SQL Server 2005 installer, which is out of our control.  We have worked through many issues in the past with this, yet no matter how many tweaks we make to our process around it, it always seems to find another way to slap us around.  It has been the bane of my existance and I send virutal fireballs in its direction nearly every day.  We will continue to fight the fight, and eventually we will emerge victorious (I hope)

Thank you! And I lol'd heartily at this edit.

[bluevapor]

Thanks for the update! Information is always a good thing. I look forward to downloading the new and improved toolset when it's ready.

[Greg the Mad]

So it may could happen that once I reinstalled the toolset that I still can't find a database? ... Hmm



... Dear SQL Server Lord, please be nice to me and my PC and allow us to use the toolset. If you decline my wish I will be forced to use a frost spell against you, to freeze you in place, followed by a arcan and lightning bold only to finish you with a walking bomb spell.



... Anyway, thanks for the update, I don't want to know whats currently happening in the toolset offices.





Greg the Mad

[Smakit]

Hmm, seems I should have sent a +5 vs SQL rune instead of that fruit basket... I'm always so terrible with gifts.



And Ranlas, thanks for the reply. I guess you pretty well had it. =) Maybe this will at least give them something to try in the future when testing, though I don't know how corporate structure and all that jazz might allow it, and I am sure it would take much more than a simple word.



Keep up the assault on those toolset issues. If we don't hear from you for some time we will all pray to the Maker that the battle goes well! (and, thanks for the hard work)

[sirkaracho]

Are you saying that if we aks when we can expect the database-connection issue to be fixed, for some of us the answer is "never"?

[Lord Sinner]

Apparently... YESSSSSSS

[nix3r]

Guys is there a detailed run-down somewhere of exactly what the current issue is, and how to avoid it / how it will affect you?



Many, many of us are unsure if we should delay on our projects, or jump straight in but backup our saves first and after 20 minutes of searching around here I'm still unsure of the consensus.

[Quaxo]

Darkmage187 wrote...

Another issue to report when loading a saved game into the editor.  Getting the following error message/window:

EditorGff40
Out of Memory

After clicking "OK" on the above message about 20 times I get the following:

Runtime Error!

Program: E\\\\Games\\\\Dragon Age\\\\tools\\\\DragonAgeToolset.exe

"This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information."

This seems to occur when attempting to load larger saved games ( e.g. 8 mb + ).  Doesn't seem to occur with smaller files. I'm running Windows XP Home Edition (5.1, Build 2600) Service Pack 3.

Opening a save file causes the toolset memory usage to jump from ~300MB to 1.5GB+ (in one case it went up to 1.89GB on my XP machine). Depended on how much memory you have and how much of it is in use when you attempt to open that save file, it's not surprising that you might run out of memory.

Are you attempting to open a quick save or a save saved through the menu? I noticed twice now that a menu save only pushed me up to 1-1.2GB whereas a quick save pushed me even higher. It might be coincidence or maybe even something to do with the way quick and regular saves are done. I haven't had time to really sit down and test that, but it's worth at least mentioning.

[sirkaracho]

Lord Sinner wrote...

Apparently... YESSSSSSS

plz BIOWARE guys

tell me thats not true

i bought the game because of the toolset, it is not my mistake that you use buggy software, the database connection issue has to be fixed

[nix3r]

nix3r wrote...

Guys is there a detailed run-down somewhere of exactly what the current issue is, and how to avoid it / how it will affect you?

Just found it on the other thread, thanks very much Bryan.

BryanDerksen wrote...

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

[GrandeLobo]

Quaxo wrote...

I'm running Windows XP Home Edition (5.1, Build 2600) Service Pack 3.

Hello,

I was wandering, because i'am running the same system, how did you get the Toolset to run on your PC, my PC, gives me the famous "unable to connect to data" error.

[Mage Dan]

I was able to install toolset fine without any issues whatsoever on an XP box with latest SP and .NET updates.



No idea where some of these issues are coming from. I did indeed have an issue however installing it on another box running Windows 7 and Steam, but there are plenty of easy workarounds for that.

[Zaszar]

I completely agree I bought the Dragon Age because of the Toolset. Could we get some clarification here please?

sirkaracho wrote...

Lord Sinner wrote...

Apparently... YESSSSSSS

plz BIOWARE guys

tell me thats not true

i bought the game because of the toolset, it is not my mistake that you use buggy software, the database connection issue has to be fixed

[ekbiddle]

Hello Mr.Patch, we are awaiting your arrival so all of us who bought your game can use your advertised toolset.

We will give you cookies when you get here.

Thanks!

[Awesome Brain Powers]

Seriously? A few of us could stand to take a breath. Read through Allan's first post:

Allan Smith wrote...

Please don't spam the thread with questions about when
it is coming out.  I will edit this post to say more when I can give
definitive information.  I can say  that it will not happen before November 16, and it will be day to day after that date until we have something that I am happy with.

So first, there's that.

For
those wondering about the "Can't connect to Database" issue. This is almost always an issue with the SQL Server 2005
installer, which is out of our control.  We have worked through many
issues in the past with this, yet no matter how many tweaks we make to
our process around it, it always seems to find another way to slap us
around.

I've bolded the important bit.

A
complicating issue with the patch is that we need to provide a path for
those of you who have created content and don't want to see it all
destroyed through the patch process.   Without going into great detail,
part of the change that we had to make for the Plot GUID affects how we
can upgrade your existing data.  We can do it,  but it is not as
straightforward as it should normally be.

The process is slower-going than even they want, because they don't want to screw the work you've already done. I applaud this, personally.

I still cannot provide a release date as all it takes is a failure on one platform/machine to send us back through another iteration.

Sound perfectly reasonable to me. In fact, it should sound perfectly reasonable to any reasonable person.

Additionally,
I am not entirely ignoring the forum, but I will not generally be
responding to a lot of questions here, as time spent doing that is time
not spent testing the toolset and the installer.

Again, perfectly reasonable. So let's quit howling at the moon and give them some time to find a way to fix it, yes? Especially since the database issue is them having to find a workaround for something that isn't even theirs.

So, thank you, Bioware Devs, very very much, for your obvious dedication to your fanbase. And thanks, the majority of the people here, for being patient, mature, and understanding.

[Darkmage187]

Quaxo wrote...

Opening a save file causes the toolset memory usage to jump from ~300MB to 1.5GB+ (in one case it went up to 1.89GB on my XP machine). Depended on how much memory you have and how much of it is in use when you attempt to open that save file, it's not surprising that you might run out of memory.

Are you attempting to open a quick save or a save saved through the menu? I noticed twice now that a menu save only pushed me up to 1-1.2GB whereas a quick save pushed me even higher. It might be coincidence or maybe even something to do with the way quick and regular saves are done. I haven't had time to really sit down and test that, but it's worth at least mentioning.

Yep, I noticed the same issue, in my case the toolset memory usage ranged from 1.6 + GB up to 2.23 GB.  I've tried both autosaves and quicksaves, and at the results are the same; most save files over 8 MB tend to lock up the toolset.  If anyone else is experiencing this issue, you might want to send a copy of the saved game file along with a brief explanation of the issue to:

toolsetsupport@bioware.com

Modifié par Darkmage187, 17 novembre 2009 - 09:22 .

[_ShadowHawk]

Perhaps I'm speaking out of turn here, but if some of these issues are due to the inability of the tool set installer to place SQL Express in a short enough path or the like, one could try downloading and installing the stand-alone database first. If the tool set installer checks for the software's existence before redundantly trying to install it again, it should simply use the already running service.

HTH.

[Argoyne]

As suggested above would it be possible to make the installer handle pre-existing sql express installs better. I have 2008 installed which came as part of the VS2010 beta 2 suite. I really only installed it cause I knew DA was needing an install and all versions of sql express prior to 2008 sp1 are not supposed to be compatible with win7/server2008r2 (quite what the issue is I've never bothered to find out the OS just likes to spit at me when it sees sql express).



The install didn't create any database so I followed the instructions on the wiki and eventually got everything working, at least on the surface haven't done anything with it yet.



I realise that folks with a pre-existing install of sql express and having no idea what they're doing with it may be a limited group but if the installer could handle it then it would be nice.

[Allan Smith]

I have edited the the top of this thread with another update. Things are proceeding well, but you will have to wait a bit longer still.

[Heptameron]

Thanks for the updates, Allan.



Just wondering—there's no reason to be paranoid of the toolset if you've got it installed already as long as you don't export anything that involves the main module (or if you do, you clean out the appropriate directories in My Documents\\BioWare)?

[Greg the Mad]

Thanks for the update. (I wonder what such a resurrected PC looks like ... zombie PCs!) And on my opinion that idea to synchronise the two patches is a good one, even if that means that my great modules ideas have to wait a week or two.

But I will wait for the update before I try the wiki walk though for the Database error ... I can hope, can't I?


Greg the Mad

Modifié par Greg the Mad, 18 novembre 2009 - 08:16 .

[Radimov]

Thanks for the update Allan.

[Cat Lance]

Thanks for the updates, Allan!

[Ginggis Khan]

The Only problem I've had it was that tool was unable to install the UNINSTALL exe file. I clicked ignore and since then (2+ weeks) toolset was working fine. Will you provide a way to remove the tool if normal process fails? I don't want any database leftovers that can potentially screm me over with your new "patched" toolset release.

[Johnmr531]

Could you guys switch to SQL Server 2008?

I dont know if it would help alleviate issues or not



My guess is the answer is no because it would cost more money, and some things may not work.

And it may not fix the issues.



But hey its a possibility lol