View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000485 | FSSCP | gameplay | public | 2005-07-24 20:50 | 2005-08-21 05:30 |
| Reporter | The Trivial Psychic | Assigned To | Goober5000 | ||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Platform | AMD-2600+ 1GB DDR400 ATI9600XT | OS | Win98SE | OS Version | SE |
| Product Version | 3.6.5 | ||||
| Summary | 0000485: FS2 Overrides Fighterbay Departure Target | ||||
| Description | When a fighterwing is given a fighterbay as a departure location, FS2 disregards this and has them jump out. Oddly enough, it still displayed the warp effect even though the box to disable it had been checked... also, even if its not checked. I've seen this in every build since Goober's July 15th build. It still works properly in Taylor's July 3rd build, which leads me to believe that this may have been introduced when the "FRED deletes departure fighterbay target ship" bug was fixed, which occurred between these 2 builds (IIRC). | ||||
| Tags | No tags attached. | ||||
|
|
The FRED departure bug fix only affected FRED. It was simply a UI problem where it tried to find the target location before having a list to search through. There wasn't a change to normal FS2 which went along with that. A quick look at the code and it's something that Goober changed recently in rev. 2.96 where a wing departure point didn't carry over to the individual ships. I would assume that this is a FRED problem where it assigns the departure point to a wing rather than the ships in that wing. |
|
|
Oh crap, I thought that was a bug. Could you tell me where it is and I'll take a look? |
|
|
Yeah, it's in mission/missionparse.cpp around line 2196, a blocked out bit of code. I would guess that FRED just doesn't have something similar and this could be moved there but I'll leave that to you to figure out. :) |
|
|
That's really odd. It's something I changed two years ago that I recently reverted because I don't think I should have changed it in the first place. There might be another undetected bug floating around the code. TP, what were the *exact* conditions leading up to this? Can you reproduce the same behavior in retail? |
|
|
Sorry for leaving this, but the 07-28 build seemed to overcome this. Unfortunately, Taylor's new 08-07 and 08-12 builds suffer from this bug, so your fix appears not to have been committed. After further testing of the 08-12, it appears that ONLY fighters are affected by this bug. I haven't confirmed yet whether this occurs ONLY when departing into bays, as it may occur when arriving from them. |
|
|
Yeah, I know exactly which part in the code is causing this, but I haven't put the fix in CVS yet because I still need to find out exactly why that code was needed in the first place. |
|
|
Update: Kazan's recent 08-14 build doesn't suffer from this. |
|
2005-08-18 18:53
|
|
|
|
Fix is now in CVS. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2005-07-24 20:50 | The Trivial Psychic | New Issue | |
| 2005-07-24 22:46 | taylor | Note Added: 0002871 | |
| 2005-07-24 22:46 | taylor | Assigned To | => Goober5000 |
| 2005-07-24 22:46 | taylor | Status | new => assigned |
| 2005-07-24 23:10 | Goober5000 | Note Added: 0002872 | |
| 2005-07-24 23:30 | taylor | Note Added: 0002873 | |
| 2005-07-27 13:44 | Goober5000 | Note Added: 0002881 | |
| 2005-08-16 20:30 | The Trivial Psychic | Note Added: 0003004 | |
| 2005-08-17 04:52 | Goober5000 | Note Added: 0003010 | |
| 2005-08-17 13:08 | The Trivial Psychic | Note Added: 0003011 | |
| 2005-08-18 18:53 | Fractux | File Added: DepartTest.fs2 | |
| 2005-08-21 05:30 | Goober5000 | Status | assigned => resolved |
| 2005-08-21 05:30 | Goober5000 | Resolution | open => fixed |
| 2005-08-21 05:30 | Goober5000 | Note Added: 0003061 |
