Scribd Logo
Încărcați

Bine ați venit la Scribd!

  • Halo Behaviour Tree AI

    Încărcat de

    Juancho Carrillo
    873 vizualizări25 pagini
    This document discusses the evolution of behavior tree AI used in the Halo video game series. It describes how Bungie Studios optimized behavior trees over five years and three game iterations. Key changes included removing rare stimulus behaviors to simplify trees, using behavior masks and inhibitions to selectively enable behaviors, improving how knowledge is maintained between behaviors, and moving concepts like vehicles out of the behavior tree for better coordination. The behavior trees evolved from a dynamic structure in Halo 2 to a more static structure in Halo 3 using these masks and stimuli to selectively control behaviors. The document suggests the behavior trees have become like a "blackboard" system and proposes formalizing information concepts and improving the GUI representation.

    Descriere originală:

    EVOLVING HALO’SBEHAVIOUR TREE AI Max Dyckhoff Bungie Studios maxd@microsoft.

    Drepturi de autor

    © © All Rights Reserved

    Formate disponibile

    PDF, TXT sau citiți online pe Scribd

    Vi se pare util acest document?

    Este necorespunzător acest conținut?

    Raportați acest document
    This document discusses the evolution of behavior tree AI used in the Halo video game series. It describes how Bungie Studios optimized behavior trees over five years and three game iterations. Key changes included removing rare stimulus behaviors to simplify trees, using behavior masks and inhibitions to selectively enable behaviors, improving how knowledge is maintained between behaviors, and moving concepts like vehicles out of the behavior tree for better coordination. The behavior trees evolved from a dynamic structure in Halo 2 to a more static structure in Halo 3 using these masks and stimuli to selectively control behaviors. The document suggests the behavior trees have become like a "blackboard" system and proposes formalizing information concepts and improving the GUI representation.

    Drepturi de autor:

    © All Rights Reserved
    Descărcați ca PDF, TXT sau citiți online pe Scribd
    Indicator pentru conținut neadecvat
    873 vizualizări25 pagini

    Halo Behaviour Tree AI

    Încărcat de

    Juancho Carrillo
    This document discusses the evolution of behavior tree AI used in the Halo video game series. It describes how Bungie Studios optimized behavior trees over five years and three game iterations. Key changes included removing rare stimulus behaviors to simplify trees, using behavior masks and inhibitions to selectively enable behaviors, improving how knowledge is maintained between behaviors, and moving concepts like vehicles out of the behavior tree for better coordination. The behavior trees evolved from a dynamic structure in Halo 2 to a more static structure in Halo 3 using these masks and stimuli to selectively control behaviors. The document suggests the behavior trees have become like a "blackboard" system and proposes formalizing information concepts and improving the GUI representation.

    Drepturi de autor:

    © All Rights Reserved
    Descărcați ca PDF, TXT sau citiți online pe Scribd
    Indicator pentru conținut neadecvat
    din 25

    EVOLVING HALOS

    BEHAVIOUR TREE AI

    Max Dyckhoff
    Bungie Studios
    maxd@microsoft.com

    INTRODUCTION
    Weve spent five years living with behaviour
    trees, and have learned how to optimise them.
    Darwinian approach to choosing features.

    STIMULUS BEHAVIOURS
    BEHAVIOUR MASKS
    MAINTAINING KNOWLEDGE
    LEFTOVERS
    REVIEW

    STIMULUS BEHAVIOURS
    Problem: Rare event-driven behaviours tested
    for every tick.
    Halo 2: Behaviors or impulses dynamically
    and asynchronously placed into tree at
    specified location.

    STIMULUS BEHAVIOURS
    Retreat

    Stimuli

    Flee
    Kamikaze
    Cower

    Leader Killed

    Leader Dead

    Grenade stuck
    Combat
    Root

    Self preserve
    Engage

    Problem: Complicates understanding of behaviour tree,


    makes it harder to debug the tree, and its really messy to
    implement.
    Halo 3: Cut stimulus behaviours.

    STIMULUS ACTIVATION
    Retreat

    Flee

    Stimuli

    Blind panic

    Kamikaze
    Cower

    Leader Killed

    Berserk

    Grenade stuck
    Leader Dead
    Combat
    Root

    Self preserve
    Engage

    Behaviour Group Child Declaration


    CHILD_ENTRY( <behaviour_name>, CHECK_STIMULUS( <stimulus_name>))

    STIMULUS BEHAVIOURS
    BEHAVIOUR MASKS
    MAINTAINING KNOWLEDGE
    LEFTOVERS
    REVIEW

    BEHAVIOUR MASKS
    Problem: Want to be able to remove certain
    behaviours from the tree in some situations.
    Halo 2: Styles were used to mask behaviours.
    One style per character
    Open ended designer specified customization

    BEHAVIOUR MASKS
    Problems:
    Designers dont understand the behaviour tree
    Players dont recognise the subtlety!

    Halo 3: Give encounters attitude.


    Timid, Normal and Aggressive styles
    Modify behaviour parameters based on attitude

    INHIBITIONS
    Designer

    Combat

    Grenades
    Vehicle

    Self preserve

    Grenade

    Engage

    Fight
    Vehicle fight

    Grenades
    Vehicles
    Root

    Enter vehicle

    Actor
    Berserking
    Berserk

    Flee
    Cower
    Retreat

    Grenade

    Behaviour Declaration
    BEHAVIOUR( <behaviour_name>, INHIBIT( <inhibition_name> | <inhibition_name_2>))

    STIMULUS BEHAVIOURS
    BEHAVIOUR MASKS
    MAINTAINING KNOWLEDGE
    LEFTOVERS
    REVIEW

    MAINTAINING KNOWLEDGE
    We have learned what information is
    appropriate to store in the tree and what is
    not.
    Halo 2:
    Search state of targets was persistent
    Vehicle attachment was transient

    MAINTAINING KNOWLEDGE
    Problem: Vehicle attachment in stack
    Forget about vehicle when entry is interrupted
    Hard to co-ordinate multiple actors
    Enter vehicle

    Flip vehicle

    Pickup actor

    Actor
    Behaviour
    Vehicle
    Vehicle

    Vehicle

    Vehicle

    Seat

    Seat

    Seat

    Entry point

    Entry point

    Entry point

    Behaviour State Stack


    t

    MAINTAINING KNOWLEDGE
    Introduced vehicle concept.
    The vehicle structure, stored in the actor
    Attachment and detachment impulses
    Entry and exit behaviours

    Benefits:
    Much more robust
    Better overall designer control
    Tight scripting integration

    STIMULUS BEHAVIOURS
    BEHAVIOUR MASKS
    MAINTAINING KNOWLEDGE
    LEFTOVERS
    REVIEW

    JOINT BEHAVIOURS
    Problem: Intelligent AI need to co-operate.
    Halo 2: Post invitations to other actors to
    participate in a Joint Behaviour.
    Halo 3: Multiple mechanisms
    Concepts
    E.g. Vehicle concept and higher level co-ordination

    Stimuli
    E.g. Combat synchronisation

    ARGUMENTS TO BEHAVIOURS
    Provide some context in which a behaviour is
    running.
    Cover: Why am I covering?

    Allow reuse of behaviours.


    Post combat: Goto behaviour.

    IMPULSES FOR CONTROL


    Growing tendency to use impulses to control
    aspects of the character.
    Go berserk
    Turn on active camouflage
    Control movement speed

    When coupled with behaviour masks, this is


    very powerful.

    STIMULUS BEHAVIOURS
    BEHAVIOUR MASKS
    MAINTAINING KNOWLEDGE
    LEFTOVERS
    REVIEW

    REVIEW
    Used to be a very dynamic behaviour tree.
    Stimuli inserted new behaviours

    Now its a static structure with lots of masks.


    Inhibitions, stimuli, styles

    Moved some concepts out of the tree.


    Vehicles, posturing

    WHAT HAVE WE CREATED?

    World View

    ITS A BLACKBOARD!
    Arbiter

    KS
    KS
    KS

    KS
    Blackboard
    KS
    KS

    WHERE NOW?
    Formalise information concepts.
    Common interface
    Easier to add new behaviour and perception

    GUI representation.
    More transparent for designers and debugging

    THE END

    Max Dyckhoff
    Bungie Studios
    maxd@microsoft.com

    S-ar putea să vă placă și