Dragon Age Toolset Wiki - User contributions [en]

Invalid curve

2011-11-20T17:16:25Z

BloodsongVengeance: toolset error directed me to wiki with this error; there wasn't any page, so i made it

<nowiki>For the Maker's sake, can someone tell this text to word-wrap, please!</nowiki>

If you are here because your Toolset popped up with a huge error that told you DON'T TOUCH NOTHIN' until you look up this serious error on the wiki... well, there was nothing here on the wiki about it. This is what happened to me, and how I avoided the destruction of the universe as we know it.

It seems to occur if you try to edit keyframes on an animation that has GAD turned on. My animation was stopping, blinking into the default pose, then going into the background base pose. I wanted to eliminate the default pose blink, so I put two keyframes near the end of the animation, and dragged the endmost one down to zero. It didn't like that.

I saved the cutscene using "Save As" and another name. Then I closed the Toolset. This new cutscene seemed to play all right (in the Toolset; haven't gone to game yet). I also copied my new camera keyframes from it to my original cutscene, just in case the new on was FUBAR.

Trying to do the same keyframe edit on that animation with GAD reproduced the error. So, my advice... Don't do that.

If it's something else, please feel free to add/edit this page.

Talk:PRCSCR.xls

2011-08-03T15:56:19Z

BloodsongVengeance: /* This Needs Serious Help */ new section

An example of one of these files would be great.

Thanks

Josh

== This Needs Serious Help ==

creating stuff for/with PRCSCR needs a step-by-step tutorial. and more information. like how to name it, that you need to convert it, where to stick it, etc etc etc.

see information on these threads:
http://social.bioware.com/forum/1/topic/71/index/750495
http://social.bioware.com/forum/1/topic/71/index/564274
and this tutorial:
http://dragonagemodding.wordpress.com/2009/11/15/creating-a-custom-merchant-for-the-players-camp-part-1/

and there's a bioware project with a gda tool on it; and i just lost the link. GAH
~~

2DA ranges in use

2011-08-03T14:24:37Z

BloodsongVengeance: /* PRCSCR */

This page is meant to enumerate row ID ranges that are used by the main game and by various popular addins, to avoid accidental overlap. See also [[Prefixes in use]] and [[Compatibility]].

Note that there's no need for 2DA row IDs to be sequential, so you can use very large row ID numbers to reduce the chances of collision.

Version 1.0 of the toolset had a bug in ExcelProcessor that caused problems with high row ID numbers, but this has been fixed in subsequent releases. See [[Bug: ExcelProcessor doesn't handle row IDs above 8.3 million correctly|the bug report]].

As of now there is a bug that prevents ID's above 255 to be used for some M2DA's. See [[Bug: High M2DA ID ranges might work in the toolset, but not in game|Bug report]] for a list of tables affected.

Another [[Bug: DLC conflicts with standalone campaigns|bug]] affects the rewards M2DA.

== ABI_base ==

According to the [[ABI_base]] page under the ''tooltipstrref'' column, anything over 500000 is considered a debuff. This would limit the range a fair amount.

{| class="wikitable" border="1"
|-
! Range
! Used by
|-
| '''0 - 200262'''
| '''Bioware - Main campaign'''
|-
| '''0 - 1000000'''
| '''Bioware - reserved'''
|-
| 24000 - 26000
| [http://social.bioware.com/wiki/datoolset/index.php/Community_Contest_Main_Page Community Contest]
|-
| 37000 - 38000
| [http://bg2redux.student.utwente.nl/trac/wiki Baldur's Gate Redux]
|-
| 50000 - 50001
| Anakin's [http://social.bioware.com/project/861/ Advanced Tactics]
|-
| 51000 - 51002
| Anakin's [http://social.bioware.com/project/1888/ Advanced Quickbar]
|-
| 450000 - 450300
| ladydesire's [http://social.bioware.com/project/815/ Tevinter Warden class]
|-
| 466000 - 466100
| Apolyon6k's [http://social.bioware.com/project/3842/ The magic of innocence]
|-
| 901974-903000 and 401974-403000(modal)
| Idomeneas' [http://social.bioware.com/project/3152/ Valeria Addon]
|-
| 1337000 - 1337008
| amcnow's [http://social.bioware.com/project/3823/ Respecification]
|-
| 2560000 - 2560500
| Timelord's [http://social.bioware.com/project/1845/ Blood and Lyrium]
|-
| 5680000 - 5680250
| Phaenan's [http://social.bioware.com/project/672/ The Winter Forge]
|-
| 30000000 - 40000000
| MCC's Senderfall: The Last Bastion (To author: unreasonable range, please correct)
|-
| 300000-300047
| rebel5555's [http://social.bioware.com/project/2646/ 2 Handed Weapon Abilities for Arcane Warriors]
|-
| 300000-300047
| rebel5555's [http://social.bioware.com/project/3637/ Dual Weapon Abilities for Arcane Warriors]
|-
| 300000-300047
| rebel5555's [http://social.bioware.com/project/2644/ Weapon and Shield Abilities for Arcane Warriors]
|}

----

== AI_TacticsPresets ==

{| class="wikitable" border="1"
|-
! Range
! Used by
|-
| '''0 - 9'''
| '''Bioware - Main campaign'''
|-
| 10 - 15
| Anakin's [http://social.bioware.com/project/861/ Advanced Tactics]
|}

----
== ambient_ai ==

{| class="wikitable" border="1"
|-
! Range
! Used by
|-
| '''0 - 1000000'''
| '''Bioware - Main campaign'''
|-
| 1000000-1001000
| [http://social.bioware.com/project/178/ Crown of Creation]
|}

----

== ANIM_base ==

{| class="wikitable" border="1"
|-
! Range
! Used by
|-
| 65000 - 65002
| BioSpirit's [http://social.bioware.com/project/1647/ Hilltop Under Siege]
|}

----

== APR_base ==

Note that there is a bug involving this 2DA: [[Bug: APR base maximum M2DA row ID is 65535 in the toolset]]

{| class="wikitable" border="1"
|-
! Range
! Used by
|-
| '''0 - 90'''
| '''Bioware - Main campaign'''
|-
| '''0 - 1000000'''
| '''Bioware - reserved'''
|-
| 24000 - 26000
| [http://social.bioware.com/wiki/datoolset/index.php/Community_Contest_Main_Page Community Contest]
|-
| 37000 - 38000
| [http://bg2redux.student.utwente.nl/trac/wiki Baldur's Gate Redux]
|-
| 40000 - 40010
| Alschemid - [http://social.bioware.com/project/3175/ Horses] and [http://social.bioware.com/project/3666/ Sandbox]
|-
| 55000 - 57000
| World of Grone (by Shodushi) [http://social.bioware.com/project/2194/ World of Grone]
|-
| 64000 - 64999
| [http://social.bioware.com/project/178/ Crown of Creation]
|-
| 65000 - 65001
| BioSpirit's [http://social.bioware.com/project/1647/ Hilltop Under Siege]
|-
| 65010 - 65025
| Mutantspicy Oracle and Enchanted Armor [Dragonage Nexus]
|-
| 1000001 - 1100000
| DA Workshop / by frosti [http://www.dragon-age-workshop.de/forum/viewforum.php?f=19/ Icewind Dale Remake]
|-
| 30000000-40000000
| MCC's Senderfall: The Last Bastion (To author: unreasonable range, please correct)
|-
|}

----

== areadata ==

{| class="wikitable" border="1"
|-
! Range
! Used by
|-
| 24000 - 26000
| [http://social.bioware.com/wiki/datoolset/index.php/Community_Contest_Main_Page Community Contest]
|}

----

== armor_massive_variation ==

{| class="wikitable" border="1"
|-
! Range
! Used by
|-
| '''0 - 8'''
| '''Bioware - Main campaign'''
|-
| 50-50
| Alschemid - [http://social.bioware.com/project/3666/ Sandbox]
|}

Note: the highest working tested ID for this variation is 141. See [http://social.bioware.com/wiki/datoolset/index.php/Bug:_High_M2DA_ID_ranges_might_work_in_the_toolset,_but_not_in_game bug report]
----

== BITM_base and ItemStats_ ==

{| class="wikitable" border="1"
|-
! Range
! Used by
|-
| 24000 - 26000
| [http://social.bioware.com/wiki/datoolset/index.php/Community_Contest_Main_Page Community Contest]
|-
| 30000 - 30500
| Ambaryerno - [http://social.bioware.com/project/415/ Arms and Armor]
|-
| 37000-38000
| [http://bg2redux.student.utwente.nl/trac/wiki Baldur's Gate Redux]
|-
| 40000 - 40200
| DA Workshop / by frosti [http://www.dragon-age-workshop.de/forum/viewforum.php?f=19/ Icewind Dale Remake]
|-
| 57000-59000
| [World of Grone (by Shodushi) [http://social.bioware.com/project/2194/ World of Grone]
|-
| 77000-79000
| [Sanguine Sunrise by LukaCrosszeria [http://social.bioware.com/project/4024/ Sanguine Sunrise]
|-
| 30000000-40000000
| MCC's Senderfall: The Last Bastion (To author: unreasonable range, please correct)
|-
| 50000 - 50100
| Feline Fuelled Games - (by Silk) [http://www.felinefuelledgames.de/ Feline Fuelled Games]
|-
|}

----

== CLA_base ==

{| class="wikitable" border="1"
|-
! Range
! Used by
|-
| '''0 - 25'''
| '''Bioware
|-
| 10000 - 10012
| Ladydesire
|-
| 24000 - 26000
| [http://social.bioware.com/wiki/datoolset/index.php/Community_Contest_Main_Page Community Contest]
|}

== crafting_recipe_types ==
{| class="wikitable" border="1"
|-
! Range
! Used by
|-
| '''0 - 7'''
| '''Bioware - Main campaign'''
|-
| '''0 - 1000000'''
| '''Bioware - reserved'''
|-
| 30000000-40000000
| MCC's Senderfall: The Last Bastion (To author: unreasonable range, please correct)
|-
| 5680000 - 5680020
| Phaenan's [http://social.bioware.com/project/672/ The Winter Forge]
|}

----

== crafting_recipes ==
{| class="wikitable" border="1"
|-
! Range
! Used by
|-
| '''0 - 91'''
| '''Bioware - Main campaign'''
|-
| '''0 - 1000000'''
| '''Bioware - reserved'''
|-
| 30000000-40000000
| MCC's Senderfall: The Last Bastion (To author: unreasonable range, please correct)
|-
| 5680000 - 5682000
| Phaenan's [http://social.bioware.com/project/672/ The Winter Forge]
|}

----

== engineevents ==

Those ranges relates to custom events types/ID and not to engineevents based [[Event_override|events overriding]].

{| class="wikitable" border="1"
|-
! Range
! Used by
|-
| '''0 - 1000000'''
| '''Bioware - reserved'''
|-
| 500 - 500
| Anakin's [http://social.bioware.com/project/861/ Advanced Tactics]
|-
| 510 - 511
| Anakin's [http://social.bioware.com/project/1888/ Advanced Quickbar]
|-
| 5680000 - 5680050
| Phaenan's [http://social.bioware.com/project/672/ The Winter Forge]
|}

----

== guitypes ==
{| class="wikitable" border="1"
|-
! Range
! Used by
|-
| '''0 - 1000000'''
| '''Bioware - reserved'''
|-
| 600 - 600
| Anakin's [http://social.bioware.com/project/861/ Advanced Tactics]
|-
| 601 - 601
| Anakin's [http://social.bioware.com/project/1888/ Advanced Quickbar]
|-
| 24000 - 26000
| [http://social.bioware.com/wiki/datoolset/index.php/Community_Contest_Main_Page Community Contest]
|-
| 666000 - 666020
| Apolyon6k's [http://social.bioware.com/project/3842/ The magic of innocence]
|-
| 1337000 - 1337001
| amcnow's [http://social.bioware.com/project/3823/ Respecification]
|-
| 1974100-1974200
| Idomeneas' [http://social.bioware.com/project/3152/ Valeria Addon]
|-
| 2560000 - 2560050
| Timelord's [http://social.bioware.com/project/1845/ Blood and Lyrium]
|-
| 5680000 - 5680010
| Phaenan's [http://social.bioware.com/project/672/ The Winter Forge]
|-
|}

----

== Heraldry ==
There is a [[Bug:_High_M2DA_ID_ranges_might_work_in_the_toolset,_but_not_in_game | bug]] with this table. The range 0-255 is known to work.
{| class="wikitable" border="1"
|-
! Range
! Used by
|-
| '''0 - 1000000'''
| '''Bioware - reserved'''
|-
| 1000001 - 1001000
| [http://social.bioware.com/project/178/ Crown of Creation] (using 201 onwards temporarily)
|-
|}
----

== itemprps ==
{| class="wikitable" border="1"
|-
! Range
! Used by
|-
| '''0 - 10022'''
| '''Bioware - Main campaign'''
|-
| '''0 - 1000000'''
| '''Bioware - reserved'''
|-
| 24000 - 26000
| [http://social.bioware.com/wiki/datoolset/index.php/Community_Contest_Main_Page Community Contest]
|-
| 37000-38000
| [http://bg2redux.student.utwente.nl/trac/wiki Baldur's Gate Redux]
|-
| 77000-79000
| Sanguine Sunrise by LukaCrosszeria [http://social.bioware.com/project/4024/ Sanguine Sunrise]
|-
| 1000001 - 2000000
| DA Workshop / by frosti [http://www.dragon-age-workshop.de/forum/viewforum.php?f=19/ Icewind Dale Remake]
|-
| 2555000-2555010
| PavelNovotny - [http://social.bioware.com/project/517/ Gay Bars of Ferelden]
|-
| 5680000 - 5680050
| Phaenan's [http://social.bioware.com/project/672/ The Winter Forge]
|-
| 7570000-7770000
| [World of Grone (by Shodushi) [http://social.bioware.com/project/2194/ World of Grone]
|-
| 536873321 - 536873322
| Elys' [http://social.bioware.com/project/522/ Mysterious Gifts]
|-
| 30000000-40000000
| MCC's Senderfall: The Last Bastion (To author: unreasonable range, please correct)
|-
| 2560000-2560050
| Timelord's [http://social.bioware.com/project/1845/ Blood and Lyrium]
|-
|}

----

== itemsets ==
{| class="wikitable" border="1"
|-
! Range
! Used by
|-
| '''0 - 30'''
| '''Bioware - Main campaign'''
|-
| '''0 - 1000000'''
| '''Bioware - reserved'''
|-
| 2555000-2555010
| PavelNovotny - [http://social.bioware.com/project/517/ Gay Bars of Ferelden]
|-
| 30000000-40000000
| MCC's Senderfall: The Last Bastion (To author: unreasonable range, please correct)
|-
| 5680000 - 5680500
| Phaenan's [http://social.bioware.com/project/672/ The Winter Forge]
|-
| 7570000-7770000
| [World of Grone (by Shodushi) [http://social.bioware.com/project/2194/ World of Grone]
|-
| 1405261000 - 1405261999
| nezroy - [http://social.bioware.com/project/1834/ Warden Shields], [http://www.dragonagenexus.com/downloads/file.php?id=793 Leliana Item Set]
|-
| 1000001 - 2000000
| DA Workshop / by frosti [http://www.dragon-age-workshop.de/forum/viewforum.php?f=19/ Icewind Dale Remake]
|-
| 7771000 - 7771500
| [http://social.bioware.com/project/2157/ Dark Times: The Confederacy of Malkuth] (reserved by Starlight on Questorion's behalf)
|-
|}

----

== ItemVariations (all) ==
{| class="wikitable" border="1"
|-
! Range
! Used by
|-
| '''0 - 30'''
| '''Bioware - Main campaign'''
|-
| '''0 - 1000'''
| '''Bioware - reserved (guessed)'''
|-
| 12000 - 12100
| [http://social.bioware.com/project/1923/ Adonnay's Weaponry] (reserved by mikemike37 on his behalf)
|-
| 77 - 99
| Sanguine Sunrise by LukaCrosszeria [http://social.bioware.com/project/4024/ Sanguine Sunrise]
|-
| 140 - 160
| [http://social.bioware.com/wiki/datoolset/index.php/Community_Contest_Main_Page Community Contest]
|-
| 101000 - 400000
| [http://social.bioware.com/project/2157/ Dark Times: The Confederacy of Malkuth] (reserved by Starlight on Questorion's behalf)
|-
|}

note: ItemVariations are affected by the bug which prevents ID's above 255 from appearing properly in the game. See [[Bug: High M2DA ID ranges might work in the toolset, but not in game|Bug report]].

----

== M2DA_base ==
{| class="wikitable" border="1"
|-
! Range
! Used by
|-
| '''0 - 1016, 2000 - 2010, 10011 - 10142, ...? '''
| '''Bioware - Main campaign'''
|-
| '''0 - 1000000'''
| '''Bioware - reserved'''
|-
| 5000 - 5014
| Anakin's [http://social.bioware.com/project/861/ Advanced Tactics]
|-
| 24000 - 26000
| [http://social.bioware.com/wiki/datoolset/index.php/Community_Contest_Main_Page Community Contest]
|-
| 37000 - 38000
| [http://bg2redux.student.utwente.nl/trac/wiki Baldur's Gate Redux]
|-
| 77000 - 79000
| [http://social.bioware.com/project/4024/ Sanguine Sunrise] by LukaCrosszeria
|-
| 100000 - 100000
| Anakin's [http://social.bioware.com/project/1907/ Event Manager]
|-
| 690000 - 690100
| [http://www.dragonagenexus.com/downloads/file.php?id=1617 Karma's Origins Companions]
|-
| 1000001 - 1100000
| DA Workshop / by frosti [http://www.dragon-age-workshop.de/forum/viewforum.php?f=19/ Icewind Dale Remake]
|-
| 1337000 - 1337001
| amcnow's [http://social.bioware.com/project/3823/ Respecification]
|-
| 2300000 - 2300100
| [http://social.bioware.com/project/178/ Crown of Creation] (M2DA prefix: COC)
|-
| 2560000 - 2560050
| Timelord's [http://social.bioware.com/project/1845/ Blood and Lyrium]
|-
| 5000000 - 5000010
| Noob766's [http://social.bioware.com/project/3827/ Companion Compatibility pack]
|-
| 5680000 - 5680050
| Phaenan's [http://social.bioware.com/project/672/ The Winter Forge]
|-
| 5680050 - 5680055
| Phaenan's [http://social.bioware.com/project/3185/ Flexible craft UI]
|-
| 5681000 - 5681005
| Phaenan's [http://social.bioware.com/project/2896/ DACrafting framework]
|-
| 6000000 - 6000050
| TreDawn - [http://social.bioware.com/project/1750/ Nesiara Companion]
|-
| 6660000 - 6660050
| Apolyon6k - [http://social.bioware.com/project/3842/ The magic of innocence]
|-
| 7000000 - 7000050
| FtG - [http://social.bioware.com/project/1688/ UI Mod]
|-
| 7000051 - 7000055
| FtG - [http://social.bioware.com/project/3663/ Custom Loading Screen]
|-
| 7000056 - 7000071
| FtG - [http://social.bioware.com/forum/1/topic/75/index/5569843 Portrait dialogue and custom tokens (test release)]
|-
| 7000075-7000080
| FtG - [http://ftg.wikidot.com/ftg-quickbar Quickbar]
|-
| 7570000 - 7770000
| [World of Grone (by Shodushi) [http://social.bioware.com/project/2194/ World of Grone]
|-
| 7777770 - 7777799
| Magic - [http://social.bioware.com/project/1429/ Void Walker] (M2DA prefix: VWK)
|-
| 9000000 - 9000050
| Ambaryerno - [http://social.bioware.com/project/415/ Arms and Armor]
|-
| 30000000 - 40000000
| MCC's Senderfall: The Last Bastion (To author: unreasonable range, please correct)
|-
| 1140150041 - 1140150091
| DLAN_Immortality - [http://social.bioware.com/project/789/ Ser Gilmore NPC]
|-
|-
| 1553521700 - 1553521750
| Alschemid - [http://social.bioware.com/project/3666/ Sandbox]
|}

----

== materialrules ==
{| class="wikitable" border="1"
|-
| '''0 - 1000000'''
| '''Bioware - reserved'''
|-
| 24000 - 26000
| [http://social.bioware.com/wiki/datoolset/index.php/Community_Contest_Main_Page Community Contest]
|-
| 37000-38000
| [http://bg2redux.student.utwente.nl/trac/wiki Baldur's Gate Redux]
|-
| 536873321 - 536873323
| Elys' [http://social.bioware.com/project/522/ Mysterious Gifts]
|-
| 1405261000 - 1405261999
| nezroy - [http://social.bioware.com/project/1834/ Warden Shields], [http://www.dragonagenexus.com/downloads/file.php?id=793 Leliana Item Set]
|}

----

== materialtypes ==
{| class="wikitable" border="1"
|-
! Range
! Used by
|-
| '''0 - 88'''
| '''Bioware - Main campaign'''
|-
| '''0 - 1000000'''
| '''Bioware - reserved'''
|-
| 24000 - 26000
| [http://social.bioware.com/wiki/datoolset/index.php/Community_Contest_Main_Page Community Contest]
|-
| 37000-38000
| [http://bg2redux.student.utwente.nl/trac/wiki Baldur's Gate Redux]
|-
| 30000000-40000000
| MCC's Senderfall: The Last Bastion (To author: unreasonable range, please correct)
|-
| 5680000 - 5680300
| Phaenan's [http://social.bioware.com/project/672/ The Winter Forge]
|-
| 536873321 - 536873340
| Elys' [http://social.bioware.com/project/522/ Mysterious Gifts]
|-
| 1405261000 - 1405261999
| nezroy - [http://social.bioware.com/project/1834/ Warden Shields], [http://www.dragonagenexus.com/downloads/file.php?id=793 Leliana Item Set]
|}

----

== PartyPicker ==
{| class="wikitable" border="1"
|-
! Range
! Used by
|-
| '''0 - 11'''
| '''Bioware - Main campaign'''
|-
| '''????'''
| '''Bioware - reserved'''
|-
| 101-199
| [http://social.bioware.com/project/178/ Crown of Creation]
|-
| 200 - 299
| DA Workshop / Author: frosti [http://www.dragon-age-workshop.de/forum/viewforum.php?f=19/ Icewind Dale Remake]
|-
| 300 - 350
| [World of Grone (by Shodushi) [http://social.bioware.com/project/2194/ World of Grone]
|-
| 1974-1980
| Idomeneas' [http://social.bioware.com/project/3152/ Valeria Addon]
|-
| 5711-5720
| [http://social.bioware.com/project/3926/ Castle Drakhaoul] by Marshal57'
|-
| 6660 - 6665
| Apolyon6k's [http://social.bioware.com/project/3842/ The magic of innocence]
|-
| 77000 - 79000
| [http://social.bioware.com/project/4024/ Sanguine Sunrise] by LukaCrosszeria
|-
| 6900000 - 6900200
| [http://www.dragonagenexus.com/downloads/file.php?id=1617 Karma's Origins Companions]
|-
| 1553521700 - 1553521710
| Alschemid - [http://social.bioware.com/project/3666/ Sandbox]
|-

|}

----

== PRCSCR ==
{| class="wikitable" border="1"
|-
! Range
! Used by
|-
| '''0 - 1000000'''
| '''Bioware - reserved'''
|-
| 24000 - 26000
| [http://social.bioware.com/wiki/datoolset/index.php/Community_Contest_Main_Page Community Contest]
|-
| 37000 - 38000
| [http://bg2redux.student.utwente.nl/trac/wiki Baldur's Gate Redux]
|-
| 77000 - 79000
| [http://social.bioware.com/project/4024/ Sanguine Sunrise] by LukaCrosszeria
|-
| 690000 - 690100
| [http://www.dragonagenexus.com/downloads/file.php?id=1617 Karma's Origins Companions]
|-
| 1000001 - 1100000
| DA Workshop / by frosti [http://www.dragon-age-workshop.de/forum/viewforum.php?f=19/ Icewind Dale Remake]
|-
| 1337000
| amcnow's [http://social.bioware.com/project/3823/ Respecification]
|-
| 2000000 - 2000050
| [http://www.dragonagenexus.com/downloads/file.php?id=942 Oracle,mutantspicy's magic vault, and other custom armors]
|-
| 5680000 - 5680020
| Phaenan's [http://social.bioware.com/project/672/ The Winter Forge]
|-
| 6000000 - 6000050
| TreDawn - [http://social.bioware.com/project/1750/ Nesiara Companion]
|-
| 7570000 - 7770000
| [World of Grone (by Shodushi) [http://social.bioware.com/project/2194/ World of Grone]
|-
| 9130000 - 9130100
| [http://social.bioware.com/user_bw_projects.php BloodsongVengeance]
|-
| 10100000
| Camp [http://social.bioware.com/project/463/ storage chest]
|-
| 10100011 - 10100013
| Didymos' [http://social.bioware.com/project/2620/ Camp Merchant Chest]
|-
| 10100014 - 10100016
| Didymos' [http://social.bioware.com/project/2717/ Item Sets Fix]
|-
| 10100100 - 10100110
| Eshme's [http://social.bioware.com/project/1929/ Sleeping Tent]
|-
| 30000000 - 40000000
| MCC's Senderfall: The Last Bastion (To author: unreasonable range, please correct)
|-
| 42006090 - 42006100
| [http://www.dragonagenexus.com/downloads/file.php?id=1120 Morrigan Restoration Patch]
|-
| 1000197400 - 1000197410
| Idomeneas' [http://social.bioware.com/project/3152/ Valeria Addon]
|-
| 1109197751 - 1109197799
| Schwinni - [http://dragonagenexus.com/downloads/file.php?id=1020 Awakening Runes Fixes], [http://dragonagenexus.com/downloads/file.php?id=1112 Awakening Blackblade Armor Dragon Drop Fix]
|-
| 1140150041 - 1140150091
| DLAN_Immortality - [http://social.bioware.com/project/789/ Ser Gilmore NPC]
|-
| 1405261000 - 1405261999
| nezroy - [http://social.bioware.com/project/1834/ Warden Shields], [http://www.dragonagenexus.com/downloads/file.php?id=793 Leliana Item Set]
|-
| 1553521700 - 1553521710
| Alschemid - [http://social.bioware.com/project/3666/ Sandbox]
|-
| 1672464532 - 1672464542
| DLAN_Immortality - [http://social.bioware.com/project/2991/ Ser Gilmore NPC Awakening]
|-
|}

----

== placeable_types ==
{| class="wikitable" border="1"
|-
! Range
! Used by
|-
| '''0 - 1000000'''
| '''Bioware - reserved'''
|-
| 14000 - 16000
| [http://social.bioware.com/wiki/datoolset/index.php/Community_Contest_Main_Page Community Contest]
|-
| 17000 - 19000
| Standalone modules (see discussion tab)
|-
| 37000-38000
| [http://bg2redux.student.utwente.nl/trac/wiki Baldur's Gate Redux]
|-
| 43050-43061
| Eshme's [http://social.bioware.com/project/1929/ Sleeping Tent] (Greater 65535 is showing bugs so this is until it is fixed)
|-
| 43062-43065
| BioSpirit's [http://social.bioware.com/project/1647/ Hilltop Under Siege]
|-
| 56000-56200
| [http://social.bioware.com/project/2472/#details Mikes Invisible Boxes]
|-
| 2696549 - 2696700
| PavelNovotny - [http://social.bioware.com/project/517/ Gay Bars of Ferelden] (NOTE: I'm using the 6000-6200 range until Bioware fixes the bug which prevents m2da ID ranges above 900000 from showing up in game.)

|-
| 7570000-7770000
| [World of Grone (by Shodushi) [http://social.bioware.com/project/2194/ World of Grone]
|-
| 30000000-40000000
| MCC's Senderfall: The Last Bastion (To author: unreasonable range, please correct)
|-
| 1000001 - 1100000
| DA Workshop / Author: frosti [http://www.dragon-age-workshop.de/forum/viewforum.php?f=19/ Icewind Dale Remake]
|-
| 1974-1978
| Idomeneas' [http://social.bioware.com/project/3152/ Valeria Addon] (They are low so they'll show in game, recall the toolset bug)
|-
|}
----

== popups ==
{| class="wikitable" border="1"
|-
! Range
! Used by
|-
| '''0 - 1000000'''
| '''Bioware - reserved'''
|-
| 1000001-1001000
| [http://social.bioware.com/project/178/ Crown of Creation]
|-
|}
----

== PRJ_base ==

{| class="wikitable" border="1"
|-
! Range
! Used by
|-
| '''0 - 1000000'''
| '''Bioware - reserved'''
|-
| 5680000 - 5680050
| Phaenan's [http://social.bioware.com/project/672/ The Winter Forge]
|-
|}

----
== String ID ==
It is not generally necessary to register String ID ranges here. The values generated by the toolset are sufficiently random to minimise the risk of collision. Exception : the Community Contest reserved the range below so that the builders will stick to that and can import VO without having to renumber the VO files.

{| class="wikitable" border="1"
|-
! Range
! Used by
|-
| '''0 - 10000000'''
| '''Bioware - reserved'''
|-
| 89000000 - 89999999
| [http://social.bioware.com/wiki/datoolset/index.php/Community_Contest_Main_Page Community Contest]
|-
|}

----

== tint_override ==
{| class="wikitable" border="1"
|-
! Range
! Used by
|-
| 500 - 520
| PavelNovotny - [http://social.bioware.com/project/517/ Gay Bars of Ferelden]
|-
| 6900 - 6920
| [http://www.dragonagenexus.com/downloads/file.php?id=1617 Karma's Origins Companions]
|-
| 1000001-1001000
| [http://social.bioware.com/project/178/ Crown of Creation]
|-
| 30000000-40000000
| MCC's Senderfall: The Last Bastion (To author: unreasonable range, please correct)
|-
| 1109197701 - 1109197750
| Schwinni - [http://dragonagenexus.com/downloads/file.php?id=1064 Helmets without wings and retints]
|-
| 1553521700 - 1553521750
| Alschemid - [http://social.bioware.com/project/3666/ Sandbox]
|}

----

== ts_material ==
{| class="wikitable" border="1"
|-
! Range
! Used by
|-
| 1405261000 - 1405261999
| nezroy - [http://social.bioware.com/project/1834/ Warden Shields], [http://www.dragonagenexus.com/downloads/file.php?id=793 Leliana Item Set]
|}

----

== TS_Category ==

{| class="wikitable" border="1"
|-
! Range
! Used by
|-
| '''0 - 1000000'''
| '''Bioware - reserved'''
|-
| 5680000 - 5680005
| Phaenan's [http://social.bioware.com/project/672/ The Winter Forge]
|-
| 1000001 - 1100000
| DA Workshop / by frosti [http://www.dragon-age-workshop.de/forum/viewforum.php?f=19/ Icewind Dale Remake]
|-
| 7570000-7770000
| [World of Grone (by Shodushi) [http://social.bioware.com/project/2194/ World of Grone]
|-
|}

----

== vfx_base ==
{| class="wikitable" border="1"
|-
! Range
! Used by
|-
| '''0 - 1000000'''
| '''Bioware - reserved'''
|-
| 24000 - 26000
| [http://social.bioware.com/wiki/datoolset/index.php/Community_Contest_Main_Page Community Contest]
|-
| 37000-38000
| [http://bg2redux.student.utwente.nl/trac/wiki Baldur's Gate Redux]
|-
| 5680000 - 5680010
| Phaenan's [http://social.bioware.com/project/672/ The Winter Forge]
|-
| 5680011 - 5680019
| BioSpirit's [http://social.bioware.com/project/1647/ Hilltop Under Siege]
|}
----

== worldmaps (has to be less than 256) ==
{| class="wikitable" border="1"
|-
! Range
! Used by
|-
| '''0 - 6'''
| '''Bioware - reserved'''
|-
| '''151 - 151'''
| Alschemid - [http://social.bioware.com/project/3666/ Sandbox]

|-
| '''210 - 220'''
| [http://social.bioware.com/project/1845/ Blood and Lyrium]
|}
----

Ambient ai.xls

2011-03-13T14:15:39Z

BloodsongVengeance: posted link to the xls file i uploaded to google docs.

See [[Ambient behaviour]] for details on how this information is used.

{{2da start|ambient_anim_patterns}}
{{2da column|Label|string|Anything in green MUST be played in order.}}
{{2da column|NoPlayNext|int|Sets bPlayNext parameter used with CommandPlayAnimation() function to FALSE.}}
{{2da column|ActionTotal|int|}}
{{2da column|Action0|float|Format: Animation.Loops}}
{{2da column|Action1|float|}}
{{2da column|Action2|float|}}
{{2da column|Action3|float|}}
{{2da column|Action4|float|}}
{{2da column|Action5|float|}}
{{2da column|Action6|float|}}
{{2da column|Action7|float|}}
{{2da column|Action8|float|}}
{{2da column|Action9|float|}}
{{2da column|Action10|float|}}
{{2da column|Action11|float|}}
{{2da column|Action12|float|}}
{{2da end}}

[https://spreadsheets.google.com/ccc?key=0AsMdSm0VGixjdGtKRzJnaC0xcWhsQUlNZnpLMkRJTHc&hl=en&authkey=CNrsmsQI#gid=1 ambient_ai.xls on Google Docs.]

[[Category:Ambient behavior]]
[[Category:XLS files]]

Area layouts used in the single player module

2010-12-28T20:39:07Z

BloodsongVengeance: can never find this by searching for lvl, level, layout, area or list. trying to make it more findable.

This will help those that dont want to go through every area layout to find the one they want. Hope this helps -RandyG
*Updated - Slonison
*Added screenshots for areas - Barrett R

The .lvl files for most of these areas can be downloaded from [http://social.bioware.com/project/1331/#files the Single player and core resource source files] project, if you wish to modify the layouts in the [[level editor]].

== arena ==
*[[:Image:Arena.jpg|arena]] - Small Castle Arena
*[[:Image:Arena2.jpg|arena2]] - Large Castle Arena

== brc ==
*[[:Image:Brc000d.jpg|brc000d]] - Dalish Camp
*[[:Image:Brc100d.jpg|brc100d]] - Brecilian Forest: West Brecilian Forest
*[[:Image:Brc101d.jpg|brc101d]] - Brecilian Forest: East Brecilian Forest
*[[:Image:Brc200d.jpg|brc200d]] - Dalish Elf Origins: Elven Ruins
*[[:Image:Brc201d.jpg|brc201d]] - Cavern (Unused?)
*[[:Image:Brc202d.jpg|brc202d]] - The Brecilian Ruins: Lower Ruins
*[[:Image:Brc203d.jpg|brc203d]] - The Brecilian Ruins: Lair of the Werewolves
*[[:Image:Brc204d.jpg|brc204d]] - The Brecilian Ruins: Ruins Upper Levels
*[[:Image:Brc300d.jpg|brc300d]] - Dalish Elf Origins: Forest Clearing
*[[:Image:Brc501d.jpg|brc501d]] - Darkspawn Encounter: Field near a Lake
*[[:Image:Brc502d.jpg|brc502d]] - Encounter: Twisted Forest
*[[:Image:Brc503d.jpg|brc503d]] - Encounter: Twisting Roads
*[[:Image:Brc504d.jpg|brc504d]] - Encounter: Kadan-Fe Camp
*[[:Image:Brc505d.jpg|brc505d]] - Encounter: Marjolaine's Assassins (Road with river and waterfall)
*[[:Image:Brc997d.jpg|brc997d]] - Dalish Elf Origins: Dalish Camp
*[[:Image:Brc999d.jpg|brc999d]] - Player Camp

== combat ==
*[[:Image:Combat.jpg|combat]] - Open Combat Area
*[[:Image:Combat2.jpg|combat2]] - Open Combat Area

== den ==
*[[:Image:den000d.jpg|den000d]] - Denerim: Palace District: Palace Exterior (during attack)
*[[:Image:den001d.jpg|den001d]] - Denerim: Palace District: Royal Palace
*[[:Image:den005d.jpg|den005d]] - Denerim: Palace District: Arl of Denerim's: Interiors
*[[:Image:den009d.jpg|den009d]] - Haven Village: Store
*[[:Image:den011d.jpg|den011d]] - Denerim: Palace District: Arl of Denerim's: Dungeon
*[[:Image:den012d.jpg|den012d]] - Denerim: Palace District: Arl of Denerim's: Exterior
*[[:Image:den020d.jpg|den020d]] - Denerim: Market District: Gnawed Noble's Tavern
*[[:Image:den101d.jpg|den101d]] - Denerim: Market District: Brother Genetivi's House
*[[:Image:den200d.jpg|den200d]] - Denerim: Alienage: Day
*[[:Image:den200n.jpg|den200n]] - Denerim: Alienage: Night (during attack)
*[[:Image:den201d.jpg|den201d]] - Denerim: Alienage: City Elf Origin's Home
*[[:Image:den202d.jpg|den202d]] - Denerim: Alienage: Alarith's Store
*[[:Image:den203d.jpg|den203d]] - Denerim: Alienage: Slum Apartments
*[[:Image:den204d.jpg|den204d]] - Denerim: Alienage: Tevinter Hospice
*[[:Image:den206d.jpg|den206d]] - Denerim: Alienage: Slaver Compound
*[[:Image:den207d.jpg|den207d]] - Denerim: Alienage: Valendrian's House
*[[:Image:den308d.jpg|den308d]] - Haven Village: Chantry
*[[:Image:den312d.jpg|den312d]] - Denerim: South Docks: The Pearl
*[[:Image:den400d.jpg|den400d]] - Denerim: Market District
*[[:Image:den401d.jpg|den401d]] - Denerim: Market District: Arl Eamon's Estate (First Floor)
*[[:Image:den403d.jpg|den403d]] - Denerim: Market District: Magic Shop
*[[:Image:den404d.jpg|den404d]] - Denerim: House (small, multiple uses)
*[[:Image:den405d.jpg|den405d]] - Denerim: House (large, Marjolaine encounter)
*[[:Image:den407d.jpg|den407d]] - Denerim: Market District: Master Wade's Emporium
*[[:Image:den408d.jpg|den408d]] - Denerim: Market District: Arl Eamon's Estate (Basement)
*[[:Image:den500d.jpg|den500d]] - Denerim: Fort Drakon (Main Floor, during attack)
*[[:Image:den501d.jpg|den501d]] - Denerim: Fort Drakon (Second Floor, during attack)
*[[:Image:den502d.jpg|den502d]] - Denerim: Fort Drakon (Rooftop, during attack)
*[[:Image:den504d.jpg|den504d]] - Denerim: Fort Drakon (Exteriors, during attack)
*[[:Image:den505d.jpg|den505d]] - Denerim: Fort Drakon (Main Floor)
*[[:Image:den510d.jpg|den510d]] - Denerim: City Gates (during attack)
*[[:Image:den520d.jpg|den520d]] - Denerim: Market District (during attack)
*[[:Image:den600d.jpg|den600d]] - Denerim: Alienage: Abandoned Orphanage
*[[:Image:den601d.jpg|den601d]] - Denerim: South Docks: Bloodmage HQ
*[[:Image:den602d.jpg|den602d]] - Denerim: Bann of West Hill's Estate
*[[:Image:den900d.jpg|den900d]] - Denerim: Back Alley (Narrow)
*[[:Image:den901d.jpg|den901d]] - Denerim: Back Alley (Wide)
*[[:Image:den998d.jpg|den998d]] - Denerim: Docks: Grey Warden Cache

== hrt ==
*[[:Image:hrt000d.jpg|hrt000d]] - Lothering
*[[:Image:hrt001d.jpg|hrt001d]] - Lothering: Chantry
*[[:Image:hrt002d.jpg|hrt002d]] - Lothering: Dane's Refuge
*[[:Image:hrt201d.jpg|hrt201d]] - Highever/Cousland Castle: Human Noble Origins
*[[:Image:hrt201n.jpg|hrt201n]] - Highever/Cousland Castle: Human Noble Origins: Attack

== lak ==
*[[:Image:lak100c.jpg|lak100c]] - Redcliffe Village (Attack)
*[[:Image:lak100d.jpg|lak100d]] - Redcliffe Village (Day)
*[[:Image:lak100n.jpg|lak100n]] - Redcliffe Village (Night)
*[[:Image:lak101d.jpg|lak101d]] - Redcliffe: General Store (Oil Drums)
*[[:Image:lak102d.jpg|lak102d]] - Redcliffe: Katelyn's Home
*[[:Image:lak103d.jpg|lak103d]] - Redcliffe: Tavern
*[[:Image:lak104d.jpg|lak104d]] - Home 3 Rooms
*[[:Image:lak105d.jpg|lak105d]] - Redcliffe: Blacksmith's Store
*[[:Image:lak106d.jpg|lak106d]] - Redcliffe: Chantry
*[[:Image:lak107d.jpg|lak107d]] - Redcliffe: House (along wooden path)
*[[:Image:lak108d.jpg|lak108d]] - Redcliffe: Dwyn's Home
*[[:Image:lak109d.jpg|lak109d]] - Redcliffe: Windmill
*[[:Image:lak110d.jpg|lak110d]] - Redcliffe: Katelyn's Home (Upstairs)
*[[:Image:lak200d.jpg|lak200d]] - Redcliffe: Castle Courtyard
*[[:Image:lak201d.jpg|lak201d]] - Redcliffe: Castle (1st Floor)
*[[:Image:lak202d.jpg|lak202d]] - Redcliffe: Castle (2nd Floor)
*[[:Image:lak203d.jpg|lak203d]] - Redcliffe: Castle (Basement)
*[[:Image:lak250d.jpg|lak250d]] - The Fade (Connor)
*[[:Image:lak300d.jpg|lak300d]] - Lake Calenhad
*[[:Image:lak302d.jpg|lak302d]] - The Circle Tower (Basement)
*[[:Image:lak303d.jpg|lak303d]] - The Circle Tower: Apprentice Quarters (1st Floor)
*[[:Image:lak304d.jpg|lak304d]] - The Circle Tower: Senior Mage Quarters (2nd Floor)
*[[:Image:lak307d.jpg|lak307d]] - The Circle Tower: Harrowing Chamber (5th Floor)
*[[:Image:lak308d.jpg|lak308d]] - The Circle Tower: Storage (Spiders)
*[[:Image:lak400d.jpg|lak400d]] - Haven Village
*[[:Image:lak401d.jpg|lak401d]] - Ruined Temple (1st Floor)
*[[:Image:lak403d.jpg|lak403d]] - Ruined Temple: Mountain Peak
*[[:Image:lak404d.jpg|lak404d]] - Ruined Temple: The Gauntlet
*[[:Image:lak405d.jpg|lak405d]] - Ruined Temple (2nd Floor)
*[[:Image:lak503d.jpg|lak503d]] - The Circle Tower: Apprentice Quarters (1st Floor) Attack
*[[:Image:lak504d.jpg|lak504d]] - The Circle Tower: Senior Mage Quarters (2nd Floor) Attack
*[[:Image:lak505d.jpg|lak505d]] - The Circle Tower: The Great Hall (3rd Floor) Attack
*[[:Image:lak506d.jpg|lak506d]] - The Circle Tower: Templar Quarters (4th Floor) Attack
*[[:Image:lak507d.jpg|lak507d]] - The Circle Tower: Harrowing Chamber (5th Floor) Attack
*[[:Image:lak510d.jpg|lak510d]] - Weisshaupt Fortress
*[[:Image:lak511d.jpg|lak511d]] - Weisshaupt: The Burning Tower
*[[:Image:lak512d.jpg|lak512d]] - Weisshaupt: The Darkspawn Invasion
*[[:Image:lak513d.jpg|lak513d]] - Weisshaupt: The Mage's Asunder
*[[:Image:lak514d.jpg|lak514d]] - Weisshaupt: The Templar's Nightmare
*[[:Image:lak515d.jpg|lak515d]] - Weisshaupt: Inner Sanctum
*[[:Image:lak519d.jpg|lak519d]] - Rocky Structure
*[[:Image:lak526d.jpg|lak526d]] - Weisshaupt: A Nightmare

== lgt ==
*[[:Image:lgt101d.jpg|lgt101d]] - Lake Calenhad: The Spoiled Princess
*[[:Image:lgt300d.jpg|lgt300d]] - Frostback Mountain
*[[:Image:lgt600d.jpg|lgt600d]] - Outside Broken Bridge (Abandoned Meadow)
*[[:Image:lgt601d.jpg|lgt601d]] - Outside Broken Bridge 2 (Roadside)
*[[:Image:lgt602d.jpg|lgt602d]] - Outside Broken Bridge 3 (Old Tegrin)
*[[:Image:lgt603d.jpg|lgt603d]] - Outside Broken Bridge 4 (Hillside Path)
*[[:Image:lgt604d.jpg|lgt604d]] - Outside Broken Bridge 5 (Zevran Attack)
*[[:Image:lgt605d.jpg|lgt605d]] - Outside Broken Bridge 6

== orz ==
*[[:Image:orz000d.jpg|orz000d]] - Orzammar: Hall of Heroes
*[[:Image:orz100d.jpg|orz100d]] - Orzammar Commons
*[[:Image:orz101d.jpg|orz101d]] - Orzammar Commons: Tapster's Tavern
*[[:Image:orz102d.jpg|orz102d]] - Orzammar Commons: Janar's Armorers
*[[:Image:orz103d.jpg|orz103d]] - Orzammar Commons: Jarvia's Carta Hideout
*[[:Image:orz105d.jpg|orz105d]] - Orzammar Commons: Figor's Imports
*[[:Image:orz106d.jpg|orz106d]] - Small Home
*[[:Image:orz107d.jpg|orz107d]] - Orzammar Commons: Orzammar Chantry
*[[:Image:orz200d.jpg|orz200d]] - Orzammar Dust Town
*[[:Image:orz201d.jpg|orz201d]] - Orzammar Dust Town: Slums Home
*[[:Image:orz203d.jpg|orz203d]] - Orzammar Dust Town: Alimar's Emporium
*[[:Image:orz300d.jpg|orz300d]] - Orzammar Diamond Quarter
*[[:Image:orz301d.jpg|orz301d]] - Orzammar Diamond Quarter: The Assembly
*[[:Image:orz302d.jpg|orz302d]] - Orzammar Diamond Quarter: Harrowmont's Estate
*[[:Image:orz303d.jpg|orz303d]] - Orzammar Diamond Quarter: Royal Palace
*[[:Image:orz304d.jpg|orz304d]] - Orzammar Diamond Quarter: Shaperate
*[[:Image:orz500d.jpg|orz500d]] - Orzammar Commons: The Proving
*[[:Image:orz601d.jpg|orz601d]] - Orzammar Prison
*[[:Image:orz700d.jpg|orz700d]] - The Deep Roads: Caridin's Cross
*[[:Image:orz701d.jpg|orz701d]] - The Deep Roads: Aeducan Thaig
*[[:Image:orz702d.jpg|orz702d]] - The Deep Roads: Ortan Thaig
*[[:Image:orz703d.jpg|orz703d]] - The Deep Roads: Unfinished Area (No Lava)
*[[:Image:orz704d.jpg|orz704d]] - The Deep Roads: Drawf Noble Origins: Thaig Chamber
*[[:Image:orz800d.jpg|orz800d]] - The Deep Roads: Dwarf Noble Origins: Deep Roads Outskirts
*[[:Image:orz900d.jpg|orz900d]] - The Deep Roads: The Dead Trenches
*[[:Image:orz901d.jpg|orz901d]] - The Deep Roads: Anvil of the Void
*[[:Image:orz999d.jpg|orz999d]] - The Deep Roads: Unused Map?

== ost ==
*[[:Image:ost000a.jpg|ost000a]] - Ostagar Camp Night
*[[:Image:ost000c.jpg|ost000c]] - Ostagar Camp Attack
*[[:Image:ost000t.jpg|ost000t]] - Ostagar Camp Day
*[[:Image:ost001d.jpg|ost001d]] - Tower of Ishal (First Floor)
*[[:Image:ost002d.jpg|ost002d]] - Tower of Ishal (Second Floor)
*[[:Image:ost003d.jpg|ost003d]] - Tower of Ishal (Third Floor)
*[[:Image:ost004d.jpg|ost004d]] - Tower of Ishal (Top Floor)
*[[:Image:ost100d.jpg|ost100d]] - Korcari Wilds
*[[:Image:ost101d.jpg|ost101d]] - Outside Flemeth's Hut
*[[:Image:ost102d.jpg|ost102d]] - Inside Flemeth's Hut

== oth ==
*[[:Image:oth000d.jpg|oth000d]] - The Fade (Harrowing)
*[[:Image:oth001d.jpg|oth001d]] - The Fade (Circle of Magi)
*[[:Image:oth999d.jpg|oth999d]] - Party picker

== rmt ==
*[[:Image:rmtst.jpg|rmtst]] - Warehouse 3 Rooms Morning
*[[:Image:rmtst01.jpg|rmtst01]] - Warehouse 3 Rooms Night
*[[:Image:rmtst03.jpg|rmtst03]] - Warehouse 3 Rooms Afternoon

[[Category:Areas]]
[[Category:Level layouts]]
[[Category:Art resources]]

Art Resources

2010-12-28T20:35:59Z

BloodsongVengeance: bloodsong adds another link to the layout list.

Art Resources are all Art created and stored into the Dragon Age Filesystem. Creators of Worldmaps will need Art Resources to shape them with Models, while creators of Facemorphs need Models of Faces. With that ,they are also creating Art Resources.
This is Part of the [[Art]] Category.

== Overview ==

Art Resources are the part of the Game which is what you hear and see. However the properties of each of the things is not. What they are instead is a property of a [[Designer Resources|Designer Resource]]. A sword, which is a [[Designer Resources|Designer Resource]], for example has attack properties, and another of these properies tell which [[Model]] it uses.

Art Resources are almost solely required by [[Designer Resources]], and as such do not make its way into the Game directly.

Any Resource is stored in the Dragon Age Filesystems [[ERF]] Files. They are created by external Tools and the Dragon Age Toolset, by multiple ways. The most common and diverse Resource is that of [[Model|Models]].
The Filename Scheme for Resources follows a general [[Naming conventions|Naming Structure]], due to its Amount and easier Management. It is also split into many [[ERF]] Files for different kinds of Resources.

=== Filestructure ===

[[ERF]] Files for Dragon Age are stored in the Folder and Subfolders:

<pre>(Dragon Age Install Dir)\packages\core\</pre>

*Browsing the Filestructure, see Article: [[ERF]]
*List of Filestypes: [[File types]]

== Modding and Creating ==

When talking Art Resources, its creation requires mostly knowing only about the Resourcetype in question. Anything about creation, exporting, formats is explained for each on their own.

A common activity in modding is overriding existing Art Resources. This is the process of recreating a special type and mimicing the Filename of the original, so that the [[Designer Resources|Designer Resource]] ,or anything that previously read that File, will now pick the modded one. Art Resources, along with [[2DA|2DA Resources]], need to be manually arranged into the Filesystem. This is normally an Override Folder of some sort, and those Resources are initially stored as single Files.

Generally, the Game and the Toolset reads multiple override Folders [[Source directory priorities|after a list of priorities]], so it wouldnt matter. However when the Art Resource should be integrated into a [[Module|custom Module]], it should be placed alongside the override folder of that [[Module]]. The reason is that the Toolset creates [[DAZIP|"DAZIP"]] [[Builder to player]] installable packages, where you select which Folder to integrate. Thus the Resources needed for the [[Module]] should not be scattered around the Filesystem.

Only the [[Builder to player]] Functionality packs those Resources into [[ERF|ERF Files]] again.

:''See also: [[Tutorials]]''

== Resourcetypes ==

=== Models ===

See Main Article: [[Model]]

=== Materials / Textures / Tints ===

See Main Article: [[Material editor]]

In closer relation to Models see Article: [[Model]]

=== Animations ===

See Main Article: [[Animation blend tree editor]]

=== Morphs ===

Facemorphs, are generated with the face-morphing tool.

See Main Article: [[Morph]]

You can download the source files for all the morphs in the main campaign from here: [http://social.bioware.com/project/1331/#files]

=== FaceFX ===

Handles facial expressions and lip-synching.

See Main Article: [[FaceFX]]

=== Visual effects ===

See Main Article : [[VFX editor]]

You can download the source files for all the visual effects in the main campaign from here: [http://social.bioware.com/project/1331/#files]

=== Audio ===

See Main Article : [[Sound and music]]

=== Level/Area layouts ===

''(Note that this is distinct from the Area editor)''

See Main Article: [[Level editor]]

You can download the source files for all the level layouts in the main campaign from here: [http://social.bioware.com/project/1331/#files]

See also [[Area layouts used in the single player module]] for a listing of what each one is.

[[Category:Art resources]]

Area

2010-12-28T20:35:10Z

BloodsongVengeance: bloodsong adds links to the layouts list. yes, all over the place!

{| style="float:right;"
|-
| {{Resource palette}}
|-
| {{Infobox area}}
|}

Areas are the spaces within which characters move around and perform actions. Items, placeables, creatures, triggers, and ambient sounds can be located inside of areas.

An area has its own coordinate system and a consistent art style so that its resources can be packaged together. Areas are limited in size. In DA, the player will travel between areas by doing area transitions. DA will keep all of the game objects in the player’s area active. They will use physics room shells on the server to determine perception and movement. Artists construct areas using the Environment Editor.

The area editor displays the selected environment in a graphics window. The currently placed objects are displayed in a tree view. Using the mouse or keyboard, the user can move objects around.

When an area is displayed in the main display, placeables and creatures can be placed within it by first selecting the item in the palette window list and then moving the mouse pointer to the correct location within the area. The object will appear and move with the mouse pointer until you left-click to affix it in place.

== Camera control and moving objects ==

Since camera control and the movements of objects is a process common to areas, stages, and cutscenes, the documentation for this can be found at [[3D control]]s.

== Toolbars ==

[[Image:Area toolbar labeled.png]]

* "Set camera to object style" causes the camera to remain pointed at the selected object; rotating the camera causes it to "orbit" around this point. "Set camera to camera style" allows the camera to be rotated in position and moved freely around the area.
* "Focus on selected object" moves the focus of the area display window to the currently selected object, if you have one selected. "Zoom to object" focuses on the currently selected object and also moves the viewpoint in close to it.
* Fade cutaway and fade punch through affect how the ceiling and other upper view-obstructing parts of the area layout are rendered see-through.
* The "display dynamic shadows" setting doesn't affect shadows that are directly "baked in" to the area's texture.
* Setting the display window to continually refresh animates certain parts of the area that have decorative animations (such as torch flames).

== Object list ==

[[Image:Area object palette right click menu.png|right]]

All of the resources currently placed within an area are listed in a menu beside the main display window. The resources are grouped according to their type and sorted alphabetically within their groups. This resource list is very handy for finding specific objects that have been placed in large and complex levels; nothing ever gets "lost" in the clutter.

Right-clicking on the object's name in the list opens a popup menu with a variety of options.

*"Copy" places a copy of the object into the clipboard.
*"Expand all," "collapse all," and "expand" manipulate the tree view.
*"Open Resource" opens the selected resource in the designer toolset. The other options available on this menu may allow you to skip this step and edit the resource's properties directly, however:
*"Open Script" opens the event script resource attached to the object.
*"Open Conversation" opens the default conversation resource attached to the object. If no default conversation is defined for this object it opens the object itself instead.
*"Open Inventory" opens the inventory of the object, allowing items to be added or removed.
*"Open Variables" opens the window for setting default variable values for the object.
*"Zoom to Object" moves the camera to focus on the object within the area display window.
*"Properties" shows the object's properties in the object inspector. Generally, clicking on this option is redundant since as soon as the object is selected from the list its properties will be displayed.

 

=== Editing objects ===

The Object Inspector Window is used to allow the user to edit properties for the objects in the area editor. Since DA is using a template model, the properties of a template can not be modified or overridden by placed instances in an area. Only a few properties can be customized on a case-by-case basis.

If you find yourself wanting to apply changes to several objects at once (items, stores, creatures, even areas), you are likely to want to try multi-edit. You can select several objects (eg by control-clicking) and any changes you make to properties in the object inspector will apply to all of them. To make this feature really usable and useful you might want to turn off the Automatically Open New Resources and the Automatically Open Checked Out Resources options in the General section of the options menu.

== Volume objects ==

[[Image:Area editor volume object.png|right]]

:''Main article: [[volume object]]''

There are four types of object that are defined by enclosed polygons drawn within the area:
* [[trigger]]s
* [[audio volume]]s
* [[reverb volume]]s
* [[music volume]]s.

Their areas are defined by clicking once for each vertex, with the final vertex being marked with a double-click that connects the final vertex to the initial vertex and closes the polygon. The interior of the area is shaded blue and when the area is selected the corner points are marked with large yellow spheres that can be dragged with the mouse pointer to adjust their location. To abort drawing an area before you've finished placing the vertexes, press the escape key.

Volumes extend vertically through space. Parts of a volume might be visually obscured by the ground or by other objects in an area, but the volume still exists and entering or exiting it works normally.

== Sound objects ==

In addition to being assigned to volumes, [[sound objects|Sound]] can be placed within the area as point sources. A sound source can be activated or deactivated by setting the "Active" property. They are omnidirectional by default, but can be focused into a "spotlight" of sound by setting the ConeInside and ConeOutside angle parameters (360 degrees is omnidirectional). The ConeOutside angle is always greater than the ConeInside angle. The sound volume of the ConeOutside area is set with the ConeOutsideVolume parameter and the overall volume of the sound source can be set with the Volume parameter (both in dB, relative to event setting). The pitch of the sound can also be adjusted with the Pitch property (in octaves, relative to event setting).

The FadeIn and FadeOut properties (in milliseconds) determine how rapidly the sound rises or falls in volume when the sound's area is entered or exited.

MaxRange and MinRange (in meters) determines the distance from the source over which the sound can be heard, with MaxRangeMult determining how the sound drops off over that distance.

Finally, the Occludable true/false property determines whether surrounding walls will block the sound.

== Waypoints ==

[[Waypoint]]s are markers you can place in an area either for use as reference points in scripting or for placing notes on the map. To place a waypoint, right-click on the area editor and select "insert waypoint" from the dropdown menu. The waypoint will be created and can be positioned within the area just like any other placeable object. See [[waypoint]] for more details on their properties.

== Stages ==

[[Stage]]s are layouts that define how a group of creatures are arranged and where cameras are placed during a conversation. See: "[[Stage]]" for details about how to create a stage. To place a stage within an area, simply select the stage from the palette window and click on the location within the area you want to create it. The stage can be moved and rotated to adjust its position.

== Creatures ==

[[Creature]]s are the most common entities the player is going to interact with; see [[Creature]] for details on how to define them.

When placing a creature within an area, you will be able to customize some (but not all) of its details to suit the situation it finds itself in. Selecting the creature within the area brings up the following relevant properties in the object inspector:

*Active: True/false, determines whether the creature is visible
*Rank: sets how much of a combat challenge the creature should present to the player
*Team: Used for keeping track of groups of creatures, for example a script may trigger when all members of a certain team have been killed.
*Trackable:
*Treasure Category: Determines what kinds of treasure is automatically generated for this creature.
*WeaponsDrawn: True/false, determines whether the creature is prepared for combat

The orientation parameter for creatures only sets its facing angle around the vertical axis.

== Merchants ==

[[Merchant]]s are triggered by a script that's usually itself triggered by a conversation node belonging to a creature (the 'merchant' that the player will actually see and interact with). The merchant object placed in the area map won't be interacted with directly.

== Placeables ==

[[Placeable]]s, also known as Interactive Objects, are parts of the scenery that the player can interact directly with and that can themselves respond in various ways to events. The internal details of placeables are defined in their own section of the editor.

Once placed in an area, the following properties can be set:
*Active: Determines whether the placeable is visible and interactive or not.
*Initial State: Some placeables will have two or more states they can be in, for example a chest may be open, closed, closed and locked, or destroyed. This sets what state the placeable starts out in when it's first spawned.
*Pick Lock Level: All placeables can be locked, though this normally only has a useful effect for things like chests and doors. This property sets how difficult a task it is for a character to unlock the placeable.
*Rank:
*Team:
*Treasure Category:

Placeables can be reoriented along all three axes.

== "Active" vs. "Inactive" objects ==

In-game, objects can be set active or inactive by script. Inactive objects are still accessible to script calls but have their command queues cleared. Objects placed in an area not on the current area list are not accessible by tag based searches. I don't remember if they are accessible by local objects,{{undocumented}} but it is generally best to act as if they are not accessible unless in the same area list (or a general object loaded into memory like a party member or a map or a map location).

== Refreshing resources ==

To improve toolset performance, many resources are cached and will need to be refreshed before changes you've made will show up in other editors. This can come up a lot in the area editor since it brings together a wide variety of other resources such as creatures, placeables, sounds, and so forth.

If you've edited a resource that's used in an area you have open you can manually force a refresh by selecting the "Refresh" option from the View menu, or by pressing F5.

[[File:Refresh resources menu.png]]

== areadata 2DA ==

See [[areadata.xls]]

== Variables ==

{{Variable table start}}
{{variable table row| AREA_COUNTER_1 to 10 | int | | Available for use by scripting.}}
{{variable table row| AREA_DEBUG | int | | {{undocumented}} }}
{{variable table row| AREA_DO_ONCE_A and B | int | | {{undocumented}} }}
{{variable table row| AREA_GAME_MODE_OVERRIDE | int | | {{undocumented}} }}
{{variable table row| AREA_ID | int | | References a row in [[areadata.xls]] for combat balance and other information}}
{{variable table row| AREA_PARTY_CAMP | int | | {{undocumented}} }}
{{variable table row| AREA_WORLD_MAP_ENABLED | int | | If this is set to 1, the party can switch to travel on the world map at any point within the area. }}
{{variable table row| CODEX_PLOT_FLAG_1 to 10 | int | | When the area is entered, any codex entries listed here will be given to the player. }}
{{variable table row| CODEX_PLOT_NAME_1 to 10 | string | | The plot names containing the codex plot flags listed above.}}
{{variable table row| ENTERED_FOR_THE_FIRST_TIME | int | | Defaults to false. If false, set true when an area is first entered and exploration XP is awarded. }}
{{variable table row| INJURY_FLAG | int | | {{undocumented}} }}
{{variable table row| PARTY_PICKER_ENABLED | int | | The player may change the composition of their party at will within this area, drawing from their pool of available party members.}}
{{variable table end}}

== Properties ==

{{Inspector start}}
{{Inspector section|General}}
{{Inspector row|Area Layout|One of the existing area models in the database. (See [[Area layouts used in the single player module]] for a list.) See also: [[Level editor]]}}
{{Inspector row|AreaList| Assigns this area to an [[area list]].}}
{{Inspector row|Comments|General information about this resource}}
{{Inspector row|Name| Name of this area as seen within the game.}}
{{Inspector row|NameRequiresReTranslation|A true/false flag used during game development for [[localization]] work}}
{{Inspector row|Resource Name|A unique string identifier the toolset and the game both use to refer to this resource}}
{{Inspector row|Script|Event script associated with this area}}
{{Inspector row|Variable 2da| 2da file containing a variable table. Only the values in the table can be set and retrieved by scripting.}}
{{Inspector row|Variables| Opens the variable table for editing, allows the initial values of the variables to be defined.}}

{{Inspector section|Actions}}
{{Inspector row|No Teleport| Sets whether you can jump to the party camp or world map from any point in the area - used in non-hostile regions where there should never be a significant obstruction to reaching the exit aside from the tedium of running there.}}
{{Inspector row|Non Hostile| may be legacy - may have been to mark certain areas as being combat-free{{undocumented}} }}

{{Inspector section|Audio}}
{{Inspector row|Music Preset| A music preset that applies throughout the area.}}
{{Inspector row|Reverb Preset| A reverb preset that applies to all sounds throughout the area. }}

{{Inspector section|Map}}
{{Inspector row|Area Map|{{undocumented}} }}
{{Inspector row|Area Map Height|{{undocumented}} }}
{{Inspector row|Area Map North| How many degrees clockwise you would need to rotate the area for 'up' to be north on the map.}}
{{Inspector row|Area Map Width|{{undocumented}} }}
{{Inspector end}}

[[Category:Areas]]

LVL

2010-12-28T20:32:45Z

BloodsongVengeance: bloodsong adds links to the lvl list (cuz i can never find it!)

The LVL format is used by the [[level editor]]. It is a rebranded [[ERF]] file; if you rename it with an .erf extension you can open it with the [[ERF editor]] and extract resources from it.

For a list of LVL files used in the Single Player Campaign, see [[Area layouts used in the single player module]].

[[Category:Level layouts]]
[[Category:File types]]

Level editor

2010-12-28T20:31:41Z

BloodsongVengeance: bloodsong adds links to the area layout list (cuz i can never find it!)

{| style="float:right;"
|-
| {{resource palette}}
|-
| {{Infobox level editor}}
|}
The level editor is used to generate the level layouts (also called Area layouts) that are the basis for creating [[area]]s. A level layout is a non-interactive [[Art Resources|resource]]; the objects placed within it serve only to provide the physical structure and appearance of the area. If you need the player to interact with objects within an area you'll need to use interactive [[placeable]]s instead.

Note that unlike the [[Area]] editor, only two modes of camera control are currently supported: "flycam" mode ([[Image:IconFlycamStyle.png]] button in the toolbar) and 3DS Max mode ([[Image:Icon3DSMaxStyle.png]] button). NWN style is not currently supported. (Use a combination of the mouse wheel + Ctrl or/and Alt (dependant on camera mode) to control the camera. In either mode Numpad 5 will reset the camera.)

Area layouts are an [[Art Resources|Art Resource]].

You can download the source files for the levels in the main campaign from here: [http://social.bioware.com/project/1331/#files]. (See also [[Area layouts used in the single player module]] for a listing of what each one is.)

== Terminology ==

*Sector: A sector is a square of geometry and is currently exported to the game as a “Chunk”. For all intents and purposes, we can consider a sector and a chunk to cover the same area. The different term is kept to distinguish between source (sector) and output (chunk). Sectors are always square.
*Chunk: A Chunk is the game-side basic building blocks of Terrain based levels. Each Chunk is self-contained, has its own levels of Detail (LOD), RIMs, model lists, tree lists, etc. It is what is streamed in and out during gameplay.
*Base Resolution: This is the starting resolution of each cell, and can be specified in the wizard.
*Cell: A cell is the basic building block of the terrain geometry. Each cell starts off at the base resolution as a square and is made up of 2 polygons.
*Blend Mask: The blend mask is the mask that is used to paint textures on the terrain. It is a blend16 algorithm, where it blends the highest 4 texture values (out of a possible 16) on each texel to come up with a texture mapped terrain.
*Texture Palette: The texture palette is essentially a list of textures, one after the other. When an artist wants to use a texture to paint on the terrain he/she would add a texture to this palette.
*Blend Texel: These are the building blocks that make up the blend Mask. Each texel is comprised of 4 sets values and each value set is essentially a percentage of how much of that texture on the palette shows up, and a mapping of where it maps onto the mask.
*Tessellation: Tessellation is the breaking up of a cell into more resolution of polygons. For each tessellation level it breaks up each polygon into 4 equal parts.

== Camera controls ==

=== Movement speed ===

In a level editor, camera movement speed in "flycam" mode can be increased and decreased by holding down a left CTRL and using a mouse wheel.

== Interior and exterior levels ==

There are two basic types of levels; interior and exterior. Many features of these two level types are the same and level editor documentation will generally be applicable to both types unless specifically noted. Their key difference is that exterior levels have a terrain mesh (the "ground") and interior levels don't. Note however that there's no reason why you couldn't use one level type to "fake" the other - for example you could create a an entirely underground cave using an "exterior" level with the terrain mesh as the cave's floor.

== Toolbar ==

[[Image:Level editor toolbar labeled.png]]

See sections below for detailed information on level editor specific toolbar buttons.

=== Terrain mesh ===

The [[terrain mesh]] is a deformable surface used in exterior levels to provide a "ground". This toolbar contains the tools that deals with the terrain mesh:

[[Image:Level editor toolbar terrain editing.png]]

Each of these buttons brings up a "brush" that's used for various tasks. See [[Terrain mesh]] for details.

=== Other tools ===
* Chunk boundary visualization - The chunk visualization tool is a button that will highlight where all the chunk/sector boundaries are, allowing the artist to plan the level accordingly. As you can see, it also highlights the models that fall into a colored chunk so that you can see which chunk these will fall into on export.
* Highlight impassible terrain - The game imposes limits on the slope of a walkable surface. Toggling this viewport button will display red highlights on the terrain wherever this limit is exceeded.
* Fade Cutaway Toggle - Cutoff, or 2 meter cutoff as it is called, is where we cut off the tops of models in interiors when we go into tactical camera mode, or overhead camera. This way we can still see the players. The cutoff tool allows the artists to visually see from the editor what will get removed when going into the tactical camera.
* Fade Punchthrough Toggle - Punch through is a system that allows the artists to put a flag on a model to say that it will get “punch through”. What this means is that when the game user is in tactical (overhead) camera mode, any model that is between the main character and the camera will get a punch through mask applied to it. This tool allows the artists to see in the editor what will get punched through in the game.
* Visualize Collision Objects - Turning on the visualize collision toggle will display all collision shapes in green/red wireframes. The green-red tinting is provided to make it easier to distinguish multiple objects from one another.
* Continuous Refresh Toggle - When the continuous refresh toggle is activated, the viewport will constantly redraw whenever it has free CPU time. This is useful for visualizing VFX and another animated models.

== Lighting ==

There are many different types of [[lighting]] and light combinations that can be placed in the editor.

There are also many tools used to create lighting and generate lighting and even visualize lighting in the editor. The goal with the editor is to give the artist the same experience as he/she would see in the game. This will help them to be able to create the levels and tweak lighting quickly without having to stop to see it in-game.

Lights for the game are split into two categories based on what they affect: levels and characters. Character lights will affect the player, NPCs, and creatures. The level lights will affect static geometry and designer placeables.

See [[Lighting]] for more detail.

== Models ==

[[Model]]s are used to create any other objects that may be used as part of the level art - walls, floors, ceilings, non-interactive furnishings, visual effects, etc. ([[Image:IconModelPlacement.png]])

:''See Article: [[Model Placement|Model Placement]]

Trees and Vegetation is added using the "scatter object" mode ([[Image:IconScatterObject.png]]).

:''See Article: [[Vegetation|Vegetation Placement]]

===Animations===

Some models have animations associated with them which may be set through the DefaultAnimation field of the Object Properties. For example, if you want a windmill or water wheel to turn you need to set that animation in the level editor. The animations for those two models are:

Windmill - wind

Waterwheel - turn

== Room visibility and connectivity==

Interior based levels have explicit connections between rooms, unlike exteriors where there is an implicit connection between two neighboring chunks. For this reason the connectivity must be set up by the artists. This should be done through planning and iteration as it will affect the streaming and performance of the level in the game.

If you select a room, you will see that that room appears highlighted in red. The Room Properties window can be brought up by pressing the Room Properties button. This behavior can be disabled by unchecking the Highlight visible rooms checkbox. All of the rooms that are visible to this room show up in green. You will see the list of these rooms show up in the Visible Rooms list in the picture above.

The ideal way to generate this visibility information is to press the button called “Generate Visibility Graph”. This will take a little bit of time, so sit back after you press it and be patient. What it does is take a render of each room in the level and generate a list of all rooms that can be seen from it.

NOTE: You must have generated pathfinding data for the level before you generate the visibility info, as it uses the pathing points in this process.

Of course this can be tweaked manually afterwards using the add and remove buttons. However if you ever press the Generate button again it will wipe out all manual changes.

The visibility system is used for streaming as well as the fog of war system, and determining what rooms are visible to the player depending on his/her current room. There is one other factor however to this, the connectivity system, which is detailed next.

The Room Connectivity System is necessary because there are things that can block visibility from one room to another. For instance if I’m looking up a hallway and I can see 3 rooms in the distance, but then I close the door in front of me, the game needs a way to know that those rooms are now invisible. This is where this system comes in.

The room connectivity system can be visualized by the other checkbox under the Connected Rooms list in the Rooms properties window.

Notice that the rooms connected to the current room show up in brown. This is a reminder that you are looking at connectivity and not visibility. As you can see only the rooms that are DIRECTLY connected to the selected room should be in this list. This has to built up manually, by clicking add and then clicking on the rooms that are connected to it. The add button in this case is more of a node, click it, then click the rooms you want to add, then you have to click it again to turn it off. This was done to make adding all the rooms faster.

== Black boxes ==

When creating an indoor layout you'll need to manually insert "black box" objects on the outer sides of the layout's walls. This allows the player to see through the walls when the camera is outside them, and obscures any parts of models that protrude out where the player shouldn't be able to see them.

== Trees, grass, and shrubberies ==

Trees, grass and shrubberies are handled somewhat differently from other models. They are created using a program called SpeedTree that includes information allowing them to respond to the wind. To place trees on a level, you first need to add that tree type's tree controller:

[[Image:Level editor insert tree controller.png]]

Once this is done you can use the scatter object tool ([[Image:IconScatterObject.png]]) to place specific examples of the vegetation you've added controllers for.

See [[Vegetation]] for a gallery of the vegetation types included with the core resources.

===Scatter Object Tool ===
The scatter object system allows the artist to place down both trees (and grass) and instanced models. An example of an instanced model would be some rocks scattered around on the ground. Objects that are scattered across the terrain level will be placed randomly inside the brush, and will also randomly fluctuate in size and orientation as well.

The Scatter object tool allows the artist to paint scatter object on the terrain. These scatter objects cannot be selected individually, but can only be added or removed with this tool. Left clicking adds scatter objects within the brush, right clicking removes them.

*Fill Rate: This is the rate at which the objects are scattered inside the brush.
*Radius: This is the radius of the brush that adds/removes scatter objects.

When the artist is painting scatter objects, he/she gets a palette, or Scatter Object Selection, from which to select which scatter object to paint. Currently there are 2 tabs, one for trees and the other for instanced models.

The artist can add items to this list by right clicking on the Terrain World and selecting Insert, and then choosing either new Tree Scatter Object or new Model Scatter object. In each case the artist will be able to browse a list of available resources.

*Ignore Density Setting: This allows the artist to ignore the density setting and paint scatter objects in much the same way as one would use a can of spraypaint.
*Maximum Density: This allows the artist to specify the maximum density of scatter objects in the brush radius, and the brush will only paint up to this maximum.
*Maximum Scale: This caps the maximum scale of the scatter objects, 1 being the same size as the original.
*Minimum Scale: This caps the minimum scale of the scatter objects, 1 being the same size as the original.
*Number of Painted Object: Lists the current number of this type of object that has been painted in the level (un-editable).
*Orient On Terrain Surface: When this is set to true, the objects will orient themselves according to the orientation of the terrain on which they are placed. For instance if you put a rock on the side of a hill, it will still appear “flat” to the ground. NOTE: Currently this does not work for trees or grass, they will always be complete vertical.

== Water tools ==

See [[Water]] for detailed documentation on placing water in the level editor.

== Wind ==

Each level can have one active wind object in it. The location of the wind object doesn't matter. The wind object defines how wind behaves on this level, which is used for such things as flapping banners and swaying trees.

To insert a wind object, right click on the terrain, and choose Insert > New Wind Object.

[[Image:Level editor wind object.png|center|]]

For other weather effects, see [[Weather]].

== Pathfinding ==

Pathfinding is generated by clicking the toolbar button [[Image:IconGeneratePathfinding.png]]. The pathfinding process lays down a grid of points that are marked "accessable" if they can be reached from a pathfinding start spot via passable terrain. This is essentially a flood-fill algorithm.

In the case of exterior areas, you must select an [[exportable area]] before it will generate it, the error message will reflect this.

To see the existing pathfinding grid, click on the [[Image:IconDisplayPathfinding.png]] toolbar button or select "Pathfinding nodes" under the "View" menu.

"Passable" or "impassable" depends on a variety of factors such as the slope of the land, obstructions, or water depth. Accessibility Start points are represented by a blue ring with a red arrow. Note that these are different from [[waypoint]]s, and are only used by the level editor for pathfinding purposes.

[[Image:Level editor pathfinding start spot.png|thumb|center|300px]]

Models will often contain collision volumes that will automatically make the places they're located impassible. Likewise, you can set a certain depth of water as being impassible and pathfinding will take this into account.

In order to get pathfinding to work, you must generate your starting point AFTER you create the exportable area, and use the name that is automatically generated for the starting point. DO NOT change the name of the starting point otherwise pathfinding will fail.

=== Terrain Collision ===

You will need to block off terrain using the Terrain Block tools [[File:terrainBlockButtons.png]]. The first button toggles the display of the terrain blocks, the second button enables you to place terrain blocks, and the third snaps existing blocks to terrain verticies. Left-clicking will start a new block, with additional left-clicks chaining the blocks together. Right-clicking will end the current chain. In addition, right-clicking on an existing block will delete it.

An example of a terrain block chain showing the path finding

[[File:terrainBlockExample.png|thumb|center|600px]]

== Hotkeys ==

{| border="1" cellspacing="0" cellpadding="2"
|-
! Key || Function
|-
| R || Standard Selection
|-
| Q || 3D Axis Manipulator
|-
| E || Rotation Manipulator
|-
| T || Local Coordinates (Toggle)
|-
! Key || Camera Functions
|-
| W || Camera Forward / In
|-
| S || Camera Back / Out
|-
| A || Camera Pan Left
|-
| D || Camera Pan Right
|-
! Key || Brush Size
|-
| - || Decrease Brush Radius
|-
| = || Increase Brush Radius
|-
! Key || Editing
|-
| Ctrl-X || Cut Selected Object(s)
|-
| Ctrl-C || Copy Selected Object(s)
|-
| Ctrl-V || Paste Selected Object(s)
|-
| Ctrl-Z || Undo last action
|-
| Ctrl-Y || Redo last action
|-
| Ctrl-A || Select All
|-
! Key || General
|-
| Ctrl-S || Save Map
|-
| Ctrl-O || Open Map
|-
| F5 || Refresh Screen
|-
| Del || Delete Selected Object
|-
| 5 (Numpad) || Camera Reset/Home (Looks at bottom right corner of map)
|-
| Ctrl-H || Hide Selected Object(s)
|-
| Ctrl-/ (Numpad) || UnHides Selected Object(s)
|-
| Ctrl-* || UnHides all hidden objects
|-
| Ctrl-\ || Invert Selection
|}

== Tips ==
Groups are your friend.

Selecting a group will select all models inside that group folder.
This allows you to move several objects at the same time as well as apply other settings to that entire group.

This also makes placing several grouped objects like torches with flame and lights very quick and easy.
For example, Setting several candles with flame effects would take a lot of time to place each candle stick individually, and then placing the flame effect exactly on top of the candle for each. By using group folders you only need to set this up once. To place more candles simply select the group folder, Ctrl+C to copy, select its parent group, or other place you want to put the next candle and Ctrl+V to past the new group. Then simply drag it to where you want it.

[[File:Tip_1.jpg|thumb|center|600px]]

In addition, the Selection Lock and Visible properties of objects can be useful when trying to manipulate objects when larger objects obscure or get in the way of the desired selection. This is especially handy with water meshes.

[[Category:Level layouts]]

== Manage exports==

The "Manage Exports" window is accessible from the Tools -> Exports -> Do All Export Operations menu option. It brings up a window where you can select from all steps in the level-exporting process:

[[File:Manage exports.png|center|]]

Area tutorial

2010-12-28T20:29:09Z

BloodsongVengeance: bloodsong adds lots of links to the area layouts list (because i can never find it!)

{{Infobox area}}
== Creating the area ==

Once you have created a new module (see [[creating a module]]), the first thing you will likely want to do is create one or more areas where your adventure is going to be set. There are several ways to reach the "new area" command; you can right-click on the resource palette window, or select "new" from the file menu.

[[Image:New resource.png|thumb|center|New resource menu]]

 

Areas are represented with the [[Image:IconArea.png]] icon. When you select it you'll be presented with a "Create New Resource" window:

[[Image:Create new resource.png|center|]]

{{sidebox|
* Resref names should be useful to the designer
* Set the "area layout" property to assign terrain to an area
* "Resource Name" and "Tag" are only seen by developers
* "Name" may be seen by players
}}

Most of the fields are already filled in with good defaults for the module you're working with. You'll need to supply a "ResRef Name", which is the name by which the resource will be known internally to the toolset. (This is the "Name" field on the "Create New Resource" dialog box.) You'll probably want to use a name that will remind you, the module designer, of the purpose or important features of the area. Changing a resource's name is difficult to do later. We're going to call the first area of the tutorial "hut_exterior".

After creating the area you'll be presented with a completely blank area editor. There will be no environment or objects of any kind. To specify what environment you'll be placing objects into, open the object inspector and select the "Area Layout" property. There will be an ellipsis button ([[Image:ellipsis.png]]) in the property's data field that will bring up a resource selection window where you can select an environment to use for this area. (See [[Area layouts used in the single player module]] for a listing of what each one is.) The environment we wish to select is in the area layout file "ost101d.arl". Once we select it, the area layout appears in the main area window.

The resource's internal resource name is hut_exterior but the player will not see this when he's playing the game. To give the area a name meaningful to the player we'll set the "Name" field to "Deep in the Swamp". All of the other defaults are fine for now, we will leave them as is.

[[Image:Area tutorial 1.png|thumb|600px|center]]

== Area Basics ==
{{sidebox|
* See [[3D control]] for camera and movement controls
* You can double-click on an object in the area's object list to zoom in to it.
}}

Moving the view around inside the area layout can be somewhat non-intuitive and frustrating at first. The toolset has a number of different control schemes it can be set to; see [[3D control]] for a summary of the various options. By default, you can:

* zoom in and out by using the mouse wheel
* rotate the camera around the target it's focused on by holding the middle button down or by holding down the Ctrl key and the right mouse button while moving the mouse
* translate the camera by holding down the Ctrl key and the left mouse button while moving the mouse

To see where you are a bit better, it is helpful to deactivate real lighting or turn on full brightness. Above the area viewer, the sun-like button should be toggled so that it isn't highlighted; see [[Area]] for a more complete summary of various options within the Area Editor.

Sometimes the Area Editor may show your level as a wireframe when you create it. You can switch from a wireframe view to a normal view by going to the View menu and choosing View/Environment/Render Mode/Normal.

Before we move along to placing a starting location, it is important to touch upon Pathfinding points. All BioWare areas include walkmesh or pathfinding information. To view pathfinding information for your area, goto View, then Environment, and then toggle Pathfinding Points on. The green dots represent areas where characters can walk. Note, in this map, the area that is walkable is quite small compared to the entire area. When placing your starting location, you should ensure it is in a walkable portion of the area.

== Setting the start point ==

{{sidebox|
* Create a waypoint to mark where the player starts the game
}}

This is going to be the starting area for the adventure, so we're going to want to define a spot within the area where the player will first appear. This is done by setting a [[waypoint]]. Waypoints are very simple objects that mark locations in an area that other objects in the game can refer to; they are not normally visible to the player. To create a waypoint, right-click somewhere in the area and select "Insert Waypoint" from the resulting menu. A waypoint will appear at the location of your mouse pointer and follow it around along the area's floor; move it to the approximate place you want to have the player appear and left-click to place it. By default the waypoint is named "Waypoint".

The waypoint will be automatically selected, indicated by a yellow wireframe box surrounding it. You'll also see the waypoint listed in the area's object list, to the left of the display window. If you lose track of the waypoint later a good way to find it again is to right-click on the waypoint in the list and select "Zoom to Object" in the resulting menu or double click on its tag to center the object in the display window. The waypoint's properties will be shown in the object inspector. We want to change the waypoint's name to something more informative, in this case to "start". More importantly for the game itself, though, we'll also want to change the waypoint's tag to "start" (it defaults to blank). An object's tag is how scripts and other resources will refer to the waypoint. Since this particular waypoint is never going to be visible to the player it's likely that the waypoint's name will never be seen at all.

The player will also start out facing in the same direction that the waypoint is facing (indicated by the arrow-shaped base of the waypoint object). If we don't want the player to start out facing in the default direction, we'll want to rotate the waypoint to point in a new direction. To rotate an object, use the toolbar to switch from standard selection mode ([[Image:Standard selection mode.png]]) to 3-axis rotation mode ([[Image:3 axis rotation mode.png]]).
When you select the waypoint in this mode you'll see a set of circles around the waypoint's base with various orientations; clicking and holding the mouse button on one of them will allow you to rotate the waypoint around its center.

[[Image:Waypoint rotation.png|center]]

Now that we have an area and a waypoint to start at, we can now tell the module that this is where the player is to appear. Reopen the "Manage Modules" window (available via a command under the File menu), select your module, and click the "Properties" button. This opens the module's properties. For the "Starting Area" property, click on the ellipsis button ([[Image:ellipsis.png]]) and select the starting area from the areas available in the module; since we've only put one area in so far "hut_exterior" will be the only available option. Once the area has been selected we can then select the starting waypoint from the waypoints currently placed in the area. Note that the list will show waypoint tags rather than names. Again, we've only put in one so this will be easy. You can also set the player to appear at the origin of the map (coordinates 0,0,0), but this is generally a poor choice and available only as a default in case there are no waypoints defined yet.

== Area transitions via doors ==

Adventures almost always have more than one area in them, so we'll create a second area to demonstrate travel between the two. The area "hut_interior" will use area layout ost102d, which is a cosy little room that represents the interior of the small hut present in the hut_exterior area.

{{sidebox|
* [[Door]]s are special placeables
* Doors can attach to "hooks" pre-built into the area layout
* Area transition doors use a different "appearance" than within-area doors
}}

Next we will need to create some doors. We'll create a default door placeable using the "New Placable" command, reached in a similar way as the "New Area" command explained earlier (placeables will be covered in the [[Placeable tutorial]], but the core game resources will come with a variety of default doors usable in many situations like this) and place it in the area near the empty doorframe built into the hut's exterior. For an area transition, use one of the "Area Transition" appearances for the door. To place the door, click on it in the palette; the mouse cursor will turn into a crosshair; then click in the area viewer near the doorframe.

As a side note, if you accidentally use one of the standard door appearances it won't work as an area transition: the door will simply swing open when clicked on instead. Each standard door appearance has a matching area transition door appearance in the resource database so this can be an easy mistake to make, but it's also easily correctable - just go back to the door's placeable resource and swap in the correct appearance, and all copies of that door in use throughout your game will be updated. The "Area Transition" doors are at the top under the Appearance list, e.g. "Area Transition, Ferelden Small" as apposed to "Door, Ferelden, Small".

You may notice that when the door you placed in the area is selected a small blue sphere will appear at one edge in addition to the yellow wireframe bounding box. This is the door's "hook". Area layouts come with hidden "hooks" pre-installed to place doors on, and doors have matching hooks of their own. If you click on the blue sphere it will turn red, and all of the compatible door hooks built into the area's layout will appear. The following image illustrates this:

[[Image:Door with door hook selected.png|400px|center|thumb|Drag the red sphere near to the blue sphere to automatically position the door]]

To hook a door up with its frame, simply click and drag the door's hook to a location very close to the matching frame hook. You don't need to get the positioning exact; if the two hooks are close enough together when you release the mouse button they'll automatically snap together. The door will be positioned and reoriented to fit correctly into the frame. Make sure you're still in the 'Standard Selection' mode ([[Image:IconStandardSelection.png]]) for the snap to occur, if you're in the more advanced 3 Axis Movement tool, the snap will not happen.

Note that door hooks are only there to make it easy to get exact matches on frames and walls that need a snug fit, to ensure that Artists and Designers don't have to spend a lot of time putting it in place. Doors will function just as well off of hooks as on them.

{{sidebox|
* Area transition effect is defined in the door's "Variables" property
}}

Next, we'll tell the game engine that the door is an area transition door and that when the player clicks on it he will be transported to another area of the game. This is done by setting two of the door's [[variable]]s. Select the door (either in the area's object palette or directly in the main display window) and right-click on it, selecting "properties" from the resulting menu. This will open the door's properties in the Object Inspector window. Select the "Variables" property and click on the ellipsis ([[Image:ellipsis.png]]) button. This will open up the variable browser for that particular instance of the door object.

There are two key variables in this list that we'll need to set:

*PLC_AT_DEST_AREA_TAG - tag of the destination area
*PLC_AT_DEST_TAG - tag of the destination waypoint within the destination area. This is a waypoint that you must add. It is NOT added automatically when you create the door.

Once we've set these the door will become an area transition door, and when the player interacts with it they'll be transported to the target area.

The destination area is "hut_interior". We'll create a waypoint just inside the hut's interior door, tagged "hut_door_interior", to serve as the place where the player appears.

Here is how the exterior door's variables should look:

[[Image:Area tutorial door variables.png|frame|center|Area transition door's variables]]

And here is the interior door, with the destination waypoint:

[[Image:Area tutorial interior door.png|frame|center|Interior door with destination waypoint]]

The interior door is set up in the same manner, with a destination area of "hut_exterior" and a matching destination waypoint of "hut_door_exterior".

{{sidebox|
* Use invisible area transition "doors" when the transition is already built into the area layout art
}}

If you want to create an area transition that doesn't look like a door, or is otherwise already represented by the level art, you can use an invisible 'door' instead. Therefore you have to create an invisible Placeable first. For details how to create a Placeable see the [[Placeable tutorial]]. The first defining point of a Placeable is the "Appearance". Appearances for these invisible placeables are named "Area Transition, Invisible". Chose one of them to your liking. If you want your area transition to show a meaningful name, you have this to add during the creation of the placeable under "Name". After you have created the placeable you can place it as you wish. Here is the yellow show box around the placeables important, because you will not see it otherwise. Now set its variables the same way as was done for the visible door.

[[Image:Area Transition, Invisible.png|frame|center|Invisible area transition]]

The player won't see this 'door' in the game, but when he moves the mouse pointer over it it will change to signify that an area transition lies there and it can be right-clicked to be activated just like a visible door.

== Area transitions via triggers ==

{{sidebox|
* Triggers use variables with a different prefix for setting their area transition effect
}}

Finally, you can also create an area transition that triggers automatically when the player walks into a predefined area. This is done using [[trigger]]s. ([[Image:IconTrigger.png]]) You'll first have to create a trigger resource, much like how you had to create a placeable door earlier, but trigger resources are much simpler and for area transitions you won't need to change any of the defaults. Create a default trigger with "New -> Trigger" (either by right-clicking the resource palette or from the File menu) and give it an informative name such as "trigger_area_transition".

Go back to your area map, select the trigger from the resource palette, and then click on the map to define the corner points of the area the trigger will occupy. Double-click the last vertex to complete the polygon. A trigger can have any number of vertices, and vertices can be moved, added, or deleted after the trigger is created so don't worry if you don't get it exactly right. Note that the blue plane the trigger uses to show the enclosed area will pass through the ground and may not be entirely visible in the toolset, but it extends infinitely upward so the trigger will still take effect if the player enters its boundaries.

To set the trigger's destination, you'll find a familiar pair of variables in the trigger's default variable table:

*TRIGGER_AT_DEST_AREA_TAG - tag of the destination area
*TRIGGER_AT_DEST_TAG - tag of the destination waypoint within the destination area

(Note the prefix "TRIGGER" instead of "PLC")

Below is an example where we've placed both a trigger and an invisible door across a pathway. Note that this is redundant, only one or the other is really needed. For most purposes a placeable area transition is probably best. (''It is worth noting that placeable area transitions prompt a popup asking the player if they want to transition when bumped, but not when clicked upon - effectively acting as either a door or a trigger.'') The waypoint shown is the arrival spot for the player when coming in from the other side; note how it's placed outside the trigger area, allowing the player to immediately back up and retreat through the area transition if he chooses.

[[Image:Area Transition, invisible with trigger.png|center]]

== Grouping Placeables ==

{{sidebox|
* Two or more placeables can be grouped together using Associations.
}}

Often the placeables within an area are related. For example, a firepit placeable probably has an associated sound emitter. The toolset needs to be told that these two objects are related.

# Create a new Placeable and change its "Appearance" to "Firepit (Dialog)", then place it in your area. Remember that if you can't see the new placable, make sure you have the correct module open.
# Next, click on the musical note icon in the Palette for "Sounds".
# In the folder tree, go to global_amb_fade > 3D_placeables > 3d_emitter and select the amb_ext_smfire1_lp and place the emitter in your area.
# Right-click on the firepit to bring up the menu and choose "Add Associated object." The cursor changes to a cross-hair.
# Click on the sound emitter placeable.

Now when you drag the firepit placeable around the area, the sound emitter will automatically follow. Use the "Managed Links" menu item if you want to remove an association. Note that associations are uni-directional; you can still move the sound emitter without moving the firepit. Examples of other useful associations: a table and all of the items on top of the table, a table surrounded by chairs, etc.

== Sound ==

Sounds are placed using the Area Editor. For more details see [[Sound]].

[[Category:Areas]]
[[Category:Tutorials]]
{{Languages}}

Talk:Builder to player

2010-11-26T19:34:16Z

BloodsongVengeance:

This could use a step-by-step guide.

I have read what Sunjammer posted under his Lil Red Riding Hood Redux project but players still cannot use my mod.

- george

It could use a list of what files one needs to be sure to find. ie: lvl, any voice-over files (wav or fsb), etc. and what, if any, files are not necessary. (ie: lightmapper files?)

[[User:BloodsongVengeance|BloodsongVengeance]] 19:34, 26 November 2010 (UTC)

Community Contest 5: Room Contest

2010-11-24T17:28:12Z

BloodsongVengeance: /* Vigil Suite by Bloodsong */

[[File:Community_Contest_back.jpg|link=Community_Contest_Main_Page]] [[File:CC_BSN_GetInvolved.jpg|link=http://social.bioware.com/group/2535/&v=discussions]]

== Brief ==

'''Create an indoor room and export it as a SEL for other modders to paste into their levels.''' The contest discussion thread can be found [http://social.bioware.com/group/2535/discussion/12096/1180655/ here].

'''DEADLINE: Monday 29 November''' - your entry must be ready for judging before midday GMT+0. It is strongly recommended you submit well before this time (sunday!) in case you run into troubles. Modifications to your submission are welcomed - the newest version of your entry will be judged, although modifications made ''after'' the submission date will not be judged.

=== Requirements ===
All entries must:
* be submitted as a SEL (see tutorial)
* make suitable use of folders to organise the lights and models
* have doorways or suitable plug pieces to enter/exit the room
* contain lights to illuminate the room

=== Guidelines ===
Strong entries will:
* be distinctive, but suitable for use in a variety of modules
* make good and varied use of environment models
* make suitable use of VFX such as light rays, candle flames, etc where needed
* ensure that lighting looks good in-game

=== Suggestions ===
Forge, armory, servants' quarters, bedchamber, tavern bedroom, tavern drinking hall, feast hall, indoor stage theater, kitchen, dungeon, torture room, prison cell, mausoleum, creature's lair, chapel, training room, barracks, meeting room, dining room, vault, guardhouse, groundskeeper's lodge, stable.

=== Allowable ===
While no "bonus points" will be given for the following, entries may:
* include multiple rooms - particularly if creating a "tileset of rooms".
* include custom props - if you do this you must state clearly on the contest page that your entry is using custom assets. ''Please avoid this unless absolutely necessary for your room - we want these SEL files to be as easily usable as possible.''

=== Not Allowable ===
Please:
* do not cut-paste from a DAO level without making serious modifications to "make it your own"
* do not submit an entire level as your work. consider what will make USEFUL rooms for slotting into a module. For example, corridors are generally not useful for slot-ins.

== Groups and Prizes ==

=== Groups ===
This contest has only one group.

* 1st place - 15 points, chooses first
* 2nd place - 10 points, chooses second
* 3rd place - 5 points, chooses third
* Best Newcomer - 3 points (unless 1st, 2nd or 3rd place)
* All other entries meeting requirements - 1 point

To receive an "entry point", your submission must meet the requirements of the contest, listed at the top of this page

=== Best Newcomer Award ===
Every judge may nominate one newcomer as their favourite newcomer entry. To qualify, the entrant must not have submitted to a community contest before. The winning newcomer will receive three points if they don't podium (in which case, theyll be getting more points anyway!).

=== Prizes ===

Please see [[Community_Contest_Prizes|Community Contest Prizes]]

== Helpful Links ==
* [http://www.youtube.com/watch?v=03WoLxjm-bs Contest 5 video tutorial]
* [[Level_editor|Level Editor]] - Builder Wiki
* [[Level_Editor_Tutorial|Level Editor Tutorial]] - Builder Wiki

= Entries =

=== Entry File(s) ===

'''File Contents:'''
* one or more SEL files
* if you have any custom props etc, include those and their source files if appropriate. ''(please try and just use DA stuff for this contest to keep things simple)''

'''File Format:'''
one .7z file (preferred)

=== Checklist ===

# Create your file (see above)
# Create a [http://www.dragonagenexus.com/ Dragon Age Nexus] page for your entry and upload the above file. Please include "Community Contest" in the title.
# Edit this page with a description and pictures of your content.
#* Please include pictures which are both functional as well as attractive (so your work can be seen clearly)
#* Link to your DA Nexus page. See the sample entry.
# Optionally, let us know in the [http://social.bioware.com/group/2535/discussion/12096/1180655/ Contest Discussion Thread] that you've entered

For the general entry guidelines (as well as more detail on the above steps), please see the [[Community_Contest_Entry_FAQ|Entry FAQs]]

For information on Judging, please see the [[Community_Contest_Judging|Judging]] page.

== Consent to Share ==

IMPORTANT - consent to share

By entering this competition you consent to share your work for other community members to benefit from.
Where appropriate, source files should be shared (prop models, VFXProj files).
The work *MUST* be your own (obviously you may use DA assets).
Others may use and modify your work in their Dragon Age mods, though are encouraged to give credit.
As the entries are judged, local copies will be saved If your work is taken down.
If your work is taken down, you allow for it to be re-uploaded, crediting the work in your name. 

== Example Entry by mikemike37==

* '''[http://www.dragonagenexus.com/downloads/file.php?id=1559 Dragon Age Nexus project page]''' (sample entry not shared, its just a SEL file in a 7zip though.)
This is just a sample entry for others to see the sort of thing judges might expect to see, and the format in which it has been submitted.

[[File:CC5_mike_roomtop.jpg|303px|Room Plan]] [[File:CC5_mike_roomcorner.jpg|400px|Room Glamour Shot]]

=== Judges' Comments ===

Judges will leave comments both as contructive suggestions for the entrant and also as impartial guidance for any looking to make use of your work.

== Inn Bedrooms by Jackkel Dragon ==

* '''[http://www.dragonagenexus.com/downloads/file.php?id=1898 Dragon Age Nexus project page]'''

A small room including two bedrooms and a stairway down to a lower floor.

Note: There is a door way that leads to "nothing" on the same floor as the bedrooms; this can lead to another bedroom (or any other room) or replaced with a normal wall.

As this room uses interior lighting, I HIGHLY recommend reading this page to avoid wierd shadows: http://social.bioware.com/forum/1/topic/74/index/4700291

Note: This is a .sel file, meaning it is imported into a room level through "import selection" from the edit menu.

PS: I was going to submit the tavern common room for this contest, but it seemed a bit sparse. Check out the inn in the module "Scars of War" to see this room and the common room side-by-side. ;)

[[File:Cc5_jackkel_screen.jpg|300px|Toolset Screenshot]]

== Dead Room by Shadow5973 ==

* '''[http://www.dragonagenexus.com/downloads/file.php?id=1901 Dragon Age Nexus project page]'''

There are two bedrooms connected by a short hallway with a body in each of the rooms. There is also a doorway in each room where they can be attached to a larger building interior. The bedrooms could be used for part of the inside of a house or similar building after an attack by bandits or darkspawn.

NOTE:
This a .sel file to be imported into the toolset.

This room uses interior lighting, so this page might be helpful: http://social.bioware.com/forum/1/topic/74/index/4700291

[[File: Image 1.png|400px|]]

=== Judges' Comments ===

Judges will leave comments both as contructive suggestions for the entrant and also as impartial guidance for any looking to make use of your work.

== Banqueting Hall by Nattfodd ==

* '''[http://www.dragonagenexus.com/downloads/file.php?id=1899 Dragon Age Nexus project page]'''
* '''[http://social.bioware.com/project/3783/ BSN project page]'''

After a hard day of battles and fights, the evening is the right moment to take a rest, banqueting and sharing the treasures with your comrades.
Eat, drink and enjoy your time: you deserve it.

NOTE:
This is a .sel file to be imported into the toolset.

[[File: Panoramic.jpg|400px|]] [[File: Throne.jpg|400px|]]

[[File: Plant.jpg|400px|]] [[File: Cooking_table.jpg|400px|]]

=== Judges' Comments ===

Judges will leave comments both as contructive suggestions for the entrant and also as impartial guidance for any looking to make use of your work.

== Library by Semper ==

* '''[http://social.bioware.com/project/3811/ BSN project page]'''

A dusty and old place for everybody brave enough to discover the long forgotten tales hidden within ancient books. The piles of books are taller than a dwarf - that is why usually at least two dwarfs are working at libraries.

NOTE:
This is a .sel file to be imported into the toolset. The entrance upstairs is this dark to provide easy integration to other levels to keep the atmosphere of the hallway/entrance leading to the library.

[[File:Entrance iso.jpg|400px|ISO View Entrance]] [[File:Overview.jpg|400px|Overview Library]]

[[File:Fireplace.jpg|400px|Fireplace]] [[File:Details.jpg|400px|Details]]

=== Judges' Comments ===

Judges will leave comments both as contructive suggestions for the entrant and also as impartial guidance for any looking to make use of your work.

== Vigil Suite by Bloodsong==

* '''[http://www.dragonagenexus.com/downloads/file.php?id=1922 Dragon Age Nexus project page]'''

This is a suite of rooms as I imagined for the commander of Vigil Keep. It has a large master living quarters with semi-private sleeping and dressing area, a guest room, and a connecting bath. It features both sloped and flat ceilings, large windows, a whole lot of clutter and lived-in-ness, and practical aspects such as 'trash can' vases, the shared chimney between rooms as heating source for the bath, and the height of luxury: the indoor commode!

[[File:VigilSuite-m-commd.jpg‎|400px|Master Living Quarters]] [[File:VigilSuite-g-room.jpg‎|400px|Guest Room]]

[[File:VigilSuite-b-wash.jpg‎|400px|Bath Washstand]] [[File:VigilSuite-m-desk.jpg‎ |400px|The Commander's Desk]]

More images are available on the DANexus page.

=== Judges' Comments ===

Judges will leave comments both as contructive suggestions for the entrant and also as impartial guidance for any looking to make use of your work.

Community Contest 5: Room Contest

2010-11-24T17:27:40Z

BloodsongVengeance: /* Entries */

File:VigilSuite-m-desk.jpg

2010-11-24T17:11:25Z

BloodsongVengeance: CC5 Vigil Suite Master Desk

CC5 Vigil Suite Master Desk

File:VigilSuite-b-wash.jpg

2010-11-24T17:09:10Z

BloodsongVengeance: CC5 Vigil Suite Bath Washstand

CC5 Vigil Suite Bath Washstand

File:VigilSuite-g-room.jpg

2010-11-24T17:08:41Z

BloodsongVengeance: CC5 Vigil Suite Guest Room overview

CC5 Vigil Suite Guest Room overview

File:VigilSuite-m-commd.jpg

2010-11-24T17:07:56Z

BloodsongVengeance: CC5 Vigil Suite: Master Living Quarters overview.

CC5 Vigil Suite: Master Living Quarters overview.

Community Contest 4: Minigame Script

2010-10-30T18:46:57Z

BloodsongVengeance: /* Entries */

[[File:Community_Contest_back.jpg|link=Community_Contest_Main_Page]] [[File:CC_BSN_GetInvolved.jpg|link=http://social.bioware.com/group/2535/&v=discussions]]

== Brief ==

Create a minigame or puzzle using scripting. The contest discussion thread can be found [http://social.bioware.com/group/2535/discussion/10583/916864/#post_916864 here].

'''DEADLINE: Monday 1 November''' - your entry must be ready for judging before midday GMT+0. It is strongly recommended you submit well before this time (sunday!) in case you run into troubles. Modifications to your submission are welcomed - the newest version of your entry will be judged, although modifications made ''after'' the submission date will not be judged.

=== Requirements ===
All entries must:
* Reserve and use a [[Community_Contest_ID_Ranges|StringID range]]
* Be thoroughly tested in-game
* Be submitted in a single, playable area (the level will not be "marked")
* Include dadbdata export of all relevant resources
* Include a playable dazip of the mini-game - should be playable from the other campaigns menu
* Include a plain-text file detailing the mini-game implementation - the objective, customization options (if present) and solutions
* Use only DA assets (placeables, levels) ''unless the relevant files are included with the submission and author's permission has been given''
* Be submitted before Monday 1 November midday (GMT+0)

=== Guidelines ===
Strong entries will:
* be easily adaptable to vary the minigame in other modules
* be unique and interesting
* use elegant and tidy scripting
* include well-written, detailed comments
* be well-designed and be free of bugs and discourage user error
* be significant as a piece of scripting: doing something new or expanding beyond the fundamentals of scripting
* make appropriate use of secondary resources (triggers, placeables, dialogues, floaty text, VFX, sound, etc)

=== Allowable ===
While no "bonus points" will be given for the following, entries may:
* use custom levels provided that the level is shared with the submission (.lvl and exported files)

== Groups and Prizes ==

=== Groups ===
This contest has only one group.

* 1st place - 15 points, chooses first
* 2nd place - 10 points, chooses second
* 3rd place - 5 points, chooses third
* Best Newcomer - 3 points (unless 1st, 2nd or 3rd place)
* All other entries meeting requirements - 1 point

To receive an "entry point", your submission must meet the requirements of the contest, listed at the top of this page

=== Best Newcomer Award ===
Every judge may nominate one newcomer as their favourite newcomer entry. To qualify, the entrant must not have submitted to a community contest before. The winning newcomer will receive three points if they don't podium (in which case, theyll be getting more points anyway!).

=== Prizes ===

Please see [[Community_Contest_Prizes|Community Contest Prizes]]

== Helpful Links ==
* [[Scripting_overview|Scripting Overview]] - Builder Wiki
* [[Scripting_tutorial|Scripting Tutorial]] - Builder Wiki
* [http://dalexicon.net/index.php?title=Main_Page Dragon Age Lexicon] - Scripting Resource

= Entries =

For information on how to enter, please see the [[Community_Contest_Entry_FAQ|Entry FAQs]]

For information on Judging, please see the [[Community_Contest_Judging|Judging]] page.

IMPORTANT - consent to share

By entering this competition you consent to share your work for other community members to benefit from.
Where appropriate, source files should be shared (dadbdata and any non-DA assets you have used including levels, props etc).
The work *MUST* be your own (obviously you may use DA assets).
Others may use and modify your work in their Dragon Age mods, though are encouraged to give credit.
As the entries are judged, local copies will be saved If your work is taken down.
If your work is taken down, you allow for it to be re-uploaded, crediting the work in your name. 

== Example Entry by YourNameHere ==

* '''[http://www.dragonagenexus.com/downloads/file.php?id=1559 Links here in this format]'''

Description here. Try to keep it short, but include as many relevant details as possible. Description here. Try to keep it short, but include as many relevant details as possible. Description here. Try to keep it short, but include as many relevant details as possible. Description here. Try to keep it short, but include as many relevant details as possible.

Description here. Try to keep it short, but include as many relevant details as possible. Description here. Try to keep it short, but include as many relevant details as possible. Description here. Try to keep it short, but include as many relevant details as possible. Description here. Try to keep it short, but include as many relevant details as possible.

[[File:terrainBlockExample.png|400px|example picture]]

=== Judges' Comments ===

Judges will leave comments both as contructive suggestions for the entrant and also as impartial guidance for any looking to make use of your work.

== Weighted RPS by Mengtzu ==

* '''[http://www.dragonagenexus.com/downloads/file.php?id=1850 Dragon Age Nexus project page]'''

Rock, Paper, Scissors as a multi-round gambling game, with weighted moves to introduce strategy and customisable AI. Multiple games with different settings may share an area, allowing a tournament/festival style implementation, as demonstrated in the sample module. By default the player earns prize tokens which may be traded in for items.

Modular functions and constants make the engine easy to extend or modify.

[[File:Rps guanyin.jpg|400px|Game in progress]]

=== Judges' Comments ===

== Nug Chase by Bloodsong ==

* '''[http://www.dragonagenexus.com/downloads/file.php?id=1859 Nug Chase on Dragon Age Nexus]'''

A simple action-oriented mini-game for players of any level. Granny Rockbottom's prize Racing Nug has escaped his pen, and you need to catch him. To do this, you need to click on the nug and get close enough to initate a conversation. If you are successful, you catch the pesky nug. If not, hilarity ensues. :X

Includes a custom Nug Wallows area/level, and a convoluted conversation tree with the NPC. Rewards are small gifts, some XP, and possibly a small amount of cash. Documentation for customizing also included.

[[File:NugChase1.jpg|400px|Nug Chase Promo]]

Please report any file/installation problems here:
* '''[http://social.bioware.com/project/3512/discussion/2597/20416/#post_20416 Nug Chase Project]'''

=== Judges' Comments ===

Judges will leave comments both as contructive suggestions for the entrant and also as impartial guidance for any looking to make use of your work.

Community Contest 4: Minigame Script

2010-10-30T18:45:47Z

BloodsongVengeance: /* Entries */

[[File:Community_Contest_back.jpg|link=Community_Contest_Main_Page]] [[File:CC_BSN_GetInvolved.jpg|link=http://social.bioware.com/group/2535/&v=discussions]]

== Brief ==

Create a minigame or puzzle using scripting. The contest discussion thread can be found [http://social.bioware.com/group/2535/discussion/10583/916864/#post_916864 here].

'''DEADLINE: Monday 1 November''' - your entry must be ready for judging before midday GMT+0. It is strongly recommended you submit well before this time (sunday!) in case you run into troubles. Modifications to your submission are welcomed - the newest version of your entry will be judged, although modifications made ''after'' the submission date will not be judged.

=== Requirements ===
All entries must:
* Reserve and use a [[Community_Contest_ID_Ranges|StringID range]]
* Be thoroughly tested in-game
* Be submitted in a single, playable area (the level will not be "marked")
* Include dadbdata export of all relevant resources
* Include a playable dazip of the mini-game - should be playable from the other campaigns menu
* Include a plain-text file detailing the mini-game implementation - the objective, customization options (if present) and solutions
* Use only DA assets (placeables, levels) ''unless the relevant files are included with the submission and author's permission has been given''
* Be submitted before Monday 1 November midday (GMT+0)

=== Guidelines ===
Strong entries will:
* be easily adaptable to vary the minigame in other modules
* be unique and interesting
* use elegant and tidy scripting
* include well-written, detailed comments
* be well-designed and be free of bugs and discourage user error
* be significant as a piece of scripting: doing something new or expanding beyond the fundamentals of scripting
* make appropriate use of secondary resources (triggers, placeables, dialogues, floaty text, VFX, sound, etc)

=== Allowable ===
While no "bonus points" will be given for the following, entries may:
* use custom levels provided that the level is shared with the submission (.lvl and exported files)

== Groups and Prizes ==

=== Groups ===
This contest has only one group.

* 1st place - 15 points, chooses first
* 2nd place - 10 points, chooses second
* 3rd place - 5 points, chooses third
* Best Newcomer - 3 points (unless 1st, 2nd or 3rd place)
* All other entries meeting requirements - 1 point

To receive an "entry point", your submission must meet the requirements of the contest, listed at the top of this page

=== Best Newcomer Award ===
Every judge may nominate one newcomer as their favourite newcomer entry. To qualify, the entrant must not have submitted to a community contest before. The winning newcomer will receive three points if they don't podium (in which case, theyll be getting more points anyway!).

=== Prizes ===

Please see [[Community_Contest_Prizes|Community Contest Prizes]]

== Helpful Links ==
* [[Scripting_overview|Scripting Overview]] - Builder Wiki
* [[Scripting_tutorial|Scripting Tutorial]] - Builder Wiki
* [http://dalexicon.net/index.php?title=Main_Page Dragon Age Lexicon] - Scripting Resource

= Entries =

For information on how to enter, please see the [[Community_Contest_Entry_FAQ|Entry FAQs]]

For information on Judging, please see the [[Community_Contest_Judging|Judging]] page.

IMPORTANT - consent to share

By entering this competition you consent to share your work for other community members to benefit from.
Where appropriate, source files should be shared (dadbdata and any non-DA assets you have used including levels, props etc).
The work *MUST* be your own (obviously you may use DA assets).
Others may use and modify your work in their Dragon Age mods, though are encouraged to give credit.
As the entries are judged, local copies will be saved If your work is taken down.
If your work is taken down, you allow for it to be re-uploaded, crediting the work in your name. 

== Example Entry by YourNameHere ==

* '''[http://www.dragonagenexus.com/downloads/file.php?id=1559 Links here in this format]'''

Description here. Try to keep it short, but include as many relevant details as possible. Description here. Try to keep it short, but include as many relevant details as possible. Description here. Try to keep it short, but include as many relevant details as possible. Description here. Try to keep it short, but include as many relevant details as possible.

Description here. Try to keep it short, but include as many relevant details as possible. Description here. Try to keep it short, but include as many relevant details as possible. Description here. Try to keep it short, but include as many relevant details as possible. Description here. Try to keep it short, but include as many relevant details as possible.

[[File:terrainBlockExample.png|400px|example picture]]

=== Judges' Comments ===

Judges will leave comments both as contructive suggestions for the entrant and also as impartial guidance for any looking to make use of your work.

== Weighted RPS by Mengtzu ==

* '''[http://www.dragonagenexus.com/downloads/file.php?id=1850 Dragon Age Nexus project page]'''

Rock, Paper, Scissors as a multi-round gambling game, with weighted moves to introduce strategy and customisable AI. Multiple games with different settings may share an area, allowing a tournament/festival style implementation, as demonstrated in the sample module. By default the player earns prize tokens which may be traded in for items.

Modular functions and constants make the engine easy to extend or modify.

[[File:Rps guanyin.jpg|400px|Game in progress]]

=== Judges' Comments ===

== Nug Chase by Bloodsong ==

* '''[http://www.dragonagenexus.com/downloads/file.php?id=1859 Nug Chase on Dragon Age Nexus]'''

A simple action-oriented mini-game for players of any level. Granny Rockbottom's prize Racing Nug has escaped his pen, and you need to catch him. To do this, you need to click on the nug and get close enough to initate a conversation. If you are successful, you catch the pesky nug. If not, hilarity ensues. :X

Includes a custom Nug Wallows area/level, and a convoluted conversation tree with the NPC. Rewards are small gifts, some XP, and possibly a small amount of cash. Documentation for customizing also included.

[[File:NugChase1.jpg|400px|Nug Chase Promo]]

Please report any file/installation problems here:
* '''[http://social.bioware.com/project/3512/discussion/2597/20416/#post_20416 Nug Chase Project]'''

=== Judges' Comments ===

Judges will leave comments both as contructive suggestions for the entrant and also as impartial guidance for any looking to make use of your work.

Community Contest 4: Minigame Script

2010-10-30T18:44:40Z

BloodsongVengeance: /* Entries */

[[File:Community_Contest_back.jpg|link=Community_Contest_Main_Page]] [[File:CC_BSN_GetInvolved.jpg|link=http://social.bioware.com/group/2535/&v=discussions]]

== Brief ==

Create a minigame or puzzle using scripting. The contest discussion thread can be found [http://social.bioware.com/group/2535/discussion/10583/916864/#post_916864 here].

'''DEADLINE: Monday 1 November''' - your entry must be ready for judging before midday GMT+0. It is strongly recommended you submit well before this time (sunday!) in case you run into troubles. Modifications to your submission are welcomed - the newest version of your entry will be judged, although modifications made ''after'' the submission date will not be judged.

=== Requirements ===
All entries must:
* Reserve and use a [[Community_Contest_ID_Ranges|StringID range]]
* Be thoroughly tested in-game
* Be submitted in a single, playable area (the level will not be "marked")
* Include dadbdata export of all relevant resources
* Include a playable dazip of the mini-game - should be playable from the other campaigns menu
* Include a plain-text file detailing the mini-game implementation - the objective, customization options (if present) and solutions
* Use only DA assets (placeables, levels) ''unless the relevant files are included with the submission and author's permission has been given''
* Be submitted before Monday 1 November midday (GMT+0)

=== Guidelines ===
Strong entries will:
* be easily adaptable to vary the minigame in other modules
* be unique and interesting
* use elegant and tidy scripting
* include well-written, detailed comments
* be well-designed and be free of bugs and discourage user error
* be significant as a piece of scripting: doing something new or expanding beyond the fundamentals of scripting
* make appropriate use of secondary resources (triggers, placeables, dialogues, floaty text, VFX, sound, etc)

=== Allowable ===
While no "bonus points" will be given for the following, entries may:
* use custom levels provided that the level is shared with the submission (.lvl and exported files)

== Groups and Prizes ==

=== Groups ===
This contest has only one group.

* 1st place - 15 points, chooses first
* 2nd place - 10 points, chooses second
* 3rd place - 5 points, chooses third
* Best Newcomer - 3 points (unless 1st, 2nd or 3rd place)
* All other entries meeting requirements - 1 point

To receive an "entry point", your submission must meet the requirements of the contest, listed at the top of this page

=== Best Newcomer Award ===
Every judge may nominate one newcomer as their favourite newcomer entry. To qualify, the entrant must not have submitted to a community contest before. The winning newcomer will receive three points if they don't podium (in which case, theyll be getting more points anyway!).

=== Prizes ===

Please see [[Community_Contest_Prizes|Community Contest Prizes]]

== Helpful Links ==
* [[Scripting_overview|Scripting Overview]] - Builder Wiki
* [[Scripting_tutorial|Scripting Tutorial]] - Builder Wiki
* [http://dalexicon.net/index.php?title=Main_Page Dragon Age Lexicon] - Scripting Resource

= Entries =

For information on how to enter, please see the [[Community_Contest_Entry_FAQ|Entry FAQs]]

For information on Judging, please see the [[Community_Contest_Judging|Judging]] page.

IMPORTANT - consent to share

By entering this competition you consent to share your work for other community members to benefit from.
Where appropriate, source files should be shared (dadbdata and any non-DA assets you have used including levels, props etc).
The work *MUST* be your own (obviously you may use DA assets).
Others may use and modify your work in their Dragon Age mods, though are encouraged to give credit.
As the entries are judged, local copies will be saved If your work is taken down.
If your work is taken down, you allow for it to be re-uploaded, crediting the work in your name. 

== Example Entry by YourNameHere ==

* '''[http://www.dragonagenexus.com/downloads/file.php?id=1559 Links here in this format]'''

Description here. Try to keep it short, but include as many relevant details as possible. Description here. Try to keep it short, but include as many relevant details as possible. Description here. Try to keep it short, but include as many relevant details as possible. Description here. Try to keep it short, but include as many relevant details as possible.

Description here. Try to keep it short, but include as many relevant details as possible. Description here. Try to keep it short, but include as many relevant details as possible. Description here. Try to keep it short, but include as many relevant details as possible. Description here. Try to keep it short, but include as many relevant details as possible.

[[File:terrainBlockExample.png|400px|example picture]]

=== Judges' Comments ===

Judges will leave comments both as contructive suggestions for the entrant and also as impartial guidance for any looking to make use of your work.

== Weighted RPS by Mengtzu ==

* '''[http://www.dragonagenexus.com/downloads/file.php?id=1850 Dragon Age Nexus project page]'''

Rock, Paper, Scissors as a multi-round gambling game, with weighted moves to introduce strategy and customisable AI. Multiple games with different settings may share an area, allowing a tournament/festival style implementation, as demonstrated in the sample module. By default the player earns prize tokens which may be traded in for items.

Modular functions and constants make the engine easy to extend or modify.

[[File:Rps guanyin.jpg|400px|Game in progress]]

=== Judges' Comments ===

== Nug Chase by Bloodsong ==

* '''[http://www.dragonagenexus.com/downloads/file.php?id=1859]'''

A simple action-oriented mini-game for players of any level. Granny Rockbottom's prize Racing Nug has escaped his pen, and you need to catch him. To do this, you need to click on the nug and get close enough to initate a conversation. If you are successful, you catch the pesky nug. If not, hilarity ensues. :X

Includes a custom Nug Wallows area/level, and a convoluted conversation tree with the NPC. Rewards are small gifts, some XP, and possibly a small amount of cash. Documentation for customizing also included.

[[File:NugChase1.jpg|400px|Nug Chase Promo]]

Please report any file/installation problems here:
* '''[http://social.bioware.com/project/3512/discussion/2597/20416/#post_20416]'''

=== Judges' Comments ===

Judges will leave comments both as contructive suggestions for the entrant and also as impartial guidance for any looking to make use of your work.

File:NugChase1.jpg

2010-10-30T18:34:00Z

BloodsongVengeance: Promo Pic for Nug Chase mini-game entry in Commmunity Contest #4

Promo Pic for Nug Chase mini-game entry in Commmunity Contest #4

Preparing a dialog for recording

2010-10-24T17:40:28Z

BloodsongVengeance: /* Creating the Dialog Script */ added more detailed instructions & pic for dummies like me

{{Infobox conversation}}
''(this article is based on the investigations of Kaldir II and KingEtzel)''

For specific information about voiceover, file conventions, integration see here: [[Voice-Over]]

== Introduction ==

When you successfully have created dialogs in your toolset, you may want to send it out to voiceactors for recording at a certain point.

You could do that by writing all dialogs in a textprocessor like MS Word and just send them those documents. However, you would have to copy and paste the whole tree of lines into the toolset one by one, in order to get even the text work ingame. On the other hand you could type your whole dialog stuff in the toolset, but then - lacking a native export function - you would have to copy and paste again to get it into a form, where voiceactors can read your dialog.

Below we describe a way of creating the dialog inside of the toolset and then, by using little SQL queries, export not only the lines but also their corresponding LineIDs so that the voiceactor can not only match the format convention, but also the naming convention for the files themselves. The only thing for you left to do is putting those recorded files into the right folder and everything should work. No need for you to rename thousands of files manually to put them into the module/game!

== Creating the Dialog Script ==

First of all, you need Microsoft SQL Server Management Studio Express to be installed: http://www.microsoft.com/downloads/details.aspx?familyid=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796&displaylang=en

Install and run it. The first time it starts, it should find your Dragon Age database (BWDATOOLSET). Just click OK.

Remember to start the tool with administrator privileges, if necessary. Otherwise you won't be granted permission to access the database.

[[File:ServerManagementTool.jpg]]

Click on "New query" at the upper Left. Enter the text below into the right pane.
Find the String ID from any line of your conversation inside the toolset, and substitute it where the #### is:

SELECT [StringID],[ModuleResRefVersionID]
FROM [bw_dragonage_content].[dbo].[t_StringText]
WHERE StringID = ####

Click the "! Execute" button. This will find the ID number of your dialogue, shown in the bottom pane under the query panel.

Copy the text below, select the entire text of your first query, and paste over it. (Or if you prefer, you can press the "New Query" button again.) Right click on the dialogue ID number in the result pane and copy/paste -- or just type it in where the #### is in this query:

Declare @ResID INT
Set @ResID = #####
SELECT A1.StringID, A2.SPEAKER, A1.Text
FROM bw_dragonage_content.dbo.t_StringText A1, bw_dragonage_content.dbo.t_ConversationLine A2
WHERE A1.StringID = A2.TextStringID AND A1.ModuleResRefVersionID = @ResID AND A2.ModuleResRefVersionID = @ResID

Press the "! Execute" button again. This will give you a list consisting of the LineIDs in the column 1, the speaker tag (blank is the OWNER) in column 2, and the spoken words in column 3. You can now mark everything and save it into CSV and reopen it with Excel. Or you can select all the lines up to the PLAYER lines and paste to your editing program of choice, etc.

Now you can send the script to your voiceactors and you have minimized unneccessary work!

[[Category:Conversations]]
[[Category:Sounds]]

File:ServerManagementTool.jpg

2010-10-24T17:29:02Z

BloodsongVengeance: MS Server Management Tool interface for extracting Toolset conversation lines.

MS Server Management Tool interface for extracting Toolset conversation lines.

Talk:VFX Tutorial

2010-10-03T12:18:45Z

BloodsongVengeance:

I would suggest breaking this page down into several smaller pages. Starting with an introduction/table of contents/downloads page; then at least 1 page per tutorial (if not more); and possibly a summary or conclusion. In other words:

* VFX Tutorial
** Introduction
** List of parts
** Donwloads
* VFX Tutorial (Part 1)
* VFX Tutorial (Part 2)
* VFX Tutorial (Part 3)
* VFX Tutorial (Part 4)
* VFX Tutorial (Conclusion)

If we can get the approach right with this then we can use it as a model for future tutorials. It might we worth looking at how Sun do their Java "trails".

[[User:Sunjammer|Sunjammer]] 22:59, 7 September 2009 (UTC)

Can someone add on to the end of the VFX tutorials, of how to actually USE the suckers once they are created? ie: how to put one in a level. how to put one in an area. how to put one on a creature/object. how to spawn one via script.
[[User:BloodsongVengeance|BloodsongVengeance]] 12:18, 3 October 2010 (UTC)

Community Contest 3 mini: Head Morph

2010-10-01T17:35:55Z

BloodsongVengeance: Bloodsong's Entry

[[File:Community_Contest_back.jpg|link=Community_Contest_Main_Page]] [[File:CC_BSN_GetInvolved.jpg|link=http://social.bioware.com/group/2535/&v=discussions]]

== Brief ==

Create a head morph for a charater of your own design. The morph must be made in the Toolset and contain MRH and MOR files. This contest is a '''Raffle''' - all entries have an even chance of winning the prizes, and '''will not be judged'''. The contest discussion thread can be found [http://social.bioware.com/group/2535/discussion/10611/ here].

This is a raffled mini contest coinciding with the [[Community_Contest_3:_Character_Contest|Character Contest]], which also includes creating conversation for the character - we'd love if you entered both!

'''DEADLINE: Monday 18 October''' - your entry must be ready for judging before midday GMT+0. It is strongly recommended you submit well before this time in case you run into troubles. Modifications to your submission are welcomed - the newest version of your entry will be judged, although modifications made after the submission date will not be judged.

=== Requirements ===
All entries must:
* Include MRH source material as well as exported MOR file and post on the [http://social.bioware.com/project/3410/ BSN Project] (do not make your own)
* Post a single, clear screenshot on the contest page
* Use only
** DA assets (hairs, textures)
** (optional) hairs from [http://www.dragonagenexus.com/downloads/file.php?id=392 More Hairstyles] (the agreed mod)
** (optional) hairs/textures which are '''your own work''' and are '''included with your submission'''
* Any further modifications must be '''your own work''' (your own textures, for example) and '''must be included''' with the files.
* Be submitted before Monday 18 October midday (GMT+0)

=== Allowable ===
While "bonus points" '''will not''' be given for the following, entries may:
* Include custom textures/hairs (please only '''your own''' work though)
* Multiple entries are always allowed, however your name will only be entered into the raffle ONCE (more entries will NOT increase your chance of winning).

=== Disallowable ===
* For this contest, please '''do not use other peoples mods''' except [http://www.dragonagenexus.com/downloads/file.php?id=392 More Hairstyles] and anything which is '''your own''' work and is included.

== Groups and Prizes ==

=== Groups ===
This contest has only one group. The winner will be selected by '''Raffle''', and '''not by judging'''.

* 1st place - 5 points, chooses first
* 2nd place - 3 points, chooses second
* 3rd place - 2 points, chooses third
* All other entries meeting requirements - 1 point

To receive an "entry point", your submission must meet the requirements of the contest, listed at the top of this page

=== Prizes ===

Please see [[Community_Contest_Prizes|Community Contest Prizes]]

== Helpful Links ==
* [[Morph|Head Morph]] - Builder Wiki
* [http://www.youtube.com/watch?v=qR8AkAfNbvk Head Morph video tutorial] - mikemike37
* [http://social.bioware.com/forum/1/topic/72/index/569359#604626 Custom face tattoo tutorial] - DarthParametric
* [http://social.bioware.com/forum/1/topic/72/index/2452603 Custom scalp tattoo tutorial] - DarthParametric

= Entries =

This contest is a little different entry procedure than others.

=== Submitting an entry ===
* Join the [http://social.bioware.com/group/2535 Community Contest Group]
* Add your MRH and MOR file to a .7z or .zip file
* Name the file "Character Name - Entrant Name.zip"
* upload the file to the [http://social.bioware.com/project/3410/ Mini Contest project]. Ensure it is "Viewable by everyone"
* upload a screenshot and make an entry on this Contest Page (below)

For general contest entry FAQs please see the [[Community_Contest_Entry_FAQ|Entry FAQs]]. Note that some may not apply to this mini contest.

For information on Judging, please see the [[Community_Contest_Judging|Judging]] page.

IMPORTANT - consent to share

By entering this competition you consent to share your work for other community members to benefit from.
Where appropriate, source files should be shared (include the MRH head morph).
The work *MUST* be your own (obviously you may use DA assets).
Do not use custom hair/textures/voicework etc unless you have explicit consent from the author to share. You must include them with your submission.
Others may use and modify your work in their Dragon Age mods, though are encouraged to give credit.
As the entries are judged, local copies will be saved If your work is taken down.
If your work is taken down, you allow for it to be re-uploaded, crediting the work in your name. 

== Example Entry by YourNameHere ==

Summary of your character here. Try to keep it less than 50 words.

[[File:Hf_har_blda_0_front.jpg|example picture]]

== Granny Rockbottom by Bloodsong Vengeance ==

Granny Rockbottom: Racing Nug Breeder of Orzammar. A cantankerous old coot who's been breeding and raising nugs for decades.

[[File:Grannyrockbottom.jpg|Granny Rockbottom]]

File:Grannyrockbottom.jpg

2010-10-01T17:34:13Z

BloodsongVengeance: CC3 entry sample pic: Granny Rockbottom by Bloodsong Vengeance

CC3 entry sample pic: Granny Rockbottom by Bloodsong Vengeance

VFX Tutorial

2010-09-17T17:04:20Z

BloodsongVengeance: /* VFX Tutorial Part 2 */

{{Infobox vfx}}

PDF Version Part 1 [[File:VFX_Tut_p1.pdf]]

PDF Version Part 2 [[File:VFX_Tut_p2.pdf]]

PDF Version Part 3 [[File:VFX_Tut_p3.pdf]]

----

== VFX Tutorial Part 1 ==

This tutorial is to get you started in creating your own visual effects to be used in the DA toolset. Tutorial #1 will cover the basics of creating, editing, and implementing the visual effect.

=== Creating a new visual effect ===

To create a new VFX, right click on the palette window and select “NEW > VFX”

[[File:new VFX.jpg|250px]]

The VFX Editor will open up showing a square grid and a “Select VFX” window in the middle. For this tutorial we will be doing a Placeable effect, so select “Placeable” and click “OK”.

On the top left, you should see a little globe called “VFXRoot” and in the Object Inspector you should see the properties of VFXRoot.
At this point, save your work by selecting “File > Save As” or clicking the Save Icon in the upper left. You will be prompted for a file name. I like to keep all of my VFX files in one place so in My Documents/Bioware/Dragon Age folder I created a VFX folder to save my files.

For this tutorial we will be creating a bonfire type of effect and to stay with Dragon Age [[Naming conventions]], we will use a 3 letter prefix, underscore, and then the file name. Name the file “fxp_bonfire_jp”
The “fxp” is for “Visual Effect Placeable” (all VFX files start with fx*) “bonfire” tells me what the effect is, and the “jp” on the end lets me know that it is my effect and not someone else’s, you can add whatever suffix you want. Click “Save” when done.

You can close the toolset at any time and return to this tutorial. You can open your effect again later by selecting “File > Open” and navigate to and select the file you just saved.

=== VFX root properties ===

[[File:t1_root_obj_inspector.jpg|250px]]

'''VFXRoot Properties:'''
I’ll just cover the ones that we will be using.

'''Name:''' This is the resource name and is what will be used when we Post to Local. Change it to match the file name.

'''Impact Length:''' Time in seconds for the stating phase of the effect. Example, a Runner starting off from the start line reaching max speed.

'''Duration Length:''' Time in seconds for the duration of the effect. Example, the time it takes the runner to reach the finish line after reaching max speed.

'''Cessation Length:''' Time in seconds for the ending of the effect. Example, the runner slowing down after crossing the finish line.

We are making a bonfire effect, so we want the fire to start off small, grow in size, then burn itself out. So set the Impact Length to 3 seconds, this will start the fire and grown to its max size. Set the Duration Length to 3 seconds. This will allow us plenty of time to vary the coloration of the flames. Set the Cessation time to 3 seconds as well, as the fire burns out.

You may be thinking that 9 seconds is a very short fire. When the effect is set in a script, the duration time is set within the function ApplyEffect*. This duration time causes the duration time of the animation to loop over and over. So for example, if this bon fire effect is applied to an object for 6 min, the duration part of the effect will loop 120 times, 3 second duration * 120 loops = 360 seconds = 6 minutes. Then the Cessation time plays and the effect is done.

After setting these times, you should now see a time line something like this, More on this in part 2.

[[File:T1_time_line.jpg|640px]]

=== Adding an emitter ===

Next we need an emitter. Right click on the window and select “Insert > Insert Emitter”. You should get a pulsating white capsule in the center of the grid and a “NewEmitter” object added to the list on the left.

[[File:T1_emitter.jpg|640px]]

Select the NewEmitter object and you will see the properties in the Object inspector window.

[[File:T1_op_properties.jpg|250px]]

'''Properties Window:'''

'''Name:''' Change the name of the emitter to “Base” this will be the main base of the fire. Naming the emitter will help sort them out when building an effect with several emitters.

'''Material Library:''' This is the library that we will be selecting our particle material from. The DA Effect Libraries start with the prefix fx_*Click on the Material Library box to open the resource window. Select the fx_firelibrary and click OK.

'''Material Object:''' This is the martial that we will use from the above selected Library. For this select “FireFlipbook”.
Before we continue, save your work and let’s talk about Flipbooks.

A flipbook is a particle that consists of columns and rows of varying images. The animation is created by the effect rapidly flipping through each image, much like a cartoon animation. At this point you should see 4 columns of flickering flames. Note that not all particles are in flipbook form, some are a static image. A simple way to see if the particle is a flipbook, and to see how many columns and rows there are is to set the Birth Rate to 1. Click on the “Emission” tab in the Object Properties and change the top parameter “Birth Rate” to 1. You should now see an image that consists of 4 rows and 4 columns of small flame images. This is a single particle, 4x4 flipbook. Set the Birth Rate back to 10, and return to the “Properties” tab of the Object Inspector, more on Birth Rate later.

[[File:T1_flip.jpg]]

'''Flipbook Type:''' Select “ContactSheet”.

'''Flipbook Random Start Frame:''' This selects a random frame within the flipbook to start with on each emission. Set this to TRUE. This will help give us diversity and make the flame look more “real”.

'''Flipbook Rows:''' This is how many Rows there are in the flipbook, set this number to 4.

'''Flipbook Columns:''' This is the number of Columns in the flipbook, set this to 4 also.

'''Flipbook Frames per Second:''' The particle image has 4 rows and 4 colunms, there are 16 total images to flip through. This value should be a factor of Rows and Columns, so 4 x 4 = 16. Set this value to at least 16 flips per second.

You should now see a single column of what nearly looks like fire.
Right now the flames flicker a bit too slow for me, so set the Flipbook Frames per Second to 32. This makes the flames flicker twice as fast because it is now flipping through all 16 images twice per second instead of once.
Save your work.

[[File:T1_fire.jpg]]

'''Age Map:'''

[[File:T1_agemap.jpg]]

In the Object Inspector click the “Age Map” Tab.

Here we can manipulate the color and the scale of the effect.

Color values are in percentage of 0 to 100% on a scale of 0 to 1, so 50% Blue would be 0.5.

Most normal fires aren’t white, so set Color B (blue) to 0. Your flame should now be yellow. Set Color G (green) to 0.4. We now have a orangey-red color.

Color A (alph) is the flames color intensity setting this to 0.5, the fire is half as intense. Set it where you like.

The scale X and Y values can be any number from 0 to infinity. Setting the scale to 1 is the particles normal size. Because the particle image is a 2d image, there is no Z scale. Changing Scale X will affect the X (width) direction of the flame and Scale Y will affect the Y (Height) direction of the particle. For now we will leave them alone.

The corresponding multipliers simply multiply the values in the general section. For example, if you set Color G back to 1, then set Green Color Multiplier to 0.4 you will have the same result. 1 * 0.4 = 0.4

There is a notable difference between the 2 however, the General settings affect the particles over the lifetime of each particle while the Multipliers affect all the particles over the length of the animation. This will be explored further in Part 2. Go ahead and play with the color settings until you have it the way you want it, and then save your work.

'''Emissions'''

[[File:T1_emissions.jpg]]

Now click on the “Emission” tab these settings control the particle emissions.

'''Birth Rate:''' This is how many particle emit per second. The default is 10, which works out for the fire pretty good. However the flicker is pretty static. So we will change that in a minute.

'''Birth Rate +/-:''' This setting will cause the particle Birth Rate to randomly vary by a positive number or a negative number. If we set this value to 1, the Birth Rate then will vary between 9 and 11 particles per second. Since a 10 Birth Rate seems to be a good number for the most particles per second, set the +/- value to 2, and change the Birth Rate to 8. This will make the max 10 and the min 6 particles per second.

'''Initial Speed:''' This is how fast the particles travel when emitted from the emitter. Changing this value appears to change how long the particles last. However this is not the case, they simple move further before the particle life has expired.

'''Initial Speed +/-:''' This setting works the same as the Birth Rate +/- setting but instead affects the Initial Speed. Set this value to 0.5 which will now give the particles a varying speed between 0.5 and 1.5.

'''Life Expectancy (s):''' This is how long each particle last, in seconds, before vanishing.

'''Life Expectancy +/-''': Again is a random variance to the value set in Life Expectancy. Set this value to 0.5, making the particle last longer and shorter as the fire burns.

'''Scale Range:''' This adds a random variance to the size of the particle much like the other +/- settings. Set this to 0. 6. You should now see the flame vary in size as it emits from the base emitter.

Play with these settings a bit to get familiar with them. In the end you should have a raging fire animation. When you are happy, save your work.

[[File:T1_fire_1.jpg]]

'''Getting the effect in game:''' Right click on the Root and select “Post to Local”. You'll find the new VFX under the model palette. It can be placed directly in the level editor or the cutscene editor but not the area editor. You can also add the effect dynamically to an area using a script.

'''Notes:''' Because an effect is Art work, at present will not be included with a Builder to Builder Create and must be sent separately. Scripting examples to come later once there is a client to test for accuracy.

[[File:T1_ptl.jpg]]

So now you have a raging fire. In part 2 of this tutorial, we will make this fire dance and sing. Part 2 will introduce using the time line settings to very coloration, scale, size and other more advanced settings as well as explore some of the settings introduce here a bit deeper. Keep the bonfire effect you created with this tutorial, we will need it in the second part. The bonfire effect can also be downloaded from the social site.

== VFX Tutorial Part 2 ==

In tutorial #1 we created a good bonfire as a base and up until now we only changed the values directly in the properties on the effect. As we can see this works well for simple effects. Changing the values in this manner alters the effect over its entire life time.
We have seen how to change the color and scale of the effect by changing the values in the properties age map. This is great for a basic flame but we want to add more life to it by making the flame vary in color and size over the length of the effect. To start, set all the Values back to default as shown in the 2 pictures below.
Note: This tutorial assumes you have read Tutorial #1 or are familiar with the basics of the VFX editor.

[[File:T2_agemap_01.jpg]][[File:T2_emission_01.jpg]]

Setting any of these values directly will affect the visual over the entire length of the effect. Instead we want to vary these values so the flame will change from reds, yellows, and orange. We also want to change its size during the impact, duration, and cessation phases of the effect. To do this, we will use the time line to set colors and scale so they change over the course of the effect.

Before we continue, we need to make a small change. Select the Root of the effect and in the Object Inspector, change the Impact time to 5 sec and the Cessation time to 8 sec. The 5 sec impact will allow us enough time to see the changes in the flame as it grows and the longer cessation time is for the smoke we will be adding later on.

[[File:T2_root_01.png]]

Select the “Base” object, at the top right corner there is a drop down window, select “Color” from the list. Note, when using the time lines, make sure you have the correct emitter object selected. In this case it is the Base emitter. You should then see a time line like the one below.

[[File:T2_color_01.jpg|680px]]

Notice at the top of the time line is reads “Particle Lifetime”. This means that the changes we make here will affect each partial over the lifetime of each particle. The lifetime of the particle is directly related to the “Lifetime” value setting in the Emissions Tab, which currently is set to 1 sec.

=== Parts of the Time line ===

[[File:T2_timeparts_01.jpg|680px]]

'''Control Point:''' The round dots allow you move the value up, down, left, or right within the time line.

'''Value Rang:''' The left side of the time line shows the value range. At this current control point, the value is 1, which is the current value for all 4 colors in the Age map.

'''Current Value:''' The dotted line shows the current value any place on the time line. Currently it is set to 1 over the entire length of the particle lifetime. When a control point is added, the line between the 2 control points will become solid.

'''Visible:''' This box shows which time lines are visible, the dotted or solid line. You can select or unselect these time lines. Currently all 4 are selected and visible. All 4 also are set at the same value so you only see one control point as all 4 are stacked from top to bottom, Color A being the one on top.

Click inside the time line and you will get a vertical bar. Drag the bar to the far right until the end of the timeline is reached. This bar represents that point in time and I will refer to this bar as the Point bar. Clicking anywhere on the time line will move the point bar to that point in time.

[[File:T1_v_bar.jpg]]

Right click on the time line and select “Add Control Point”. This adds a node at the point in which the point bar and the time line intersects. Also note that the Colors in the age map turn red, this indicates that the values are now controlled by the time line and can vary in value depending on the point in time. Also note that this adds a Control Point to each time line that is visible, so all 4 colors get an added node.
Before we continue, save your work. Next turn the Loop Animation Off by clicking on it at the top right so it is no longer highlighted.

[[File:T2_timeparts_02.jpg]]

There are 2 ways that we can set the values on the time line, directly in the value box of the Age Map, or by dragging the control points on the time line. To see how it affects the animation, first make sure the point bar is to the far right at 100. Change the value Color B to 0 directly in the Age Map properties, just as we did in Tutorial 1. You should now see a blue line starting at 1 and dropping to 0 at the end of the time line. By changing the value on the Age Map, you affect the control point that intersects with the Point Bar. The Flame should now be white at the bottom and Yellow at the top.

[[File:T2_cb.jpg|680px]]

To see what happens to each particle, go to the Emission tab and change the birth rate to 1. You will see the particle start from the emitter as white, and then gradually change to yellow. Set the Birth rate back to 10 and return to the Age Map.

Now move the point bar to the far left on 0. Notice that the value in Color B on the Age Map is again 1. Change this to 0 also and the left most control point will drop to 0 and you time line should now look like this.

[[File:T2_cb_2.jpg|680px]]

The small box in the lower right corner in the above image indicates which time lines are visible. Right now all 4 colors are visible on the time line. Next we will affect the green color by dragging the control points instead of changing the value directly in the Age Map. However the green time line in underneath the Alpha time line. So to make it visible, click the check mark to unselect the Alpha Color. The Alpha line goes away and we can now see the Green time line. Also uncheck the Red and Blue color time lines so only the Green is visible.

Next Click and hold on the far left (0) control point of the Green time line and drag it down a bit, about half way between 1 and 0, you should see the flame change colors as you drag it down. Grab the right most control point and drag it down to 0. You should now have a flame that is brighter red at the bottom and darker at the top.

[[File:T2_cg.jpg|680px]]

Now we are going to add 2 more control points to the Green time line. Move the Point Bar to 5 on the Particle Lifetime line, right click and select “Add Control Point”. Now move the Point Bar to 10 on the timeline and add a second control point. Grab the first control point we just added, the one at 5, and drag it up to about 0.7. This will create a bright flicker at the base of the fire.

[[File:T2_cg_2.jpg|680px]]

Now we just need to fade out the top of the flame a bit so the bottom is more intense than the top. Uncheck the green timeline and check the Color A (Alpha). Color A is a transparency color and can be use to alter the intensity of the particle. Grab the Right most control point and drag it down to about 40% (0.4). You will see that the top is less visible than the bottom of the flame. Save your work.

=== Changing its size ===

Right now the flame is a single column that is the same size at the top as it is at the base, this is not very realistic so we will remedy that by changing the scale of the particle.

In the drop down menu at the top right, select “Scale”. Again you will see a time line labeled “Particle Lifetime” a Control point, and a box showing the “Scale Y” and “Scale X” time lines. As we did before, move the Point Bar to the far right at 100 and right click and select “Add Control Point”. Now uncheck the Scale X time line so only the Scale Y line is visible. Move the Left control point to about 1.5 and the right control point to about 1.75. Check the Scale X timeline to make it visible and move the left control point to about 1.5 and the right control point to 0.5. This will widen the base and stretch the top to a point much like a real fire.

[[File:T2_scale.jpg|680px]]

Now the fun begins. Up until now we have been changing values over the lifetime of the particles. Now we will start changing values over the Impact, Duration, and Cessation time of the effect, but first save your work.

Select the “Emissions” Tab in the Object Properties. In the drop down menu, select “Birth Rate”. This time you will see a bit different looking time line. At the top you will see 3 sections, Impact which starts at 0 and ends at 5000, Duration starting at 5001 and ending at 8000, and the Cessation which starts at 8001 and ends at 1600. These times correlate to the 5 sec Impact, 3 second Duration, and the 8 second Cessation times specified in the VFX root.

'''TIP:''' You can Zoom Extents by double clicking inside the time graph, or zoom in/out by using the mouse scroll wheel.

When an effect is used in game, the Impact time plays, then the Duration time is looped for the length of the applied effect, then the Cessation time plays. For example, if the fire effect is applied to a wood pile for 3 min, the Impact time plays then the 2 second duration is looped for 3 min then the cessation time plays. With this in mind, we want the fire to build up to the a full blown fire, then taper off and go out.

In the Birth Rate time line, add 3 more control points, one at the Duration start, one at the duration end, and one at about 12000. Starting from the left move the left most control point to 0, move the second Control Point to 10, the third Control Point to 10 and the fourth to 0.

[[File:T2_br_2.jpg|680px]]

Notice that the flame stops burning like it was before. This is because now the total effect length is a factor. Slide the Point Bar back and forth on the time line, you can see what happens to the fire at any point in time. Now to view the animation of the effect, you must click the Play button in the upper right corner. The Point Bar will scroll across the time line and the results can be viewed in the effect window.

The fire should now start out slow and build up then taper off and go out at around 12 seconds. You can click on the Loop Animation if you want and the effect will continue to loop until paused by the Pause Animation button or by clicking in the time line.

Now select Life in the drop down menu. Right now each point in time the flame last 1 second. We want to change this so the flame when first starting out or ending doesn’t last that long. Keep the tip I gave above in mind, and make the Life time line look like the one in the picture. The Control Point times from left to right are 0, 1, 1.4, 1, 0 then save your work.

[[File:T2_life.jpg|680px]]

'''Let’s Dance:'''

Right now we have our fire looking pretty good, but there is one element still missing, the wavering and dancing of a real fire. On the Emission table item 12 and 13 are “Spawn Spread X (Deg)” and “Spawn Spread Y (Deg)”. These settings affect the spread of the particles in the X and Y directions, that is the particles can emit in varying directions in degrees from the emitter. Set both of these to 20 degrees.

Now our fire dances. Note that these settings could be set using the time line “Spawn Spread” as well, feel free to play with that if you wish.

We can get a better Idea of what our effect will look like in game by adding a reference model. Right click on the Root and select “Insert > Insert Reference Model”. In the Resource window Name field we can filter the list to make it easier to find what we are looking for, so enter *fire* and press enter. Now your resource list will only show those items with the word fire in it.

[[File:T2_resource.jpg]]

Choose the resource “plc_firepit_01_1”. Turn Bounding box Off by clicking it at the top to un-highlight it. This gets rid of the yellow square around the objects. Turn the Collision Plane on by clicking on it to highlight it. This will simulate a stone floor at the walk mesh level.

Now play you animation. You can also select the Base object and click anywhere in the time line, for example if you place the Point Bar anyplace in the Duration time you can watch your fire burn at it’s full potential.

'''Challenge:''' Replace the plc_firepit_01_1 with the plc_bonfire01_1 reference model. Scale your fire up, and increase it’s life time to engulf the wood pile in flames.
Don’t forget to save your work.

[[File:T2_fin.jpg|680px]]

This concludes Part 2 of the tutorial. In Part 3 we will be adding smoke and lighting to the flame and make the flickering flame reflect off of surrounding objects.

== VFX Tutorial Part 3 ==

This tutorial assumes you have read Tutorial #1 and #2 and are now familiar with using the time lines to adjust values over time. You can down load the final effect from Tutorial #2 from the social site if you need it to continue with Tutorial #3.

'''Where there’s smoke:'''

Our fire is missing 2 more elements to be complete, smoke and lighting.

First we will add the smoke.
Right click on the effect Root and select “Insert > Insert Emitter”. You will see a second emitter appear on top of the first one.
Select the new emitter and in the Object Inspector properties, change its name to Smoke. For Material Library, select fx_smoke_vol. For Material Object select fx_smoke_vol_blend.

In the First tutorial we talked about the Flipbook Type: Contact Sheet. For this effect we will be using the Flipbook Type: Volume. This works similar to the Contact Sheet type except that the Flipbook Rows is the number of layers, usually 2 or 4. The Flipbook Columns should always be 1 and the Frame per second is a factor of the 2, i.e. Rows x Columns. Set these to 2, 1, and 2 respectively.

In the Age map, set the colors R, G, B to 0.5 and Color A to 0.7. Our smoke should now look more like smoke, but we have a ways to go yet.
Smoke usually bellows upwards and spreads out as it rises. We can simulate this with a combination of the Scale and Scale Multiplier time lines.
Select the smoke emitter and the Scale time line from the top right drop down menu. We want the smoke to grow in size both in the X and Y directions, but more so in the X direction.

[[File:T3_scale.jpg|thumb|680px|center]]

Both X and Y should start at 1 and X should end around 5.5 and Y should end around 3.5 over the life of the particle. This will give us a funnel shape.

Now select the Scale Multiplier time line. We can use this line to make the smoke grow in proportion to the flame during it’s impact, duration, and cessation times.

Start out at a 0 multiplier and raise it to 1 at the start and during the duration time, then taper it back down to 0 during the Cessation time. Notice that at around 12000, the flame is gone and we are only left with smoke for the last 4 seconds of the effect.

[[File:T3_scale_mult.jpg|thumb|680px|center]]

Now we need to change a few of the Emissions. Set the Birth rate to 3, Life Expectancy to 2.5 and Life Expectancy +/- to 0.5. If you recall from previous tutorials the +/- will give us a variance on how long the particle last. As we did with the flame, we want the smoke to also waver from left to right and forward and back, set the Spawn Spread X (Deg) and Spawn Spread Y (Deg) to 10.

'''Changing Position:'''

By now you may have noticed that when you play the effect in full, the smoke stays at ground level. Smoke naturally rises from the top of the flame, not from the base. This is OK during the Impact and cessation phase as the fire is small and near the ground level. However, we need the smoke to rise to the top of the flame during the Duration phase. To do this we will use the position time line to make the smoke rise, and lower as the flame grows.

With the smoke emitter selected, select the Position Time Line. Unselect the X and Y position time lines so only the Z line is visible. Add a control point at the start and end of the Duration time. Also add a control point at around 12000 and one at the end of the effect time.

Raise the control points at the start and end of the duration to about 1.2, so it looks like the pic below.

[[File:T3_position.jpg|thumb|680px|center]]

Now when you play the effect, the smoke should rise and lower with the flame. Feel free to play with any of these settings to get the look you like best.

'''Fade it out:'''

If you zoom out and look at the Animation as a whole you will notice that the smoke just suddenly disappears at the top, looks a bit odd. Instead we will fade it out so this isn’t seen.

Select the Smoke emitter and then select the Color time line. Uncheck all the colors except the Alpha color. Add 2 or 3 control points towards the end of the time line and tapper the alpha down to 0 at the end of the particle life time. This makes the smoke fade out naturally. Save your work.

[[File:T3_colora.jpg|thumb|680px|center]]

'''Light My Fire:'''

Before we continue, let’s put our fire into a game scene. Select the VFX Root and in the Object Inspector, under “Layout Settings”. You can select a area and see what your effect will look like in game. In Layout, select the area resource. Your effect should be near the upper right corner.

[[File:T3_arena.jpg|thumb|680px|center]]

Play the VFX a few times, notice there is no light given off by the fire.

Right click the VFX root and select Insert > Insert Light. A new light object will be inserted on top of the fire emitter. It’s right where we need it to be, by default.

[[File:T3_light_2.jpg]]

Light Properties:
Affects Characters: Set this to true. This setting specifies if the light should reflect off nearby creatures and characters.
Affects Level: same as above but it applies to the surrounding terrain.
Name: Name your light, I called mine “Flicker”

First we need to give the light some color, a good yellowish – red should do. Set Color G to 0.5 and Color B 0. To make the fire flicker, we will change the intensity of the color to coincide with the flame.

Select the Flame object and then select the “Color Intensity” time line from the drop down list. Add several control points and adjust the intensity up and down so it climaxes during the duration, similar to the image shown.

[[File:T3_intens.jpg|thumb|680px|center]]

Be sure to drop the intensity to 0 at around 12000 as this is where the flame goes out.

TIP: You can manually slide the time bar left and right on the time line to get a visual check of the intensity control points.

Now we have a nice bon fire complete with smoke and lighting.

[[File:T3_flame.jpg|thumb|680px|center]]

'''Challenge:''' Using the Material Library “fx_distortionmatlib” add a third emitter and give your fire distortion.

This concludes the basic VFX Tutorials, Thanks for reading.
Author: Jassper

[[Category:Tutorials]]
[[Category:VFX]]

Talk:2DA

2009-11-19T00:07:03Z

BloodsongVengeance:

Some more information on the usage of these files would be great.

'''Questions:'''

-- What todo with these files?

-- Where to put them?

-- Do you need to copy them or modify the original? (why is there only one set of these?, should not every module have it's own set?)

-- Where to find them? (tools\source)

-- How do they fit in the whole toolset thing?

-- Meaning and usage in your own mod.

-- Best practices?

For all the people coming from the NWN Toolsets, that should be straight forward.

But for newcomers, this can be a bit confusing.

Thanks
Josh

also -- where the heck ARE these files?