🧰
Developer
  • ENGAGE SDK overview
  • Setting up the ENGAGE SDK
    • Registering as an ENGAGE developer
    • Setting up your local git repository
    • Installing the Unity Editor
    • Opening the ENGAGE SDK Unity project
    • Checking for SDK updates
    • Installing a platform build module
  • ENGAGE SDK project folders
  • General guidelines for 3D models
    • Optimizing 3D models
  • Locations
    • Guidelines for locations
    • Creating a new location
    • Building a location bundle
    • Testing a location locally on Windows
    • Configuring an object as a teleport target
    • Configuring the start position
    • Seats
      • Creating a seat
      • Using the summon to seat system
    • Network states
      • Network State Manager
      • Location Network States
      • Example network state configurations
        • Network state toggle object
        • Network state animation start/stop
        • Network state change animation
          • Creating an animation in Unity
          • Using Animator.Play(string)
          • Defining Animator transitions
          • Using Animator.SetTrigger(string)
        • Network state sync animation
        • Network state position toggle
        • Network state automatic door
        • Network state toggle skybox
        • Network state change materials
    • Adding grabable objects to a location
      • Resetting network objects with a button
      • Resetting network objects when out of bounds
    • Locations reference information
      • Basic requirements for a location
  • Immersive Effects (IFX)
    • Guidelines for IFX
    • Creating an IFX
    • Building an IFX bundle
    • Testing IFX locally on Windows
    • Specialized IFX
      • Animated IFX
        • Animation overrides
          • Legacy animations
          • Animator animations
          • Configuring additional Effect Life Run Control properties
      • Audio IFX
      • Interactive IFX
  • List of available prefabs
  • Available scripts
    • External Video Player
  • Profiling
  • Publishing to ENGAGE
    • Publishing checklists
    • Pushing files to your GitHub repository
  • AFX
    • Getting started
      • Changelog
    • AFX Graphs
      • Creating an AFX graph
      • Editing an AFX graph
      • Navigation and keyboard shortcuts
      • Adding an AFX graph to a game object
      • Nodes
      • Ports
      • Connections
      • Flows
        • Starting a flow
        • Using multiple flows
        • Chaining flows
        • Controlling flows
      • References
      • Using AFX Events
    • Networking AFX
      • Network State Modules
      • Ownership of networked objects
    • Animation curves
    • Node dictionary
      • ENGAGE
        • AFX Companion
          • Constant Collision
          • Grab Object
          • PathData
        • Networking
          • Network State Modules
        • Physics
        • Player
        • Seat
      • Events
        • Collision
        • Unity
        • AFX Events
      • Flow
      • Reference
      • Unity
        • Component
          • Animation
            • Set Parameters
          • Audio
            • Audio Reverb Zone
            • Audio Source
          • Collider
          • FX
          • Rendering
            • Camera
            • Light
            • Material
          • UI
        • Constraint
        • GameObject
        • Input
        • Physics
          • Raycast
            • Layer Mask
          • RigidBody
            • Joint
              • Hinge
              • Spring
          • Wheel Collider
        • Time
        • Transform
          • Get
          • Set
          • Space Switching
      • Variable
        • Bool
        • Comparison
        • Float
        • Int
        • List
        • Math
          • MathF
        • String
        • Unity Component
        • Vector
          • Quaternion
          • Vector2
          • Vector 3
            • Vector3 Math
    • Sample graphs
Powered by GitBook
On this page
  1. AFX
  2. Node dictionary
  3. Variable

Comparison

PreviousBoolNextFloat

Last updated 7 months ago

You can use comparison nodes to compare two values. The output is a Boolean value that indicates whether the comparison is true or false.

Not all data types are valid inputs for all comparison nodes. For example, you can use an Equal node to determine if two Vector3 objects are equal - i.e. x, y, and z components are equal. However, it's not meaningful to check if one Vector3 is less than another.

If you want to compare the magnitude of two Vector3 objects, or perform other comparisons, see the Vector 3 section of the node dictionary.

If you connect invalid inputs to a comparison port, the node will display an Unsupported Types message.

Available comparison nodes

Name
Comparison
Description

Equal

A == B

Outputs true if A is equal to B.

Greater Than

A > B

Outputs true if A is greater than B. Compatible with integers and floats only.

Greater Than Equal

A >= B

Outputs true if A is greater than B, or if A is equal to B. Compatible with integers and floats only.

Less Than

A < B

Outputs true if A is less than B. Compatible with integers and floats only.

Less Than Equal

A <= B

Outputs true if A is less than B, or if A is equal to B. Compatible with integers and floats only.

Not Equal

A != B

Outputs true if A is not equal to B.

Inputs:

Name
Type
Description

A

<varies>

The value to compare with B.

B

<varies>

The value that A is compared with.

Outputs:

Name
Type
Description

Output

Boolean

True if the comparison is true. False otherwise.

Invalid data type inputs