The 3D Rad Exporter plugin is primarily used to convert 3D models created in modeling software like SketchUp and Blender into the .x (DirectX) format required for 3D Rad game development. For SketchUp Users
The most common version of this plugin is for SketchUp. It allows you to export your designs directly to 3D Rad-compatible formats. Installation: Download the .rbz file from the 3D Rad Forum.
In SketchUp, install it via the Extension Manager (Window > Extension Manager > Install Extension). Do not simply move the .rbs file into the tools folder manually, as this often fails.
Exporting: Once installed, the "3D Rad Exporter" option should appear under the Tools menu.
Texture Handling: A common issue is textures not appearing correctly after export; this can sometimes be mitigated by ensuring textures are correctly applied to faces rather than groups. For Blender Users
Blender also has a dedicated 3D Rad exporter addon that enables the creation of custom content like skins and rigged meshes.
Compatibility: The addon typically requires Blender 2.67 or newer and works on 64-bit Windows systems.
Alternative Method: If the plugin fails, you can export your Blender model as an FBX or OBJ and then use a third-party converter like fragMOTION to finalize it as a .x file for 3D Rad. Alternative: Using .DAE (Collada)
If you encounter issues with specific exporter plugins, you can download .dae files from the SketchUp 3D Warehouse and convert them using online converters or open them in SketchUp to use the 3D Rad Exporter tool. Content Creation Tips
Coordinate Systems: SketchUp and 3D Rad use different axes; your model might appear "on its side" upon import. This can be fixed by rotating the model -90 degrees on the X-axis in a tool like fragMOTION before the final export. 3d rad exporter plugin
Importing into 3D Rad: Once you have your .x file, use the RadImp or RadImp .NET tools within 3D Rad to import it as a rigidbody or skinmesh. 3D Rad Lesson 5 - "Creating Custom Content"
This is the most common version of the exporter, designed to bridge SketchUp models to the 3D Rad engine.
: Converts SketchUp geometry into DirectX (.x) files that 3D Rad can import as rigid bodies or skinmeshes. Installation The plugin usually comes as an For SketchUp 2016 and later, it is typically placed in the folder found in the user's AppData directory (e.g.,
C:\Users\(Username)\AppData\Roaming\SketchUp\SketchUp 2016\SketchUp\Plugins
: Once installed, an "Extensions" or "3D Rad" menu option appears in SketchUp, allowing you to select "Export as generic DirectX file". Blender Exporter Plugin
A dedicated script also exists for Blender users to prepare assets for 3D Rad. Capabilities : Can export meshes, rigid bodies, and even animations. Installation
: Involves placing an executable in the 3D Rad installation directory and installing a script via Blender's plugin manager. Key Detail
: When exporting animations, it may output them in a sequential mesh format (e.g., ) rather than a single combined model. Common Alternatives & Troubleshooting FragMOTION : If direct plugins fail, many users use fragMOTION
as an intermediary to import OBJ files and export them as the specific DirectX files required by 3D Rad. Texture Issues The 3D Rad Exporter plugin is primarily used
: Users sometimes report texture mapping problems when exporting directly from SketchUp Free/Make, occasionally requiring secondary tools like ZbylsXExporter for better results. download link
The 3D Rad Exporter plugin is a specialized tool used to bridge the gap between 3D modeling software—primarily Google SketchUp and Blender—and the 3D Rad game engine. Its primary purpose is to convert 3D models into the Microsoft DirectX (.x) file format, which is the native format 3D Rad uses for game objects. The Evolution of the Exporter
The "story" of this plugin is one of a community-driven effort to keep an aging but beloved game engine accessible to hobbyist developers.
The SketchUp Era: In the early 2010s, SketchUp was the "go-to" for beginners because of its simplicity. The 3D Rad Exporter for SketchUp allowed users to design environments and export them directly into 3D Rad. However, as SketchUp evolved (from Google to Trimble), installation paths changed, often requiring users to manually move .rbz or .rbs files into specific plugin folders like AppData\Roaming\SketchUp\...\Plugins.
The Blender Shift: As users looked for more professional features like skinmeshes (animated characters), the community developed a Blender 3DRad Exporter. This was vital because 3D Rad’s built-in tools often struggled with complex physics objects or detailed animations, and Blender provided a more robust pipeline.
Technical Challenges: A recurring theme in the plugin's history is the struggle with texture mapping and coordinate systems. Users often reported issues where textures wouldn't export correctly or models would appear rotated 90 degrees, leading to the use of secondary "fix-it" tools like fragMOTION or 3D Builder to center and re-export models before they would work in 3D Rad. Key Features & Workflow
DirectX Conversion: The core function is converting native CAD geometry into the .x format.
Physics Preparation: In SketchUp, the plugin often helped define which parts of a model should be treated as RigidBodies or Skinmeshes once imported.
Community Maintenance: Because 3D Rad is no longer actively updated by its original developers, these plugins are maintained by community members on forums like the 3D Rad Boards. Popular Versions Plugin Version Host Software Primary Use 3DRadExporter.rbz SketchUp 2016+ Exporting static buildings and scenery. Blender 3DRad Addon Blender 2.67+ Exporting animated characters and complex physics. Pandasoft Exporter Professional-grade DirectX exporting for 3D Rad. Question about Sketchup and the 3D Rad exporter Introduction In the fragmented ecosystem of 3D content
The emergence of as a accessible game engine was a turning point for hobbyist developers, but its true utility was unlocked by the 3D Rad Exporter plugin
. This tool served as the vital bridge between complex 3D modeling software and the engine's simplified assembly environment, transforming static art into interactive digital experiences. The Bridge Between Art and Logic
At its core, the 3D Rad Exporter—most notably for software like Google SketchUp
—solved a fundamental compatibility problem. While 3D Rad excelled at physics and logic "tiles," it lacked robust internal modeling tools. The exporter allowed creators to design intricate geometries in industry-standard programs and port them into the engine with their UV maps, textures, and scales intact. Without this seamless transition, the engine would have remained a playground for basic primitives rather than a platform for detailed racing simulators or first-person explorations. Technical Efficiency and Accessibility
One of the exporter's greatest strengths was its commitment to simplicity . By converting models into the
(DirectX) format optimized for 3D Rad, it automated what used to be a tedious manual conversion process. It handled complex tasks—such as centering the origin point and managing polygon counts—ensuring that the resulting assets didn't crash the engine’s real-time physics solver. This democratization of technical workflow allowed artists with zero coding knowledge to see their visions come to life. Legacy in Indie Development The plugin did more than just move files; it fostered a community of modularity
. Because exporting became so easy, a massive library of community-made assets (cars, buildings, and landscapes) flourished. This ecosystem allowed beginner developers to "kitbash" games together, focusing on gameplay mechanics rather than the steep learning curve of technical 3D optimization. Conclusion
The 3D Rad Exporter plugin remains a classic example of how a single utility tool can define the success of a creative platform. By lowering the barrier to entry, it turned 3D Rad from a niche experiment into a legitimate starting point for a generation of indie game designers. It proved that the strength of a game engine isn't just in its rendering power, but in how well it talks to the tools creators already love. format or the historical impact on the SketchUp community?
In the fragmented ecosystem of 3D content creation, the ability to move assets seamlessly between software packages is not a luxury but a necessity. 3D Rad, a now-discontinued but historically significant real-time 3D authoring tool, carved a niche for rapid prototyping and lightweight interactive applications. Unlike monolithic engines like Unity or Unreal, 3D Rad relied on a proprietary, component-based system. For a modern 3D artist, exporting a high-fidelity model from Blender, Maya, or 3ds Max directly into 3D Rad’s native format is impossible without a dedicated translator. This is the role of the 3D Rad Exporter Plugin. Developing such a plugin requires a deep understanding of both the source software’s API (Application Programming Interface) and the target engine’s binary serialization. This essay explores the technical architecture, file format intricacies, material pipeline challenges, and practical workflow integration of writing a robust exporter for 3D Rad.
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.