View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001837 | FSSCP | gameplay | public | 2008-12-05 07:26 | 2012-07-04 07:08 |
| Reporter | Zacam | Assigned To | Goober5000 | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Summary | 0001837: New un-assigned pilot: Squadron re-assignment does not work | ||||
| Description | In trying to test if Insignia _could_ support anything other than PCX/DDS and trying to determine why a DDS will only show when there is a PCX to replace, I came across this interesting issue. If you create a new pilot, but do not engage in _any_ missions via campaign continuation and load a tech-room mission that makes the player part of a squadron (on a ship capable of displaying a squadron logo and the correct logo has been specifically and correctly selected), no squadron insignia displays on the player ship. Additionally, specifying (in the same mission) any wings with a valid logo via +Squad Logo: also does not render an insignia under the above conditions. | ||||
| Additional Information | The first case I can somewhat understand. Not being a member of a squadron means you can not be RE-assigned to another. The condition is a null assertion resulting in a null action. (And does not generate any warnings or errors in fs2_open.log). Possible fix is for new un-associated pilots to belong to Squadron "None" with logo "Dummy.pcx" that somehow is hidden from Squadron selection in the barracks. This way, non-affiliated pilots can still render logo's in standalone missions or for testing, which will prevent the second case from coming true. Could even (potentially?) be merged with whatever fix allows for a *.DDS flie name allowed to be used in the +SquadReassignLogo: area. | ||||
| Tags | No tags attached. | ||||
|
|
This has absolutely nothing to do with the DDS issue. I'm not sure what the problem is here; the code specifically does not assign a squadron or squad logo to the player if he's not in campaign mode. (I would imagine this is to prevent the squadrons from always being overwritten if he plays single missions while in the middle of a campaign.) As for your +Squad Logo discovery, can you attach a sample mission? |
|
|
Test Mission Attached. For best results, create a new pilot. Do not begin or engage ANY campaign missions before launching this one. Alpha 1 should should display the 242nd Suicide Logo. Beta Wing (3 ships) should (and will) show the Volition Squadron Logo. The only thing I did not try to do, is set "Squad Logo: " in Alpha wing instead of defining the squad re-assign in the mission parameters, this may be a more viable work around. And I know it has nothing to do with the logo filetype, I just found this while doing various tests regarding it. |
|
|
Well, there isn't any mission attached. I would say it got deleted, but the log shows no record of you attaching one. :-/ Though your comment above says that Beta wing will show the Volition logo as expected. So is there really any bug here? |
|
|
Per conversation with Zacam, it sounds like this is all expected behavior. There is the issue of a DDS squadron insignia requiring an equivalent PCX insignia, but that is a separate bug, and according to Taylor not easily fixable. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2008-12-05 07:26 | Zacam | New Issue | |
| 2009-01-20 05:04 | Goober5000 | Note Added: 0010568 | |
| 2009-01-20 05:04 | Goober5000 | Assigned To | => Goober5000 |
| 2009-01-20 05:04 | Goober5000 | Status | new => acknowledged |
| 2009-02-01 22:51 | Zacam | Note Added: 0010636 | |
| 2009-02-01 22:52 | Zacam | Note Edited: 0010636 | |
| 2012-07-01 06:13 | Goober5000 | Note Added: 0013746 | |
| 2012-07-04 07:08 | Goober5000 | Note Added: 0013816 | |
| 2012-07-04 07:08 | Goober5000 | Status | acknowledged => closed |
| 2012-07-04 07:08 | Goober5000 | Resolution | open => no change required |
