Overview
Corona built its following on a simple position: almost nothing to configure. Where other renderers ask for a dozen sampling parameters that interact in ways nobody fully predicts, this one has essentially one quality control and otherwise gets on with it. The result is that artists spend their time on lighting and materials rather than on tuning a renderer, and the images come out clean.
The interactive renderer is central to how it is used. A live window updates as geometry, lights, materials and the camera are changed, converging progressively, so decisions are made against a nearly final image instead of a rough preview. Rendering can be stopped at any point and resumed later from the same state, and a render can be told to run to a time limit, a noise level or a pass count.
Materials are physically based with layering for coatings, sheen and translucency, and the bundled library covers the usual architectural set of metals, woods, glass, fabrics and finishes. Light sources are physical with real units, there is a sun and sky model, and the virtual frame buffer carries a full post processing stack with exposure, bloom, glare, tone mapping, light mix and denoising, all applied after the render without going back to the renderer.
What it does well
One quality setting
A single control governs render quality, removing the sampling parameter tuning that other engines demand.
Interactive rendering
A live window converges as the scene is edited, so lighting and material decisions are made against a near final image.
Resumable renders
Stop and continue later from the same state, or run to a time limit, a noise threshold or a pass count.
Physical materials and lights
Layered physically based materials with a bundled architectural library, and lights in real photometric units.
Post processing in the frame buffer
Exposure, tone mapping, bloom, glare, light mix and denoising applied after rendering without recomputing the image.
Changes in this build
- Denoiser improved, clearing interiors at noticeably lower pass counts.
- Material library expanded with more architectural finishes and fabrics.
- Faster handling of scenes with very high instance counts.
- Light mix extended to grouped sources for easier post balancing.
- Improved conversion from other renderers' material setups.
What is in the package
- Corona renderer plug-in installer, 64-bit
- Material library with architectural presets
- Standalone image editor for the frame buffer format
- Distributed rendering components for a render farm
- Sample scenes for lighting and material setup
System requirements
| Processor | Intel or AMD 64-bit, eight cores or more strongly recommended |
| Memory | 32 GB recommended, 16 GB minimum for simple scenes |
| Graphics | Any GPU supported by the host application |
| Storage | 10 GB free plus space for the material library |
| Display | 1920 x 1080 minimum, colour accurate panel recommended |
| System | Windows 10 or Windows 11, 64-bit, with a compatible host installed |
Installation
- Close the host modelling application completely.
- Extract the archive to a local folder.
- Run the installer and select the host version you are targeting.
- Apply the included configuration step before first launch.
- Open a sample scene and run an interactive render to confirm the plug-in loaded.
Before you start
The plug-in build has to match the host version, installing against the wrong one leaves it unlisted.
This renderer is processor bound, core count matters far more than the graphics card.
Distributed rendering needs the same plug-in version on every node.
Questions about this title
Is it processor or graphics based?
Processor based, so core count is what determines render times.
Does it have an interactive mode?
Yes, a live window converges while the scene is edited.
Can renders be resumed?
Yes, a stopped render continues later from the same state.
Is a material library included?
Yes, a physically based architectural library ships with the plug-in.
About this listing
This entry was checked on a clean install of Windows 10 / 11 (64-bit) before it was published, and it is rechecked whenever the package is rebuilt. The figures on this page come from the site index rather than from the publisher, so the download count is what people here have actually pulled.
If a mirror stops answering, use the contact form and it gets replaced. Reports about a specific title are handled faster than general messages because they name the file, the mirror and the point at which the transfer stopped.
Requests for a different version, a different language build or an older release go on the requests page. Older versions of a title are usually still held even when only the current one is listed.