Occurs on DayZServer local instance running: dayzOffline.nasdara

Server initialization writes about ~4,500 warnings to the RPT logs re: various P3D geometry/component issues and missing config entries.

Most of them come from: dz\structures_takistan while some reference structures_sakhal and structures_bliss

The main issues:

• 26 Takistan models are placed as houses with no config class. Mostly desert pipes and container trailers. The warning repeats at runtime as areas stream in.

• 733 doors and windows across 103 building classes are missing geometry components. Mainly Land_House_*, Land_TajbegPalace_* and Land_Hospital_Takistan. Affected doors may lack collision or fail to open.

• 14 Takistan models have an unknown object class (thing, pond, decal), and 11 Takistan proxies/props are missing (“Cannot open object”).

• About 1,000 degenerate convex components (fewer than 4 faces) in Geometry/Fire/View LODs across Takistan, Sakhal, Chernarus and Bliss structures. These can leave holes in collision.

• 130 Size: '/' not an array warnings from failed config lookups: hitMudDry is missing on base ammo classes.

None of these stop/crash the server or the client.

I've attached a PDF that contains an extended report and has full counts, affected models and classes.

I'm also attaching a more recent .RPT log for reference v1.30.164289.70 + with a few additional mods in launch params. However; relevant log entries are still applicable despite this difference in modlist/build version.

• Launch DayZServer locally with the referenced launch params; it is likely that -newErrorsAreWarnings=1 being the most important (untested without this enabled)

• Allow initialization to complete

• Refer to server .RPT logs for significant amounts of output regarding impacted .p3d and missing config entries

  
  

• Keywords to search logs for:

• takistan

• components

• geometry

• not an array

• A cleaner server init & runtime alleviated of asset/config warnings for missing components on vanilla assets. More specifically:

  • Every model placed as a house has a matching Land_* config class, and its object class property is one the engine recognizes.

  • Every door and window in a building’s config has matching components in the Geometry, View and Fire LODs, so it collides, blocks bullets and opens correctly.

  • All referenced proxies, props and textures exist in the PBOs and load without “Cannot open object” or texture errors.

  • Geometry, Fire and View LODs contain only closed convex components, with no degenerate pieces under 4 faces, and component counts stay within performance limits.

  • Config lookups find the entries they expect. Base ammo classes define hitMudDry, nested classes like Food, FoodStages, DamageSystem and Crew sit inside their parent classes and not at the root of CfgVehicles, and Headtorch_ColorBase defines Beam.color.

  • No base-game warnings repeat during runtime as areas stream in.