Stage/ru - Revision history

Kelamor: Небольшая правка

2013-06-24T02:49:10Z

Небольшая правка

Kelamor: Небольшая правка

2013-06-24T02:22:15Z

Небольшая правка

Kelamor: Edit

2011-11-01T02:20:05Z

Edit

Kelamor: Create russian page

2011-10-27T22:50:17Z

Create russian page

New page

{{rupage|Сцены|Диалоги|В процессе перевода}}
{| style="float:right;"
|-
| {{Resource palette}}
|}

Stages are used in [[conversation]]s that take place in a predefined location. They are like the direction of a stage play, allowing the activities of the conversation's participants and the positioning of the camera to be controlled while the lines are being spoken.

The default The "face to face" conversations will occur whenever a stage isn't specified for the conversation

A stage '''template''' can be created using DA's stage editor. The setup includes the following:
* Setting the player's position (position includes also initial orientation)
* Setting all NPC actors' positions
* Setting party members' positions
* Placing one or more cameras overlooking the stage
* Defining the focal length and clipping plane of the camera
* The ability to import and edit existing stages to allow for template usability.
* Ability to define/import/edit functional shots (see below) for a stage.
* Ability to compensate cameras procedurally, for varying heights from speaker to listener, to account for racial height difference and terrain differences.
* Defining the stages borders. This will be used to prevent creatures from stepping into the stage. (Otherwise we'll have to manually prevent creatures from walking in, and that's very likely to fail).
* Saving the stage object as a one defined structure. The main aspect that defines the stage is the number of NPC actors involved, but there may be more than one template for the same number of NPCs actors.

[[Image:Stage tutorial 1.png|600px|thumb|center|A simple stage with two places and one camera]]

== Using a stage ==
The stage then appears in the toolset in the stage palette and can be placed inside an area. The user orients the stage and gives it a tag. In the toolset, it should be possible to view placed objects in and around the stage area.

[[Image:Stage tutorial 2.png|thumb|300px|center|The above stage placed using the [[area]] editor. Note how one of the places overlaps the NPC assigned to it, so that the NPC won't suddenly move to a new position when the stage is used.]]

The user then adjusts the following setting on the stage <b>instance</b>:
* Select a position for the player (default is node #1)
* Select a position for the conversation owner (default is node #2)
* Select follower positions (default nodes #3, #4 and #5). Note: the player can not select a specific follower in a specific node — he just selects what positions will be used for followers, and the engine places them depending on current party arrangement.
* Select a position for all other actors (random assignment by default). This is done by assigning a creature or placeable tag into a position marker.
* For each actor position: specify if the actor is active or not. If a position is active then the actor is visible when the dialog is triggered. If the actor is inactive, then he is invisible when the dialog triggers. Functional shots can be used later to show actors entering or leaving dialog. These functional shots will need to use stage cameras and turn actors visible or invisible.

Later, if someone updates a stage template, only the global data is updated on instances. For example: actor assignments and cameras that have been manually moved should remain the same; Actor positions and other cameras might change.

The next step is for the designer to assign a specific stage tag (of instances) for dialog trees. Note that a single dialog file usually has more than one tree, and each one might be assigned a different stage.
When placing a stage, the toolset associates a stage camera for each line in the tree. The toolset will assign cameras if adding new lines into a tree which already has a stage associated with it. This way the user can preview a camera shot of each line.

== The stage in the game ==
Whenever the player clicks on a character to initiate dialog and the initiated dialog is associated with a stage, the game immediately snaps all actors into their positions (with a possible quick fade, we'll first try with no fade), and might turn some of them invisible, if they are inactive.
The game also cleans up the stage area from any other objects that might be inside at the moment by turning them invisible for the duration of the dialog (optional: we may not allow path-finding into stages at all). Then, the game plays each dialog line with the camera that was automatically associated by the toolset.
Note that the dialog is played in-game — ambient creatures that are in the area are still visible and walk around, but they can not enter the stage boundaries. This applies only for creatures that are non-hostile towards any actor in the stage. Hostile creatures (towards actors) are frozen and invisible during the entire dialog.
Designers should still try to avoid having dialogs and combat clash at all.

== Functional Shots ==

=== What is a functional shot? ===
A functional shot is a cinematic procedure that may be attached to a single dialog line. This cinematic procedure has parameters, including at least the participating actor/s. The functional shots are used to display small sections of cinematics that might happen several times during the game. For example: shaking hands, drawing weapons etc'.
The functional shots are also used to control actors getting in and out of stages. For example: we'll have a functional shot called ‘1 actor enters dialog' and when running, it will communicate with the staging system to make the actor visible and use one of the stage cameras to display the actor coming into the stage.
Functional shots should also be used to override the automatic camera selection of the staging system. For example: if the user wants to change a camera's orientation or zoom level.

=== Creating a functional shot ===
Functional shots can be created inside DA's cutscene editor tool. In it, the user creates the cutscene and specifies what aspects of the cutscene should be a parameter:
* All actors are considered parameters always. The user should only number the actors.
* Camera: when flagged as a parameter, the toolset selects a stage camera instead when the functional shot is selected for a line. There can be only 1 camera parameter per functional shot.
* Dialog line: can include up to 1 dialog line, and it will always be considered a parameter. The user will be able to attach a functional shot with a dialog parameter only to dialog line that have spoken text in them.
* Interactive Placeable: for example: if an actor steps through a door.
These shots are supposed to be short and simple (up to 5 seconds). Anything more than that should be considered a full-fledged cutscene.

=== Using a functional shot ===
Functional shots appear in their own palette in the toolset.
The user first selects the name of the functional shot, and then selects the parameters. The toolset automatically picks the speaker as actor #1 and the listener as actor #2, but the user may change these selections. Note that a placeable may also be an actor.
A single functional shot can be associated with any single dialog line that belongs to a staged dialog tree.
A functional shot should know how to communicate with the staging system in order to activate disabled actors and use stage cameras.

==Stage properties==
{{inspector start}}
{{inspector section|General}}
{{inspector row|Comment| }}
{{inspector row|Resource Name| }}
{{inspector row|Tag| A non-unique string identifier used mostly by scripts and other resources to refer to this resource.}}
{{inspector section|Area}}
{{inspector row|Area| Select an existing area and the stage editor will have that area displayed in it, making it easier to place actors and cameras with respect to the scenery. Works best with a stage that's only used in one spot.}}
{{inspector row|Position in Area| Defines the position in the area that the stage's center is located at. The easiest way to find the coordinates of a location is to open the area in the area editor and copy them from an object or waypoint located there. When placing the stage in the area editor, copy these position and orientation properties to make the stage line up exactly the same as it does in the stage editor.}}
{{inspector row|Yaw in Area| The orientation of the stage in the area. }}
{{inspector end}}

==Camera properties==
{{inspector start}}
{{inspector section|General}}
{{inspector row|FOV| The field of view for the camera}}
{{inspector row|Tag| A non-unique string identifier used mostly by scripts and other resources to refer to this resource.}}

{{inspector section|Camera Adjustment}}
{{inspector row|Look At Type| The type of look at adjustment. "None" means that no camera adjustment will be performed (the primary look at target is still used by DOF.) "Simple" adjustment just adjusts the camera up or down based on the average change in height between all its look at targets. "Over-the-shoulder" adjustment adjusts the height based on the looking from place, and the angle based on the primary looking at place. !!"Terrain" isn't mentioned in the tooltip!!}}
{{inspector row|Looking At (Primary)| The primary place that this camera is looking at. This is used by both over-the-shoulder and simple look at. It is also used when applying depth of field. }}
{{inspector row|Looking At (Secondary)| A list of all places being looked at. This is only used by simple look at. }}
{{inspector row|Looking From| This field is used by over-the-shoulder camera adjustment. This is the place whose shoulder is being looked over. }}

{{inspector section|DOF}}
{{inspector row|00.Apply DOF| Whether depth of field will be applied to this camera. }}
{{inspector row|00.Override DOF| If true this camera specifies DOF settings that override the default procedural settings. Otherwise the procedural system will generate reasonable settings based on its parameters.}}

{{inspector section|Location}}
{{inspector row|Orientation| }}
{{inspector row|Position| }}
{{inspector end}}

==Place properties==

{{inspector start}}
{{inspector section|General}}
{{inspector row|Tag| A non-unique string identifier used mostly by scripts and other resources to refer to this resource.}}

{{inspector section|Cameras}}
{{inspector row|Close Up Camera| This camera will be used for automatic close-up shoots of actors standing on this place. See [[Process camera for line]]}}
{{inspector row|Default Camera| This camera will be used by default to look at actors standing on this place. See [[Process camera for line]]}}
{{inspector row|Wide Camera| This camera will be used for automatic wide shots of actors standing on this place. See [[Process camera for line]]}}

{{inspector section|Location}}
{{inspector row|Orientation| }}
{{inspector row|Position| }}

{{inspector section|Visualization}}
{{inspector row|Source| The source object to display in this place for visualization. This property is for visualization only; it is not used beyond the stage editor. }}
{{inspector end}}

[[Category:Stages]]
[[Category:Conversations]]

{{languages|Stage}}

@@ Line 21: / Line 21: @@
 * Настройка установленных камер (резкость, поле зрения и т.п.).
 * Возможность импортировать и редактировать существующие сцены.
-* Возможность определения, импорта, редактирования functional shot (см. ниже) для сцены.
+* Возможность определения, импорта, редактирования функциональных действий (см. ниже) для сцены.
 * Возможность программной компенсации высоты камеры для различной высоты от говоруна к слушателю, для учета расовых различий высоты и рельефа местности различия.
 * Определение границ сцены. Эта информация будет использоваться для предотвращения попадания в сцену ненужных существ. (В противном случае нам придется вручную предотвращать попадание других существ в сцену, а это, скорее всего, не получится).
@@ Line 51: / Line 51: @@
 Всё же разработчики должны избегать одновременного включения диалогов и боевых столкновений.
-== Functional Shots ==
+== Функциональные действия ==
-=== What is a functional shot? ===
+=== Что такое функциональные действия? ===
-A functional shot is a cinematic procedure that may be attached to a single dialog line. This cinematic procedure has parameters, including at least the participating actor/s. The functional shots are used to display small sections of cinematics that might happen several times during the game. For example: shaking hands, drawing weapons etc'.
+Функциональное действие - это маленькие анимации, которые назначаются для реплики диалога. Они используются для показа действий участвующих объектов/субъектов, которые могут использоваться по несколько раз за диалог, например рукопожатие, доставание оружия и т.п.
-The functional shots are also used to control actors getting in and out of stages. For example: we'll have a functional shot called ‘1 actor enters dialog' and when running, it will communicate with the staging system to make the actor visible and use one of the stage cameras to display the actor coming into the stage.
-Functional shots should also be used to override the automatic camera selection of the staging system. For example: if the user wants to change a camera's orientation or zoom level.
+Функциональные действия также используются для показа входа на сцену и выхода актёров. Например, анимация называется "1 actor enters dialog" и когда оно срабатывает, актёр становится видимым с использованием нужной камеры показывается его вход в сцену.
 Functional shots can be created inside DA's cutscene editor tool. In it, the user creates the cutscene and specifies what aspects of the cutscene should be a parameter:
 * All actors are considered parameters always. The user should only number the actors.

@@ Line 10: / Line 10: @@
 По умолчанию, при отсутствии ассоциированой сцены, для диалога используется встроенная сцена "Лицом к лицу".
-В тулсете присутсвует специальный редактор для создания сцен, вызвать который можно открыв имеющуюся либо вновь созданную сцену.
+В тулсете присутствует специальный редактор для создания сцен, вызвать который можно открыв имеющуюся либо вновь созданную сцену.
 Настройка сцены включает в себя:
-* Установка позиции ГГ и иных участников диалога (позиция включает в себя и начальную ориентацию);
+* Установка позиции ГГ и иных участников диалога (позиция включает в себя и начальную ориентацию).
-* Размещение одной или более камер;
+* Размещение одной или более камер.
-* Настройка установленных камер (резкость, поле зрения и т.п.);
+* Настройка установленных камер (резкость, поле зрения и т.п.).
-* The ability to import and edit existing stages to allow for template usability.
+* Сохранение объекта сцены, как одной определенной структуры. Главный аспект, который определяет сцену - количество участвующих актёров, но для того же числа актёров может быть больше шаблонов.
-* Ability to define/import/edit functional shots (see below) for a stage.
-* Ability to compensate cameras procedurally, for varying heights from speaker to listener, to account for racial height difference and terrain differences.
-* Defining the stages borders. This will be used to prevent creatures from stepping into the stage. (Otherwise we'll have to manually prevent creatures from walking in, and that's very likely to fail).
-* Saving the stage object as a one defined structure. The main aspect that defines the stage is the number of NPC actors involved, but there may be more than one template for the same number of NPCs actors.
-−
-[[Image:Stage tutorial 1.png|600px|thumb|center|Простая сцена с двумя позициями и одной камерой]]
 == Использование сцены ==
 Созданная сцена появляется на палитре ресурсов и может быть размещена на локации, после чего можно установить позицию и ориентацию сцены, а также установить для неё удобный тэг (если на локации используется несколько одинаковых сцен). В свойствах сцены на локации необходимо установить видимость объектов, расположенных на самой сцене и на локации.
-[[Image:Stage tutorial 2.png|thumb|300px|center|Размещение сцены на локации происходит с помощью редактора {{ulink|area|локаций}}. Обратите внимание как одна из позиций перекрывает говоруна, что позволит избежать перемещения говоруна на новое место при инийиализации сцены (начало разговора).]]
+<gallery>
-The user then adjusts the following setting on the stage <b>instance</b>:
+Позже, если шаблон сцены будет изменён, обновляются только глобальные данные. Например: заданные действия актеров и камер, которые были заданы на сцене, установленной в локации, останутся без изменений, а позиции актёров и камер, изменятся.
-* Select a position for the player (default is node #1)
+Для реплик, подчинённых реплике с установленной сценой, эти данные наследуются, он их можно изменить.
-* Select a position for the conversation owner (default is node #2)
-* Select follower positions (default nodes #3, #4 and #5). Note: the player can not select a specific follower in a specific node &mdash;  he just selects what positions will be used for followers, and the engine places them depending on current party arrangement.
-* Select a position for all other actors (random assignment by default). This is done by assigning a creature or placeable tag into a position marker.
-* For each actor position: specify if the actor is active or not. If a position is active then the actor is visible when the dialog is triggered. If the actor is inactive, then he is invisible when the dialog triggers. Functional shots can be used later to show actors entering or leaving dialog. These functional shots will need to use stage cameras and turn actors visible or invisible.
-Later, if someone updates a stage template, only the global data is updated on instances. For example: actor assignments and cameras that have been manually moved should remain the same; Actor positions and other cameras might change.
+== Сцена в игре ==
-The next step is for the designer to assign a specific stage tag (of instances) for dialog trees. Note that a single dialog file usually has more than one tree, and each one might be assigned a different stage.
+Всякий раз, когда инициируется диалог, связанный со сценой, игра немедленно снимает всех участников в их позициях, за исключением не нужных, которые делаются невидимыми. Игра также очищает область сцены от любых других объектов, которые могут находиться внутри в данный момент, сделав их невидимыми на время диалога. Впоследствии игра проходит по линиям реплик в диалоге, используя ассоциированные камеры.
-When placing a stage, the toolset associates a stage camera for each line in the tree. The toolset will assign cameras if adding new lines into a tree which already has a stage associated with it. This way the user can preview a camera shot of each line.
-== The stage in the game ==
+Обратите внимание, что во время диалога окружающие объекты, которые находятся вне области сцены, видны и продолжают жить своей псевдожизнью, но войти в область сцены они не смогут (напомним, нужные границы устанавливаются в редакторе сцен). Это применимо только для существ, которые не являются враждебными по отношению к любому актеру в сцене. Враждебные существа будут заморожены и невидимы в течение всего диалога.
-Whenever the player clicks on a character to initiate dialog and the initiated dialog is associated with a stage, the game immediately snaps all actors into their positions (with a possible quick fade, we'll first try with no fade), and might turn some of them invisible, if they are inactive.
+Всё же разработчики должны избегать одновременного включения диалогов и боевых столкновений.
-The game also cleans up the stage area from any other objects that might be inside at the moment by turning them invisible for the duration of the dialog (optional: we may not allow path-finding into stages at all). Then, the game plays each dialog line with the camera that was automatically associated by the toolset.
-Note that the dialog is played in-game &mdash;  ambient creatures that are in the area are still visible and walk around, but they can not enter the stage boundaries. This applies only for creatures that are non-hostile towards any actor in the stage. Hostile creatures (towards actors) are frozen and invisible during the entire dialog.
-Designers should still try to avoid having dialogs and combat clash at all.
 == Functional Shots ==
@@ Line 70: / Line 73: @@
-==Stage properties==
+==Свойства сцены==
 {{inspector start}}
 {{inspector section|General}}