See http://forum.bioware...set/?p=19892496 for links about how to get a newer version of SQL Server working with the toolset (refers to 2008R2 but confirmed to work with 2014 in the last post in that thread).

I'd say create a new tutorial (it can link back to the create a new item tutorial easily enough if that is a prerequisite).

Ignore my previous - it is half right at best!
 
While I was able to recreate your problem when I set ShowItemsInGroups to 1 I think it was more coincidence than anything and unfortunately setting it back to 0 didn't fix it. Belatedly I realised it wasn't the grouping that was the problem but that the editor was grouping on the Flag Name instead of the Type that was the problem. Armed with this new insight I started poking the XML and the Toolset ...
 
I believe what happened was you inadvertently dragged the Flag Name column header down onto the list of flags. This does not appear to do anything at the time however when you close the Toolset it updates the Layout#.xml file with some new settings. Then when you next open the toolset, the Plot Editor is suddenly grouping on the Flag Name for no obvious reason!
 
So to actually fix your issue you can:

• delete the Layout#.xml file, or
• manually fix the contents Column# elements the Layout#.xml file (see below)

 

How to Manually Fix the Plot Editor's Grouping

 

If you open the Layout#.xml file and navigate to the Plot Editor's Columns element:

settings > DragonAgeToolset > DefaultLayout > Editors > PlotEditor > PlotsReportControl > Columns

You will probably see something like this:

          :
          <PlotsReportControl type="empty">
            <Columns type="empty">
              <Count>10</Count>
              <Column0 type="empty">
                <ItemIndex>1</ItemIndex>
                <Visible>0</Visible>
                <StaticWidth>50</StaticWidth>
                <AutoWidth>50</AutoWidth>
              </Column0>
              <Column1 type="empty">
                <ItemIndex>0</ItemIndex>
                <SortIncreasing>0</SortIncreasing>
                <StaticWidth>430</StaticWidth>
                <AutoWidth>120</AutoWidth>
              </Column1>
              :

I've only shown the Column0 and Column1 elements because those are the two we are interested in but there should be elements all the way up to Column9. If the Plot Editor was grouping on a different field then the theory would be the same but it would involve Column1 and another column element.
 
Column0 appears to be the Flag Name and Column1 appears to be the Type (i.e. Main or Defined flag). Normally don't see a column for Type: it is hidden and is only used for grouping.
 
Within the two Column# elements the important elements are the ItemIndex and Visible elements. For Column0 (Flag Name) we want the ItemIndex to have a value of 0 and there should be no Visible element. For Column1 (Type) we want the ItemIndex to have a value of 1 and the Visible element to have a value of 0 (meaning it is hidden).
 
When you are done it should look something like:

          :
          <PlotsReportControl type="empty">
            <Columns type="empty">
              <Count>10</Count>
              <Column0 type="empty">
                <ItemIndex>0</ItemIndex>
                <StaticWidth>434</StaticWidth>
                <AutoWidth>120</AutoWidth>
              </Column0>
              <Column1 type="empty">
                <ItemIndex>1</ItemIndex>
                <SortIncreasing>0</SortIncreasing>
                <Visible>0</Visible>
                <StaticWidth>50</StaticWidth>
                <AutoWidth>50</AutoWidth>
              </Column1>
              :

In C:\Users\<username>\Documents\BioWare\Dragon Age\Toolset\ there should be a file called layouts#.xml (where # is a number).
 
The easiest approach is simply to move or delete that file. That will reset every UI change you've made to the toolset but then that's what the File > Restore Environment menu option should have done for you.
 
If you feel a little more adventurous (and are comfortable editing XML) then all you should need to do is change the value in the ShowItemsInGroups element for the Plot Editor from a 1 to a 0.

NOTE: there are potentially a couple of ShowItemsInGroups elements in the file so you want the following one:

settings > DragonAgeToolset > DefaultLayout > Editors > PlotEditor > PlotsReportControl > Header > ShowItemsInGroups

Plot flags used to display in groups under two headings, split between main and defined. Somehow this got messed up, and now each flag is split up under an individual heading and I can no longer sort them by anything other than flag name. Does anyone know what arcane combination of keystrokes I must have accidentally typed at some point to make this happen, and how I can fix it? I can't find a setting anywhere to change this, and it's incredibly annoying. :\

 

Try the File > Restore Environment menu option. That should reset the Toolset's layout to how it was when you first opened it. If that doesn't work we may have to hunt for and manually delete your settings file.

Unhandled events or partially handled events (i.e. anything that doesn't set bEventHandled to TRUE) from creature_core and player_core drop through into rules_core.

Has anyone heard of the toolset missing ALL Single Player Resources AND how to fix this without uninstalling/reinstalling the toolset?  I hope there is a way to fix this without requiring an uninstall/reinstall so that she (potentially) loses all of her translations.  But it is the only way that I can see to fix this.

Yes. I can't remember the exact details but there was an issue that could result in an empty database but that was back in the very early days (possibly during the Toolset Beta). Also there's this though may only be relevant during installation.

 

Any chance you can throw the images up on imgur or the like or email them to me so I can see what you are seeing (PM me if you need my email address). Before doing anything too hasty (as Treebeard would say) it would be good to ensure there isn't a simple fix.

 

But if the worst comes to the worst there are a couple of options:

 

There is a B2B of all the Design Resources that could be reloaded. However if they are already in the database she'd end up with duplicates of everything. Best to take a back up of the database prior to loading this so she can simply restore back if anything goes horribly wrong.

 

Alternatively she can use the BAK file provided with the toolset to restore it to it's original condition. Be warned she would lose everything she's worked as the current data is completely overwritten in the process. Again taking a back up of the database prior to restoring the original is a good idea in case it's not what she wants.

 

You may be seeing a pattern here: taking backups of the database before you start messing with core resources is always good idea!

DP, the working link on the wiki is to v1.00, rather than v1.01... is that a concern or is one as good as the other?
 
ETA that manually changing the link address from '...DragonAgeToolset1.00Setup...' to ',,,DragonAgeToolset1.01Setup...' allows me to download the preferred version so just ignore my silly question please and thank you.

 
The CDN link was pointing to the wrong version. I've fixed that.
 

Which of these files should i download? this toolset is really confusing.

Alas that page is simply a repository of links to various resources on both the old BioWare Social Network and their new CDN so I appreciate it doesn't make much sense to a newcomer!
 
The only file you absolutely need is the Toolset. Ideally you want v1.01.

If you want to make your own levels (rather than reusing the ones BioWare created) then you'll need the Lightmapper script and a particular version of Python which we don't list on that page (see this section for details). You can install it if/when you decide to dabble in that dark art!
 
The entry under Design Resources was something I believe we needed for populating empty database. It's a builder-to-builder file containing all the core and single player (design) resources. It is not something we typically require any more unless, for example, you wanted to do a full manual database install (in contrast to the automated process or restoring from backup).
 
The remaining files under Art Resources are original BioWare resource files which can provide you with a head start if you want to start modifying the underlying art resources rather than just reusing them. They also be a handy learning tool because you can see what settings, etc. BioWare used to get a particular effect, etc.

 

That link worked. However, after i  now installed it-  it won't  connect to the database instead!.

 

What version of Windows are you installing on? Did you get any error messages during installation? Do you know SQL Server installed and if it is running?

 

Also it can be a bit daunting but you can try the Database Troubleshooting Guide!

Do you need one? I'm not a XBox user but it appear to be free on the marketplace for you (http://marketplace.x...bf-0016454108c0) also, and more importantly, so is the Stone Prisoner (http://marketplace.x...cf-0005454108c0) which is actual playable content (and one of my favourite companions).

I suspect it depends on which version you want to update to.

 

I recall that people have had it working with 2008 so I did a bit of digging and there is some references (e.g. http://forum.bioware...8-standard-x64/) to it working with both 2008 Express and 2008 R2. The secret appears to be to restore it from backup (which BioWare very decently provided for us) which sets the 2005 compatibility (Type 90) mode. I found this walk-through (https://jerbecca.wor...l-express-2008/) someone has created (which I'll need to port over wiki for safekeeping).
 
Not sure if anyone has tried any of the newer versions of SQL Server but all of the versions since 2008 have had this compatibility level (https://msdn.microso...y/bb510680.aspx) so the same approach might work on 2012 or 2014.

The plot is vgk210pt_woolsey (or plt_vgk210pt_woolsey) and its Main flags are:

VGK_WOOLSEY_MERCHANT_GATHERING_QUEST_JOURNAL             =   1
VGK_WOOLSEY_MERCHANT_GATHERING_QUEST_COMPLETE            =   2 <- reward & ends plot
VGK_WOOLSEY_ARMAAS_GATHERED                              =   3
VGK_WOOLSEY_INTRO_MERCHANT_RESCUED                       =   4
VGK_WOOLSEY_YURIAH_HAS_NEW_STOCK                         =   5
VGK_WOOLSEY_LILLITH_GATHERED                             =   6 
VGK_WOOLSEY_MERCHANT_GATHERING_QUEST_READY               =   7
VGK_WOOLSEY_MERCHANTS_GATHERED                           =   8
VGK_WOOLSEY_PC_LEFT_KEEP_AFTER_TALKED_TO                 =   9
VGK_WOOLSEY_UPGRADE_MERCHANT_BOARD                       =  10
VGK_WOOLSEY_UPGRADE_SOLDIER_PATROL                       =  11
VGK_WOOLSEY_UPGRADE_INTRO_MERCHANT                       =  12
VGK_WOOLSEY_MERCHANT_GATHERING_QUEST_GIVEN               =  13
VGK_WOOLSEY_UPGRADE_SOLDIER_FLAG                         =  14
VGK_WOOLSEY_UPGRADE_MERCHANT_BOARD_FLAG                  =  15

You are unlikely to need them but the Defined flags are:

VGK_WOOLSEY_ALL_MERCHANTS_FOUND_BUT_QUEST_NOT_COMPLETE   = 256
VGK_WOOLSEY_ALL_MERCHANTS_FOUND                          = 257
VGK_WOOLSEY_TWO_MERCHANTS_COMPLETE_AND_SOLDIERS_ASSIGNED = 258
VGK_WOOLSEY_MERCHANT_QUEST_NOT_GIVEN_AND_LEFT_KEEP       = 259
VGK_WOOLSEY_SOME_MERCHANT_BOARD_QUESTS_COMPLETED         = 260

So you might be able to force it to complete using flag 2, like so:

runscript zz_getsetplotflag set vgk210pt_woolsey 2 1

Alternatively you could try setting flag 6 to true to ensure that it knows you have Lillith which might allow you to complete the quest in the normal way.

 

Either way make sure you save your game before playing around with the plot flags so if doesn't work as expected you can revert back and try another Main flag.

I've emailed Jesse to see if the changes were intentional or accidental but as DP says it may be time to resurrect the conservancy project from last year.

I've now also updated my Windows 7 PC to Windows 10 Pro. The only hiccup (can't even call it an issue) I encountered is that Windows didn't start the SQL Server (BWDATOOLSET) service so I got the old the "Unable to connect to database" error when I tried to start the toolset for the first time. If anyone isn't sure how to fix that issue refer to this section in the wiki.

Since some users encountered problems with installing/using the toolset with Windows 8 and Windows 8.1, I thought it might be useful to start a thread to collate information about how the toolset gets own with Microsoft's latest offering.

 

Have you installed Windows 10? Was it a clean install or an upgrade (and if so from which version)? Did you install the Dragon Age Toolset or was it already installed? Does the toolset run, how does it perform, any issues, etc?

 

For my part I've just installed Windows 10 on my laptop. My laptop was Windows 8 and I had installed the toolset when I got it with just a couple of minor issues (discussed/linked in the Windows 8.1 thread) and I'd been using it for months without a problem (other than my general dislike of the Windows 8 UI). I hadn't been able to update to Windows 8.1 because Microsoft took exception to the fact I'd moved my Users folder to my D:\ drive!

 

When Microsoft announced Windows 10 free upgrade (or Start Menu Emancipation Project), I bit the bullet and restore the laptop to factory settings, updated all the way to Windows 8.1 and reinstalled the toolset. In doing so I did get a couple of compatibily warning with regards to SQL Server 2005 Express but I was given the option to continue on regardless. The install was completed and the toolset started without incident. Admittedly I haven't done much more than start the toolset and open a couple of resources so I suspect I would still have to resolve the same issues I'd encountered under Windows 8 with regards backing up/restoring the database, etc.

 

This evening I updated to Windows 10 Home (I had to do it manually as Windows Update kept failing) and everything has appears to have gone smoothly. I booted up the toolset and, after an agonising few seconds, it opened without incident. Again in the interests of full disclosure I only started it and opened a couple of resources (no, of course one of them wasn't a script, honest!). If I encounter any issues when I have a reason to start creating additional databases or using backup/restore database I'll post an update.

 

TL;DR: Toolset installed under Windows 8.1 appears to work under Windows 10!

You don't need to register the game any more: we have direct links (and links to the mirrored copy on BioWare's CDN) to the Toolset and associated resources on the Community:Toolset_source_files page in the wiki.
 
Note the only thing we don't have there is the correct version of python used by the light mapper.

There's a visual reference in the wiki if it helps.

Another way to do the same thing which people might find easier, or at least more familiar, than SSSAC is to use the Windows Services management console:

• Open the Services management console:
  • Open the Start > All Programs > Administrative Tools menu and click on the Services shortcut, or
  • Open the Start menu and type Services in the Search for programs and files field and click on the Services program, or
  • Press Windows + R and type services.msc and click OK
• When the Services management console opens, scroll down until you get to SQL Server (BWDATOOLSET) entry
  • PRO TIP: typing S or SQ will get you there a lot quicker!
• If the Status is not Started:
  • Click the Start link (top left of the window), or
  • Right click and select the Start menu option
  • NOTE: you can also start or stop services through their Properties window (below) or the Windows Task Manager if you prefer
• If the Startup Type is not Automatic:
  • Open the service's Properties window:
    • Double click on the service, or
    • Right click on the service and select the Properties ... menu option
  • When the Properties window opens, select Automatic from the Startup Type dropdown list on the General tab

We have direct links (and links to the mirrored copy on BioWare's CDN) to the Toolset and associated resources on the Community:Toolset_source_files page in the wiki.
 
Note the only thing we don't have there is the correct version of python used by the light mapper.

I'm not aware of any way to listen for a keypress that's been exposed to scripting. There might be a way to do it through hacking the UI (see FollowTheGord's user page for links) or you could create a custom ability and pop it the first 12 slots of your quick-bar.

 

There is a reference category in the wiki which includes the functions category. Broken functions should be flagged with the broken functions category when they are discovered however I suspect there are more than the five listed there.

 

Not sure what you are looking for in terms of "global variables". If you are talking about settings or configuration you might want to look at the INI file or one of the many 2DA files. If you are talking about scripting then values are generally transferred/persisted through effect/event variables or an object's local variables. And while it is technically possible create a variable outside of a function it is only "global" to that script or scripts that included it I wouldn't recommend doing this.

 

I can't say how others discover things but for me it is reading the wiki; searching the internet and then trial and error/a lot of testing.

The "download the toolset" link on the old BSN is only accessible if you have registered a PC version of DA:O ... fortunately the file are accessible to everyone. We have direct links (and links to the mirrored copy on BioWare's CDN) on the Community:Toolset_source_files page in the wiki.

 

Note the only thing we don't have there is the correct version of python used by the light mapper.

The "download the toolset" link on the old BSN is only accessible if you have registered a PC version of DA:O ... fortunately the file are accessible to everyone. We have direct links (and links to the mirrored copy on BioWare's CDN) on the Community:Toolset_source_files page in the wiki.

 

Note the only thing we don't have there is the correct version of python used by the light mapper.

Like I have anywhere to go!

Sorry the delay in getting back to you. Unfortunately work happened and wouldn't stop happening!

 

Anyway if memory served I had to set myself up as a dbo (database owner) for the toolset's database but we'll check a couple of things first to ensure you have a database and its running first ...

 

If the toolset installed (i.e. you didn't get any big scary warning during the installation like the ones you are seeing now) then you should already have SQL Server Express 2005 installed. If so you don't need to reinstall it. We can confirm it easily (and to ensure it is running): bring up Services console (start > run > services.msc), and look for a service called SQL Server (BWDATOOLSET).

 

If you don't have this service then it means the toolset's database hasn't installed. You probably want to uninstall the toolset, try reinstalling and it paying close attention to any  messages that pop up. The normal installation will install the editor and then install SQL Server Express 2005. If you encounter a problem screenshot it or note the details and let us know.

 

If do have this service installed but it's not running then (if we are lucky this is your only problem): simply right-click on it and select the Properties menu option. In the middle of the General tab you should see a drop down labelled Startup type; ensure this is set to Automatic, then click the Start button. Once the service has started click the OK button to save your changes, close the Services console and try running the toolset again. If the toolset starts, connects and you can see modules you're golden, if not keep reading ...

 

If the service is installed and running but you can't connect to the database then it's probably a user rights/privileges issue. To fix this you'll need to download Microsoft SQL Server Management Studio Express (MS SSMSE) and make your normal Windows log in a database owner for the toolset. I believe if you follow steps 1, 2 (if required) and 3 in this post that will resolve that problem.

 

Let us know how you get on.

You could give them a choice but the question is how would you present that choice to the player is an elegant way?

1. We could extend the guard's conversation with some (silent) options. Kind of clunky/immersion breaking but gets the job done.
2. We could do something through game play: for example insert a character into the Post-Coronation Hall who say something about the invitations having to be sent out and has the Player having to decide on a venue. This could set a plot flag that we subsequently look up to determine the transition. This would require someone to do some voice over work and the player would have to be aware they need to speak to the "wedding planner" before leaving.
3. Or we could make it data driven using a 2DA or the INI file but that runs the risk of the player putting in the wrong data.

So it's perfectly possible however it probably means a lot more cutscene work for very little gain.

I don't know about Windows 8.1 specifically but I have it installed on Windows 8.0 and it works fine. I do recall there were some minor issues with the database but nothing that couldn't be resolved.

 

If the installation is failing when is that happening and what is the error message you are encountering?