OXIDENODES / DOCUMENTATION
Example documentation · A starting point for editing. Exact installation steps and release compatibility will be added later.
Overview
OxideNodes connects Blender Geometry Nodes authoring with procedural geometry in Godot. Create a graph in Blender, export it, and change its exposed inputs in your Godot project.
One graph, adjustable results
Graph editing stays in Blender. After export, the graph structure is fixed: the evaluator generates new geometry from the inputs you expose, rather than providing another node editor inside Godot.
The basic workflow
- Author your Geometry Nodes setup in Blender.
- Expose the parameters or geometry inputs you want to change.
- Export the graph and its referenced resources.
- Evaluate it in Godot, or bake the result into static assets.
Start with installation, then try your first graph.
Installation
The planned distribution uses a Blender authoring add-on and a precompiled Godot GDExtension. End users should not need a compiler or build tools.
Setup checklist
- Choose the Blender add-on for your Blender version.
- Choose the Godot evaluator for your Godot version and operating system.
- Install the add-on in Blender and enable it.
- Add the evaluator to your Godot project and confirm that the extension loads.
The exporter and evaluator communicate through a versioned bridge protocol. Both must support a common protocol version.
To complete this page: add supported versions, download links, installation screenshots, and exact menu names for the release.
Your first graph
For a first test, use a small graph with a single exposed parameter, such as the size of a generated shape. This keeps the result easy to check.
- Create a simple Geometry Nodes setup in Blender.
- Expose one parameter through the group interface and verify that changing it affects the output.
- Export the setup, reviewing any capability diagnostics.
- Load the exported package through the Godot integration.
- Change the exposed parameter and compare the result with Blender.
What gets exported?
The package separates the graph from its geometry and referenced resources. Its conceptual layout is:
asset-name.oxide/
graph.oxide.json
assets/
Example walkthrough: replace this with a verified sample graph and the exact export/import steps when ready.
Exposed inputs
Exposed inputs are the controls that remain adjustable after export. They can include scalar values, vectors, menu parameters, and input geometry.
Parameters and source geometry
Use parameters for values such as size or spacing. Geometry inputs supply source data that the graph transforms into a separate result. Evaluation does not modify that source in place.
What stays fixed?
Resources that are not exposed as inputs are frozen into the exported package. To change the graph structure or those fixed resources, edit the original in Blender and export again.
Evaluation & baking
The project is designed to support procedural evaluation in both the Godot editor and exported games.
Evaluation
Keep the exported graph and adjust its exposed inputs when you need a procedural result. The evaluator processes the fixed graph with the current input values.
Baking
Baking captures a particular graph and input snapshot as static engine assets. It is useful when the result no longer needs to change procedurally.
Time-dependent setups need an explicit time input or a frozen snapshot. Treat the chosen inputs and source data as part of the bake.
Troubleshooting
The extension does not load
Check that the evaluator build matches your Godot version and operating system. Read the Godot console for the specific loading error.
A graph cannot be exported
Review the export diagnostics for unsupported operations. The export process is designed to check capabilities before a graph reaches the runtime; some operations may need baking or a different graph setup.
An input is missing
Check that it is exposed through the graph interface in Blender, then export again. Internal fixed values do not become adjustable automatically.
Reporting a problem
Include your Blender and Godot versions, add-on and evaluator versions, the exact diagnostic message, and a small graph that reproduces the issue.