/
transition

transition

Owned by 4A Games
Sept 29, 2022

Overview

The main part of the AS is an object that allows you to confirm whether there is a path between blocks A and B.

This is based on the blender, therefore it shares a certain number of its properties (because it blends blocks A and B during the transition between them).


Properties

Transition

A parameter setup section consists of:

  • Param – the skeleton parameter name (skeletons have parameters that can be controlled by the code or scripts via specialized blocks).
  • Op – the operation that is to be performed with this parameter.
  • Type – expected value type.
  • Value – the value to compare with.
  • Precision – required precision.
TimeBlend time when following through with the transition.
ForceForced transition. If the script reaches a block with such a transition, an attempt to follow it is taken immediately. The only way to stop it from happening is to use the parameters.
WeightThe transition’s weight, required for controlling accessibility for the requests. When searching, it will tally up the weight of all elements to be chained through as it moves from the current position to the target.
Condition
Request

A request essentially is an instruction to "carry out the transition with this name". Next, a search is conducted for transitions including the named request in their Request field, and then a path is plotted to the one with the nearest weight.

OR Mode

OR logic is applied to the block's parameters.

The transitions can be parametric. Before the transition, several conditions are checked. This applies ONLY to passing through with the transition. The parameters are disregarded when searching for requests.

ProgressShows current progress.
Current TimeShows the current time.
Raw ModeJust another way of representing the parameters in the output.
Param CountThe number of parameters. When added, sections for setting up these parameters will appear.
Events
EventsSame as in blender.





Max Wait Time
Just check if Next Event in Events
Just check if Next Event NOT in Events
Signals

The signals are just like the ones used in blenders.
On Eval

When a transition is attempted (almost unused).

On StartAt the start.
On Stop At the end.
On this page:

 

Related content

AS Editor How To's
AS Editor How To's
Exodus SDK
More like this
blender
blender
Exodus SDK
More like this
motion
motion
Exodus SDK
More like this
random_transition
random_transition
Exodus SDK
More like this
Main window (AS Editor)
Main window (AS Editor)
Exodus SDK
More like this
bone part
bone part
Exodus SDK
More like this

Exodus SDK © 2005-2023, 4A Games Limited. Developed by 4A Games®.
4A Games® is a registered trademark, and 4A Games Limited, Exodus SDK and their respective logos are trademarks of 4A Games Limited.
Published by Deep Silver. Deep Silver is a division of PLAION GmbH, Austria. Deep Silver and Plaion are registered trademarks of PLAION GmbH.
Metro Exodus is inspired by the internationally best-selling novels METRO 2033 and METRO 2034 by Dmitry Glukhovsky.
All other trademarks, logos and copyrights are property of their respective owners. All rights reserved.
By using this site, downloading or using the Exodus SDK or related content, you are agreeing to be bound by the terms of the End User License Agreement.

EULA