View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000623 | FSSCP | user interface | public | 2005-11-15 16:26 | 2005-11-16 05:28 |
| Reporter | phreak | Assigned To | taylor | ||
| Priority | high | Severity | crash | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Platform | P4 3.6 GHz | OS | Windows XP | OS Version | SP2 |
| Product Version | 3.6.7 | ||||
| Summary | 0000623: CTD as the final mission to Rouge Intentions Chapter 1 is loading | ||||
| Description | Many people have posted on the forums about this bug and i've been looking into it and it seems that the Wss_slots array is null and is being passed as an argument in commit_pressed(). This mission is a red alert mission and this problem may occur with other red alert missions. To complete the mission, i switched to a build from July 2005 and its works fine on that. | ||||
| Tags | No tags attached. | ||||
|
|
I'm wondering if this bug is related to any of my changes here: http://lore.maxgaming.net/~scp/mantis/bug_view_page.php?bug_id=0000532 |
|
|
Actually, that's probably not the case. The CTD occurs in 3.6.7, and 3.6.7 was released in September (before that fix). edited on: 11-15-05 16:18 |
|
|
Wss_slots has something to do with the loadout code. I think the best idea would be to start working backwards from 3.6.7 and see which build it first appears in. Thankfully, redmenace has been keeping the CVS builds updated nicely, so that helps speed things up. I forget the exact date of my build that worked, but I think it was the 7/15 build. |
|
|
I had this same problem a few weeks ago. I tracked it down to, something I can't remember right now, but I'll go back to that tree and see what I did. It was a init order thing where something was getting skipped in the case of a redalert mission (and some other case I think). This had the do with the teams change since Wss_slots is a ptr now and the ptr doesn't always get initted. No Assert()'s or anything were provided to check for this either. Guess I'll take this one since I should already have a fix for it somewhere. |
|
|
Yep, that was it. Two lines and it's fixed. I'll commit in an hour or two when I get back home. |
|
|
yay~! |
|
|
Ok, that should do it. I did some cleanup and threw a bunch of Assert()'s in there too. We probably need to keep and eye on those for the next few builds but it got through my testing at least. Didn't tackle multi during testing though so that's still a question mark, but it should be fine. |
|
|
Fixered. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2005-11-15 16:26 | phreak | New Issue | |
| 2005-11-15 21:15 | Goober5000 | Note Added: 0003855 | |
| 2005-11-15 21:17 | Goober5000 | Note Added: 0003856 | |
| 2005-11-15 21:17 | Goober5000 | Note Edited: 0003856 | |
| 2005-11-15 21:18 | Goober5000 | Note Edited: 0003856 | |
| 2005-11-15 23:15 | phreak | Note Added: 0003861 | |
| 2005-11-16 02:11 | taylor | Note Added: 0003863 | |
| 2005-11-16 02:11 | taylor | Status | new => assigned |
| 2005-11-16 02:11 | taylor | Assigned To | => taylor |
| 2005-11-16 02:29 | taylor | Note Added: 0003864 | |
| 2005-11-16 05:24 | phreak | Note Added: 0003865 | |
| 2005-11-16 05:27 | taylor | Note Added: 0003866 | |
| 2005-11-16 05:28 | taylor | Status | assigned => resolved |
| 2005-11-16 05:28 | taylor | Resolution | open => fixed |
| 2005-11-16 05:28 | taylor | Note Added: 0003867 |
