View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0005037 | The Dark Mod | Mapping | public | 24.05.2019 17:35 | 03.01.2021 04:33 |
Reporter | joebarnin | Assigned To | stgatilov | ||
Priority | low | Severity | crash | Reproducibility | always |
Status | resolved | Resolution | fixed | ||
Platform | PC | OS | Windows | OS Version | 10 |
Product Version | TDM 2.07 | ||||
Target Version | TDM 2.09 | Fixed in Version | TDM 2.08 | ||
Summary | 0005037: dmap crashes on specific map | ||||
Description | When 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 Reproduce | dmap bad.map - DarkMod will crash (vaporize, with no error dialog or anything). | ||||
Additional Information | 1) 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. | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
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. |
|
Setting to resolved. If this is still reproducible in 2.09 beta, please include assets such as textures, models, etc needed to compile the map. |
|
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 |
02.01.2021 17:57 | nbohr1more | Note Added: 0013344 | |
02.01.2021 17:57 | nbohr1more | Status | feedback => resolved |
02.01.2021 17:57 | nbohr1more | Resolution | open => fixed |
02.01.2021 17:57 | nbohr1more | Fixed in Version | => TDM 2.09 |
03.01.2021 04:33 | stgatilov | Fixed in Version | TDM 2.09 => TDM 2.08 |