Arma Reforger Tools / Enfusion Workbench 1.8.0.13 (PC Steam)

No third-party mods. Custom minimal test project (ReforgerEpoch) using official Arma Reforger terrain materials.

Arma Reforger Workbench 1.8.0.13 consistently crashes with an access violation when painting terrain using the official Grass_01, Grass_02 or Grass_03 terrain materials.

I reproduced this issue on both a minimal 256 × 256 m test terrain and a larger 12.288 × 12.288 km custom terrain.

After isolating individual material settings, I found a reproducible workaround: removing the Plant Mat reference from a copy of Grass_01.emat prevents the crash while retaining the terrain textures and clutter vegetation.

The issue appears similar to the existing report "World Editor crashes when painting Grass_01 or Dirt_03 on a new terrain."

Steps to reproduce

1. Create a new world containing a GenericTerrainEntity.

2. Create a small terrain measuring 256 × 256 m.

3. Open Terrain Tool → Paint.

4. Add the official Grass_01.emat as a terrain material.

5. Initialize the surface map with a tile texture size of 256.

6. Apply a single brush stroke.

Actual result: Workbench immediately crashes with an access violation and generates a crash report.

Expected result: Grass_01 should be paintable without crashing Workbench, including its Plant Mat and Clutter Config functionality.

Additional tests

• Dirt_01.emat works correctly on the same test terrain.

• Grass_01.emat, Grass_02.emat and Grass_03.emat all cause immediate crashes.

• Painting Grass_01 over an existing Dirt_01 layer also causes a crash.

• The issue occurs on both the small test terrain and the larger custom terrain.

• The crash is reproducible after restarting Workbench.

Confirmed workaround

I duplicated the official Grass_01.emat into my own addon and named the copy Grass_NoPlants.emat.

I then modified the following setting:

• Plant Mat: cp_grass_01.emat → None

• Clutter Config: c_set_Grass_01.conf (unchanged)

With Plant Mat set to None, the modified material can be painted successfully without crashing Workbench.

The terrain textures render correctly, and small clutter vegetation is still generated.

I also tested removing Clutter Config. Painting continued to work, but some vegetation disappeared. Restoring Clutter Config while keeping Plant Mat disabled restored the small vegetation without reintroducing the crash.

I subsequently tested Grass_NoPlants.emat on my larger 12.288 × 12.288 km terrain. Painting worked successfully, and the painted surface and vegetation persisted after saving, closing and restarting Workbench.

These tests suggest that the crash is associated with Plant Mat processing or its interaction with other terrain material resources, rather than terrain size, the underlying dirt layer or the grass textures alone.

The precise underlying cause has not yet been determined.

Crash information

Crash-GUID: 017fa5af-536f-41fc-bf52-1741eafdfd6f

Workbench version: 1.8.0.13

Exception: Access violation

Grass_01 crash:
Illegal read by 0x7ff6bf37671b at 0x0

Grass_02 crash:
Illegal read by 0x7ff6bf37671b at 0x1a1

Grass_03 crash:
Illegal read by 0x7ff6bf37671b at 0x1a0

The crashes occurred during terrain painting. The logs did not reveal a specific missing material or texture resource.

System information

• OS: Windows

• CPU: Intel Core i7-7700 @ 3.60 GHz

• RAM: 16 GB

• GPU: NVIDIA GeForce GTX 1080

• VRAM: 8 GB

• NVIDIA driver: 582.66

• Platform: PC Steam

• Modlist: No third-party mods. Minimal custom test project using official Arma Reforger terrain materials.

Related issue

The existing report "World Editor crashes when painting Grass_01 or Dirt_03 on a new terrain" describes similar symptoms on newly created terrain. My findings may help narrow down the cause, although I cannot confirm that both reports have the same underlying defect.

Request

Could you please investigate the Plant Mat processing path during terrain painting?

Is this a known issue in Workbench 1.8.0.13, and is there a supported workaround that preserves full grass rendering?

I can provide the crash logs, minidumps and a minimal reproduction project if needed.