313 réponses à ce sujet

[Deruu]

So will my corrupted save games be fixed?

If not then I can't be arsed to continue playing :/

[Martymer]

Thanks. It's good to know that the issues are being acknowledged, and I'm glad that we're being informed that something is being done. I also think it's great that we know we'll have to wait a few days. No stupid "we're working on 'a patch' (that does ... eh... something, I guess) and it'll be out 'when it's done' (just like Duke Nukem Forever)". Plenty of bad designers should take notes.

[Smakit]

The info is much appreciated. While in a magical land of make believe, we all (you fellas at BW included, of course =)) would have liked it out of the barn, day 1, with no problems - this kind of stuff happens.



It is nice to see you at least are keeping us in the loop and informed. I do worry with the holidays coming up on how it will progress, but at least it is rolling. I definitely agree with others about the lighting issues - and there may be others I haven't even noticed, as my usage has been here and there with the toolset currently.



I wish you guys the best of luck - and stay away from all those germs, viruses, and darkspawn there, and get better soon.

[bluevapor]

Great to hear you guys are working on it! I've avoided downloading the toolset so as not to cause problems with the game, but I can't wait to start tinkering with it.

[sirkaracho]

Doug-Le-Guedin wrote...

Hi all!
I'm french and I don't understand if the "Unable to connect to the databse" issue will be fixed ?
Can you reply to my message by a simple Yes or No ?

They mentioned nothing about that in the first Post, i hope it will be fixed too.

[AnTeevY]

Well that's mostly a Microsoft SQL issue, i doubt that they can fix this...

[Valfreyja]

Well I've got that issue too and I've doublechecked everything, even tested the connection and it all works -except the bloody toolset- who can't connect at all.

[KREUGER44]

sirkaracho wrote...

Doug-Le-Guedin wrote...

Hi all!
I'm french and I don't understand if the "Unable to connect to the databse" issue will be fixed ?
Can you reply to my message by a simple Yes or No ?

They mentioned nothing about that in the first Post, i hope it will be fixed too.

There are houndreds of people complaining about this and surely maybe thousands having this issue. I hope Bioware will consider to solve this in the patch, please. I´m one of them. 

[BryanDerksen]

One problem is that "Unable to connect to the database" could be a symptom of all sorts of different possible underlying problems. We've found a few issues that might give rise to it and we'll be fixing those in the next toolset release, but that doesn't guarantee that we've found all of them.



One that we just uncovered serendipitously while fixing the "missing generate FaceFX" bug is that there's a registry key that can cause this message to come up if it's missing.



Location

HKEY_LOCAL_MACHINE\\SOFTWARE\\BioWare\\Dragon Age\\Toolset\\Environment



Name:

DefaultDatabaseConnection



Value

Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=bw_dragonage_content;Data Source=.\\\\BWDATOOLSET



If you're having the cannot connect error, check your registry to see if this key is there. Since the FaceFX bug is being caused by a registry key being missing it's possible that some of the connection failures are being caused by this too.

[Highlen]

great news

[georage]

** Can you unlock the Bioware levels so modders can mod them and add them to custom mods?



** Can you fix the lightprobe/water problem?



** Can you make it so I can use the toolset on a machine that does not have the full game installed? I understand the toolset may need to game resources, but I'd like to toolset (or at least script) at work.

[shreddog]

BryanDerksen wrote...

Location
HKEY_LOCAL_MACHINE\\\\SOFTWARE\\\\BioWare\\\\Dragon Age\\\\Toolset\\\\Environment

I tried that, didn't work. Btw my Bioware folder was located under HKEY_CURRENT_USER, not local_machine. Can that be the problem? Maybe the toolset is looking in the wrong spot

[BryanDerksen]

It looks in both locations, so that's not the root cause of this particular "unable to connect" error. Maybe one of our other fixes will catch it, I hope.



We haven't done anything with the lightmapper just yet, our priority has been to fix these various showstopper bugs that have cropped up and get a release out addressing them as soon as possible. Assuming nothing else unexpected blows up that'll probably be next on our agenda afterward.



I don't think a stand-alone gameless toolset is on the agenda. Some of the agreements we made that allowed us to distribute third-party components such as FaceFX, FMOD, Speed Tree, and so forth for free stipulate that we can only distribute them to owners of the game, so producing a stand-alone toolset that included those components could potentially get us into trouble. The disk check copyprotection doesn't kick in for the toolset, though, so you could perhaps install the game at work and then leave your disk at home?



Can't give an ETA on when we're releasing additional designer resources, but rest assured that I raise the issue at regular intervals in here.

[sirkaracho]

thanks for giving us all kinds of little details, nice to know whats going on and that you guys want to fix all stuff

[Heptameron]

Will the patched installer fix a current installation, or will the people with the toolset installed right now have to uninstall and reinstall?

[-Semper-]

don't get me wrong, the last thing i want to do is blaming someone for this mess - but after months of qa (or is ea broke?!) and bugfixing that toolset seems more like a horrible joke



especially the lightmap, water and corrupting the core glitch . that's something that arise the first minute testing the toolset. how could that happen?! i mean... it's not completely a new code, just a "better nwn". in general how could bioware build up dragon age with this piece of software like they said?



i think that they don't let us modify or even load up their modules is something ea is responsible for. they're just afraid that the dlc (right now it cashed out about a million dollar) would rot in the shelves if the community produce good quality content for free too fast. but that's just a assumption.



man... i'm so dissapointed.

[Valfreyja]

shreddog wrote...

BryanDerksen wrote...

Location
HKEY_LOCAL_MACHINE\\\\\\\\SOFTWARE\\\\\\\\BioWare\\\\\\\\Dragon Age\\\\\\\\Toolset\\\\\\\\Environment

I tried that, didn't work. Btw my Bioware folder was located under HKEY_CURRENT_USER, not local_machine. Can that be the problem? Maybe the toolset is looking in the wrong spot

Hm then I'm either doing something horribly wrong or it's not stored in either for me. It seems to be stored in the "MyDocuments" folder for me and when I went to check, it had no environment folder at all...

[LionFranco]

-Semper- wrote...

don't get me wrong, the last thing i want to do is blaming someone for this mess - but after months of qa (or is ea broke?!) and bugfixing that toolset seems more like a horrible joke

especially the lightmap, water and corrupting the core glitch . that's something that arise the first minute testing the toolset. how could that happen?! i mean... it's not completely a new code, just a "better nwn". in general how could bioware build up dragon age with this piece of software like they said?

i think that they don't let us modify or even load up their modules is something ea is responsible for. they're just afraid that the dlc (right now it cashed out about a million dollar) would rot in the shelves if the community produce good quality content for free too fast. but that's just a assumption.

man... i'm so dissapointed.

Man, you have to realize that these things dont show up on all systems. It wasnt going to show up in most bug tests and qa tests, as  many of the pc's they would use to run the game and toolset have all the needed files installed already, so stuff like this really can only be found once it gets out into the market, that is why forums like this and patches are so important in PC gaming, because atleast once these problems have been found, they can be fixed.

Dont blame bioware or ea, blame the millions of different possible pc software and hardware configurations that cannot be accounted for when doing bug testing.

[-Semper-]

LionFranco wrote...

Man, you have to realize that these things dont show up on all systems. It wasnt going to show up in most bug tests and qa tests, as  many of the pc's they would use to run the game and toolset have all the needed files installed already, so stuff like this really can only be found once it gets out into the market...

well, the lightmap and water bug and also the corrupted saves are affecting everybody playing with the toolset - so do i know. and that's for sure something that has been noticed during qa, particularly when the initial release day is 8 months ago! considering the first damaged german/european version of the game... yes, dragon age is massive and damn good (heck, i love it!) and i know bugfree software will never be, but it all adds up under ea's guidance.

Modifié par -Semper-, 14 novembre 2009 - 11:12 .

[Jazpar]

bjornis wrote...

shreddog wrote...

BryanDerksen wrote...

Location
HKEY_LOCAL_MACHINE\\\\\\\\\\\\\\\\SOFTWARE\\\\\\\\\\\\\\\\BioWare\\\\\\\\\\\\\\\\Dragon Age\\\\\\\\\\\\\\\\Toolset\\\\\\\\\\\\\\\\Environment

I tried that, didn't work. Btw my Bioware folder was located under HKEY_CURRENT_USER, not local_machine. Can that be the problem? Maybe the toolset is looking in the wrong spot

Hm then I'm either doing something horribly wrong or it's not stored in either for me. It seems to be stored in the "MyDocuments" folder for me and when I went to check, it had no environment folder at all...

I miss that folder too. exactly like bjornis.

[shreddog]

Jazpar&Bjornis we're talking about the registry here, not the game folders. To edit your registry you have to use the windows regedit.exe utility. But be careful, if you change settings or mess something up there there is no way to undo it.

[Valfreyja]

Think I'll just wait for a patch or something in that case.

[Solitude_Aeturnus]

That is part of QA.  There is only four different configurations that need to be tested.  AMD/ATI, AMD/NVIDIA, INTEL/ATI, INTEL/NVIDIA.  With that, XP, Vista, and 7 which all can be done using virtualization but I am sure a company who tests software, has a license for this.  Secondly, there was a beta of the toolset in which this should have found the XP SP2 rebooter.  At some point and time, before the release, something had to have changed, period, or the toolset we got isn't anything like the original they used to make this game.

Modifié par Solitude_Aeturnus, 14 novembre 2009 - 06:27 .