rdInst Manual version 1.50

Last updated 11th April 2025

Section 1. Introduction

Welcome to rdInst, a plugin that provides Handling of InstancedStaticMeshes, Spawned Actors and Niagara Effects, Auto-Instancing,Prefabs, very configurable Streaming, Proxies, Procedural Population, and Runtime Splines.

The main features of this plugin are:

  • Fast ISM and HISM instances, managed or unmanaged.
  • Managed Spawning of Actors and Niagara systems, even from the Construction Script.
  • Auto-Instancing at Runtime for very easy-to-use instancing, proxies and pickups.
  • Fast, highly programmable, configurable and randomizable Prefabs.
  • Proxy Actors that swap in full actors from instances in the level when you get close (full state saving).
  • A Spawning system that spawns Instances, Actors and Niagara systems (pooled and/or distributed over frames) – even spawn more Spawning actors to create very optimized and simple large scale worlds. Load-On-Demand.
  • A powerful Procedural Population Actor
  • Spherical and Frustum based fast entity population system.
  • Mass Movement system (coming soon)
  • Mass Physics system (coming soon)
  • Fast integrated PickUp system with powerful Highlighting.
  • Support for PCG with custom spawner nodes.
  • Runtime Spline creation and manipulation.
  • A lot of utility functions for Scalability, Construction optimization, Runtime instance to Proxy scan data conversion etc.

To use this plugin, just enable it (defaults to enabled) – all the tools will be available.

Note: If you’re here for the auto-instancing, all you need to do is select rdInstSettings from the outliner and tick the “Enable Auto-Instancing” box – that’s your reading for the day done.

Version 1.43 adds a couple of Editor Only features – the first is an about window (available in the Main Tools menu) and an Instance Settings window in the Content Browser Context menu.

If you’re using the runtime features of rdInst, the plugin will be needed for your packaged builds, but is small and quite portable.

The Manager uses UHierarchicalInstancedStaticMeshComponents (HISMCs) or UInstancedStaticMeshComponents (ISMCs) via a bool in rdInstBaseActor. You can set that and the type of instance removal (remove or recycle) with the rdSetUpInst() node or method.

The preferred type used to be (and up until 5.4 still is) HISMCs as they have a unique way of removing Instances which makes them faster to manage, without any apparent overhead. With Nanite though, the preferred is ISMs, and as of UE5.3, they also have the instance index “swapping” that HISMs have.

rdInst defaults to recycling instances rather than removing which allows you to know that the instance indexes will always be correct – it also provides a number of speed benefits.

For detailed information on each of the Nodes and C++ functions, you can read up on them in the rdInst Reference Manual.

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25