02b45cc4

Guide
- Move sets
- Pose constraints
- The variation harness
- Getting content into a running game
- Components
- Entity queries
- Booleans and handoff
- The editing pipeline
- Element selection
- Face materials
- Foliage mode
- Icons
- The editor shell
- Editable meshes in a scene
- Editor modes
- Building to a number
- Scene menus
- The shape tool
- Snapping
- Sub-object picking
- Sculpt and paint mode
- Writing an editor plugin
- Block-out shapes
- Booting an application
- 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
- Saving and restoring a world
- Admission, health and the control plane
- Durable state and the ledger
- Placing players
- Placing realms
- Shards, keys and specs
- The cluster
- The service plane
- Transfer tickets
- Transferring players
- Upgrading a fleet
- Writing a realm
- Drawing foliage
- Drawing grass
- Impostors
- Culling and streaming instances
- Turning on dynamic global illumination
- 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
- Making everything cast a shadow
- Drawing a terrain
By kind
- Components39
- Systems48
- Controls165
- Shaders48
- Graph nodes64
- Importers22
- Annotations45
- Diagnostics8
- Log events64
All namespaces275
Releases1

MemoryProviders

class

Editor/Vixen.Editor.Profiler/MemorySnapshot.cs:50

csharp

public sealed class MemoryProviders

Where the memory view's numbers come from, for the arenas this assembly cannot see into.

No guide page documents this yet — the page shows what the code says about itself.

Remarks

⚠ Two delegates rather than two references, and the reason is layering. GPU heap usage is the graphics backend's — VK_EXT_memory_budget on Vulkan, residency on D3D12 — and asset residency is the editor's asset database. A profiler assembly that referenced both would be a panel that cannot be tested without a device and a project on disk, which is the bargain every other model here refuses to make.

Fields and properties (2)

public Func<IEnumerable<MemoryRow>>? Gpu
What the GPU's heaps report, or where nothing can say.
public Func<IEnumerable<MemoryRow>>? Assets
What is resident, or .

Used by (5)

DiagnosticsModuleVixen.Editor.Diagnostics
EditorApplicationVixen.Editor.App
MemorySnapshotVixen.Editor.Profiler
MemoryViewVixen.Editor.Profiler
StatisticsAndMemoryTestsVixen.Editor.Profiler.Tests