80 réponses à ce sujet

[Vae_Victis]

Oh and Dalish, the Wiki was my first resource, and it is crap. The instructions it gives you dont even apply to XP apparently, so it was no help at all. And i tried many of the fixes mentioned in the Wiki, even if they didnt apply to my problem, and still no luck.

I have XP and Steam. I had problems at first but using the intructions on the Wiki my installation went smooth as silk. Haven't hit a single snag since.

I reinstalled the Toolset, I didn't have the files the Wiki mentioned so I did as it suggested and created a dummy txt file.

[Zihlur]

Actually, he meant it would have installed without a hitch.



But I agree that it is silly and uneducated like of someone to say things without fully understanding something.



Anyway, my gripe is that they didn't include the core files of the game, forcing people to create something that could possibly not work or break something that DOES work (Lolz me). A couple more in-depth tut's would help... after all, when a random non-Bioware affiliated person can make a better tut for the toolset than they can... well... somethings wrong.

[EvilEdison]

I'm starting to wonder if the toolset issues are just a screening process. Someone said in another post that if you can't handle the frustration of the install, the frustration of the toolset will kill you! I paraphrase of course

[leotime0]

sirkaracho wrote...

we paid for it, so of course everything should be "handed" to us

 
you paid for the game not the toolset

[Ticladesign]

The whole install issue was a no-brainer tbh - took me just a few to read the right threads and the Microsoft website link. It was fixed in no time.



The Area editor, it was okay.. didnt expect it to be very easy. Running the made module, now that was an issue. And it still is, as any module I make seems to break the OC in one way or the other. Best guess is that this happens because it's not a modulair game with closed off modules that dont affect the main game. I would have preferred a modulair game, though. Maybe a next game can be modulair again, with all the features some miss I guess. (easy to use toolset, closed modules, MP, ect.)



But it will be hard to do.. as players these days demand more and more complex game systems that in turn makes the toolset more and more complex.



The big problems i'm having are mostly the needed time needed for the level editor, not knowing too well how to save a lvl without errors (thus it not saving) and getting some light in my level, right now my eyes just hurt from peering in an area thats just too dark to see propperly in.



Music also doesnt seem to happen.. I might be missing something (script?)

And when testing my character does not seathe weapons after an encounter, unable to transition afterwards.



Can encounters also respawn? I cant find the encounter Tab, guessing it's a trigger, but not sure how that works.



But Campaign corruption after exporting a self made module (or addin) is my biggest gripe. Would have preferred a closed off module file that would not touch the main game resources.

[LionFranco]

Ticladesign wrote...

The whole install issue was a no-brainer tbh - took me just a few to read the right threads and the Microsoft website link. It was fixed in no time.

Again, i spent 2 days working on this for most of those 2 days. I resolved the major corruption issues this caused that threatened to destroy my computer, and am now down to only a simple issue, that should be easily fixable, but NOTHING that has been posted, either on the forums or in the wiki has worked, and i have tried EVERYTHING i could find that has been posted up until now.

[Arkenor Oakshadow]

The toolset seems to be working for me, but darned if I can actually get it to do anything I want it to. Making my head hurt, but I am not beaten yet. I'm hoping that at least some of my problems are due to bugs or the thing with half the utilities being the wrong version, because this is seriously shaking my faith in my modding ability.

Maybe things will get easier as more documentation appears.

Modifié par Arkenor Oakshadow, 09 novembre 2009 - 05:28 .

[Toom316]

DFM2005 wrote...

I'm going through some of bioware's code for this game, one thing i've noticed is some of the code is from 2006.

It's basically an updated version of NWN2, it's like i thought earlier when i mentioned about why they didn't use the Witcher engine for this game.

It's because they were already to far into the game, to scrap it especially because it was costly to develop. So alot of the problems I'm thinking is because, they are trying to merge this old database with the newer OS's plus the trouble of services packs.

The reason i'm thinking this is because you hardly see any new games using sql only game i've seen using sql was super power 2 and that was from 2005.

That's one of the reasons you have to release the game prematurely for funding purposes, like all the other games i've seen this done with the goods are always down the road.

So to me it's not that big of a deal i can wait.

I guess you know less then you think. The game itself does not use SQL.  The Toolset DOES use SQL because it is the same toolset the dev's used to make the game. It was designed to be used by a group of people (gasp). The whole point of the SQL database was so that a group of developers could all be working on the same level at the same time. Each one designing different buildings and such and being able to put them all togeather.


Would it have been nice for them to strip out the sql database and build it into the tools for a end user product? I a sure it would have been but at the same time we would have lost all the additional options the sql database provides us while working with a group of people.

As it stands now myself and my team of dev's love the sql database. It provides us a easy way to see what each one of us is working on and provides a central spot for all of our efforts into our mod. (We have a single dedicated server setup that we have all mapped as a network drive and we also setup the sql server onto that box. We all connect to that box via the toolset so we see each others progress in real time on level layouts and such.)

Most of peoples issues with the toolset are having to do with them trying to install it on a XP machine without SP3. SP3 is a requirement to get the toolset in and working correctly.

Modifié par Toom316, 09 novembre 2009 - 05:26 .

[EvilEdison]

Is your remaining issue that you cannot get the SQL to install correctly? Trust me, I feel your frustration. I spent an entire afternoon getting this to work (although most of that time involved a great deal of ranting and yelling).



You've probably done these things, but for the record, have you updated to Service Pack 3 and also removed MSXML6 before trying to reinstall the toolset? When you removed MSXML6, did you do it via Add/Remove programs or did you use the Windows Installer Cleanup utility?

[Astorax]

All other issues aside, I don't believe SP2 was part of Lion's problems as he's been reading and working on things consistently.



I'm sorry you're having a hard time with it, but I'd echo the suggestion of a number of folks here, and take a break from trying to work with the toolset for a few weeks until the problems are ironed out.



The main issue here is that for Bioware, they have a dedicated IT department to ensure that everything is working. Generally speaking, what fixes any given problem doesn't get built into a knowledge base that is then made available...so we're all now fumbling with the same issues they did when they got someone new in on the toolset. The problem is, we're not IT professionals so we're fumbling a bit to get things working.



Patience is rough when there's something here waiting to be discovered and played with I realize, but if you're having problems, that's all I can suggest.



Also, for whoever it was that's corrupting the OC with any saved modules...just to be sure, you did created a new module before creating any areas or scripts of any kind, right? If you don't, without realizing it by default the toolset brings up the original campaign's module and if you dive right in creating areas, etc, you're actually modifying the Single Player game.

[EvilEdison]

Arkenor Oakshadow wrote...

The toolset seems to be working for me, but darned if I can actually get it to do anything I want it to. Making my head hurt, but I am not beaten yet. I'm hoping that at least some of my problems are due to bugs or the thing with half the utilities being the wrong version, because this is seriously shaking my faith in my modding ability.

Maybe things will get easier as more documentation appears.

Keep in mind that the people who develop video games go to school for several years to develop their skills and learn the various tools they use. It is unfair to yourself to expect that you will understand how everything works in less than a week.

[sirkaracho]

leotime0 wrote...

sirkaracho wrote...

we paid for it, so of course everything should be "handed" to us

 
you paid for the game not the toolset

no, i payed for the full package, and that package consists of the game AND the toolset, and i got that package only because of the toolset, the game is just a big bonus to me

i have EVERY right to get a working toolset as it was advertised, if its okay for you that the toolset is not working than ok thats your opinion, but that doesnt have to be my opinion to, and that the package was advertised to include a working toolset is a FACT

[Eidolonn]

sirkaracho wrote...

leotime0 wrote...

sirkaracho wrote...

we paid for it, so of course everything should be "handed" to us

 
you paid for the game not the toolset

no, i payed for the full package, and that package consists of the game AND the toolset, and i got that package only because of the toolset, the game is just a big bonus to me

i have EVERY right to get a working toolset as it was advertised, if its okay for you that the toolset is not working than ok thats your opinion, but that doesnt have to be my opinion to, and that the package was advertised to include a working toolset is a FACT

The toolset works just fine.  It just may take some troubleshooting to get it installed.  Such is life.

[sirkaracho]

no, it doesnt work, it even killed my system, i tried to install it since friday, nothing works, its just a pool of bugs



if you are being serious and thats not a fake post from some EA guy, then you just have tons of luck that those solutions did work for you

[Toom316]

sirkaracho wrote...

no, it doesnt work, it even killed my system, i tried to install it since friday, nothing works, its just a pool of bugs

if you are being serious and thats not a fake post from some EA guy, then you just have tons of luck that those solutions did work for you

I installed and had the toolset working within 2-3 mins. This was on a Windows 7 x64 machine. Just ran the installer and read what the installer said and followed its directions. It installed everything just fine. Clicked the launch toolset icon and it worked without any issues.

So to say the Toolset does not work is just lying. It does work.  That in no way says that it will work for everyones setup. Everyone has different OS's and are at different service packs, ect. For me on a fresh Windows 7 x64 install it worked without any issues what so ever.

I just looked at the Game Box and NO-Where on the box does it state it comes with a toolset. 

[Eidolonn]

sirkaracho wrote...

no, it doesnt work, it even killed my system, i tried to install it since friday, nothing works, its just a pool of bugs

if you are being serious and thats not a fake post from some EA guy, then you just have tons of luck that those solutions did work for you

The only issue that could possibly fall into the category of "killed my system" is the issue with SQL 2005 and XP Service Pack 2.  This is NOT a BioWare issue, by the way.

But since you have offered no other specifics other than this generic (exaggerated) description, there is no way to address your issue directly.

[Nalencer]

The toolset works. Bioware developed the entire long, extremely complex OC with it, so it must. But that's not to say it works out of the box on every system imaginable. This stuff takes some work to get up and running.

[Eidolonn]

Toom316 wrote...
I just looked at the Game Box and NO-Where on the box does it state it comes with a toolset. 

That is actually irrelevant.  The toolset was provided to all people that purchased DA:O.  The only way that you can use the toolset is by purchasing the game, thus the two go hand in hand. It may not be on the box, but this was an advertised feature and was used as a selling point by BioWare.

All that aside, we have the game and we have the toolset.  Both work quite excellently.  There are some bugs to work out, just like with any other piece of complicated software. 

People can either help to troubleshoot and resolve those problems, do nothing and wait, or complain about them.  Only one is productive while another is counter-productive.  It's your choice which type of person you wish to be.

[gassaway]

My 2 cents. I bought thegame for the tool set I love NWN tools and was hopeing for the same quality... I feel like a peewee ballplayer playing a professional team. Its frustating and over the top im not a professional programmer and dont plan on becoming one but I could always turn out stuff for the guys with NWN it was easy to catch on this DA stuff is just too much to enjoy for the casual player/programer

[Eidolonn]

gassaway wrote...

My 2 cents. I bought thegame for the tool set I love NWN tools and was hopeing for the same quality... I feel like a peewee ballplayer playing a professional team. Its frustating and over the top im not a professional programmer and dont plan on becoming one but I could always turn out stuff for the guys with NWN it was easy to catch on this DA stuff is just too much to enjoy for the casual player/programer

But just think if you DO master it.  It's actually not too far off from NWN, and definitely closely related to NWN2.

My intent is to focus on my strengths that parlay from NWN and NWN, while slowly mastering the new functionality and features.  The former should give me plenty to work on now, and the latter will give me plenty to work on later.

[sirkaracho]

So to say the Toolset does not work is just lying. It does work.  That in no way says that it will work for everyones setup. Everyone has different OS's and are at different service packs, ect. For me on a fresh Windows 7 x64 install it worked without any issues what so ever.

there is so much software out there that works for everybody, at least everybody can install most of the software out there, so saying that its ok that software doesnt work for many people because there are different configurations out there is just a lazy excuse, i dont have some alien system from outer space, i have windows xp, service pack 3, no special things configured that would prevent software from working

I just looked at the Game Box and NO-Where on the box does it state it comes with a toolset.

that statement of yours is just an insult to all of us legal customers, the toolset is advertised everywhere, it DOES belong to the product and is the sole reason for many to buy this game, at least for me it is

The only issue that could possibly fall into the category of "killed my
system" is the issue with SQL 2005 and XP Service Pack 2.  This is
NOT a BioWare issue, by the way.

of course it is biowares issue, where they forced to use bugged software to include into their product? i bought other "make your rpg"-software before, and guess what? it didnt install buggie sql things, it just worked

This stuff takes some work to get up and running.

i payed for the work to get this stuff running by buying it, the only work i as a customer am expected to do is just installing the software and then using it, its okay if they say "you need this and that free software to run the toolset" and nobody is perfect, so mistakes happen, the guys at bioware still have the chance to make things right, but i bought dragon age because of the toolset, and so i am in a bad mood because none of the solutions worked for me, and postings like that from toom316 "NO-Where on the box does it state it comes with a toolset." make it only worse - the toolset clearly belongs to the package i bought, the toolset was and is advertised everywhere and is hyped as THE revolutionary rpg building tool

ok if somebody wants to help me:

windows xp service pack 3
dragon age collectors edition
after setting the windows system32 folder to unprotected and the complete dragon age folder too, it installs without any bug, but i cant start the toolset because there is no database

i then opened that sql program where i can drag and drop rights to the admin and i dragged the rights for the database over

setting the sql stuff to "local" service doesnt work, i get an error then

i also typed those two lines into the command window:

reg query "HKLM\\SOFTWARE\\BioWare\\Dragon Age\\Toolset\\Environment" /v DefaultDatabaseConnection

reg add "HKCU\\Software\\BioWare\\Dragon Age\\Toolset\\Environment" /v
DefaultDatabaseConnection /t REG_SZ /d "Provider=SQLOLEDB.1;Integrated
Security=SSPI;Persist Security Info=False;Initial
Catalog=bw_dragonage_content;Data Source=.\\BWDATOOLSET"

the second line asked me to overwrite some default stuff, i tried both, yes and no

then comes the line that should create my database:

"c:\\Programme\\Microsoft SQL Server\\90\\Tools\\Binn\\SQLCMD.EXE" -S .\\\\BWDATOOLSET -E -Q "RESTORE DATABASE bw_dragonage_content FROM DISK = 'C:\\Programme\\Dragon Age\\tools\\dbbak\\bw_dragonage_content.bak' WITH MOVE 'bw_dragonage_content' TO 'C:\\Programme\\Dragon Age\\tools\\toolssql\\Data\\bw_dragonage_content.mdf', MOVE 'bw_dragonage_content_log' TO 'C:\\Programme\\Dragon Age\\tools\\toolssql\\Data\\bw_dragonage_content.ldf"

i get a prelogin failure on that line

it doesnt work, "SOME troubleshooting" is just an insult, it doesnt work, i dont know what else to do, it is not that i was not willing to go about some troubleshooting and get that thing to work, but nothing helped, if anybody can help me: plz do, if bioware is working on a solution: plz tell us


dont get me wrong, mistakes happen, EA is the devil, and i am sure there are many hard working guys at bioware, they still have the chance to proof that they are the kings of rpg and tools and stuff, but right now what they are selling would be a reason to get them into real trouble if that what they are selling would be a car or something

[LionFranco]

EvilEdison wrote...

Is your remaining issue that you cannot get the SQL to install correctly? Trust me, I feel your frustration. I spent an entire afternoon getting this to work (although most of that time involved a great deal of ranting and yelling).

You've probably done these things, but for the record, have you updated to Service Pack 3 and also removed MSXML6 before trying to reinstall the toolset? When you removed MSXML6, did you do it via Add/Remove programs or did you use the Windows Installer Cleanup utility?

Thanks Ed, i appreciate the people that have been supportive with my issue.

Of course for the people that mentioned it, I have WinXP SP3 installed, so that isnt the issue.

I do have one question. You mention removing MSXML6 before installing the toolset. Now MSXML6 was an issue at one point, apparently i had a corrupted install, and i removed it via the msicuu2 program or whatever the windows installer cleanup utility is called. But i thought i was supposed to make sure MSXML6 was installed, so i found the most recent version and installed it (even though it calls it a parser, if that makes a difference).

So should i remove MSXML6 completely, and let the toolset install it, and do you think that could be the cause of the MSSQL issues?

I really want to mess with this toolset, and if it is even half as intuitive as the NWN2 toolset, then i'll be able to work with it just fine.

I wish i had been able to get my original NWN module published, but alas it fell prey to fatal error with my pc and i lost it all, and i havent finished anything in the NWN2 toolset yet.

If this MSXML6 thing might be the issue i'd be happy, and i'll try this evening when i get home from work, but i'm skeptical at this point.

[Eidolonn]

sirkaracho wrote...

i get a prelogin failure on that line

Check your services.  Is your SQL service started?  If it is started, change the login account from LOCAL SYSTEM to the account (user name) that you are currently logged into your computer as (or use the administrator account).  Supply the password if you have one.  Restart the SQL service.

Proceed with the toolset installation from that point.

If none of that works, please check your Windows Event Log and report back what errors are displayed there for Application and System.

[Maria Caliban]

sirkaracho wrote...

we paid for it, so of course everything should be "handed" to us

You paid for a game. The toolset was a free download off the site.

[EvilEdison]

LionFranco wrote...
So should i remove MSXML6 completely, and let the toolset install it, and do you think that could be the cause of the MSSQL issues?

Yes. After I upgraded to Service Pack 3, I tried to install the toolset again. Kept getting an error message that it couldn't install SQL server. Removed MSXML6 using Windows Cleanup Utility (couldn't remove it in Add/Remove for some reason) and then tried to install toolset again. Worked like a charm.