4 réponses à ce sujet

[nametab]

Every file I create in the DA:O Toolset is read only and I can't apply any changes to it. I can create a file, then save it under a different name and everything seems to be working fine. But when I save that file and reopen it it's marked as "read only" again.

I tried to uncheck the "read only" box in the properties of the folder, in which my toolset files are stored, but everytime I open the properties box it is rechecked again (I'm using Windows 7 by the way).

I can, however, create and edit .lvl files, which I save under a completely different folder in My Documents.

It's kind of ironic, cause I've just recently switched to a new PC. On the old machine I had a problem with lightmapping which prevented me from building my own levels, but I could do everything else. Now it's the other way around - I can make my levels but cannot populate them or assign them to areas.

[BryanDerksen]

Did you do a builder-to-builder load into this database at some point, and/or do any error messages come up when you try creating a new database resource? I recall running into some problems after doing a builder-to-builder load on a test machine a long time back that was caused by a problem with bad string ID ranges, it resulted in new resources failing to be created with a "cannot save resource" error. It didn't prevent things from being edited, though.

[BryanDerksen]

Okay, this is a puzzler. I've asked around the office and nobody has any really solid ideas for why something like this would happen. A resource that's checked out to you should simply not be read-only.



One speculative idea for what might be wrong is that you've somehow wound up with read access but not write access to the database. Are you comfortable working with MS SQL Server Management Studio Express? It's a free download from Microsoft and will allow you to get under the hood and look at some of the settings for your database. For this particular situation you'll want to see if the dragon age content database has the "bw_db_write" role (http://social.biowar...se_from_scratch has some information on this area).



When you reinstalled the toolset, did you uninstall the old version and tell it to uninstall the database too when it asked? If the problem lies with the database, it's possible that a reinstall will leave the broken database installation intact in the bacground depending on which options you choose during uninstallation/reinstallation.

[BryanDerksen]

We're getting into a tool that I haven't used much myself here, so unfortunately I'm not able to give a huge amount of advice. I'll do what I can.

When you run Studio Manager Express the first thing you'll be asked is which database server to connect to. There's a dropdown list, you'll want "<your computer name>\\BWDATOOLSET" (the default toolset database). Windows authentication should work.

I put up a screenshot of how the roles screen looks on my test computer. I think that all that's needed is for those roles to exist, I don't recall needing to do any special configuration to set them up once they were created.

http://social.biowar...se_installation and http://social.biowar...se_from_scratch may also have some clues to help you figure out what's going on in Management Studio Express.

[BryanDerksen]

Totally a stab in the dark, but perhaps the toolset hasn't been given sufficient rights by the OS to write to the database? Try right-clicking on the toolset and using "run as administrator" to see if that solves it.



Unfortunately I haven't actually used Windows 7 before myself so I'm not too familiar with its permissions. We're still primarily a Windows XP shop in here.