View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001571 | FSSCP | mediaVP | public | 2008-01-14 09:38 | 2008-04-04 17:16 |
| Reporter | Zacam | Assigned To | taylor | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | no change required | ||
| Platform | Morkaleb | OS | WinXP 32bit/64bit | OS Version | 3.1c |
| Summary | 0001571: Debug Log FSO 3.6.9 & 3.6.10 w/ MVP 3.6.10 Beta | ||||
| Description | Wokka! Error opening file (scripting.tbl)! TABLES: Unable to parse 'scripting.tbl'! Error code = 5. Wokka! Error opening file (interface.tbl)! WMCGUI: Unable to parse 'interface.tbl'! Error code = 5. Wokka! Error opening file (armor.tbl)! TABLES: Unable to parse 'armor.tbl'! Error code = 5. WARNING: "Too many beam sections for weapon BFRed - max is 5" at Weapons.cpp:2977 **The following are probably irrelevant since they are NOT ships, however..** Model warp.pof has a null moment of inertia! (This is only a problem if the model is a ship.) Model shockwave.pof has a null moment of inertia! (This is only a problem if the model is a ship.) Model subspacenode.pof has a null moment of inertia! (This is only a problem if the model is a ship.) Model starfield.pof has a null moment of inertia! (This is only a problem if the model is a ship.) ***...These are weapons that may require inertia and these...*** Model hornet.pof has a null moment of inertia! (This is only a problem if the model is a ship.) Model NewHornet.pof has a null moment of inertia! (This is only a problem if the model is a ship.) Model cmeasure01.pof has a null moment of inertia! (This is only a problem if the model is a ship.) Model cargo03.pof has a null moment of inertia! (This is only a problem if the model is a ship.) ****...these ARE ships!**** Model fighter2v-01.pof has a null moment of inertia! (This is only a problem if the model is a ship.) Model fighter2t-05.pof has a null moment of inertia! (This is only a problem if the model is a ship.) Model fighter06.pof has a null moment of inertia! (This is only a problem if the model is a ship.) Model capital2s-01.pof has a null moment of inertia! (This is only a problem if the model is a ship.) Model science01.pof has a null moment of inertia! (This is only a problem if the model is a ship.) Unknown special object type $path29 while reading model Base2r-01.pof Unknown special object type $path45 while reading model capital2t-01.pof Unknown special object type $path29 while reading model corvette2r-01.pof Unknown special object type $reactor while reading model science01.pof Warning: Ignoring unrecognized subsystem fighterbay, believed to be in ship capital01.pof Warning: Ignoring unrecognized subsystem asteroid02a, believed to be in ship Base2r-01.pof Warning: Ignoring unrecognized subsystem bunker01a, believed to be in ship Base2r-01.pof Warning: Ignoring unrecognized subsystem bunker02a, believed to be in ship Base2r-01.pof Warning: Ignoring unrecognized subsystem comtowera, believed to be in ship Base2r-01.pof Warning: Ignoring unrecognized subsystem fighterbaya, believed to be in ship Base2r-01.pof Warning: Ignoring unrecognized subsystem asteroid01a, believed to be in ship Base2r-01.pof Warning: Ignoring unrecognized subsystem fighterbay, believed to be in ship capital2t-01.pof Warning: Ignoring unrecognized subsystem reactor, believed to be in ship capital2V-01.pof Warning: Ignoring unrecognized subsystem bridge, believed to be in ship capital2V-01.pof Warning: Ignoring unrecognized subsystem fighterbay01, believed to be in ship capital2V-01.pof Warning: Ignoring unrecognized subsystem fighterbay02, believed to be in ship capital2V-01.pof Warning: Ignoring unrecognized subsystem fighterbay01, believed to be in ship capital2s-01.pof Warning: Ignoring unrecognized subsystem fighterbay02, believed to be in ship capital2s-01.pof Warning: Ignoring unrecognized subsystem fighterbay 1, believed to be in ship capital04.pof Warning: Ignoring unrecognized subsystem fighterbay 2, believed to be in ship capital04.pof WARNING: "For ship 'TAC 1', detail level mismatch (POF needs 5)" at Ship.cpp:8966 (Repeated multiple times) WARNING: "Couldn't fix up turret indices in spline path Model: science01.pof Path: $path04 Vertex: 0 Turret model id:16 This probably means that the turret was not specified in the ship table(s)." at Ship.cpp:9048 WARNING: "Couldn't fix up turret indices in spline path Model: capital2t-01.pof Path: $path02 Vertex: 1 Turret model id:22 This probably means that the turret was not specified in the ship table(s)." at Ship.cpp:9048 WARNING: "Couldn't fix up turret indices in spline path Model: capital2t-01.pof Path: $path02 Vertex: 2 Turret model id:22 This probably means that the turret was not specified in the ship table(s)." at Ship.cpp:9048 WARNING: "Couldn't fix up turret indices in spline path Model: capital2t-01.pof Path: $path02 Vertex: 3 Turret model id:11 This probably means that the turret was not specified in the ship table(s)." at Ship.cpp:9048 WARNING: "Couldn't fix up turret indices in spline path Model: capital2t-01.pof Path: $path02 Vertex: 3 Turret model id:22 This probably means that the turret was not specified in the ship table(s)." at Ship.cpp:9048 WARNING: "Couldn't fix up turret indices in spline path Model: capital2t-01.pof Path: $path03 Vertex: 2 Turret model id:21 This probably means that the turret was not specified in the ship table(s)." at Ship.cpp:9048 WARNING: "Couldn't fix up turret indices in spline path Model: capital2t-01.pof Path: $path03 Vertex: 2 Turret model id:28 This probably means that the turret was not specified in the ship table(s)." at Ship.cpp:9048 WARNING: "Couldn't fix up turret indices in spline path Model: capital2t-01.pof Path: $path03 Vertex: 3 Turret model id:11 This probably means that the turret was not specified in the ship table(s)." at Ship.cpp:9048 WARNING: "Couldn't fix up turret indices in spline path Model: capital2t-01.pof Path: $path03 Vertex: 3 Turret model id:21 This probably means that the turret was not specified in the ship table(s)." at Ship.cpp:9048 WARNING: "Couldn't fix up turret indices in spline path Model: capital2t-01.pof Path: $path04 Vertex: 3 Turret model id:11 This probably means that the turret was not specified in the ship table(s)." at Ship.cpp:9048 WARNING: "Couldn't fix up turret indices in spline path Model: capital2t-01.pof Path: $path04 Vertex: 3 Turret model id:21 This probably means that the turret was not specified in the ship table(s)." at Ship.cpp:9048 WARNING: "Couldn't fix up turret indices in spline path Model: capital2t-01.pof Path: $path04 Vertex: 3 Turret model id:28 This probably means that the turret was not specified in the ship table(s)." at Ship.cpp:9048 Could not find a usable muzzle glow bitmap for 'AAAf'! WARNING: "Could not find a usable muzzle glow bitmap (AAAbeamAglow) for weapon 'AAAf'!" at Weapons.cpp:3737 Could not find a usable muzzle glow bitmap for 'AAAh'! WARNING: "Could not find a usable muzzle glow bitmap (AAAbeamAglow) for weapon 'AAAh'!" at Weapons.cpp:3737 A LOT of "Could not create debris, no more slots left" <--Probably EXE process not VP related. message 'Bosch' with invalid head. Fix by assigning persona to the message. message 'Make This Brief' with invalid head. Fix by assigning persona to the message. message 'Unfettered Access' with invalid head. Fix by assigning persona to the message. message 'efforts to intercept failed' with invalid head. Fix by assigning persona to the message. message 'Get Out' with invalid head. Fix by assigning persona to the message. message 'Guard us' with invalid head. Fix by assigning persona to the message. message 'Asteroids' with invalid head. Fix by assigning persona to the message. | ||||
| Steps To Reproduce | A variety collection of errors noted within The training missions and the first 4 campaign missions. I also jumped ahead to Loop-01 "Rebels & Renegades". Some of these have been reported elswhere I'm sure, so I do apologize for any duplicates, you may consider them confirmations of existing ones. | ||||
| Additional Information | Since I was focusing on the MediaVP's for this run, I only focused on errors or warnings that were duplicated between both 3.6.9 and 3.6.10 exe's. So far, there are no cases of one reporting an error and not the other. | ||||
| Tags | No tags attached. | ||||
