Skip to content
Brass Orrery

Orrery Terrain · OrreryTerrain module · struct

FOrreryTerrainRvtStatus

What the terrain's colour runtime virtual texture is doing (UOrreryTerrainSubsystem::GetRvtStatus).

Declaration

USTRUCT(BlueprintType)
struct FOrreryTerrainRvtStatus
Blueprint Make and Break Orrery Terrain Rvt Status
The graph as text
  1. Break Orrery Terrain Rvt Status (structure)
    • In Orrery Terrain Rvt Status (OrreryTerrainRvtStatus): not connected
    • Out Active (Boolean): not connected
    • Out Pending Invalidations (Integer): not connected
    • Out Settling (Boolean): not connected
    • Out Boosting (Boolean): not connected
    • Out Seconds Since Activity (Float): not connected
    • Out Uploads Per Frame (Integer): not connected
Header
#include "OrreryTerrainSubsystem.h"
Module
PublicDependencyModuleNames.Add("OrreryTerrain"); in your module’s Build.cs.
Stability
Stable: changes within a major version only add.
Thread
Game thread only. (the header’s rule)
Blueprint
“Orrery Terrain Rvt Status”, a Blueprint type

Description

Experimental in v1.0.

The engine exposes no public count of the RVT pages still to be produced, so this reports the terrain's own reasons for pages to be produced: edits waiting to invalidate, an edit's settle, and the upload boost that follows the RVT's start, a change of its resident set and a view jump (r.OrreryTerrain.Rvt.Boost*). Each lasts some seconds after its last event, enough for the raised upload budget to produce what the view asks for in the cases measured; a view that turns without moving, or a scene that asks for more pages than that, can still show pages being produced after IsRvtIdle turned true.

Properties

NameTypeDefaultMeaning
bActiveBlueprintReadOnlyboolfalse

The terrain draws through its colour RVT (the heightfield tier in Read mode).

False: the rest is zero, and the RVT is idle.

PendingInvalidationsBlueprintReadOnlyint320

Changed rectangles of edits still waiting to invalidate their RVT pages.

bSettlingBlueprintReadOnlyboolfalse

An edit's settle runs: its pages are being drawn again, until a few seconds after its last invalidation.

bBoostingBlueprintReadOnlyboolfalse

The upload boost runs: the RVT began, its resident set changed or the view jumped, within the last few seconds.

SecondsSinceActivityBlueprintReadOnlyfloat0.f

Seconds since the settle or the boost was last started or extended; 0 while either runs.

UploadsPerFrameBlueprintReadOnlyint320

Virtual texture pages the engine may upload per frame now (VirtualTextureScalability::GetMaxUploadsPerFrame): the editor's budget in the editor and PIE, else r.VT.MaxUploadsPerFrame with the terrain's raise, when it made one.

Blueprint