View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001025 | FSSCP | --------- | public | 2006-08-08 05:46 | 2006-08-20 13:49 |
| Reporter | Nalin | Assigned To | Goober5000 | ||
| Priority | normal | Severity | crash | Reproducibility | always |
| Status | closed | Resolution | open | ||
| Summary | 0001025: Consistant crash when playing Silent Threat mission: Exodus | ||||
| Description | I continually get a crash at the start of the Silent Threat mission "Exodus" (md_09.fs2) from the Freespace Port 3.0.3 mod. Anything after 3.6.9 RC5 crashes. Basically, the light test and the RC6 build crashes, yet RC5 and under do not. I have attached the log files created during the crash after running the debug light-test build. | ||||
| Tags | No tags attached. | ||||
|
2006-08-08 05:46
|
|
|
|
What happens just before it crashes? Is it immediate, or can you fly around first? |
|
|
It varies. Sometimes it happens right before the ship blows up. It once crashed when my wingmen warped in and I switched to the right view to watch it happen. But I have never been able to get passed the Krios blowing up. |
|
|
Well I couldn't get it to crash in either release or debug. Try this build and see if it still crashes: http://fs2source.warpcore.org/temp/temp.zip |
|
|
I tried playing the mission again with the RC6 buid yet I could not get it to crash, although I noticed something odd. I tested the mission again by loading it from the Tech Room. When I started the mission this way, I began with 100 health and full missiles. However, when I played through the campaign normally, I entered the mission with 23 health and only a couple missiles. I had thought this was weird since I ended the previous mission with a lot more than 23 health. I had thought starting with 23 health and only around 5 missiles was normal for this mission. I wonder if this bug can only be duplicated by playing through the campaign normally? Unfortunately, I don't have the time to test this theory. I might be able to test it this Saturday if I remember. As it is, I don't have any free time at all until Saturday for an extended play time. >_> Is there an easy way to sort of hack a pilot to resume the campaign from the mission before "Exodus"? |
|
|
Exodus is a red-alert mission, meaning it loads the status of your ship from the last time you played a mission that ended in red-alert -- not necessarily the previous mission. This is just a Volition bug that showed up in Silent Threat because of the generally poor quality of the whole campaign. It'll be fixed with the new pilot code. If you couldn't get it to crash any more, then we should probably close this bug. |
|
|
Closed. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2006-08-08 05:46 | Nalin | New Issue | |
| 2006-08-08 05:46 | Nalin | File Added: fs2_crash.rar | |
| 2006-08-08 14:49 | Goober5000 | Note Added: 0006394 | |
| 2006-08-08 19:06 | Nalin | Note Added: 0006405 | |
| 2006-08-14 17:54 | Goober5000 | Status | new => assigned |
| 2006-08-14 17:54 | Goober5000 | Assigned To | => Goober5000 |
| 2006-08-18 02:43 | Goober5000 | Note Added: 0006470 | |
| 2006-08-18 04:48 | Nalin | Note Added: 0006471 | |
| 2006-08-18 12:53 | Goober5000 | Note Added: 0006472 | |
| 2006-08-20 13:49 | Goober5000 | Status | assigned => closed |
| 2006-08-20 13:49 | Goober5000 | Note Added: 0006498 |
