caa30e12

Guide
- Agents and actions
- Authoring a behaviour tree
- Behaviour trees
- The blackboard
- The AI debugger
- Environment queries
- GOAP
- Perception
- Sensors
- Utility
- Nodes over the world
- Move sets
- Pose constraints
- The variation harness
- Getting content into a running game
- Fuzzing a format that has a grammar
- Symbols
- Component defaults
- Components
- Entity queries
- Booleans and handoff
- The editing pipeline
- Editor scripts
- Element selection
- Face materials
- Foliage mode
- The frame panel
- Icons
- The editor shell
- Inspectors in markup
- Editable meshes in a scene
- Editor modes
- Building to a number
- Scene menus
- The shape tool
- Snapping
- Sub-object picking
- Sculpt and paint mode
- Water mode
- Writing an editor plugin
- Block-out shapes
- Booting an application
- Floating things on water
- Character movement
- Editable meshes
- Growing a forest
- Foliage instances
- Grass
- Mesh booleans
- Mesh operations
- Mesh surfaces
- Networked players
- Players and possession
- Splines
- Terrain brushes
- The terrain heightfield
- Painting a terrain
- Sculpting a heightfield
- Where the water surface is
- Saving and restoring a world
- Leashing and spawn tables
- Attributes and the modifier algebra
- Chat channels, routing and moderation
- Collections, achievements and transmog
- Abilities and damage
- Definitions and the content walk
- Dynamic events and world bosses
- Currencies, vendors, trade, mail and the auction
- Effects
- Gameplay events
- Player housing
- Dungeons, raids and lockouts
- Interactables, gathering and crafting
- Inventory and the container algebra
- Items
- Authoring a loot table
- Loot tables
- Gameplay modules
- Mounts and vehicles
- Levels, talents and reputation
- Arenas, battlegrounds and objectives
- The quest and event-chain editor
- Quests, stages and objectives
- Gameplay randomness
- Requirements
- Weapons and hit claims
- Parties, guilds, friends and presence
- Gameplay tags
- Maps, discovery and travel
- Admission, health and the control plane
- Durable state and the ledger
- The gameplay bridge
- Matchmaking, queues and ratings
- Placing players
- Placing realms
- Shards, keys and specs
- The cluster
- The live verbs, at three in the morning
- The service plane
- Transfer tickets
- Transferring players
- Upgrading a fleet
- Writing a realm
- Choosing a frame
- Drawing foliage
- The ambient split, and the nodes that fill it
- Drawing grass
- Impostors
- Culling and streaming instances
- Turning on dynamic global illumination
- The look profile
- Meshes and materials, type by type
- Drawing particles
- Lighting a scene in lux and lumens
- Making a room look different
- The post-processing node kinds
- Tracing rays against the scene's own triangles
- A pass that reads the frame so far
- Render quality presets
- Making everything cast a shadow
- The Standard Frame
- Drawing a terrain
- Streaming texture mip tails
- Fog a shadow can fall through
By kind
- Components48
- Systems55
- Controls169
- Shaders63
- Graph nodes64
- Importers28
- Annotations45
- Diagnostics8
- Log events69
All namespaces315
Releases1

QueryResults

class

Core/Vixen.Ai/Queries/QueryPoint.cs:60

csharp

public sealed class QueryResults

The working set of one query run: the points, their scores, and every factor behind them.

Read the guide page for this →

Remarks

⚠ Reused between runs rather than allocated per run, which is the difference between an environment query being affordable on a schedule and being a thing projects turn off. A query generating four hundred points over a dozen agents is a list of four hundred structs, cleared and refilled; a run that allocated would allocate that much per agent per interval.

The per-factor detail is optional and off unless Detailed is set. It is what the editor's preview table and the debug overlay read — why is this point worse than that one — and it is points × tests floats, which is exactly the cost nobody wants to pay in a shipped build.

Fields and properties (8)

public int Count
How many points there are.
public ReadOnlySpan<ScoredQueryPoint> Points
Every point, in the order the generators made them.
public int Factors
How many factors each point recorded, or zero when nothing was recorded.
public bool Detailed
Whether the per-factor detail is kept.
public Symbol Query
Which query produced this.
public int Generated
How many points a generator made before anything was filtered.
public int Surviving
How many survived every filtering test.
public int Best
The index of the best point, or -1 when nothing survived.

Methods (3)

public bool TryBest(out QueryPoint point)
The best point, if there is one.
public ReadOnlySpan<float> DetailOf(int index)
What one point's factors read, when the detail was kept.
public void Clear()
Forgets everything, keeping the room it was in.

Used by (13)

EnvironmentQueryVixen.Ai
QueryContentTestsVixen.Ai.Tests
QueryPreviewVixen.Ai.Diagnostics
QueryPreviewTestsVixen.Ai.Diagnostics.Tests
QueryRunnerVixen.Ai.Nodes
QueryScorerExitCriteriaTestsVixen.Ai.Tests
QueryTestPurposeTestsVixen.Ai.Tests
RunQueryServiceVixen.Ai.Nodes
RunQueryTaskVixen.Ai.Nodes
WorldQueryTestsVixen.Ai.Nodes.Tests
QueryDocumentVixen.Editor.AssetEditors
QueryDocumentTestsVixen.Editor.AssetEditors.Tests
QueryViewVixen.Editor.AssetEditors