View Issue Details

IDProjectCategoryView StatusLast Update
0005037The Dark ModMappingpublic12.04.2020 05:49
Reporterjoebarnin Assigned Tostgatilov  
PrioritylowSeveritycrashReproducibilityalways
Status feedbackResolutionopen 
PlatformPCOSWindowsOS Version10
Product VersionTDM 2.07 
Target VersionTDM 2.09 
Summary0005037: dmap crashes on specific map
DescriptionWhen I dmap the attached map, DM crashes. qconsole.log indicated that the problem might be related to AAS generation. Through trial and error, I determined that a specific Monster Clip brush is causing the problem (primitive 4863).
Steps To Reproducedmap bad.map - DarkMod will crash (vaporize, with no error dialog or anything).

Additional Information1) If you modify bad.map to remove primitive 4863 (no other changes), the map compiles just fine. Specifically, I removed this from the .map file:

// primitive 4863
{
brushDef3
{
( 0 0 1.000000005875993 -1884.361603784897 ) ( ( 0.02604166604578495 0 0 ) ( 0 0.02604166604578495 0 ) ) "textures/common/monster_clip" 0 0 0
( 0 1.000000024935951 0 3706.092831062408 ) ( ( 0.02604166604578495 0 0 ) ( 0 0.02604166604578495 0 ) ) "textures/common/monster_clip" 0 0 0
( 0.9999999701189963 0 0 -3711.634363160325 ) ( ( 0.02604166604578495 0 0 ) ( 0 0.02604166604578495 0 ) ) "textures/common/monster_clip" 0 0 0
( 0 0 -1.000000005875993 1823.998788228923 ) ( ( 0.02604166604578495 0 0 ) ( 0 0.02604166604578495 0 ) ) "textures/common/monster_clip" 0 0 0
( 0 -1.000000024935951 0 -3815.649337090202 ) ( ( 0.02604166604578495 0 0 ) ( 0 0.02604166604578495 0 ) ) "textures/common/monster_clip" 0 0 0
( -0.9999999701189963 0 0 3679.666988360232 ) ( ( 0.02604166604578495 0 0 ) ( 0 0.02604166604578495 0 ) ) "textures/common/monster_clip" 0 0 0
}
}

2) Another data point. I opened this map in DR and made that brush (4863) one unit larger in each dimension. dmap then worked in this case too.
TagsNo tags attached.

Relationships

related to 0005212 resolvedstgatilov dmap: crash when merging leaf nodes in AAS 

Activities

joebarnin

joebarnin

24.05.2019 17:35

reporter  

bad.zip (670,710 bytes)
stgatilov

stgatilov

30.12.2019 16:29

administrator   ~0011986

I'm afraid dmap has a chance of crashing on unlucky combination of brushes. It is unlikely to be universally fixable.
In most cases, the problem goes away when you try to isolate the problematic brush from the map (even if you take its room with it).

I would look into this problem, but cannot reproduce it.
dmap writes that the map is "leaky" and stops compilation. I heard that a map without materials that it uses sometimes works like that.

Issue History

Date Modified Username Field Change
24.05.2019 17:35 joebarnin New Issue
24.05.2019 17:35 joebarnin File Added: bad.zip
30.12.2019 16:29 stgatilov Note Added: 0011986
12.04.2020 05:21 stgatilov Relationship added related to 0005212
12.04.2020 05:49 stgatilov Assigned To => stgatilov
12.04.2020 05:49 stgatilov Status new => feedback
12.04.2020 05:49 stgatilov Target Version => TDM 2.09