View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001793 | FSSCP | user interface | public | 2008-10-10 05:41 | 2009-01-20 05:19 |
| Reporter | chief1983 | Assigned To | FSO 4 | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | suspended | ||
| Platform | x86-64 | OS | Windows | OS Version | XP32 SP3 |
| Product Version | 3.6.9 | ||||
| Summary | 0001793: Strange behavior with hidden ships in tech room | ||||
| Description | I'm reporting this while it's still fresh in my memory, exactly what I did to cause it. It seems like there's some bizarre behavior with hiding ships in the tech room. Perhaps weapons too, not sure. Basically things seem to become visible in the tech room when they shouldn't when switching between multiplayer and single player. First seen using pre-release FSPort 3.1 data. | ||||
| Steps To Reproduce | Ok, I was working with the new FSPort 3.1 files. I had not yet used a multiplayer user with this mod yet. I went to the tech room as a single player user, and many things were hidden, as they should be. I'm not sure exactly what was hidden, but I don't believe there were any #stuff ships visible, and I know there was only the one GTA fighter, the Apollo. I noticed the 'in tech database multi' flag was applied to many of the ships, so I clone a multiplayer pilot I already had from regular FS2 and selected that pilot. Not only did all the ships with 'in tech database multi' show up in the tech room, all the ships with # identifiers in their names did as well. I didn't think that was supposed to be the case, but I'm guessing 'ship copy' brought over that flag as well. So I saw the stealth loki, bastion, galatea, etc. I went back to the barracks, and switched back to my single player pilot, and when going back to the tech room, all of these ships are now still visible. | ||||
| Additional Information | I'm not sure what of this is supposed to be expected behavior, but I was under the impression that the # ships were never supposed to show up in normal operation, and that switching back to a single player pilot should still honor the 'in tech database multi' flag. It's like it automatically unlocked them for my single player pilot the way a campaign would. If I do more testing on this I'll keep it updated. | ||||
| Tags | No tags attached. | ||||
|
|
You may need to hit the View Advanced button to read all of this, I noticed it doesn't show or indicate the Steps to Reproduce field unless you use that view. |
|
|
Ok, I've tried to do this in a simpler form. I created a new pilot when the game started. It had the proper tech entries. I also told it not to show tips again. I went to the barracks, and converted this pilot. I selected the new multiplayer pilot, told it not to show me tips again, went to the tech room, and there were the ships that shouldn't be showing up, anything with a # in its name AND the base entry is supposed to be in the multi tech database. So I go back to the barracks to my single player pilot, and the ships aren't showing up. Not sure what broke my pilot previously, but it was a more complicated situation. Anyway, seeing that that pilot is sane, I went back to the multiplayer pilot. Tech room still broken. I quit the game with this pilot loaded. Reran, selected that pilot at the start, ships with # are gone. The original bug may be related to the use of Ctrl+Shift+S. However, these ships with # in the name should never be showing up through normal operation, which they seem to do. |
|
|
This is due to a limitation of the pilot file. Since the pilot saves only the ship indexes, not the names, you are likely to get bizarre results when you switch mods with the same pilot. It's for this reason that we recommend creating a new mission at the pilot selection screen when the game first starts. This won't be fixed until the new pilot code is introduced in 3.7. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2008-10-10 05:41 | chief1983 | New Issue | |
| 2008-10-10 20:11 | chief1983 | Note Added: 0009927 | |
| 2008-10-11 02:58 | chief1983 | Note Added: 0009929 | |
| 2009-01-20 05:19 | Goober5000 | Note Added: 0010572 | |
| 2009-01-20 05:19 | Goober5000 | Assigned To | => FSO 4 |
| 2009-01-20 05:19 | Goober5000 | Status | new => closed |
| 2009-01-20 05:19 | Goober5000 | Resolution | open => suspended |
