View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002365 | FSSCP | tables | public | 2010-12-31 00:53 | 2011-01-06 05:08 |
| Reporter | chief1983 | Assigned To | chief1983 | ||
| Priority | normal | Severity | crash | Reproducibility | have not tried |
| Status | resolved | Resolution | fixed | ||
| Platform | x86-64 | OS | Windows 7 | OS Version | Professional |
| Product Version | Antipodes 8 | ||||
| Fixed in Version | 3.6.13 | ||||
| Summary | 0002365: ASSERTION: "ti->texture.bitmap_id != -1" at trails.cpp:203 | ||||
| Description | Turns out, just missing a missile trail bitmap can lead to a crash in debug builds. It plays through fine without it though, so I think we don't need to Assert this, perhaps just warn. Also, when hit, it would help to report the name of the texture that was missing, perhaps even the weapon missing it if possible. I know the texture name is accessible at that point in 'ti'. Additionally, we might want to see if this could be reported sooner, like on mission load, instead of waiting until the missile is fired. | ||||
| Steps To Reproduce | Should be able to reproduce by creating a weapon tbm for the rockeye and giving it a nonexistent missile trail file. Then fire up a mission with rockeyes and let 'em rip. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2010-12-31 00:53 | chief1983 | New Issue | |
| 2011-01-04 15:56 | chief1983 | Steps to Reproduce Updated | |
| 2011-01-06 05:08 | chief1983 | Note Added: 0012589 | |
| 2011-01-06 05:08 | chief1983 | Assigned To | => chief1983 |
| 2011-01-06 05:08 | chief1983 | Status | new => resolved |
| 2011-01-06 05:08 | chief1983 | Resolution | open => fixed |
| 2011-01-06 05:08 | chief1983 | Fixed in Version | => 3.6.13 |
