Loading

3d Rad Exporter Plugin

3d Rad Exporter Plugin

A professional exporter plugin is defined by its usability. Within the host application (e.g., a Maya Python plugin or a Blender add-on), the developer must provide a modal dialog with the following controls:

Error handling is critical. If the exporter encounters a mesh with more than 65,535 vertices (the limit for 16-bit indices in 3D Rad), it must either split the mesh into sub-meshes or warn the user to reduce geometry. Without this, the exported file will trigger a silent memory overflow in the 3D Rad runtime.

Before we discuss the plugins, we must understand the problem. 3D Rad utilizes proprietary file extensions (typically .rad, .x or custom binary formats). The base installation includes a handful of sample models, but these are rarely sufficient for a commercial or serious hobby project.

You have three options to get custom models into 3D Rad:

The plugin method is the only professional solution. It automates the conversion of normals, UV unwraps, texture paths, and (crucially) hierarchy data.

If you want to build a "3D Rad Exporter" for a specific software (like Blender), do not build a 3D Rad plugin. Build a Blender Python Add-on. 3d rad exporter plugin

Why? 3D Rad imports standard formats (OBJ, X, 3DS). If you write a plugin that exports to these formats from Blender/Maya, 3D Rad will automatically accept them.

Step-by-Step for a Blender Exporter:


Scenario: A medical physics team needs to simulate a linear accelerator bunker.

Traditional Method:

Using 3D RAD Exporter:


Goal: Export 3D models and scenes from common DCC tools (Blender/Maya/3ds Max) into the 3D Rad engine format (.rad or engine-specific package), preserving geometry, materials, lights, animations, and scene hierarchy with minimal user setup.

To illustrate the power of the exporter plugin, let's walk through a real-world scenario.

Goal: Export a fully textured, drivable car with rotating wheels and a glass shader.

Step 1: Model in Blender

Step 2: Set up the hierarchy

Step 3: Apply materials

Step 4: Use the 3D Rad Exporter Plugin

Step 5: In 3D Rad

Result: Within 10 minutes of exporting, the car drives with full physics, reflections, and collisions—all thanks to a functioning exporter plugin.

Modern radiation transport codes (such as MCNP, GEANT4, or proprietary RAD engines) require highly specific geometry definitions. These engines typically rely on Constructive Solid Geometry (CSG) or boundary-representation (BREP) meshes. A professional exporter plugin is defined by its usability

However, designers and engineers typically work in high-end 3D modeling software (e.g., Blender, Maya, SolidWorks). Exporting from these environments often results in:

A professional exporter plugin is defined by its usability. Within the host application (e.g., a Maya Python plugin or a Blender add-on), the developer must provide a modal dialog with the following controls:

Error handling is critical. If the exporter encounters a mesh with more than 65,535 vertices (the limit for 16-bit indices in 3D Rad), it must either split the mesh into sub-meshes or warn the user to reduce geometry. Without this, the exported file will trigger a silent memory overflow in the 3D Rad runtime.

Before we discuss the plugins, we must understand the problem. 3D Rad utilizes proprietary file extensions (typically .rad, .x or custom binary formats). The base installation includes a handful of sample models, but these are rarely sufficient for a commercial or serious hobby project.

You have three options to get custom models into 3D Rad:

The plugin method is the only professional solution. It automates the conversion of normals, UV unwraps, texture paths, and (crucially) hierarchy data.

If you want to build a "3D Rad Exporter" for a specific software (like Blender), do not build a 3D Rad plugin. Build a Blender Python Add-on.

Why? 3D Rad imports standard formats (OBJ, X, 3DS). If you write a plugin that exports to these formats from Blender/Maya, 3D Rad will automatically accept them.

Step-by-Step for a Blender Exporter:


Scenario: A medical physics team needs to simulate a linear accelerator bunker.

Traditional Method:

Using 3D RAD Exporter:


Goal: Export 3D models and scenes from common DCC tools (Blender/Maya/3ds Max) into the 3D Rad engine format (.rad or engine-specific package), preserving geometry, materials, lights, animations, and scene hierarchy with minimal user setup.

To illustrate the power of the exporter plugin, let's walk through a real-world scenario.

Goal: Export a fully textured, drivable car with rotating wheels and a glass shader.

Step 1: Model in Blender

Step 2: Set up the hierarchy

Step 3: Apply materials

Step 4: Use the 3D Rad Exporter Plugin

Step 5: In 3D Rad

Result: Within 10 minutes of exporting, the car drives with full physics, reflections, and collisions—all thanks to a functioning exporter plugin.

Modern radiation transport codes (such as MCNP, GEANT4, or proprietary RAD engines) require highly specific geometry definitions. These engines typically rely on Constructive Solid Geometry (CSG) or boundary-representation (BREP) meshes.

However, designers and engineers typically work in high-end 3D modeling software (e.g., Blender, Maya, SolidWorks). Exporting from these environments often results in: