View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000331 | FSSCP | gameplay | public | 2005-02-26 08:09 | 2005-03-15 05:20 |
| Reporter | x0563511 | Assigned To | WMCoolmon | ||
| Priority | normal | Severity | crash | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Summary | 0000331: Error: Can't open file <cruiser03x.pof> | ||||
| Description | Whenever the game attempts to open this file, with or without the mv_*.vp files, the game crashes. For example: Happens on the mission after the Romans Blunder (the icini escapes, you destroy some freighters and two cruisers). (NOT the training missions. The real mission after. | ||||
| Additional Information | fs2_open_T-20050212.exe / fs2_open_T-20050212-dbg.exe Error: Can't open file <cruiser03x.pof> File:U:\src\cvs\fs2_open.linux\code\Model\ModelRead.cpp Line: 1613 Call stack: ------------------------------------------------------------------ model_load() ship_page_in() level_page_in() freespace_mission_load_stuff() game_start_mission() game_enter_state() gameseq_set_state() game_process_event() gameseq_process_events() WinMainSub() WinMain() WinMainCRTStartup() kernel32.dll 7c816d4f() ------------------------------------------------------------------ I find it strange the error is in fs2_open.linux, as I am using windows. | ||||
| Tags | No tags attached. | ||||
|
|
It appears the problem exists in the ships table, present in both mv_aseffects.vp, mv_models.vp, and possibly mv_textures.vp (also occurs within the zpack - how did this escape testing anyways?) Strangely, putting this file into the data/tables directory and changing cruiser03x.pof to cruiser03.pof seems to resolve this particular issue, but then the game crashes with a windows error (Were sorry for the inconvenience, ect. freespace2 needs to close ect.) |
|
|
http://dynamic4.gamespy.com/~freespace/forums/showthread.php?s=&threadid=29938 |
|
|
http://dynamic4.gamespy.com/~freespace/forums/showthread.php?s=&threadid=29938 Does not wholly resolve issues. This does resolve the instance of that file missing, but then i get a general windows error, and the game exits. (without fail, it always does). The game, without any mv_*.vp installed, still sporadically crashes, but my system has some memory problems (specifically attempts to access adress 0x000000). The above error is not caused by this, however. |
|
|
"specifically attempts to access adress 0x000000" I see you're not a programmer.... :) This is about the same as saying your car as some trouble parking when the parking spot is 5 feet up in the air. It's a bug, but it's also being fixed. Have you tried any of the latest builds? |
|
|
Yes, i get the same issue. As far as that memory error: Some CPU/RAM intensive programs/games periodically crash, all attempting to read from that area of RAM. If my understanding of x86 architechture is correct, that is the first byte of the BIOS - the one the system executes at startup. Isn't that usually just a jump to another location anyways? Really, there is no reason why anyhting user-level should be reading from that address. If I'm just being a moron, forgive me :) I should mention that my event log contains a couple of troubling entries every time I boot: AMLI: ACPI BIOS is attempting to write to an illegal IO port address (0xcf8), which lies in the 0xcf8 - 0xcff protected address range. This could lead to system instability. Please contact your system vendor for technical assistance. AMLI: ACPI BIOS is attempting to read from an illegal IO port address (0xcfc), which lies in the 0xcf8 - 0xcff protected address range. This could lead to system instability. Please contact your system vendor for technical assistance. AMLI: ACPI BIOS is attempting to write to an illegal IO port address (0x70), which lies in the 0x70 - 0x71 protected address range. This could lead to system instability. Please contact your system vendor for technical assistance. AMLI: ACPI BIOS is attempting to read from an illegal IO port address (0x71), which lies in the 0x70 - 0x71 protected address range. This could lead to system instability. Please contact your system vendor for technical assistance. The trouble is, I am my own system vendor :) I think it is just time for a new motherboard, CPU, and RAM anyways. It's been 4 years, the first two with overclocked hardware (the CPU is only 2 years old - the first one was the OCed one) edited on: 02-27-05 17:39 |
|
|
Seems like a content problem to me rather than an actual code problem. |
|
|
This is by definition a content problem. And if memory serves, this is just waiting on the next official release for WMC to update the media VP's to something that is correct. The crashing isn't the bug that this report is about, probably one with another report already on Mantis. Although I am a tad bit confused about the linux version being in the error block, I don't think it's anything more serious than the merge of the Linux branch. edited on: 03-14-05 19:53 |
|
|
This bug is/will be fixed with the next mediaVP release. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2005-02-26 08:09 | x0563511 | New Issue | |
| 2005-02-26 21:45 | x0563511 | Note Added: 0001689 | |
| 2005-02-27 10:35 | kasperl | Note Added: 0001693 | |
| 2005-02-27 10:55 | x0563511 | Note Added: 0001694 | |
| 2005-02-27 14:15 | kasperl | Note Added: 0001695 | |
| 2005-02-27 22:36 | x0563511 | Note Added: 0001699 | |
| 2005-02-27 22:39 | x0563511 | Note Edited: 0001699 | |
| 2005-03-13 19:41 | administrator | Assigned To | => WMCoolmon |
| 2005-03-13 19:41 | administrator | Status | new => feedback |
| 2005-03-13 20:29 | Lightspeed | Note Added: 0001851 | |
| 2005-03-15 00:52 | StratComm | Note Added: 0001928 | |
| 2005-03-15 00:53 | StratComm | Note Edited: 0001928 | |
| 2005-03-15 05:20 | WMCoolmon | Status | feedback => resolved |
| 2005-03-15 05:20 | WMCoolmon | Resolution | open => fixed |
| 2005-03-15 05:20 | WMCoolmon | Note Added: 0001957 |
