Corona Scatter vs ForestPack: Exterior Performance Benchmarks for ArchViz

RenderVault EditorialApril 16, 202611 min read

🎨 Nano Banana 2 Featured Image Prompt

"Ultra-photorealistic aerial view of a modern residential complex surrounded by dense landscaping, thousands of individually scattered trees, shrubs, and ground cover plants, golden hour lighting, long dramatic shadows across manicured lawns, split-screen comparison overlay showing polygon wireframe density on one half and final render on the other, architectural photography style, 8K, Canon tilt-shift lens simulation"

Exterior architectural visualization scenes are among the most demanding rendering tasks in the industry. A single residential complex render can easily exceed 80 million polygons once vegetation, ground cover, grass, and decorative planting are scattered across the landscape. The choice of scattering tool directly determines whether that scene renders in 25 minutes or 90 minutes — and whether it even fits in your workstation's RAM at all.

Corona Scatter (built into Corona Renderer since version 8) and ForestPack Pro (by iToo Software) are the two dominant scattering solutions in production ArchViz. Both are excellent tools, but they make fundamentally different engineering trade-offs that produce dramatically different performance characteristics depending on scene complexity, vegetation density, and hardware configuration. We ran controlled benchmarks across four standardized exterior scenes to provide the data you need to choose the right tool for your specific workflow.

Benchmark Methodology

Hardware

  • CPU: AMD Ryzen Threadripper 7970X (32 cores / 64 threads)
  • RAM: 128 GB DDR5-5200
  • GPU: NVIDIA RTX 4090 (24 GB VRAM) — viewport only, CPU rendering
  • Storage: 2 TB NVMe Gen4 SSD

Software

  • 3ds Max 2025.3
  • Corona Renderer 12 (Corona Scatter built-in)
  • ForestPack Pro 8.1.2

Test Scenes

Four scenes of escalating complexity, each using identical vegetation assets (GrowFX trees, Maxtree shrubs, Megascans ground cover):

  • Scene A — Garden Path: ~5M scattered polygons (200 trees, 2000 shrubs)
  • Scene B — Residential Yard: ~22M scattered polygons (800 trees, 15000 ground cover)
  • Scene C — Housing Complex: ~58M scattered polygons (2500 trees, 40000 shrubs/cover)
  • Scene D — Masterplan Overview: ~110M scattered polygons (6000 trees, 80000 cover)

Each scene was rendered at 4K (3840×2160) using Corona's progressive renderer with a noise limit of 3% and a pass limit of 100. The same Corona Sun, Sky, and camera settings were used across all tests.

Results: Render Time

Render times measured from the start of geometry parsing to completion of the noise limit pass:

Benchmark ResultsScene       | Corona Scatter | ForestPack Pro | Difference
------------|---------------|----------------|------------
Scene A     |   4 min 12s   |   4 min 38s    | CS 9% faster
Scene B     |  11 min 45s   |  12 min 02s    | CS 2% faster
Scene C     |  28 min 33s   |  24 min 18s    | FP 15% faster
Scene D     |  67 min 41s   |  48 min 55s    | FP 28% faster

The crossover point is striking. Corona Scatter is marginally faster in scenes below ~30M scattered polygons, where its tight integration with the Corona rendering pipeline avoids the overhead of ForestPack's third-party geometry handoff. But once scene complexity exceeds approximately 40-50 million scattered polygons, ForestPack's optimized instancing engine and more aggressive LOD culling produce a substantial and widening render time advantage.

Results: RAM Consumption

Peak RAM usage measured during geometry parsing (the memory-critical phase):

RAM UsageScene       | Corona Scatter | ForestPack Pro | Difference
------------|---------------|----------------|------------
Scene A     |    8.2 GB     |    7.1 GB      | FP 13% less
Scene B     |   21.4 GB     |   16.8 GB      | FP 21% less
Scene C     |   52.3 GB     |   34.7 GB      | FP 34% less
Scene D     |  112.6 GB     |   68.2 GB      | FP 39% less

This is where the difference is most consequential for real-world production. At Scene D complexity, Corona Scatter requires 112 GB of RAM — which exceeds the capacity of most professional workstations (64 GB is still the most common configuration in ArchViz studios). ForestPack achieves the same visual density with 68 GB, keeping the scene within reach of 64 GB systems if other scene elements are optimized. For studios working on masterplan visualizations, this difference determines whether a scene can render locally or must be sent to a render farm.

Results: Viewport Performance

Viewport navigation speed in the 3ds Max viewport with the scattering visible (using each tool's viewport display mode):

Viewport FPS (Nitrous, Standard Quality)Scene       | Corona Scatter | ForestPack Pro | Notes
------------|---------------|----------------|------
Scene A     |    45 FPS     |    52 FPS      | Both comfortable
Scene B     |    28 FPS     |    38 FPS      | FP proxy display better
Scene C     |    11 FPS     |    22 FPS      | FP significantly smoother
Scene D     |     3 FPS     |    14 FPS      | CS nearly unusable

ForestPack's viewport representation system — which uses configurable point cloud, bounding box, and billboard proxies — provides consistently better viewport performance. Corona Scatter relies on 3ds Max's native point cloud display, which becomes unwieldy at high scatter counts. In production, you will spend significant time navigating these scenes to adjust cameras and check compositions; the viewport FPS difference at Scene C and D complexity translates to meaningful productivity impact over the course of a project.

Where Corona Scatter Wins

Despite ForestPack's advantages at scale, Corona Scatter has compelling strengths that make it the better choice for specific workflows:

  • Zero-config simplicity. Corona Scatter requires no plugin installation, no license management, no version compatibility concerns. It is built into Corona Renderer and just works.
  • Material integration. Corona Scatter items inherit Corona material properties natively, including Corona's physical material, layered material, and scatter-specific material variations. ForestPack sometimes requires material workaround for Corona-specific features.
  • Include/exclude by material. Corona Scatter can restrict scattering to specific surface materials without requiring spline or map-based distribution — simply paint a material on the terrain area and scatter only on that material ID.
  • Small to medium scenes. For projects with fewer than 30 million scattered polygons (most residential and small commercial projects), Corona Scatter delivers equivalent visual quality with less setup complexity.

ForestPack Production Setup

For studios that regularly work with large exterior scenes (housing complexes, campus masterplans, landscape architecture), ForestPack's configuration should be optimized for maximum memory efficiency. Here are the critical settings we use on every ForestPack scatter object in production:

MaxScript-- RenderVault: ForestPack Production Optimizer
-- Applies memory-efficient settings to all ForestPack objects in scene
(
    local fpObjects = for obj in objects
        where classof obj == Forest_Pro or classof obj == ForestPack_Pro
        collect obj

    format "Found % ForestPack objects\n" fpObjects.count

    for fp in fpObjects do (
        -- Display settings: use point cloud in viewport
        if hasProperty fp #display_type do
            fp.display_type = 3  -- 0=Mesh, 1=Proxy, 2=Billboard, 3=Points

        -- LOD: aggressive distance culling
        if hasProperty fp #lod_enabled do fp.lod_enabled = true
        if hasProperty fp #lod_distance do fp.lod_distance = 150.0  -- meters
        if hasProperty fp #lod_mode do fp.lod_mode = 1  -- Smooth transition

        -- Optimization: render-time only geometry
        if hasProperty fp #optimization_enabled do
            fp.optimization_enabled = true

        format "  Optimized: %\n" fp.name
    )

    format "\n--- ForestPack optimization applied to % objects ---\n" fpObjects.count
    format "Settings: Point cloud display, LOD at 150m, optimization ON\n"
)

The lod_distance of 150 meters is calibrated for standard residential/commercial exterior camera positions. For aerial or masterplan views, increase this to 300-500 meters. For close-up garden detail shots, reduce to 50-80 meters. The LOD system replaces distant vegetation with simplified proxy geometry, which is the primary mechanism behind ForestPack's superior RAM efficiency at scale.

Recommendation Summary

  • Use Corona Scatter for projects under 30M scattered polygons: residential gardens, single building exteriors, courtyard scenes, and any project where setup speed is prioritized over maximum performance.
  • Use ForestPack Pro for projects above 30M scattered polygons: housing developments, campus masterplans, landscape architecture, and any scene where RAM constraints are a concern. The setup overhead is justified by the 28-39% memory savings and 15-28% render time reduction at scale.
  • Hybrid approach: In some production scenes, we use both — Corona Scatter for small decorative planting near the camera (flower beds, potted plants) and ForestPack for large-scale vegetation (tree arrays, ground cover fields). This gives you the material integration benefits of Corona Scatter where they matter most and the memory efficiency of ForestPack where polygon counts are highest.

Running your own benchmarks on these tools? Share your results — we will incorporate community data into future updates of this comparison.