Support
Help with Fyr Baker: the manual, the community Discord, or email.
- Open the manual
Documentation
Installation, first bake, workflows, map settings, export, and troubleshooting.
- Join Discord
Lighthouse community
The community Discord where I share Fyr development alongside my art and other creative projects. It is not the place for billing, refunds, or technical issues.
- Report a bug
Bug reports
Email a bug report with your Blender version, OS, GPU, and steps to reproduce.
- Send email
Email support
For purchases, billing, refunds, and installation or plugin problems, write to support@fyrplugins.com. The target is a reply within two business days, and complex bugs may need follow-up questions first.
Frequently asked questions
Not covered here? Use the options above.
Fyr Baker targets Blender 5.1 or later.
Fyr Baker has two bake renderers. The native Fyr renderer is an external backend built for texture projection work; it is currently Windows-only and runs on the GPU. The Cycles renderer runs the same bake projects through Blender's own Cycles engine on every platform, on CPU or GPU. Auto mode picks Fyr when an output can run natively and Cycles otherwise, and the renderer can also be chosen per output.
Yes. The full Fyr Baker workflow, including bake projects, groups, cages, the map stack, and naming presets, works on macOS and Linux. Bakes use Blender's Cycles on CPU or GPU. The native Fyr renderer is currently Windows-only, and native macOS or Linux versions are not promised. Some outputs are approximations under Cycles compared with the native renderer. The add-on marks per-map fidelity in the map settings.
After purchase you receive the plugin .zip. In Blender, open Preferences → Add-ons → Install, then select the .zip. No separate Python package installation should be required.
Yes. Fyr Baker organizes assets into reusable bake projects, texture sets, and named bake groups with low, high, and optional cage assignments. Auto-matching can build groups across the scene from name prefixes and suffixes (_low/_high, _lp/_hp, _cage), and Match By Mesh Name keeps one high-poly from bleeding onto a neighbouring low-poly. The setup stays in the Blender scene, so you can adjust it and re-run outputs without rebuilding the project structure.
A bake project is set to one of two workflows. "High to Low Bake" is the classic projection workflow: high-poly detail is transferred onto low-poly targets through a cage. "Bake Selected Materials" has no high-poly role. It flattens the materials already on your selected objects into portable PBR texture sets. You can also enable "Use Low as High" inside a high-to-low group to bake without assigning a separate high-poly mesh.
Yes. Fyr Baker compiles Blender shader graphs into its own intermediate representation and evaluates them natively on the GPU, including noise, Voronoi, gradients, colour and vector math, converters, and secondary-ray nodes such as Ambient Occlusion, Bevel, and Raycast. A Bakeability panel in the Shader Editor shows per-channel whether each output is native, needs Cycles, or cannot be baked, and clicking a result focuses the node responsible. Anything outside native coverage routes to Cycles automatically, so a material never silently fails.
Yes. UDIM support covers tile-aware naming, per-tile output targets and resolutions, automatic tile discovery, native Blender tiled images, and tile-aware incremental rebuilds.
No. Fyr Baker ships with no license keys, no activation servers, and no subscription. You buy it once and install the .zip.
Fyr Baker exposes Tangent-space Normal, Object Normal, World Normal, and Bent Normal outputs. Tangent-space normals use MikkTSpace tangents with OpenGL or DirectX orientation, and a separate Material Normal output bakes a material's own Normal Map and Bump nodes. Bent Normal records the average unoccluded surface direction for indirect-lighting workflows.
No. A resident backend worker stays alive between bakes and dirty tracking works at the per-map, per-group level, so only what actually changed is re-evaluated. Bake sessions report live progress and can be cancelled at any time.
Make sure Blender is on a supported version, your graphics driver is up to date, and the issue still happens after restarting Blender. If it continues, report it with your Blender version, operating system, GPU, driver version, and steps to reproduce.
We offer refunds within 14 days of purchase if Fyr Baker doesn't work as described. Include your order ID and a description of the issue.
Both plugins are in active development. You can sign up for a launch notification on each product page.
Fyr Exporter and Fyr Visualizer target Blender 5.1 or later. If that changes before launch, the product pages and release notes will be updated.