View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000917 | FSSCP | tables | public | 2006-05-23 11:16 | 2006-05-27 06:48 |
| Reporter | IPAndrews | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | open | ||
| Summary | 0000917: Modular tables for weapons don't replace beams | ||||
| Description | When using a modular table for a beam weapon and there is already a table entry for the beam weapon in weapons.tbl, the beam configuration in the modular table is used _in addition_ to the one in the weapons.tbl . So the new look beam is actually overlayed over the old look beam when the weapon is fired. | ||||
| Additional Information | This looks a bit silly. :) | ||||
| Tags | No tags attached. | ||||
|
|
Are you using +Index: option in the beam texture sections? |
|
|
This _is not_ a bug. It is a design attribute of modular tables. By default, things are added on, rather than replaced, since that's the default for ships, weapons, and other major elements. Rather than varying this for whatever way I felt would be more useful, I just stayed with the same thing and added fields to allow replacement, as I went. Hence the addition of the +Index: field. |
|
|
Not a bug, unless the +Index: field fails to work properly. (If you want to discuss the design setup further, start a thread on the forums) |
