If you have a walk cycle in Blender (Action Editor), the plugin should bake that animation to a series of keyframes that the Rad runtime can interpret. Without this, your character will be a T-pose statue.
Unlike flat STL exports, the 3D RAD Exporter maintains the scene graph. If a "Room" object contains a "Table" object, the RAD file reflects this hierarchy. This allows the simulation engine to perform efficient spatial partitioning (Bounding Volume Hierarchies), significantly speeding up ray-tracing calculations.
You build a custom element (DLL) that sits in the 3D Rad project folder. When the project runs, the DLL reads the raw file (e.g., model.fbx) and generates the mesh in memory.
This guide focuses on Approach B (The Runtime Loader), as it functions as a true "Plugin." 3d rad exporter plugin
You build a standalone executable that reads a file (e.g., a Blender export) and converts it into a proprietary file format that your custom 3D Rad element reads.
There are two ways to build an "Exporter Plugin":
The most famous tool in this niche is not a single plugin but a collection of scripts often referred to collectively as the "3D Rad Exporter" or "Rad Exporter Plugin." Originally developed by community members like Micheus and Vidi, these scripts bridge Autodesk 3ds Max and Blender to the 3D Rad runtime. If you have a walk cycle in Blender
The proprietary .rad output is an ASCII or binary file structure organized hierarchically.
Structure Overview:
HEADER Version: 3.1 Units: cm Global_Offset: [x, y, z]MATERIAL_LIB Mat_01 Name: "Concrete", Density: 2.3, Z_Eff: 14 Mat_02 Name: "Steel", Density: 7.8, Z_Eff: 26 This guide focuses on Approach B (The Runtime
GEOMETRY_HIERARCHY Volume_001 Type: Mesh Material: Mat_02 Vertices: [...] Triangles: [...] Transform: [Matrix 4x4]