View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000826 | FSSCP | tables | public | 2006-02-23 04:21 | 2006-03-07 17:39 |
| Reporter | bfobar | Assigned To | taylor | ||
| Priority | normal | Severity | trivial | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Summary | 0000826: CTD on failed texture load gives poor error message. | ||||
| Description | I downloaded the In to the Depths of Hell chapter 2 user made campaign from Hades Combine and discovered the following: It comes with all files and modular tbm files for some user made weapons and ships except for 2-3 that seem to have been forgotten. The problem is the following: In cases where the FS2 open code reads a table file and comes across a mistake, like a file referenced that doesn't exist or a bad line, the code is not very informative as to what's wrong. It just gives an error that it expects $Name or #End and a line number. Could this possibly be improved so that the error message includes the actual text in the line and maybe what the name of the weapon or ship was? Also in the weapons loadout screen, if the weapon has a bad table entry for its "Icon:" field, the game goes CTD. | ||||
| Additional Information | 2/20/06 build. Putting in a the name of a real icon file on the computer into the field fixes the problem. I would just like to request a slightly more informative error message in the code. The root of the problem is obviously a campaign with modded tables that doesn't have included or listed which files are needed. | ||||
| Tags | No tags attached. | ||||
|
|
In general it should either give an error immediately (if it's fatal) when parsing a tables, and it would be descriptive to that fact, or it would be delayed until mission load or something and it would still be a descriptive message to that fact. If there is a table that gives the error you indicate for a missing image/texture then please attach the table. The weapon loadout screen may be fixed now, but I haven't actually tested it myself fully yet. A quick test showed that it's fixed but you'll have to give the next CVS build a try to find out for sure. |
|
|
Can this be resolved? |
|
|
Not sure, it hasn't been verified. It was fixed in my testing though so I guess I'll just resolve this and if bfobar is still able to reproduce then he can just reopen the bug. |
|
|
Fixered. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2006-02-23 04:21 | bfobar | New Issue | |
| 2006-02-23 05:18 | taylor | Note Added: 0004900 | |
| 2006-02-23 05:18 | taylor | Status | new => assigned |
| 2006-02-23 05:18 | taylor | Assigned To | => taylor |
| 2006-03-07 17:27 | Goober5000 | Note Added: 0005064 | |
| 2006-03-07 17:39 | taylor | Note Added: 0005073 | |
| 2006-03-07 17:39 | taylor | Status | assigned => resolved |
| 2006-03-07 17:39 | taylor | Resolution | open => fixed |
| 2006-03-07 17:39 | taylor | Note Added: 0005074 |
