Summary
Terrain Builder exports object IDs as (layerIndex << 24) | objectIndexInLayer. If a project has a layer with index 128 or higher, every object in that layer gets an ID ≥ 0x80000000, which is negative as a signed int32. binarize.exe crashes with an access violation (0xC0000005) when it reaches the first such object. It writes no error message, and the log is cut off mid-line.

Indices of deleted layers are not reused, so a project can hit this limit with fewer than 128 live layers.

1. In Terrain Builder, open or create a project whose highest layer index is 128 or more.

2. Place objects in that layer.

3. Export WRP.

4. Binarize the WRP (same parameters as the “Binarize WRP” workflow).

Expected
Binarize completes, or Terrain Builder warns about the layer limit or renumbers object IDs on export.

Actual
binarize.exe exits with code 0xC0000005. The log stops mid-line on the last object before the first ID ≥ 0x80000000. No error is reported.

Details from our terrain

• 1,450,119 objects in 142 layers, with layer indices 0–146. Indices 2, 27, 58, 64 and 69 are unused because those layers were deleted.

• 35,389 objects have IDs ≥ 2³¹. The highest ID is 2,449,473,975 (layer 146).

• Objects are stored layer by layer in the 1WZD file, and binarize processes them in file order. It processed 1,384,884 objects before crashing. The first object of layer 128 is #1,384,920. The ~35 missing lines are consistent with unflushed log output.

• The same terrain binarizes successfully after either of these changes:

  • the layer count is reduced so that the highest index is below 128;

  • a third-party editor renumbers object IDs to 1…N.

• For comparison, the vanilla ChernarusPlus.wrp uses layer indices up to 39 (max ID 654,324,539), so official terrains don’t hit this.