View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000660 | FSSCP | gameplay | public | 2005-12-26 20:49 | 2005-12-31 07:06 |
| Reporter | pvh | Assigned To | |||
| Priority | normal | Severity | crash | Reproducibility | always |
| Status | closed | Resolution | open | ||
| Summary | 0000660: First nebula mission crashes during first contact with Shivans in the Nebula | ||||
| Description | I can crash my FSSCP consistently at the point where the Shivans first appear in the nebula. This is with all stock VPs both 1.00 and 1.20 and the 3.6.7 media VPs. Please contact me if you would like more information, I would be very happy to help figure this out. I am a coder, though I am not familiar with FS code yet. (pvh@pvh.ca) | ||||
| Additional Information | Linux, with trivial command-line options (./fs2). | ||||
| Tags | No tags attached. | ||||
|
|
Are you using a current CVS build or the 3.6.7 release? Use a debug build and attach the ~/.fs2_open/data/fs2_open.log file. |
|
2005-12-27 05:35
|
|
|
|
I am running 3.6.7 release. I cannot checkout from warpcore.org as documented in various places. Perhaps the information is out of date? Attached my debug log. Here is the output to console. ----------------------------- pvh@arroyo:~/mnt/fsnew $ ./fs2_open_d Future debug output directed to: /home/pvh/.fs2_open/data/fs2_open.log WARNING: "Couldn't open texture 'TerranHuge_Bitmap' referenced by weapon 'Terran Huge Turret'" at weapon/weapons.cpp:2028 WARNING: "Couldn't open glow texture 'CapTurret_Glow' referenced by weapon 'Terran Huge Turret'" at weapon/weapons.cpp:2069 WARNING: "Couldn't open texture 'Terran_Turret' referenced by weapon 'Terran Turret'" at weapon/weapons.cpp:2028 WARNING: "Couldn't open texture 'Terran_Turret' referenced by weapon 'Terran Turret Weak'" at weapon/weapons.cpp:2028 WARNING: "Couldn't open texture 'HVasuden_Bitmap' referenced by weapon 'Vasudan Huge Turret'" at weapon/weapons.cpp:2028 WARNING: "Couldn't open glow texture 'CapTurret_Glow' referenced by weapon 'Vasudan Huge Turret'" at weapon/weapons.cpp:2069 WARNING: "Couldn't open texture 'VasTurret_Bitmap' referenced by weapon 'Vasudan Turret'" at weapon/weapons.cpp:2028 WARNING: "Couldn't open glow texture 'CapTurret_Glow' referenced by weapon 'Vasudan Turret'" at weapon/weapons.cpp:2069 WARNING: "Couldn't open texture 'Shiven_Megafunk' referenced by weapon 'Shivan Megafunk Turret'" at weapon/weapons.cpp:2028 WARNING: "Couldn't fix up turret indices in spline path Model: cruiser01.pof Path: $path02 Vertex: 1 Turret model id:13 This probably means the turret was not specified in TurretAngleFix-shp.tbm" at ship/ship.cpp:7808 WARNING: "Couldn't fix up turret indices in spline path Model: cruiser01.pof Path: $path02 Vertex: 2 Turret model id:13 This probably means the turret was not specified in TurretAngleFix-shp.tbm" at ship/ship.cpp:7808 WARNING: "Couldn't fix up turret indices in spline path Model: cruiser01.pof Path: $path02 Vertex: 3 Turret model id:13 This probably means the turret was not specified in TurretAngleFix-shp.tbm" at ship/ship.cpp:7808 WARNING: "Couldn't open texture 'red_glow_small' referenced by model 'fighter2t-02.pof'" at model/modelread.cpp:2310 WARNING: "Couldn't open texture 'red_glow_small' referenced by model 'fighter2t-02.pof'" at model/modelread.cpp:2310 WARNING: "Couldn't open texture 'yellow_glow2_small' referenced by model 'fighter2t-02.pof'" at model/modelread.cpp:2310 Segmentation fault ----------------------------- |
|
|
The CVS server is down at the moment so you'll have to wait for that to get fixed before grabbing a checkout. From the log I notice a couple of things, you need to use either -jpgtga or -img2dds in order those missing textures to show up. You video drivers are a bit old and may not work well with -img2dds though. Upgrade those if you can. I know about all of the stability stuff with newer versions so the upgrade suggestion is just a suggestion if you are keeping an old version for a reason. It would probably be a good idea to update your OpenAL version too, the code is getting a bit picky about some of the 0.0.7 releases. Go with a relatively current 1.0 version (probably 0.0.8 or higher) or make the attempt at 1.1. And do try to get a log file with the crash since that may show something that was leading up to the crash (Int3() call or something like that). Edit: Assuming that log wasn't with a crash, it ended with a QUIT_GAME event so I'm guessing it was a clean shutdown. edited on: 12-27-05 01:50 |
|
|
pvh@arroyo:~/mnt/fsnew $ ./play Future debug output directed to: /home/pvh/.fs2_open/data/fs2_open.log WARNING: "Couldn't fix up turret indices in spline path Model: cruiser01.pof Pa th: $path02 Vertex: 1 Turret model id:13 This probably means the turret was not specified in TurretAngleFix-shp.tbm" at ship/ship.cpp:7808 WARNING: "Couldn't fix up turret indices in spline path Model: cruiser01.pof Pa th: $path02 Vertex: 2 Turret model id:13 This probably means the turret was not specified in TurretAngleFix-shp.tbm" at ship/ship.cpp:7808 WARNING: "Couldn't fix up turret indices in spline path Model: cruiser01.pof Pa th: $path02 Vertex: 3 Turret model id:13 This probably means the turret was not specified in TurretAngleFix-shp.tbm" at ship/ship.cpp:7808 ./play: line 3: 17624 Segmentation fault ./fs2_open_d -spec -glow -jpgtga - nomotiondebris -2d_poof -missile_lighting -no_vsync -dualscanlines -targetinfo - rearm_timer -ballistic_gauge -nobeampierce -ship_choice_3d -3dwarp -warp_flash - snd_preload -fps -allslev -ambient_factor 65 -orbradar |
|
2005-12-27 12:32
|
|
|
|
Well, still reproducible with upgraded video drivers and recommended commandline options. I did note the ship.cpp:7808 message on the commandline output. I intend to take a look and see if it is relevant tomorrow. OpenAL will be a bit more of a pain to update, so I'm putting it off for now. |
|
|
More notes, this is mission SM1-05, and is duplicable under all circumstances with or without the enemies being onscreen. I have updated to OpenAL 1.1, which did not have any effect. I very occasionally make it through the first fight. Once I made it as far as the Titan, and another time it crashed during the second wave of enemies. Can I get some VP checksums to make sure I don't have corrupt resources? -p edited on: 12-28-05 00:07 |
|
|
Also try removing the MediaVPs and see if it still crashes. Here are the retail VP checksums from the English 1.2 version: 0d9fd69acfe8b29d616377b057d2fc04 root_fs2.vp 2a47bdf14860071cf0196d92e9ee7c2f sparky_fs2.vp 97661124cdc47c0a2f0678982b8cbd91 sparky_hi_fs2.vp 0d662decc0b443ccb8e8aa2e3a0887ce smarty_fs2.vp e88f0e0011b3e525a5ad625933684c03 stu_fs2.vp 8ca7330cfe63329b41868efc2e40e048 tango1_fs2.vp 6fb6e9a36248980540155a9777c51c47 tango2_fs2.vp d42c20b6ffb4782e431899c211ae55c4 tango3_fs2.vp f7f346e4c0339ba38cff4d9d4dc663f3 tangoA_fs2.vp d1f3c39d4fe1bbd56b7b06fe66eef4a6 warble_fs2.vp |
|
|
No media VPs, same problem! Other missions are playing fine, I have played through to SM1-08 (or so) without any further glitches, including fights with Manticores and another nebula level. I am beginning to suspect that this is a bug only uncovered by the level. I have not been able to build wxfred2 yet, but I'm working on that. Perhaps there is some insight in the event that spawns those two first enemy wings. Are they unique in some way? I have not yet found crashes in any mission other than this one. Is there any way I could get a fresh copy of the CVS tree? Perhaps via scp? Edit: We could take this to a slightly more interactive medium if you like. I am 3664795 on ICQ, and I have presences on most other chat networks. Also, I can give you access to this machine if you'd like to try a remote session to see for yourself. edited on: 12-28-05 03:12 |
|
|
CVS should be back up now so try to get a checkout, run a debug build in gdb and post the backtrace when it crashes. I've tried the mission several times myself since this bug was reported and haven't had a problem so far. |
|
|
A fresh CVS build appears to fix this bug. I just played through the mission with no trouble. |
|
|
Cool. If it starts happening again just reopen this bug. |
|
|
Closered. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2005-12-26 20:49 | pvh | New Issue | |
| 2005-12-26 20:59 | taylor | Note Added: 0004052 | |
| 2005-12-27 05:35 | pvh | File Added: fs2_open.log | |
| 2005-12-27 05:35 | pvh | Note Added: 0004053 | |
| 2005-12-27 06:48 | taylor | Note Added: 0004055 | |
| 2005-12-27 06:50 | taylor | Note Edited: 0004055 | |
| 2005-12-27 12:32 | pvh | Note Added: 0004057 | |
| 2005-12-27 12:32 | pvh | File Added: 2.log | |
| 2005-12-27 12:54 | pvh | Note Added: 0004058 | |
| 2005-12-28 03:06 | pvh | Note Added: 0004059 | |
| 2005-12-28 05:07 | pvh | Note Edited: 0004059 | |
| 2005-12-28 07:33 | taylor | Note Added: 0004060 | |
| 2005-12-28 08:10 | pvh | Note Added: 0004061 | |
| 2005-12-28 08:12 | pvh | Note Edited: 0004061 | |
| 2005-12-29 05:13 | taylor | Note Added: 0004063 | |
| 2005-12-31 00:41 | pvh | Note Added: 0004080 | |
| 2005-12-31 07:06 | taylor | Note Added: 0004084 | |
| 2005-12-31 07:06 | taylor | Status | new => closed |
| 2005-12-31 07:06 | taylor | Note Added: 0004085 |
