View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001042 | FSSCP | gameplay | public | 2006-09-10 05:34 | 2006-09-13 02:01 |
| Reporter | leeisl | Assigned To | taylor | ||
| Priority | normal | Severity | crash | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Summary | 0001042: CTD after Bastion cutscene | ||||
| Description | After the "Bastion Dies" cutscene the game exits straight to desktop. | ||||
| Tags | No tags attached. | ||||
| has duplicate | 0001136 | resolved | (FSP) Red alerts cause an assert failure |
|
|
Does it do the same thing when you view the movie in the techroom too? If so then it's likely a movie related issue. If not then it's probably a mission related issue. |
|
|
Only happens if Clash of the Titans II is played before it during a campaign. Otherwise the movie played normally and the mission briefing shows without trouble. |
|
|
Happened to me too. (I'm glad leeisl reported this and the red tint, as I completely forgot about them.) Same behavior: CTD only when being played in the campaign. Might have something to do with red-alert, since all the other MVEs play fine. |
|
|
Hmm, thought it might be a red-alert issue. Does it give an error message, or log anything? I'll have to try this out myself I guess and see if gdb can make anything of it. |
|
|
No error messages or logs, the games simply exits straight to desktop. |
|
|
Just to clarify when it happens: - If you play Clash of the Titans II, then the movie plays, then the crash. - So after it crashes and you go back into the game, you continue, it plays the movie, and it doesn't crash. Is that correct? If so then it looks to be an issue with the red-alert wingman status when it tries to bash out the weapon config for the various ships in the wings. I'm still tracing through it to figure out exactly why/where/what is going on, not to mention why it works fine if you don't play Clash of the Titans II first. |
|
|
Re clarification: Yes, that's what happens. Sorry, I didn't think to keep my log around. I'll see if I can put together a two-mission campaign that reproduces it. |
|
|
I've already been testing with a two mission campaign. :) The problem seems to be with Wss_slots_teams[], and it doesn't appear to be getting reset properly between missions. If you only do the one mission then it's got all of the correct data but moving between missions it appears to keep the old configuration (at least in the red-alert case). Since some of your wingmen die, they should no longer exist in Wss_slots, but it as it still holds some config info for them it there will be issues when it runs through the ship/weapon select screen setup. And I think that's where it's crashing (at least I'm getting hit with Assert's there and there are a lot of really bad Some_Array[-1] issues). I haven't had the chance to figure out exactly how it prunes out stale ships from a wing. Well, I know the functions for it, I just don't know when and from where it's happening. I assume that something is just getting missed. |
|
|
Hmm. Maybe the "ghost ships" bug is related. Red alert has never really worked 100%. |
|
|
Well the problem is that if it just uses red-alert data when setting up the wings then it works. If it's coming from a previous mission to a red-alert mission then it doesn't have the wings setup properly. This seems like broken behavior and not some retail, or even pilot file, related issue. I suppose that it could be pilot file related, but I didn't really change that stuff enough to have broken this. My first guess is that it's some issue related to the change for wings team support. There were numerous issues with that (NULL ptrs, things not get reset properly, etc.) in the first place when the changes were originally made, so perhaps this is just one more that we didn't notice until now. I'm working on it though, shouldn't take too long to track down once I get the time to actually sit down and do it. |
|
|
Oooh, ship_select_common_init() was missing from red_alert_init(). weapon_select_common_init() was added to fix a previous bug (I remember doing that to address the ptrs problem), but I either didn't notice that the ship ptrs needed to be reset as well, or I tried it and it started crashing on me. I'll have to test it again to make sure, but I think that this is the problem. So far it's testing ok though. And as you mentioned, I think that this will likely fix the "ghost ships" issue as well. |
|
|
Sorry, karajorma, but I've already fixed this. :) |
|
|
Fixered. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2006-09-10 05:34 | leeisl | New Issue | |
| 2006-09-10 20:43 | taylor | Note Added: 0006590 | |
| 2006-09-11 04:47 | leeisl | Note Added: 0006594 | |
| 2006-09-11 22:30 | Goober5000 | Note Added: 0006597 | |
| 2006-09-12 00:03 | taylor | Note Added: 0006598 | |
| 2006-09-12 04:49 | leeisl | Note Added: 0006599 | |
| 2006-09-12 07:01 | taylor | Note Added: 0006600 | |
| 2006-09-12 12:56 | Goober5000 | Note Added: 0006601 | |
| 2006-09-12 17:07 | taylor | Note Added: 0006602 | |
| 2006-09-12 18:31 | Goober5000 | Note Added: 0006603 | |
| 2006-09-12 19:47 | taylor | Note Added: 0006605 | |
| 2006-09-12 20:32 | taylor | Note Added: 0006606 | |
| 2006-09-12 21:39 | karajorma | Status | new => assigned |
| 2006-09-12 21:39 | karajorma | Assigned To | => karajorma |
| 2006-09-12 22:07 | taylor | Note Added: 0006609 | |
| 2006-09-12 22:08 | taylor | Assigned To | karajorma => taylor |
| 2006-09-13 02:01 | taylor | Status | assigned => resolved |
| 2006-09-13 02:01 | taylor | Resolution | open => fixed |
| 2006-09-13 02:01 | taylor | Note Added: 0006613 | |
| 2007-02-06 03:28 | Goober5000 | Relationship added | has duplicate 0001136 |
