Version: 1.30.164200.56, PC Steam, Windows
Terrain: custom terrain, 20x20 km, world name islacero, mod @IslaCeroRD, mission dayzOffline.islacero
What happened:
A new custom terrain with no navmesh file yet cannot start in DayZ 1.30 at all, so the NavMeshGenerator can never connect to create the first navmesh.
The server reaches Loading landscape 'islacero' and then crashes:
AI (F): Unable to load navmesh for 'islacero'.
ENGINE (F): Crashed
Exception code: C0000005 ACCESS_VIOLATION
This was tested in all of these ways, all crashing at the same point:
1. Normal dedicated server: DayZServer_x64 -config=ServerDZ-IslaCero-Prueba.cfg -port=2302 -profiles=C:\DayZIslaCeroPrueba -mod=@IslaCeroRD
Result 2026-11-03 01:44: server reached Loading landscape 'islacero', then Unable to load navmesh, then Crashed, C0000005 at 714DF07C.
2. Navmesh data server: DayZDiag_x64 -server -mod=@IslaCeroRD -startNavmeshDataServer -port=2302 -config=ServerDZNV.cfg
Result 2026-11-03 01:21: same crash, C0000005 at 5C62A1EC.
3. Borrowed navmesh from Chernarus, by reference only: navmeshName = "\dz\worlds\chernarusplus\navmesh\navmesh.nm"
Result 2026-11-03 01:21: same crash at Loading landscape.
4. Borrowed navmesh from Nasdara, 1.30 format: navmeshName = "\dz\worlds\nasdara\navmesh\navmesh.nm"
Result 2026-11-03 01:48: same crash at Loading landscape, C0000005 at 5C62A1EC.
5. Isolated diagnostic copy, world name islacerodiag, config with NO Navmesh class at all, separate mod @IslaCeroDiagnostico, separate mission and profile, normal server port 2304
Result 2026-11-03 02:06: same crash at Loading landscape 'islacerodiag', AI (F): Unable to load navmesh for 'islacerodiag', ENGINE (F): Crashed, C0000005 at 714DF07C.
The official wiki says navmesh is not mandatory and the game will cope without it. In 1.30 it does not cope: the server cannot start at all, with or without the Navmesh class, with a missing navmesh, or with a borrowed navmesh from another world.
Expected result:
The server starts without a navmesh (AI frozen, as documented), or at least the navmesh data server stays up so the NavMeshGenerator can create the first navmesh for a new terrain.
Related issue: DZG-2465, where another custom map creator reports that generating new navmeshes for custom maps does not work in 1.30.
Attachments: RPT files from the normal server test, the Nasdara data server test, and the isolated diagnostic test.