Dragon Age Toolset Wiki - User contributions [en]

Cutscene tutorial

2009-11-23T21:23:50Z

Beerfish:

[[Cutscene]]s can be stand-alone cinematic sequences that are triggered by scripts in the course of the game, or they can be inserted into [[conversation]]s in place of the simplified cinematics that conversations can automatically generate.

Our example situation in this tutorial will serve as the beginning of a conversation between the player and two NPCs. The player has just arrived at the campsite where these two NPCs are staying. He walks up to the fire. One of the NPCs is happy to see the player and greets him, but the other is distrustful. The two share a brief exchange to establish this before the interactive part of the conversation begins.

== Creating a new cutscene ==

To create a brand new blank cutscene resource, create a new resource in the usual way:

[[Image:New resource.png]]

The result is opened in the cutscene editor.

[[Image:Cutscene new.png|thumb|center|600px]]

There are two basic sections to the cutscene editor; the viewports (top) and the timeline (bottom).

=== Viewports ===

{{sidebox|
* Viewports can be attached to various cameras to preview what they can see
* Add a "Safe Frame" to camera viewports to ensure the correct aspect ratio
* Set a viewport to "User" to see where cameras are positioned from another perspective
}}

The camera viewports in the cutscene editor work similarly to the viewports in the stage editor. You can set the number and layout of viewports under the "View" menu:

[[Image:Cutscene tutorial viewport layout.png]]

And for each individual viewport you can select which camera it's showing and set other display options by right-clicking on the title bar of the viewport:

[[Image:Cutscene tutorial viewport properties.png]]

When you set a viewport to show the view through one of the cutscene's cameras, it's a good idea to turn on that viewport's "Safe Frame" option as well. This will put a border on the viewport showing what will be visible when the cutscene plays.

Note that when you play the cutscene in the cutscene editor, only the currently selected viewport (the one with the blue title bar) will show the cutscene "live" - the others won't update the view displayed in them until they're selected. To preview the cutscene as the player would see it, then, you should set one of the viewports to "Active Camera" and ensure that this viewport is selected when you play the cutscene in the editor. If the "Active Camera" viewport turns gray, try setting the cutscene property "Enable Level Effects" to false.

=== Timeline ===

{{sidebox|
* There is always exactly one MASTER object in a cutscene.
* Each active object is listed on the timeline, with multiple "tracks" for each.
* All objects have position tracks (divided into X, Y and Z tracks). Some objects have additional built-in tracks.
* Other actions and effects can be added to generic tracks. Objects can have as many generic tracks as you want.
}}

Below the viewport is the timeline. Along the top of the timeline is a time scale; it can be set either to show frames (at 30 frames per second) or milliseconds by changing the "Time Scale" property if the cutscene in the object inspector. A marker indicates what point in the timeline the viewports are currently showing.

Below are a set of rows containing the various actors, cameras, and other objects active in the cutscene. This is where most of the editing is going to take place. Each object will have a number of "tracks", which will contain commands that are sent to the actors at particular times in the course of the cutscene.

[[Image:Cutscene tutorial timeline.png]]

The first object in the track list is the "MASTER" object. This is a special object that every cutscene has exactly one of. The MASTER object is the cutscene equivalent to the root node of a conversation tree, a repository for global settings and effects. For example the MASTER object contains the track that determines which camera is active at any given time. The MASTER object cannot be deleted. By default, a MASTER object appears in the cutscene editor as a small greenish sphere; you can change the MASTER object's appearance in the cutscene option settings.

A new cutscene also has a camera, called Camera 1. This camera can be deleted or renamed if you like; we can add new cameras as needed later on.

Every object has "Position" and "Orientation" tracks that control their locations in space. Cameras also have a FOV (field of view) track.

Objects can have other "generic" tracks added by the editor as needed. These generic tracks contain all the other commands and directions we can give.

== The setting of the cutscene ==

{{sidebox|
* The MASTER object should be moved somewhere near the center of your cutscene.
* You can optionally set a stage for your cutscene, enabling stage-related actions for objects.
}}

Establishing the setting of a cutscene is done in the object inspector in the group of properties labeled "Setting". The most important of these is the "Area" property, which allows you to set the cutscene in an existing [[area]]. We already have a suitable area that was created in an earlier tutorial; the area "great_outdoors".

By default the MASTER object and Camera 1 will be located at the coordinates 0,0,0 in the area. You'll want to move the camera to the appropriate location within the area using standard [[3D control]]s for movement and view management. The MASTER object is invisible when the cutscene is played in-game so it usually doesn't matter where you put it. However, there are some settings that depend on the MASTER object's location - for example, you can set level-of-detail for models so that the model's LOD varies depending on how close it is to the MASTER object - so it's probably a good idea to put MASTER somewhere near the middle of where you'll be having the cutscene's action take place.

You can also set a stage for the cutscene. This is optional, but setting a stage enables "Jump to Stage Place" and "Jump to Stage Camera" actions that could help make setting the cutscene up easier if you already have a good stage defined in the area.

=== Adding objects and creatures ===

{{sidebox|
* Objects already present in the area the cutscene is set in are inactive by default. You need to activate them to control them.
* Other objects can be added from the resource palette as normal.
}}

All of the objects that are normally present in the area (such as creatures and placeables) will be visible in the cutscene editor, but they'll all initially be marked as "inactive". This means that, although they'll be visible in the cutscene when it plays, they won't be controllable; they'll just do whatever ambient activities they would be doing normally. In the case of our campsite area there are two creatures that were placed here in the area editor; the happy camper, named camp_happy, and the angry camper, named camp_angry. We need to seize control of them to make them active participants in the cutscene's activities. To make them active, right-click on them and select "activate objects":

[[Image:Cutscene activate object.png]]

The object will then become an active object in the cutscene, getting its own entry in the timeline that will allow you to control its actions.

[[Image:Cutscene object activated.png]]

We'll activate both of these campers since they'll both be taking part in the cutscene's dialogue.

You can also add objects that aren't normally a part of the area. Simply open the object palette, select the creature or placeable you wish to use in the cutscene, and then click in the viewport to add the object to that location. It will automatically be made active and get an entry in the timeline. The player won't see these objects during regular play, since they're not a part of the area - they're only in the cutscene.

If you want to make an area object disappear during the cutscene you'll need to activate it (allowing you to control it) and then add a track with an action that makes it invisible in the first frame. It will go back to normal again when the cutscene ends and the game resumes, cutscenes are run entirely separate from the main action of the game and have no direct effects on it.

=== Adding the player ===

{{sidebox|
* Use the "Mapping Tag" property on an actor to make the game replace it with another object (such as PLAYER) at run-time.
}}

Normally we don't have to worry about placing the player in an area since the player controls his own movements and actions. But when we're doing a cutscene we can control the player just like any other actor, so we'll need a way to insert the player as an active object. Furthermore, since we'll have no idea what the player is going to look like at any given moment, we'll need to have a way to insert the player as he appears in the game when the cutscene begins.

This is done by inserting a "dummy" virtual actor and then setting the actor's "Mapping Tag" property to the special "PLAYER" tag.

[[Image:Cutscene dummy player.png|thumb|center|600px]]

It doesn't matter what the dummy actor looks like now, it will be replaced with the player's character later on, so we'll just use a default male human model to make it both simple and obvious.

There are ways to tweak the way the cutscene plays based on other characteristics of the player, for example by modifying the position of the camera to account for the player's height or by adding additional dummies to represent followers. We won't go into these more advanced topics in this tutorial.

=== Adding cameras ===

{{sidebox|
* Remember to enable Safe Frame when attaching a viewport to a camera.
* Use an "Active Camera" viewport to preview the cutscene.
* Use a "User" viewport to see camera positions from the outside.
}}

We could film a cutscene entirely from one camera if we liked, either as a single static shot or by moving the camera around to new positions as needed. It's easier and more convenient in most cases just to add several different cameras, however, and use the "Active Camera" track on the MASTER object to switch between them.

For our cutscene we're going to want three different cameras; one camera that's a wide shot showing the player arriving at the campfire, one camera focused on the angry camper, and one focused on the happy camper. We could add more than just these three to make the scene even more dynamic but for simplicity we'll stick to just those for now. We can add more later.

Cameras are added by right-clicking in the viewport and selecting "Insert → Camera".

[[Image:Cutscene insert camera.png]]

You can then position them using standard [[3D control]]s. To make it easier to get the camera set up with the correct view, a good technique is to set one of the viewports to display the camera's feed; you can then reorient and reposition the camera using that viewport's camera controls while getting immediate feedback as to what the camera will see in its new state.

We're also going to rename the three cameras at this point with names intended to remind us of what their purposes are. We'll name them "Arrival Camera", "Happy Camera", and "Angry Camera". We'll want "Arrival Camera" to be active initially, so we may as well use the original camera for this role; it's already set active by default. We'll see how to switch which camera is active later in this tutorial.

We now have all the basic props we need to get the cutscene going.

== Adding an animation to an actor ==

{{sidebox|
* Set the "Pose" property for actors to make them breathe and fidget naturally when not doing other animations.
* Other animations are set by adding "Play Animation" actions to a generic track.
* Animation filenames are often arcane and hard to find.
}}

If you play the cutscene now the first thing you'll probably notice is that the actors are all standing perfectly motionless. Normally someone who's standing still isn't really standing ''perfectly'' still; they breathe, they shift their weight from foot to foot, and so forth. Since almost every actor we use is going to need to do this we don't want to have to spend a lot of effort setting it up, and fortunately we don't have to. Every actor has a "Pose" property in the object inspector. Simply set this pose to "Standing Neutral" and the actors will display this default subtle movement whenever no other animations are being explicitly imposed on them.

[[Image:Cutscene set pose.png]]

Our next task is somewhat less trivial; we want to show the player walking up to the fire. We're going to have to add a walking animation to the player's actor that runs for a short period of time and then stops.

To do this we'll need to add a new track to the actor's timeline. Right-click on the actor's entry in the timeline and select "Add Track" from the resulting menu:

[[Image:Cutscene add track.png]]

The new track will be named "New Track" by default and will start out empty. Actors in cutscenes will sometimes have dozens of tracks directing their actions so we'll want to rename the track to something a little more informative. In this case we'll name it "Walk to fire". To have it actually cause the player's actor to walk to the fire we'll need to add a "[[Play animation]]" action to it. Right-click on the track and select "Add Action" to get the menu to select this.

[[Image:Cutscene add action.png]]

The action will be added starting at the point you're currently viewing in the timeline, so you may wish to move the timeline's time slider back to the beginning before adding this animation. You can reposition an action along the timeline simply by dragging it with the mouse.

Initially the action has no animation associated with it. To set the animation, select the action in the timeline and then in the Object Inspector go to the "Animation" property and click on the ellipsis ([[Image:ellipsis.png]]) button.

Unfortunately this is where things turn a bit arcane since the names of the various animation files are often very unclear and not all will appear in the default list. You may need to resort to trial and error to find one you like, but there are many hundreds of animations available in the game's resources so this could take some time. See [[animation list]] and [http://social.bioware.com/project/30/#files Beerfish Excel Utilities] for a list of many of them.

In this case the animation we want, "mh.dg_f_5p" ("male human dialog forward five paces"), doesn't appear in the default list of animations available in the animation picker. You'll need to click the ellipsis button next to the "Custom Animation" field and find it in the complete list of all animation resources.

[[Image:Cutscene finding an animation.png]]

If you try playing the cutscene now you'll see that the player's actor will spend a little over five seconds walking and then come to a natural stop - about as long as we needed. But the actor will be animated in place, his legs taking steps but not actually moving him anywhere. This is where position keys and GAD comes in.

== Moving an actor ==

=== Position and orientation keys ===

{{sidebox|
* Objects be moved over time by setting "key frames" on their position and orientation tracks.
* Intermediate frames are interpolated between key frames.
* You can set the curve type between key frames with the "transition out" property for each key.
}}

Every object in a cutscene has a pre-defined "Position" track with three sub-tracks for its X, Y and Z coordinates. Most objects also have a pre-defined "Orientation" track with three subtracks for roll, pitch, and yaw. These tracks can be used to cause an object to move around within the area over the course of the cutscene.

Movement is handled by setting the position and orientation of objects at specific points in time, called key frames, and then interpolating intermediate positions and orientations. To set a key frame, right-click on the actor's entry in the timeline and select "key position". This will set a key for the current position and orientation at the current time in the timeline. You can set position and orientation keys separately if you like. Since this operation is so common there's a very convenient shortcut for it; "k" inserts a key for the currently selected object's position and orientation, "p" inserts a key for its position, and "o" inserts a key for its orientation. Alternately, select the object and click the key command in the toolbar: [[Image:IconKey.png]]

[[Image:Cutscene key selection.png]]

For our purposes right now all we'll need to do is set a key frame at the beginning of the timeline. Move the pointer to the beginning, select the player actor, and set a key. Small boxes will appear on the position and orientation tracks to mark the key frame.

[[Image:Cutscene key marker.png]]

These markers essentially mean "at this particular point in time, dummy_player will be in this particular place and facing in this particular direction."

To get an actor to move over time you could set two key frames - one at the beginning of the movement, with the actor in his starting position, and one at the end of the movement, with the actor at his end position. You can set how the cutscene engine interpolates between the two positions by setting the "Transition Out" property of the starting keyframe to either Bezier (a smooth curve), Linear (a straight line), or Step (a sudden jump from the starting position to the end position). See the [[curve editor]] page for more detail.

We're not going to actually do this in this case, however; we'll try it at a later point in this tutorial to move a camera around. For this particular actor it would be difficult to manually match the actor's walking action with his motion over the ground. If the animation and the movement don't match the actor's feet will "skate" unrealistically along the surface.

There's an easier way to match an animation such as this one with movement through the scene; a mechanism called GAD.

=== Using GAD ===

{{sidebox|
* GAD is a mechanism by which an animation applies a built-in displacement to the object it's animating.
* You need to set at least one key frame for an object to use GAD, even if you don't otherwise use key frames to move it.
}}

GAD is a displacement that is automatically added to the actor's current position as the animation plays. Each animation has its own GAD information built into it, custom-designed to make the actor move in a manner appropriate to its actions. If we enable it the actor will be moved forward as the animation plays.

Not all animations have GAD associated with them. For example, having an actor wave his hand wouldn't displace him, so there would be no GAD associated with that animation. We only need to worry about GAD in cases like this one where the animation should accompany movement.

To enable GAD select the animation action and set "Play Gad" to true in the object inspector. If no key frames have been defined for the actor the cutscene editor will pop up a warning at this point suggesting that we add position and orientation keys before we add GAD:

[[Image:Cutscene gad warning.png]]

It's important to set at least one set of keys for an object using GAD. The animation's GAD may seem to work correctly without it at first, but unexpected and unpredictable errors could occur later that will send the actor careening off into the distance.

Once we've set a key frame and have set the action's "Play Gad" option to true you'll see that the actor now moves forward as he walks. This is good, but since we started him off in the position he's meant to end in it results in the actor walking straight through the campfire. You'll need to move the actor back so that he starts farther away from the fire.

Note that if you've already set a keyframe as described in the previous section you'll need to re-set it for the actor's new location (or alternately set the "update keys" mode with the [[Image:IconUpdateKeys.png]] tool), otherwise the moment the animation starts the actor will instantly jump back to the place he was where you set the keyframe. Once you set a keyframe for an actor, moving the actor around in the cutscene editor doesn't really change its position unless you re-set the keyframe to the new position. Keyframes and the curves interpolating between them always take precedence.

{{sidebox|
* An animation's "Extend Gad Beyond Action" property makes Gad's displacement persist after the animation ends.
}}

The other GAD properties are set to the most appropriate defaults automatically when you select an animation but one particular property bears mention here in case you run into trouble with it later on; the "Extend Gad Beyond Action" property. In the case of this walking animation it defaults to true. That means that once the animation ends, the displacement that the actor has undergone as a result of it will remain in effect - he will stay in the final position he walked to. If this were set to false, once the animation ended all of the displacement the actor had gained as a result would be undone and he'd instantly jump back to where he started walking from again. If at some point in the future you find your actors doing this, this property is the first place to look for the answer.

There's one final detail we'll tweak here. The walking animation begins with the player starting from a standstill, which is not the impression we want to convey; the player has supposedly been walking for some time before the camera started rolling. We could set the animation to begin playing partway through by changing the animation action's "Start Offset" property, but since this is happening at the beginning of the cutscene's timeline an easier approach is to simply select the animation action and drag it so that it begins a half second before the cutscene does. The cutscene will only begin displaying at the 0 mark and anything that falls before this point in time will never be shown so the initial half second of the actor's walk animation will go unseen.

== Moving a camera ==

The scene now has some of the dynamic action we wanted, showing the player walking up to the campfire and stopping at its edge. But it's still a rather dull introduction and we can do better. Instead of a static camera shot we can set the camera so that it pans across the scene to follow the player's arrival.

Select the Arrival Camera and open up its track list. It has Position and Orientation tracks just like the other actors, and can have keyframes set just the same. With the time marker set to 0, move the Arrival Camera so that its view shows how you want the shot framed at the beginning of the cutscene. In our example we're going to set it so that it shows the player in the center of the frame. With the camera still selected, press "k" to set a key frame for the camera.

[[Image:Cutscene camera start position.png]]

(You may notice that the Field of View (FOV) track also gets a key marker. We won't be changing the camera's FOV so you can ignore that.)

Next move the timeline scrubber to the end of the walking animation at the 5 second mark. The player's actor will now be at the final position where he'll be standing for the conversation. Change the camera's orientation, panning to the right so that all of the actors can be seen in its field of view. In our case the camera's too close to encompass everyone so we'll also move its position to allow it to see them all.

Once you have the shot lined up correctly, press "k" to set a second keyframe.

[[Image:Cutscene camera end position.png]]

You may notice that the User viewports now show a red line tracing out the selected object's trajectory through space (if not, you may need to click the "show trajectories" [[Image:IconShowTrajectory.png]] button in the toolbar). As the first five seconds of the cutscene plays, the Arrival Camera should slide smoothly along the red line and rotate smoothly on its axes to transition from the first keyframe to the second keyframe (If it suddenly jumps from one position to the other instead you may need to click the "default curve mode" tool [[Image:IconDefaultCurveMode.png]] and try setting the keys again, or change the "transition out" property of the keyframe to Bezier).

You can fine-tune the trajectory of the camera by adding additional keyframes between the starting and ending ones. In our case we see that when the time marker is set to the middle of the camera's movement the player slips slightly out of frame.

[[Image:Cutscene camera middle position unadjusted.png]]

We can fix this by changing the camera's position and orientation as needed, and then adding a new keyframe with "k". In this case we'll pull the camera back slightly so that its motion through space becomes a curve instead of a straight line.

[[Image:Cutscene camera middle position adjusted.png]]

We now have a nice, dynamic establishing shot. The scene begins with the player alone and in the center of the camera's shot, and as he walks toward the fire the camera moves and pans around him to show him arriving in the presence of our two campers.

== Switching cameras ==

{{sidebox|
* A track on the MASTER object defines which camera is currently "active."
}}

Once the player arrives he is going to be greeted by the camper who is happy to see him. To give a clear shot of who's doing the talking, we'll want to switch the active camera from Arrival Camera to Happy Camera.

The track where the active camera gets changed is attached to the MASTER object. Move the timeline's time indicator to the point in time where you wish to switch active cameras, in this case 5.5 seconds (giving the scene a half-second view of the player after he's come to a halt). Right-click on the Active Camera track and select Add Action. The only option available for this track is the "Switch Camera" action so go ahead and add one. In the new Switch Camera action's properties set it to switch the active camera to Happy Camera.

Now when the cutscene is played we'll get an establishing shot showing the player walking up to the fire and then switch to a closeup of the happy camper so that he can deliver his greeting.

[[Image:Cutscene switch active camera.png]]

== Adding dialogue ==

{{sidebox|
* Lines of dialog can be inserted from an existing [[conversation]] resource. For convenience, create a new conversation to hold the dialog for a cutscene.
* Caption text, voice over, and facial performance are all included with each line.
* If you edit the conversation later, the changes will be reflected in the cutscene. Remember to generate new VO and FaceFX in the conversation editor.
}}

There are three major components to dialog in Dragon Age; the text of the line being spoken (which is displayed as a caption at the top of the screen), the voice-over for the line being spoken, and the facial performance that makes the virtual actor lip-synch and display appropriate emotions.

There's already got a tool in the toolset that is designed for handling all of these things; the conversation editor. Actors in a cutscene can be given "Speak Line" actions that cause them to deliver lines from an existing dialog, with all three components added together into the actor's performance automatically.

To create the dialog for this cutscene we'll now create a new conversation resource. This conversation is not going to be used in the game directly so we'll be able to ignore many of the more advanced features and settings covered in the conversation tutorial; its only purpose is to serve as a repository of dialog lines for use in this cutscene.

The following screenshot shows our intended conversation. The only things that we need to define for it is the text of the dialog and optionally the emotion settings for RoboBrad to use when generating facial performance. As with our previous conversation we'll generate synthesized placeholder voice-over and generate FaceFX based on that; when we record real voice over later on we can simply update this conversation with it and the cutscene's performance will change to match.

[[Image:Cutscene conversation.png]]

To help keep track of which lines are spoken by which actors you could also optionally set the speaker tag on each line to identify who's doing the talking. This particular conversation has only two speakers so we won't bother with that. The cutscene engine won't need speaker tags, we'll be explicitly telling it who is saying each line. You'll only need to set those things if you wish to preview the conversation before using its lines in the cutscene.

Once you've created your dialogue go back to the cutscene editor and add a new track to the camp_happy actor. Rename it to something informative, such as "Dialogue". Move the timeline marker to the spot where you want the actor to start speaking and add a new "Speak Line" action.

In the Speak Line action's properties, set the "Source Conversation" property to the conversation resource we just created. Then, select the specific line you want the actor to speak in the "Source Line" property (it will have a drop-down menu with all of the lines from the source conversation in it).

That's all you need to do to get the actors to talk. You may wish to add one other detail at this point; head tracking. This is the action that causes actors to turn their heads toward a specific target, usually the person they're talking to or who is talking to them. It's added as its own action, so create another track and add a headtracking action to it with the player as the target. In this case we want the happy camper to turn his head toward the player right before he starts speaking.

== Adding other details ==

{{sidebox|
* Headtracking actions make actors look at other objects in the cutscene.
* You can have more than one action on a track provided they don't overlap.
}}

We've now gone through all the basics, so we'll just finish fleshing out the conversation with a few other details that are done the same way as the examples above.

To add a little more animation to the scene, we add another track for camp_happy with an animation action (mh.dg_hnd_salute_01, a salute) to play during his spoken line. This animation is simpler to deal with than the walking animation because it doesn't displace the actor; there's no need to define position keys or worry about enabling GAD.

We'll set camp_angry's headlook so that she turns toward camp_happy while he's speaking; when we subsequently switch cameras to show her line of dialog she'll already be looking in his direction.

For camp_happy's next line, however, we'll make the headtracking change visible during his shot so the player will see how his attention has switched to camp_angry. Note that we can reuse the existing "Dialogue" and "Headtracking" tracks for this actor; we don't need to create a new track for every single action that an actor performs. So long as the durations of the actions on a track don't overlap they can coexist peacefully.

Finally, after camp_angry's last line we'll set her headtracking to look back toward the player. He's going to get the next word in when we integrate this cutscene into a conversation so this is a good way to indicate that the conversation's focus has gone to the player now.

Once we've finished crafting the cutscene we now know how long its duration needs to be. You can now go to the conversation's properties in the Object Inspector and set the cutscene's duration to the desired length.

The finished timeline of our cutscene:

[[Image:Cutscene finished timeline.png]]

[[Category:Tutorials]]
[[Category:Cutscenes]]

=== Cutscene Tips and Tricks ===

Here are a few tips and tricks that might save the cutscene creator some time and perhaps hair pulling.

- Head tracking is often used to look at another actor or a visible item in the cutscene. However you can further manipulate the head of the actor by having the actor look at invisible objects. You can have the actor look from one invisible object to another or move the invisible object around in the cutscene to get the actor to look at things independent of visible actors or items.

- You may find it useful to give meaningful names to your cameras if you are using more than one or two. (You might name a camera after the actor or placeable that it follows or name one camera ‘close-up’ and another ‘wide-angle’ for example.)

- If you are panning a camera around a room following a series of actors or placeables and you find that the camera suddenly decides to rotate in the other direction you can force it to stay moving in the direction you desire by adding or subtracting 360 degrees from the position/orientation you are using to move the camera.

- Feel free to experiment with animations. Try using animations that are not normally meant for your actor type, you might find some interesting or bizarre movements for your actor.

- You can put multiple actions along one track as long as they do not overlap rather than using many different tracks.

- Pay attention to what your key frames ‘transition out’ are set to when moving your cameras. Step will jump the camera from position to position while Bezier and Linear will move the camera in a smoother motion. If you are not getting the desired effect when moving cameras check what your key frames ‘transition out’ are set to.

- If you have a longer more detailed cutscene you can keep the number of cameras you use to a reasonable number by just moving one (or more) around while another camera is the ‘active’ camera.

- For testing purposes change the length of the cutscene in the cutscenes properties to a smaller value and enlarge that number as you add on to the cutscene. In this way you won’t need to wait for a long period of time for the cutscene to end.

- After placing an animation on a track you can speed up the animation by left clicking on the small circular arrows on one end and dragging it shorter or make the animation play slower by dragging the animation longer on the track.

- You can make the content of your scene seem to change by placing invisible objects in the cutsence, using an fx to obscure the view and making the object visible while the fx is playing. (For example you might have some invisible rock debris. Use a cave in fx with clouds of dust to obscure the screen. While the fx is playing make the debris visible. When the fx is finished your debris will be in place.)

- If you find that your actor is walking across surfaces (such as water for instance) when they should be following the ground you can set ‘items follow surface’ in the area that your cutscene is based on. The actor should then walk on the ground and thus wade into the water. Conversely if you want a character or placeable to not follow the surface of the ground (for instance if you want a placeable or actor to be near or on the surface of water) move the actor or placeable higher by adjusting the Z axis of the boat or actor. (An example of using a placeable partly submerged in water might be something like a boat.)

- In a cutscene you can only activate things that are unique. As in if you plopped down three identical chests in an area, when trying to activate them all in a cutscene it will not allow this and gives you a warning message. In the example above you would have to make three different chests (though they could look the same) to be able to activate them all in the cutscene.

File:EnvProp4.jpg

2009-09-16T03:39:51Z

Beerfish:

Model list

2009-09-16T03:37:37Z

Beerfish:

{{Infobox level editor}}
The idea behind showing these models is to give the player a quick view of the actual model that corresponds with a model file name. Most of the files have meaningful names however the builder will still find that he/she has to place the model in the level to see what it looks like. These will allow the builder to quickly view model images and thus save them time in level building.

The base folders and their meanings are:

*base
*blk - black boxes of various sizes and proportions, used to obscure the portions of models that lie "outside" an interior level where the player shouldn't be able to see.
*c - creature
*cai - Cave Int.
*cav
*cdr
*che
*chi
*cn - Commmon Body Meshes
*cs
*df - dwarf female accessories and components
*dm - dwarf male accessories and components
*dne - dwarf noble exterior level pieces
*dni - dwarf noble interior level pieces
*dse - dwarf slum exterior level pieces
*dsi - dwarf slum interior level pieces
*dwe - Dwarven Ext. (Orzammar City)
*dwi - Dwarven Interior
*ef - elf female accessories and components
*el
*em - elf male accessories and components
*fca
*fce - Ferelden Castle/City Ext.
*fci - Ferelden Castle Int.
*fde
*fdi
*fhe
*fhec
*fhi - Ferelden human interior level pieces
*fne - Ferelden noble exterior level pieces
*frt
*fti
*ftr
*fve
*fx
*fxa
*fxc
*fxe
*fxg
*fxm
*fxp
*hf - human female accessories and components
*hm - human male accessories and components
*hro
*kn
*lightrig
*material
*nm
*plc - placeables
*prp - props
*prv
*qm
*sb - Skybox
*sca
*sr
*tce - Tevinter Castle Ext.
*tci - Tevinter Castle Int.
*tfi
*tools - models used by the toolset
*trn
*tti
*tve
*tvi
*tvm
*ue
*uem - Face Bits
*uh - Face Bits
*uhm - Face Bits
*ul
*ulm
*v
*vfx
*vis - vista objects
*vst - vista objects
*w - weapon models
*water - waterfall pieces
*zz - models used in debugging

Since the model names are often inscrutable you will likely wish to make use of the [[scratch space]] in the [[level editor]] by bringing out all of the models from a particular group of interest and copying and pasting those you wish to use from there.

* Black models are used to surround indoor areas so that players can see inside the walls when the camera is outside them.
* All screen shots are taken with a level of 64 x 64 size (smallest size possible). This allows you to see a relative scale of the model. Most are placed within the level area but some are much larger than the area.
* Many of these images are not exactly to scale, the idea is to see what the image looks like rather than to see the exact size to scale.
* Some model images such as ceilings and roofs will be taken from underneath looking into the sky.
* Some model images look the same but are of different size.
* Some models extend below the grounds surface when placed.
* The models in this sheet are architectural and environmental. Models that are props, placeables, fx, body parts etc can all be viewed in other areas of the toolset.

== Black boxes ==

[[File:blk.jpg]]

== Cave ==

[[File:cai1.jpg]]
[[File:cai2.jpg]]
[[File:cai3.jpg]]

[[File:cav1.jpg]]
[[File:cav2.jpg]]
[[File:cav3.jpg]]
[[File:cav4.jpg]]
[[File:cav5.jpg]]
[[File:cav6.jpg]]

== Cave Deep Road ==

[[File:cdr1.jpg]]
[[File:cdr2.jpg]]

== Chantry exterior ==

[[File:che1.jpg]]

== Chantry interior ==

[[File:chi1.jpg]]
[[File:chi2.jpg]]
[[File:chi3.jpg]]
[[File:chi4.jpg]]

== Dwarf slum exterior ==

[[File:dse1.jpg]]

== Dwarf slum interior ==

[[File:dsi1.jpg]]
[[File:dsi2.jpg]]
[[File:dsi3.jpg]]

== Fereldan castle ==

[[File:fca1.jpg]]
[[File:fca2.jpg]]
[[File:fca3.jpg]]
[[File:fca4.jpg]]
[[File:fca5.jpg]]
[[File:fca6.jpg]]
[[File:fca7.jpg]]

[[File:fce1.jpg]]

[[File:fci1.jpg]]
[[File:fci2.jpg]]
[[File:fci3.jpg]]
[[File:fci4.jpg]]

== Fereldan dungeon interior ==

[[File:fdi1.jpg]]
[[File:fdi2.jpg]]
[[File:fdi3.jpg]]

== Fereldan human exterior ==

[[File:fhe1.jpg]]
[[File:fhe2.jpg]]
[[File:fhe3.jpg]]
[[File:fhe4.jpg]]
[[File:fhe5.jpg]]
[[File:fhe6.jpg]]

[[File:fhec1.jpg]]
[[File:fhec2.jpg]]

== Fereldan human interior ==

[[File:fhi1.jpg]]
[[File:fhi2.jpg]]
[[File:fhi3.jpg]]
[[File:fhi4.jpg]]
[[File:fhi5.jpg]]

[[File:frt1.jpg]]

== Fereldan tavern interior ==

[[File:fti1.jpg]]
[[File:fti2.jpg]]
[[File:fti3.jpg]]
[[File:fti4.jpg]]
[[File:fti5.jpg]]
[[File:fti6.jpg]]

== Fereldan village exterior ==

[[File:fve1.jpg]]

== "Hero" sets ==

These tiles consist of models that were custom-made for certain situations in the main campaign.

[[File:hro1.jpg]]
[[File:hro2.jpg]]
[[File:hro3.jpg]]
[[File:hro4.jpg]]
[[File:hro5.jpg]]

== Tevinter castle exterior ==

[[File:tce1.jpg]]

== Tevinter castle interior ==

[[File:tci1.jpg]]
[[File:tci2.jpg]]

== Tevinter Fade interior ==

[[File:tfi1.jpg]]
[[File:tfi2.jpg]]
[[File:tfi3.jpg]]
[[File:tfi4.jpg]]

== Tevinter tower interior ==

[[File:tti1.jpg]]
[[File:tti2.jpg]]
[[File:tti3.jpg]]
[[File:tti4.jpg]]
[[File:tti5.jpg]]

== Tevinter exterior ==

[[File:tve1.jpg]]
[[File:tve2.jpg]]
[[File:tve3.jpg]]

== Tevinter interior ==

[[File:tvi1.jpg]]
[[File:tvi2.jpg]]
[[File:tvi3.jpg]]
[[File:tvi4.jpg]]
[[File:tvi5.jpg]]
[[File:tvi6.jpg]]

== Tevinter road ==

[[File:tvm1.jpg]]

== Vista objects ==

These objects are intended to be put far outside the walkable area of an exterior level to act as distant "horizon" objects.

[[File:vis1.jpg]]

[[File:vst1.jpg]]

== Environmental Props ==

The following images are environmental props from the 'prp' subsection of 'models'. Props are models that can be placed in your levels to dress them up. They are not interactive (as in they cannot have inventory or be 'used' in any way.) If the module maker requires items to be placed in the module that can be interacted with they must use 'Placeables' rather than 'Props' The images below are by no means all of the props, just some of the large environmental ones. There is a large variety of props so you are encouraged to go through the whole list of prop models to enhance the look of your level. Also the images below are not to scale they are merely intended so that the module maker can quickly scan them to see if any of them catch his or her fancy.

[[File:EnvProp1.jpg]]
[[File:EnvProp2.jpg]]
[[File:EnvProp3.jpg]]
[[File:EnvProp4.jpg]]
[[File:EnvProp5.jpg]]
[[File:EnvProp6.jpg]]
[[File:EnvProp7.jpg]]
[[File:EnvProp8.jpg]]
[[File:EnvProp9.jpg]]
[[File:EnvProp10.jpg]]
[[File:EnvProp11.jpg]]
[[File:EnvProp12.jpg]]
[[File:EnvProp13.jpg]]
[[File:EnvProp14.jpg]]

== Banners,Flags,Standards,Signs,Tapestry,Wall Hangings,Rugs,Carpets ==

The images below are all 'Props (prp)' which are found under the 'Models' in the palette window.
The images are not to scale but are intended to show what the prop looks like. Props are not interactive and are used to dress up levels. If the module maker requires interactive items in their module level they must use 'placeables' rather than 'props'

[[File:Bannersetc1.jpg]]
[[File:Bannersetc2.jpg]]
[[File:Bannersetc3.jpg]]
[[File:Bannersetc4.jpg]]

[[Category:Level layouts]]

File:EnvProp14.jpg

2009-09-16T03:21:20Z

Beerfish:

File:EnvProp13.jpg

2009-09-16T03:21:10Z

Beerfish:

File:EnvProp12.jpg

2009-09-16T03:20:56Z

Beerfish:

File:EnvProp11.jpg

2009-09-16T03:20:42Z

Beerfish:

File:EnvProp10.jpg

2009-09-16T03:20:30Z

Beerfish:

File:EnvProp9.jpg

2009-09-16T03:20:17Z

Beerfish:

File:EnvProp8.jpg

2009-09-16T03:20:01Z

Beerfish:

File:EnvProp7.jpg

2009-09-16T03:19:49Z

Beerfish:

File:EnvProp6.jpg

2009-09-16T03:19:35Z

Beerfish:

File:EnvProp5.jpg

2009-09-16T03:19:09Z

Beerfish:

File:EnvProp3.jpg

2009-09-16T03:18:52Z

Beerfish:

File:EnvProp2.jpg

2009-09-16T03:18:37Z

Beerfish:

File:EnvProp1.jpg

2009-09-16T03:18:18Z

Beerfish:

File:Bannersetc4.jpg

2009-09-16T03:18:01Z

Beerfish:

File:Bannersetc3.jpg

2009-09-16T03:17:47Z

Beerfish:

File:Bannersetc2.jpg

2009-09-16T03:17:34Z

Beerfish:

File:Bannersetc1.jpg

2009-09-16T03:17:21Z

Beerfish:

Level editor

2009-08-11T20:08:05Z

Beerfish:

The level editor is used to generate the level layouts that are the basis for creating [[area]]s. A level layout is a non-interactive 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.

== Creating a new level ==

When creating a new level layout you'll be presented with a wizard that sets up several basic attributes. Note that some of these attributes can't be changed once the level has been created.

[[Image:Level editor level creation wizard start.png|center|frame]]

The first choice is whether to have a terrain mesh (the "ground") or not. If you choose to have a room-based level you'll have to place chunks of floor, walls, and ceiling to enclose the player on all sides. Room-based levels have no further attributes that need to be configured during new level creation, so if you select "room-based" you'll be taken straight to the level editor from here.

[[Image:Level editor level creation wizard terrain basic.png|center|frame]]

If you choose terrain-based, you'll be asked to define some attributes for the terrain mesh. By default you're shown the basic set of attributes:
*Terrain mesh dimensions, in meters. Note that 64 by 64 is about the minimum that can produce a serviceable level, and that 256 by 256 is the maximum before one starts risking bad performance - though levels can be made larger than this if one takes care.
*Base mesh resolution - determines the size of the individual triangles that make up the terrain mesh. The default has 2 meter triangles. Note however that you'll be able to manipulate the terrain at a much higher resolution than this by using the tessellation tool; each tessellation level splits the previous level's triangles up into four smaller triangles.
*Chunk size - chunks are the basic simulation unit used by the engine. The default 32m is a good chunk size. You'll probably not want to reduce it smaller since you can't have the terrain mesh overhang from one chunk into another; smaller chunks could place limits on the sorts of terrain warping you'll be able to do later.
*Create a default water plane - Creating additional water planes later on is quick and easy, but this option provides a pre-made one by default.

[[Image:Level editor level creation wizard terrain advanced.png|center|frame]]

If you click the "advanced" button you'll be provided with a different presentation of the level's dimensions. Instead of defining its dimensions directly you can set how big chunks are and how many chunks there are in each dimension, defining the level's overall dimensions implicitly.

There's one important attribute that can only be set in the advanced pane; the texel map's resolution. A texel is a "texture element", a sort of high-level pixel equivalent that defines a texture instead of just a single uniform colour. The terrain is "painted" with texels, described later.

== Layout name ==

The name of a layout is limited to seven characters. BioWare uses the following naming system:

*Three-letter prefix that describes the region or plot the layout is for. For example, "ost" for Ostagar and environs.
*Three-digit number that uniquely identifies the layout within that region. Increments of one hundred are commonly used for major areas to allow sub-regions to be grouped together.
*A single character identifying variants of the layout. For example, a "d" suffix for the "daytime" version of an exterior layout. "d" is also often used to mean "default", for areas where day and night are irrelevant (deep in a cave, for example).

So for example the layout "ost101d" is a layout in the Ostagar region with a daytime ambience.

== Toolbar ==

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

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

== 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.

== 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.

*[[Image:IconTerrainDeform.png]] "Deform" allows the terrain mesh to be raised or lowered, or it can extrude the ground "outward" or "inward" along its surface normal. In other words, if you were to apply the brush to the side of a cliff in extrude mode you could create a cave-like hollow or a bulging overhang. Note that the walkmesh used by the game is two-dimensional, ie, it doesn't allow pathfinding both over and under an overhang. The walkmesh will always be generated on the overhanging part of the land. Also note that you cannot have an overhang from one terrain chunk into another terrain chunk - turn on "view chunk boundaries" to check if this has happened and reposition any overhangs that violate these boundaries.

*[[Image:IconTerrainPlateau.png]] "Plateau" flattens out the land the brush is applied to, removing bumps or dips and making the ground level. This is a good tool for making a path through rough terrain, or for smoothing out a flat field.

*[[Image:IconTerrainSmooth.png]] "Smooth" is a more generic form of flattening tool. It doesn't force the ground toward a horizontal plane, instead just averaging out the nearby terrain in whatever orientation it averages out to.

*[[Image:IconTerrainTessellate.png]] "Tessellate" changes the resolution of the terrain's mesh, increasing or decreasing the number of triangles a given region. This allows for a more fine-grained control of the shape of the land and prevents small features from being given obvious straight edges caused by the underlying triangle mesh. Left-clicking increases the number of triangular subdivisions and right-clicking reduces it. The "max level" and "min level" settings on the tool constrain these values - lower numbers indicate a coarser mesh with fewer, larger triangles.

*[[Image:IconTexturePaint.png]] "Texture paint" paints materials from the material palette onto the terrain. The material palette for any given level can hold up to eight materials, and they can be blended together seamlessly.

*[[Image:IconTextureSmooth.png]] "Texture smooth" blurs the boundaries between different material types, allowing them to fade more gradually from one terrain material type to another.

*[[Image:IconTextureRelax.png]] "Relax map" causes stretched ground textures to relax back toward their default resolution. Terrain texture stretching can occur when you deform the ground. For example, if you were to stretch the ground upward in a small area to form a tall cliff, the texture on the cliff's face would be vertically stretched and could look unrealistic as a result.

== 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. To place them click on the [[Image:IconModelPlacement.png]] icon in the toolbar to go into model placement mode.

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

=== Model palette ===

The model palette contains all the basic building blocks that you'll have available to build a level layout with. These building blocks are created using third-party 3D studio programs such as 3DSMax, a process that we won't go into here.

Unlike the database resource palette, the model palette doesn't have a heirarchy of folders and subfolders. Since there are usually a vast number of models available this can make the palette cluttered and difficult to work with. To make it more manageable you should set the toolset's configuration to "fake" a folder structure. The toolset will divide models up based on their names, using underscores as dividers; for example the models dwe_face and dwe_orzent would both be placed inside a "dwe" folder. The option for setting this can be found under the palette options menu:

[[Image:Options menu use fake model folders.png|center]]

Models are grouped into "tilesets" with pieces that share common structural themes. For example, there might be a "dwarven fortress" tileset that contains a variety of structural pieces and furniture of dwarven manufacture, and a "Tevinter" tileset that contains a variety of pieces with Tevinter architectural motifs.

Since the names of these models can often be a bit inscrutable, a more convenient way of working with models that you're frequently using on a level (such as wall segments) is to bring them into the level's "scratch space" and copy them as needed. Objects in the scratch space can be positioned within the level just like ordinary objects but will not be exported when the level is exported for use as an area layout.

[[Image:Level editor scratch space.png|center|thumb|600px|These three fence pieces are in the scratch space, and so will not be exported with the rest of the objects in this level.]]

=== Selecting objects ===

When clicking on models in the layout there will often be other foreground objects that are in the way, preventing the immediate selection of the object you wanted. Simply keep clicking on the same spot to cycle through all of the objects that are underneath the mouse pointer.

=== Moving and placing objects ===

Clicking on the "snap options" button [[Image:IconSnapOptions.png]] on the toolbar brings up the following options:

[[Image:Level editor snap options.png]]

"snap to grid" causes the position of objects you place or move to be constrained to specific points in an imaginary three-dimensional grid. This is very useful when placing things such as floor tiles, which must be arranged in a precise grid in order for their edges to match up correctly.

"snap rotation" similarly constrains the rotation of objects to specific angles.

"snap to surface" is useful when placing furniture and other objects on an existing surface (terrain, floor, etc.). It forces the object to rest "on" the surface. Once placed you can disable surface snapping and fine-tune the object's location as needed.

== 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.

== Light probes ==

Light probes are used to generate the appearance of nearby reflective surfaces. A light probe consists of an imaginary sphere that is textured with a pre-rendered view of its surroundings in every direction; reflective objects will use the texture of the nearest light probe to produce an approximation of what a reflection should look like. Light probes are particularly important where water planes are used.

The following example shows a light probe with the reflection texture rendered onto it (to make the light probe's texture visible you need to have "view models fully lit" turned off and "display light maps" turned on). The water below the light probe is using the probe's texture to determine its reflection.

[[Image:Level editor light probe.png]]

If you make any changes to the level that would make a visible difference to what a light probe "sees" you'll have to re-render the light probes to update the reflection texture. This command is under the menu "Tools -> Render -> Render light probes", or you can click the toolbar button [[Image:IconRenderLightProbe.png]]

== 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.

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]]

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. To manually "fence off" an area, use the "Generate Terrain Collision" tool ([[Image:IconGenerateTerrainCollision.png]] in the toolbar) to place invisible barriers that pathfinding will treat as impassible. You should include some sort of visual barrier as well, if possible, to let the player know why he can't pass through that spot.

== 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.

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

== 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.

== Exportable area ==

A layout requires at least one exportable area. This is the area that the player will be able to operate in and percieve when the layout is exported for use in the game.

It's possible to have a large level with several different exportable areas. The player will have to go through an area transition to travel between exportable areas, just as if they were separate layouts entirely, but by combining them into one level in the level editor it becomes easier to maintain consistency between them. This is particularly useful in layouts where a player in one exportable area can see into the other exportable area but not reach it directly.

== File name and associated 'Vegetation' images ==

[[File:Bushes1.jpg]]
[[File:Bushes2.jpg]]
[[File:Bushes3.jpg]]

[[File:Grasses1.jpg]]
[[File:Grasses2.jpg]]
[[File:Grasses3.jpg]]
[[File:Grasses4.jpg]]
[[File:Grasses5.jpg]]
[[File:Grasses6.jpg]]

[[File:Trees1.jpg]]
[[File:Trees2.jpg]]
[[File:Trees3.jpg]]
[[File:Trees4.jpg]]
[[File:Trees5.jpg]]
[[File:Trees6.jpg]]

== Level Editor Models ==

The idea behind showing these models is to give the player a quick view of the actual model that corresponds with a model file name. Most of the files have meaningful names however the builder will still find that he/she has to place the model in the level to see what it looks like. These will allow the builder to quickly view model images and thus save them time in level building.

- Black models are used to surround indoor areas so that players can see inside the walls when the camera is outside them.
- All screen shots are taken with a level of 64 x 64 size (smallest size possible). This allows you to see a relative scale of the model. Most are placed within the level area but some are much larger than the area.
- Many of these images are not exactly to scale, the idea is to see what the image looks like rather than to see the exact size to scale.
- Some model images such as ceilings and roofs will be taken from underneath looking into the sky.
- Some model images look the same but are of different size.
- Some models extend below the grounds surface when placed.
- The models in this sheet are architectural and environmental. Models that are props, placeables, fx, body parts etc can all be viewed in other areas of the toolset.

[[File:blk.jpg]]

[[File:cai1.jpg]]
[[File:cai2.jpg]]
[[File:cai3.jpg]]

[[File:cav1.jpg]]
[[File:cav2.jpg]]
[[File:cav3.jpg]]
[[File:cav4.jpg]]
[[File:cav5.jpg]]
[[File:cav6.jpg]]

[[File:cdr1.jpg]]
[[File:cdr2.jpg]]

[[File:che1.jpg]]

[[File:chi1.jpg]]
[[File:chi2.jpg]]
[[File:chi3.jpg]]
[[File:chi4.jpg]]

[[File:dse1.jpg]]

[[File:dsi1.jpg]]
[[File:dsi2.jpg]]
[[File:dsi3.jpg]]

[[File:fca1.jpg]]
[[File:fca2.jpg]]
[[File:fca3.jpg]]
[[File:fca4.jpg]]
[[File:fca5.jpg]]
[[File:fca6.jpg]]
[[File:fca7.jpg]]

[[File:fce1.jpg]]

[[File:fci1.jpg]]
[[File:fci2.jpg]]
[[File:fci3.jpg]]
[[File:fci4.jpg]]

[[File:fdi1.jpg]]
[[File:fdi2.jpg]]
[[File:fdi3.jpg]]

[[File:fhe1.jpg]]
[[File:fhe2.jpg]]
[[File:fhe3.jpg]]
[[File:fhe4.jpg]]
[[File:fhe5.jpg]]
[[File:fhe6.jpg]]

[[File:fhec1.jpg]]
[[File:fhec2.jpg]]

[[File:fhi1.jpg]]
[[File:fhi2.jpg]]
[[File:fhi3.jpg]]
[[File:fhi4.jpg]]
[[File:fhi5.jpg]]

[[File:frt1.jpg]]

[[File:fti1.jpg]]
[[File:fti2.jpg]]
[[File:fti3.jpg]]
[[File:fti4.jpg]]
[[File:fti5.jpg]]
[[File:fti6.jpg]]

[[File:fve1.jpg]]

[[File:hro1.jpg]]
[[File:hro2.jpg]]
[[File:hro3.jpg]]
[[File:hro4.jpg]]
[[File:hro5.jpg]]

[[File:tce1.jpg]]

[[File:tci1.jpg]]
[[File:tci2.jpg]]

[[File:tfi1.jpg]]
[[File:tfi2.jpg]]
[[File:tfi3.jpg]]
[[File:tfi4.jpg]]

[[File:tti1.jpg]]
[[File:tti2.jpg]]
[[File:tti3.jpg]]
[[File:tti4.jpg]]
[[File:tti5.jpg]]

[[File:tve1.jpg]]
[[File:tve2.jpg]]
[[File:tve3.jpg]]

[[File:tvi1.jpg]]
[[File:tvi2.jpg]]
[[File:tvi3.jpg]]
[[File:tvi4.jpg]]
[[File:tvi5.jpg]]
[[File:tvi6.jpg]]

[[File:tvm1.jpg]]

[[File:vis1.jpg]]

[[File:vst1.jpg]]

File:Vst1.jpg

2009-08-11T20:02:45Z

Beerfish: vst1 models

vst1 models

File:Vis1.jpg

2009-08-11T20:02:31Z

Beerfish: vis1

vis1

File:Tvm1.jpg

2009-08-11T20:02:16Z

Beerfish: tvm1 models

tvm1 models

File:Tvi6.jpg

2009-08-11T20:01:39Z

Beerfish: tvi6 models

tvi6 models

File:Tvi5.jpg

2009-08-11T20:01:24Z

Beerfish: tvi5 models

tvi5 models

File:Tvi4.jpg

2009-08-11T20:01:08Z

Beerfish: tvi4 models

tvi4 models

File:Tvi3.jpg

2009-08-11T20:00:54Z

Beerfish: tvi3 models

tvi3 models

File:Tvi2.jpg

2009-08-11T20:00:36Z

Beerfish: tvi2 models

tvi2 models

File:Tvi1.jpg

2009-08-11T20:00:22Z

Beerfish: tvi1 models

tvi1 models

File:Tve3.jpg

2009-08-11T19:59:43Z

Beerfish: tve3 models

tve3 models

File:Tve2.jpg

2009-08-11T19:59:28Z

Beerfish: tve2 models

tve2 models

File:Tve1.jpg

2009-08-11T19:59:13Z

Beerfish: tve1 models

tve1 models

File:Tti5.jpg

2009-08-11T19:58:54Z

Beerfish: tti5 models

tti5 models

File:Tti4.jpg

2009-08-11T19:58:39Z

Beerfish: tti4 models

tti4 models

File:Tti3.jpg

2009-08-11T19:58:22Z

Beerfish: tti3 models

tti3 models

File:Tti2.jpg

2009-08-11T19:58:07Z

Beerfish: tti2 models

tti2 models

File:Tti1.jpg

2009-08-11T19:57:54Z

Beerfish: tti1 models

tti1 models

File:Tfi4.jpg

2009-08-11T19:57:34Z

Beerfish: tfi4 models

tfi4 models

File:Tfi3.jpg

2009-08-11T19:57:21Z

Beerfish: tfi3 models

tfi3 models

File:Tfi2.jpg

2009-08-11T19:57:05Z

Beerfish: tfi2 models

tfi2 models

File:Tfi1.jpg

2009-08-11T19:56:46Z

Beerfish: tfi1 models

tfi1 models

File:Tci2.jpg

2009-08-11T19:56:28Z

Beerfish: tci2 models

tci2 models

File:Tci1.jpg

2009-08-11T19:56:11Z

Beerfish: tci1 models

tci1 models

File:Tce1.jpg

2009-08-11T19:55:56Z

Beerfish: tce1 models

tce1 models

File:Hro5.jpg

2009-08-11T19:55:40Z

Beerfish: hro5 models

hro5 models

File:Hro4.jpg

2009-08-11T19:55:26Z

Beerfish: hro4 models

hro4 models

File:Hro3.jpg

2009-08-11T19:55:10Z

Beerfish: hro3 models

hro3 models

File:Hro2.jpg

2009-08-11T19:54:51Z

Beerfish: hro2 models

hro2 models

File:Hro1.jpg

2009-08-11T19:54:30Z

Beerfish: hro1 models

hro1 models