==========================================================================
DEBUG SPEW: No debug_filter.cfg found, so only general, error, and warning
categories can be shown and no debug_filter.cfg info will be saved.
==========================================================================
FreeSpace 2 Open version: 3.6.13
Passed cmdline options:
-spec_exp 8.2
-spec_static 3.5
-spec_point 8.6
-spec_tube 1.0
-ambient_factor 70
-mipmap
-missile_lighting
-glow
-spec
-3dshockwave
-orbradar
-rearm_timer
-targetinfo
-3dwarp
-ship_choice_3d
-warp_flash
-snd_preload
-mod blueplanet2,blueplanet,mediavps_3612
Building file index...
Found root pack 'C:\Games\FreeSpace2\blueplanet2\bp2-adv-visuals.vp' with a checksum of 0x241c257f
Found root pack 'C:\Games\FreeSpace2\blueplanet2\bp2-audio1.vp' with a checksum of 0x51171798
Found root pack 'C:\Games\FreeSpace2\blueplanet2\bp2-core.vp' with a checksum of 0xe386a796
Found root pack 'C:\Games\FreeSpace2\blueplanet2\bp2-visuals1.vp' with a checksum of 0xd263c407
Found root pack 'C:\Games\FreeSpace2\blueplanet2\bp2-visuals2.vp' with a checksum of 0xd3552477
Found root pack 'C:\Games\FreeSpace2\blueplanet\bp-adv-visuals.vp' with a checksum of 0xbba0f03c
Found root pack 'C:\Games\FreeSpace2\blueplanet\bp-audio1.vp' with a checksum of 0xe79b67ce
Found root pack 'C:\Games\FreeSpace2\blueplanet\bp-audio2.vp' with a checksum of 0xb50d55b7
Found root pack 'C:\Games\FreeSpace2\blueplanet\bp-core.vp' with a checksum of 0x6b804787
Found root pack 'C:\Games\FreeSpace2\blueplanet\bp-visuals1.vp' with a checksum of 0x316467fa
Found root pack 'C:\Games\FreeSpace2\blueplanet\bp-visuals2.vp' with a checksum of 0x39fe8221
Found root pack 'C:\Games\FreeSpace2\mediavps_3612\MV_Advanced.vp' with a checksum of 0x4b8b0f5a
Found root pack 'C:\Games\FreeSpace2\mediavps_3612\MV_AnimGlows.vp' with a checksum of 0x6a554026
Found root pack 'C:\Games\FreeSpace2\mediavps_3612\MV_Assets.3612.vp' with a checksum of 0x59649c21
Found root pack 'C:\Games\FreeSpace2\mediavps_3612\MV_Assets.vp' with a checksum of 0x529cc70f
Found root pack 'C:\Games\FreeSpace2\mediavps_3612\MV_Effects.3612.vp' with a checksum of 0x9c510aa0
Found root pack 'C:\Games\FreeSpace2\mediavps_3612\MV_Effects.vp' with a checksum of 0xb9a9a485
Found root pack 'C:\Games\FreeSpace2\mediavps_3612\MV_Music.vp' with a checksum of 0xb3e21469
Found root pack 'C:\Games\FreeSpace2\mediavps_3612\MV_RadarIcons.vp' with a checksum of 0x31dd7781
Found root pack 'C:\Games\FreeSpace2\mediavps_3612\MV_Root.3612.vp' with a checksum of 0x7c9d7e74
Found root pack 'C:\Games\FreeSpace2\mediavps_3612\MV_Root.vp' with a checksum of 0x6ffd5c78
Found root pack 'C:\Games\FreeSpace2\multi-voice-pack.vp' with a checksum of 0xd50e7442
Found root pack 'C:\Games\FreeSpace2\root_fs2.vp' with a checksum of 0xce10d76c
Found root pack 'C:\Games\FreeSpace2\smarty_fs2.vp' with a checksum of 0xddeb3b1e
Found root pack 'C:\Games\FreeSpace2\sparky_fs2.vp' with a checksum of 0x164fe65a
Found root pack 'C:\Games\FreeSpace2\sparky_hi_fs2.vp' with a checksum of 0xa11d56f1
Found root pack 'C:\Games\FreeSpace2\stu_fs2.vp' with a checksum of 0xd77da83a
Found root pack 'C:\Games\FreeSpace2\tango1_fs2.vp' with a checksum of 0x4c25221e
Found root pack 'C:\Games\FreeSpace2\tango2_fs2.vp' with a checksum of 0x86920b82
Found root pack 'C:\Games\FreeSpace2\tango3_fs2.vp' with a checksum of 0x705e8d71
Found root pack 'C:\Games\FreeSpace2\warble_fs2.vp' with a checksum of 0xd85c305d
Searching root 'C:\Games\FreeSpace2\blueplanet2\' ... 3 files
Searching root pack 'C:\Games\FreeSpace2\blueplanet2\bp2-adv-visuals.vp' ... 31 files
Searching root pack 'C:\Games\FreeSpace2\blueplanet2\bp2-audio1.vp' ... 156 files
Searching root pack 'C:\Games\FreeSpace2\blueplanet2\bp2-core.vp' ... 72 files
Searching root pack 'C:\Games\FreeSpace2\blueplanet2\bp2-visuals1.vp' ... 641 files
Searching root pack 'C:\Games\FreeSpace2\blueplanet2\bp2-visuals2.vp' ... 2012 files
Searching root 'C:\Games\FreeSpace2\blueplanet\' ... 0 files
Searching root pack 'C:\Games\FreeSpace2\blueplanet\bp-adv-visuals.vp' ... 358 files
Searching root pack 'C:\Games\FreeSpace2\blueplanet\bp-audio1.vp' ... 41 files
Searching root pack 'C:\Games\FreeSpace2\blueplanet\bp-audio2.vp' ... 683 files
Searching root pack 'C:\Games\FreeSpace2\blueplanet\bp-core.vp' ... 52 files
Searching root pack 'C:\Games\FreeSpace2\blueplanet\bp-visuals1.vp' ... 374 files
Searching root pack 'C:\Games\FreeSpace2\blueplanet\bp-visuals2.vp' ... 1488 files
Searching root 'C:\Games\FreeSpace2\mediavps_3612\' ... 0 files
Searching root pack 'C:\Games\FreeSpace2\mediavps_3612\MV_Advanced.vp' ... 1283 files
Searching root pack 'C:\Games\FreeSpace2\mediavps_3612\MV_AnimGlows.vp' ... 1641 files
Searching root pack 'C:\Games\FreeSpace2\mediavps_3612\MV_Assets.3612.vp' ... 315 files
Searching root pack 'C:\Games\FreeSpace2\mediavps_3612\MV_Assets.vp' ... 1527 files
Searching root pack 'C:\Games\FreeSpace2\mediavps_3612\MV_Effects.3612.vp' ... 10 files
Searching root pack 'C:\Games\FreeSpace2\mediavps_3612\MV_Effects.vp' ... 1876 files
Searching root pack 'C:\Games\FreeSpace2\mediavps_3612\MV_Music.vp' ... 32 files
Searching root pack 'C:\Games\FreeSpace2\mediavps_3612\MV_RadarIcons.vp' ... 24 files
Searching root pack 'C:\Games\FreeSpace2\mediavps_3612\MV_Root.3612.vp' ... 13 files
Searching root pack 'C:\Games\FreeSpace2\mediavps_3612\MV_Root.vp' ... 94 files
Searching root 'C:\Games\FreeSpace2\' ... 16 files
Searching root pack 'C:\Games\FreeSpace2\multi-voice-pack.vp' ... 307 files
Searching root pack 'C:\Games\FreeSpace2\root_fs2.vp' ... 157 files
Searching root pack 'C:\Games\FreeSpace2\smarty_fs2.vp' ... 10 files
Searching root pack 'C:\Games\FreeSpace2\sparky_fs2.vp' ... 3027 files
Searching root pack 'C:\Games\FreeSpace2\sparky_hi_fs2.vp' ... 1337 files
Searching root pack 'C:\Games\FreeSpace2\stu_fs2.vp' ... 2355 files
Searching root pack 'C:\Games\FreeSpace2\tango1_fs2.vp' ... 32 files
Searching root pack 'C:\Games\FreeSpace2\tango2_fs2.vp' ... 15 files
Searching root pack 'C:\Games\FreeSpace2\tango3_fs2.vp' ... 10 files
Searching root pack 'C:\Games\FreeSpace2\warble_fs2.vp' ... 52 files
Found 35 roots and 20044 files.
ERROR: Unknown Language Checksum: -1162327434
Using default language settings...
Setting language to English
TBM => Starting parse of 'mv_core-lcl.tbm' ...
Initializing OpenAL...
OpenAL Vendor : Creative Labs Inc.
OpenAL Renderer : Software
OpenAL Version : 1.1
Found extension "ALC_EXT_EFX".
Sample rate: 44100 (44100)
EFX enabled: NO
Playback device: Generic Software on Speakers / Headphones (IDT High Definition Audio CODEC)
Capture device: Microphone Array (IDT High Defi
... OpenAL successfully initialized!
Failed to init speech
Initializing OpenGL graphics device at 1920x1080 with 32-bit color...
Initializing WGL...
Requested WGL Video values = R: 8, G: 8, B: 8, depth: 32, double-buffer: 1
Actual WGL Video values = R: 8, G: 8, B: 8, depth: 32, double-buffer: 1
OpenGL Vendor : ATI Technologies Inc.
OpenGL Renderer : ATI Mobility Radeon HD 4670
OpenGL Version : 3.3.10600 Compatibility Profile Context FireGL
Using extension "GL_EXT_fog_coord".
Using extension "GL_ARB_multitexture".
Using extension "GL_ARB_texture_env_add".
Using extension "GL_ARB_texture_compression".
Using extension "GL_EXT_texture_compression_s3tc".
Using extension "GL_EXT_texture_filter_anisotropic".
Using extension "GL_ARB_texture_env_combine".
Using extension "GL_EXT_compiled_vertex_array".
Using extension "GL_EXT_draw_range_elements".
Using extension "GL_ARB_texture_mirrored_repeat".
Using extension "GL_ARB_texture_non_power_of_two".
Using extension "GL_ARB_vertex_buffer_object".
Using extension "GL_ARB_pixel_buffer_object".
Using extension "GL_SGIS_generate_mipmap".
Using extension "GL_EXT_framebuffer_object".
Using extension "GL_ARB_texture_rectangle".
Using extension "GL_EXT_bgra".
Using extension "GL_ARB_texture_cube_map".
Using extension "GL_EXT_texture_lod_bias".
Using extension "GL_ARB_point_sprite".
Using extension "GL_ARB_shading_language_100".
Using extension "GL_ARB_shader_objects".
Using extension "GL_ARB_vertex_shader".
Using extension "GL_ARB_fragment_shader".
Using extension "GL_ARB_shader_texture_lod".
Found special extension function "wglSwapIntervalEXT".
Compiling shader: main-v.sdr (null-v.sdr), main-f.sdr (null-f.sdr)
Compiling shader: main-v.sdr (l-v.sdr), main-f.sdr (lb-f.sdr)
Compiling shader: main-v.sdr (b-v.sdr), main-f.sdr (b-f.sdr)
Compiling shader: main-v.sdr (b-v.sdr), main-f.sdr (bg-f.sdr)
Compiling shader: main-v.sdr (l-v.sdr), main-f.sdr (lbg-f.sdr)
Compiling shader: main-v.sdr (l-v.sdr), main-f.sdr (lbgs-f.sdr)
Compiling shader: main-v.sdr (l-v.sdr), main-f.sdr (lbs-f.sdr)
Compiling shader: main-v.sdr (lf-v.sdr), main-f.sdr (lfb-f.sdr)
Compiling shader: main-v.sdr (lf-v.sdr), main-f.sdr (lfbg-f.sdr)
Compiling shader: main-v.sdr (lf-v.sdr), main-f.sdr (lfbgs-f.sdr)
Compiling shader: main-v.sdr (lf-v.sdr), main-f.sdr (lfbs-f.sdr)
Compiling shader: main-v.sdr (l-v.sdr), main-f.sdr (null-f.sdr)
Compiling shader: main-v.sdr (l-v.sdr), main-f.sdr (lg-f.sdr)
Compiling shader: main-v.sdr (l-v.sdr), main-f.sdr (lgs-f.sdr)
Compiling shader: main-v.sdr (l-v.sdr), main-f.sdr (ls-f.sdr)
Compiling shader: main-v.sdr (la-v.sdr), main-f.sdr (la-f.sdr)
Compiling shader: main-v.sdr (la-v.sdr), main-f.sdr (lba-f.sdr)
Compiling shader: main-v.sdr (ba-v.sdr), main-f.sdr (ba-f.sdr)
Compiling shader: main-v.sdr (ba-v.sdr), main-f.sdr (bga-f.sdr)
Compiling shader: main-v.sdr (la-v.sdr), main-f.sdr (lbga-f.sdr)
Compiling shader: main-v.sdr (la-v.sdr), main-f.sdr (lbgsa-f.sdr)
Compiling shader: main-v.sdr (la-v.sdr), main-f.sdr (lbsa-f.sdr)
Compiling shader: main-v.sdr (lfa-v.sdr), main-f.sdr (lfba-f.sdr)
Compiling shader: main-v.sdr (lfa-v.sdr), main-f.sdr (lfbga-f.sdr)
Compiling shader: main-v.sdr (lfa-v.sdr), main-f.sdr (lfbgsa-f.sdr)
Compiling shader: main-v.sdr (lfa-v.sdr), main-f.sdr (lfbsa-f.sdr)
Compiling shader: soft-v.sdr (soft-v.sdr), soft-f.sdr (soft-f.sdr)
Loading built-in default shader for: soft-v.sdr
Loading built-in default shader for: soft-f.sdr
Compiling shader: soft-v.sdr (soft-v.sdr), soft-f.sdr (soft-f.sdr)
Loading built-in default shader for: soft-v.sdr
Loading built-in default shader for: soft-f.sdr
Max texture units: 8 (16)
Max elements vertices: 2147483647
Max elements indices: 16777215
Max texture size: 8192x8192
Max render buffer size: 8192x8192
Can use compressed textures: YES
Texture compression available: YES
Post-processing enabled: NO
Using trilinear texture filter.
Using GLSL for model rendering.
OpenGL Shader Version: 3.30
... OpenGL init is complete!
Size of bitmap info = 742 KB
Size of bitmap extra info = 48 bytes
ANI cursorweb with size 24x24 (25.0% wasted)
GRAPHICS: Initializing default colors...
SCRIPTING: Beginning initialization sequence...
SCRIPTING: Beginning Lua initialization...
LUA: Opening LUA state...
LUA: Initializing base Lua libraries...
LUA: Beginning ADE initialization
ADE: Initializing enumeration constants...
ADE: Assigning Lua session...
SCRIPTING: Beginning main hook parse sequence....
Wokka! Error opening file (scripting.tbl)!
TABLES: Unable to parse 'scripting.tbl'! Error code = 5.
TBM => Starting parse of 'mv_flak-sct.tbm' ...
TBM => Starting parse of 'mv_dbrs-sct.tbm' ...
TBM => Starting parse of 'mv_exp-sct.tbm' ...
TBM => Starting parse of 'bp2-trigger-sct.tbm' ...
TBM => Starting parse of 'bp2-tcard-sct.tbm' ...
TBM => Starting parse of 'bp2-stupid-sct.tbm' ...
TBM => Starting parse of 'bp2-debrisgrav-sct.tbm' ...
TBM => Starting parse of 'bp2-csc-sct.tbm' ...
TBM => Starting parse of 'bp2-betty-sct.tbm' ...
SCRIPTING: Inititialization complete.
SCRIPTING: Splash screen overrides checked
SCRIPTING: Splash hook has been run
SCRIPTING: Splash screen conditional hook has been run
Using high memory settings...
Wokka! Error opening file (interface.tbl)!
WMCGUI: Unable to parse 'interface.tbl'! Error code = 5.
TBM => Starting parse of 'mv_effects-sdf.tbm' ...
TBM => Starting parse of 'bp-sdf.tbm' ...
Windows reported 16 joysticks, we found 0
Current soundtrack set to -1 in event_music_reset_choices
TBM => Starting parse of 'mv_music-mus.tbm' ...
TBM => Starting parse of 'bp-mus.tbm' ...
TBM => Starting parse of 'bp2-mus.tbm' ...
TBM => Starting parse of 'mv_effects-mfl.tbm' ...
TBM => Starting parse of 'bp-mfl.tbm' ...
TBM => Starting parse of 'bp2-mfl.tbm' ...
Wokka! Error opening file (armor.tbl)!
TABLES: Unable to parse 'armor.tbl'! Error code = 5.
TBM => Starting parse of 'mv_effects-amr.tbm' ...
TBM => Starting parse of 'bp2-amr.tbm' ...
TBM => Starting parse of 'bp-aip.tbm' ...
TBM => Starting parse of 'bp2-aip.tbm' ...
TBM => Starting parse of 'mv_effects-wxp.tbm' ...
TBM => Starting parse of 'bp-wxp.tbm' ...
BMPMAN: Found EFF (exp20.eff) with 75 frames at 20 fps.
BMPMAN: Found EFF (ExpMissileHit1.eff) with 92 frames at 20 fps.
BMPMAN: Found EFF (exp04.eff) with 49 frames at 22 fps.
BMPMAN: Found EFF (exp05.eff) with 93 frames at 20 fps.
BMPMAN: Found EFF (exp06.eff) with 92 frames at 22 fps.
BMPMAN: Found EFF (capflash.eff) with 40 frames at 10 fps.
BMPMAN: Found EFF (Maxim_Impact.eff) with 23 frames at 30 fps.
ANI Lamprey_Impact with size 80x80 (37.5% wasted)
BMPMAN: Found EFF (explo3.eff) with 48 frames at 22 fps.
BMPMAN: Found EFF (HFlakExp.eff) with 48 frames at 22 fps.
BMPMAN: Found EFF (exp06b.eff) with 92 frames at 22 fps.
BMPMAN: Found EFF (bomb_flare.eff) with 69 frames at 20 fps.
TBM => Starting parse of 'mv_core-wep.tbm' ...
TBM => Starting parse of 'mv_effects-wep.tbm' ...
TBM => Starting parse of 'mv_assets-wep.tbm' ...
TBM => Starting parse of 'bp-wep.tbm' ...
TBM => Starting parse of 'bp2-wep.tbm' ...
[removed some crap]
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
+Team: value was out of range in the mission file! This was probably caused by a bug in an older version of FRED. Using -1 for now.
Starting mission message count : 294
Ending mission message count : 298
Current soundtrack set to -1 in event_music_reset_choices
Loading model 'Wraith.pof'
Potential problem found: Unrecognized subsystem type 'gpodf', believed to be in ship Wraith.pof
Potential problem found: Unrecognized subsystem type 'gpodl', believed to be in ship Wraith.pof
Potential problem found: Unrecognized subsystem type 'gpodr', believed to be in ship Wraith.pof
Potential problem found: Unrecognized subsystem type 'panelbl', believed to be in ship Wraith.pof
Potential problem found: Unrecognized subsystem type 'panelbr', believed to be in ship Wraith.pof
Potential problem found: Unrecognized subsystem type 'paneltl', believed to be in ship Wraith.pof
Potential problem found: Unrecognized subsystem type 'paneltr', believed to be in ship Wraith.pof
Potential problem found: Unrecognized subsystem type 'raill', believed to be in ship Wraith.pof
Potential problem found: Unrecognized subsystem type 'railr', believed to be in ship Wraith.pof
Potential problem found: Unrecognized subsystem type 'spiner', believed to be in ship Wraith.pof
Potential problem found: Unrecognized subsystem type 'throttle', believed to be in ship Wraith.pof
IBX: Found a good IBX to read for 'Wraith.pof'.
IBX-DEBUG => POF checksum: 0xf57e7c82, IBX checksum: 0xc002fce6 -- "Wraith.pof"
Loading model 'capital01.pof'
Potential problem found: Unrecognized subsystem type 'fighterbay', believed to be in ship capital01.pof
IBX: Found a good IBX to read for 'capital01.pof'.
IBX-DEBUG => POF checksum: 0x8e4830bc, IBX checksum: 0x4b14997f -- "capital01.pof"
Submodel 'turret01b' is detail level 1 of 'turret01a'
Submodel 'turret01c' is detail level 2 of 'turret01a'
Submodel 'turret02b' is detail level 1 of 'turret02a'
Submodel 'turret02c' is detail level 2 of 'turret02a'
Submodel 'turret03b' is detail level 1 of 'turret03a'
Submodel 'turret03c' is detail level 2 of 'turret03a'
Submodel 'turret04b' is detail level 1 of 'turret04a'
Submodel 'turret04c' is detail level 2 of 'turret04a'
Submodel 'turret05b' is detail level 1 of 'turret05a'
Submodel 'turret05c' is detail level 2 of 'turret05a'
Allocating space for at least 25 new ship subsystems ... a total of 200 is now available (25 in-use).
Loading model 'KarunaMk1.pof'
Potential problem found: Unrecognized subsystem type 'rotatora', believed to be in ship KarunaMk1.pof
Potential problem found: Unrecognized subsystem type 'Reactor02', believed to be in ship KarunaMk1.pof
Potential problem found: Unrecognized subsystem type 'Reactor01', believed to be in ship KarunaMk1.pof
Potential problem found: Unrecognized subsystem type 'Fighterbay', believed to be in ship KarunaMk1.pof
IBX: Found a good IBX to read for 'KarunaMk1.pof'.
IBX-DEBUG => POF checksum: 0xeb4d4687, IBX checksum: 0x03bd3b22 -- "KarunaMk1.pof"
Submodel 'engine01b' is detail level 1 of 'engine01a'
Submodel 'engine01c' is detail level 2 of 'engine01a'
Submodel 'engine01d' is detail level 3 of 'engine01a'
Submodel 'engine01b-destroyed' is detail level 1 of 'engine01a-destroyed'
Submodel 'engine01c-destroyed' is detail level 2 of 'engine01a-destroyed'
Submodel 'engine01d-destroyed' is detail level 3 of 'engine01a-destroyed'
Submodel 'engine02b' is detail level 1 of 'engine02a'
Submodel 'engine02c' is detail level 2 of 'engine02a'
Submodel 'engine02d' is detail level 3 of 'engine02a'
Submodel 'engine02b-destroyed' is detail level 1 of 'engine02a-destroyed'
Submodel 'engine02c-destroyed' is detail level 2 of 'engine02a-destroyed'
Submodel 'engine02d-destroyed' is detail level 3 of 'engine02a-destroyed'
Submodel 'engine03b' is detail level 1 of 'engine03a'
Submodel 'engine03c' is detail level 2 of 'engine03a'
Submodel 'engine03d' is detail level 3 of 'engine03a'
Submodel 'engine03b-destroyed' is detail level 1 of 'engine03a-destroyed'
Submodel 'engine03c-destroyed' is detail level 2 of 'engine03a-destroyed'
Submodel 'engine03d-destroyed' is detail level 3 of 'engine03a-destroyed'
Submodel 'engine04b' is detail level 1 of 'engine04a'
Submodel 'engine04c' is detail level 2 of 'engine04a'
Submodel 'engine04d' is detail level 3 of 'engine04a'
Submodel 'engine04b-destroyed' is detail level 1 of 'engine04a-destroyed'
Submodel 'engine04c-destroyed' is detail level 2 of 'engine04a-destroyed'
Submodel 'engine04d-destroyed' is detail level 3 of 'engine04a-destroyed'
Submodel 'rotatorb' is detail level 1 of 'rotatora'
Submodel 'rotatorc' is detail level 2 of 'rotatora'
Submodel 'rotatord' is detail level 3 of 'rotatora'
Submodel 'rotatorb-destroyed' is detail level 1 of 'rotatora-destroyed'
Submodel 'rotatorc-destroyed' is detail level 2 of 'rotatora-destroyed'
Submodel 'rotatord-destroyed' is detail level 3 of 'rotatora-destroyed'
Loading model 'Torrent.pof'
IBX: Found a good IBX to read for 'Torrent.pof'.
IBX-DEBUG => POF checksum: 0x8a9221fb, IBX checksum: 0x2e125f81 -- "Torrent.pof"
Loading model 'corvette2t-01.pof'
IBX: Found a good IBX to read for 'corvette2t-01.pof'.
IBX-DEBUG => POF checksum: 0x3aaebe96, IBX checksum: 0x42b3e9a3 -- "corvette2t-01.pof"
Loading model 'cruiser2t-01.pof'
IBX: Found a good IBX to read for 'cruiser2t-01.pof'.
IBX-DEBUG => POF checksum: 0xb6b2d965, IBX checksum: 0x8b764fcf -- "cruiser2t-01.pof"
Loading model 'cruiser01x.pof'
IBX: Found a good IBX to read for 'cruiser01x.pof'.
IBX-DEBUG => POF checksum: 0xd2d59346, IBX checksum: 0x152fa60b -- "cruiser01x.pof"
Submodel 'radar01d-dish' is detail level 3 of 'radar01a-dish'
Submodel 'radar01c-dish' is detail level 2 of 'radar01a-dish'
Submodel 'radar01b-dish' is detail level 1 of 'radar01a-dish'
Submodel 'turret09d-01-main' is detail level 3 of 'turret09a-01-main'
Submodel 'turret09c-01-main' is detail level 2 of 'turret09a-01-main'
Submodel 'turret09b-01-main' is detail level 1 of 'turret09a-01-main'
Submodel 'turret09c-02-sub' is detail level 2 of 'turret09a-02-sub'
Submodel 'turret09b-02-sub' is detail level 1 of 'turret09a-02-sub'
Allocating space for at least 33 new ship subsystems ... a total of 400 is now available (221 in-use).
Loading model 'fgstrikebmb.pof'
IBX: Found a good IBX to read for 'fgstrikebmb.pof'.
IBX-DEBUG => POF checksum: 0x2c385027, IBX checksum: 0xa68dc912 -- "fgstrikebmb.pof"
Submodel 'thruster01b' is detail level 1 of 'thruster01a'
Submodel 'thruster01c' is detail level 2 of 'thruster01a'
Submodel 'thruster01d' is detail level 3 of 'thruster01a'
Submodel 'thruster02b' is detail level 1 of 'thruster02a'
Submodel 'thruster02c' is detail level 2 of 'thruster02a'
Submodel 'thruster02d' is detail level 3 of 'thruster02a'
Loading model 'fighter2t-03.pof'
IBX: Found a good IBX to read for 'fighter2t-03.pof'.
IBX-DEBUG => POF checksum: 0x437b0cfb, IBX checksum: 0x7a6fa692 -- "fighter2t-03.pof"
Loading model 'Bonus2t-01.pof'
IBX: Found a good IBX to read for 'Bonus2t-01.pof'.
IBX-DEBUG => POF checksum: 0xf10b290a, IBX checksum: 0x2f27e40e -- "Bonus2t-01.pof"
Submodel 'hercd' is detail level 3 of 'herca'
Submodel 'hercb' is detail level 1 of 'herca'
Submodel 'hercc' is detail level 2 of 'herca'
Loading model 'pfighter01.pof'
IBX: Found a good IBX to read for 'pfighter01.pof'.
IBX-DEBUG => POF checksum: 0xbc3ad812, IBX checksum: 0xc5dbc284 -- "pfighter01.pof"
Submodel 'thruster01b' is detail level 1 of 'thruster01a'
Submodel 'thruster01c' is detail level 2 of 'thruster01a'
Submodel 'thruster01d' is detail level 3 of 'thruster01a'
Loading model 'fighter2t-04.pof'
IBX: Found a good IBX to read for 'fighter2t-04.pof'.
IBX-DEBUG => POF checksum: 0xe611ce17, IBX checksum: 0x97cf5fc2 -- "fighter2t-04.pof"
Loading model 'fighter2t-05.pof'
IBX: Found a good IBX to read for 'fighter2t-05.pof'.
IBX-DEBUG => POF checksum: 0xbfb37609, IBX checksum: 0x207ec69a -- "fighter2t-05.pof"
Loading model 'ezec8guns.pof'
IBX: Found a good IBX to read for 'ezec8guns.pof'.
IBX-DEBUG => POF checksum: 0x1a29459f, IBX checksum: 0x042fe26d -- "ezec8guns.pof"
Loading model 'UEFoculus.pof'
IBX: Found a good IBX to read for 'UEFoculus.pof'.
IBX-DEBUG => POF checksum: 0x6eb73ec5, IBX checksum: 0x9fb3720f -- "UEFoculus.pof"
Loading model 'fighter2t-02.pof'
IBX: Found a good IBX to read for 'fighter2t-02.pof'.
IBX-DEBUG => POF checksum: 0xb236e2c1, IBX checksum: 0x153c31b5 -- "fighter2t-02.pof"
Loading model 'carrier3t-01.pof'
Potential problem found: Unrecognized subsystem type 'fighterbay', believed to be in ship carrier3t-01.pof
IBX: Found a good IBX to read for 'carrier3t-01.pof'.
IBX-DEBUG => POF checksum: 0xe52e4a6b, IBX checksum: 0xfdbd76fb -- "carrier3t-01.pof"
Loading model 'corvette3t-01.pof'
IBX: Found a good IBX to read for 'corvette3t-01.pof'.
IBX-DEBUG => POF checksum: 0xd009b1ca, IBX checksum: 0xe057b300 -- "corvette3t-01.pof"
Loading model 'bomber2t-01.pof'
IBX: Found a good IBX to read for 'bomber2t-01.pof'.
IBX-DEBUG => POF checksum: 0x13bb548d, IBX checksum: 0xad039fff -- "bomber2t-01.pof"
Submodel 'bomb0x-d' is detail level 3 of 'bomb0x-a'
Submodel 'bomb0x-c' is detail level 2 of 'bomb0x-a'
Submodel 'bomb0x-b' is detail level 1 of 'bomb0x-a'
Loading model 'Bomber2T-03.pof'
IBX: Found a good IBX to read for 'Bomber2T-03.pof'.
IBX-DEBUG => POF checksum: 0xd02b1bbd, IBX checksum: 0xf53ed53f -- "Bomber2T-03.pof"
Loading model 'navbuoy.pof'
IBX: Found a good IBX to read for 'navbuoy.pof'.
IBX-DEBUG => POF checksum: 0x7c9f8f53, IBX checksum: 0xf7820816 -- "navbuoy.pof"
Loading model 'SuperCap2S-01.pof'
BMPMAN: Found EFF (supertile1-glow.eff) with 40 frames at 10 fps.
BMPMAN: Found EFF (supertile2-glow.eff) with 35 frames at 30 fps.
BMPMAN: Found EFF (supertile3-glow.eff) with 40 frames at 30 fps.
BMPMAN: Found EFF (supertile4-glow.eff) with 40 frames at 30 fps.
Potential problem found: Unrecognized subsystem type 'fighterbay', believed to be in ship SuperCap2S-01.pof
IBX: Found a good IBX to read for 'SuperCap2S-01.pof'.
IBX-DEBUG => POF checksum: 0x33218381, IBX checksum: 0xa1acc7db -- "SuperCap2S-01.pof"
Submodel 'supercap2s-01c' is detail level 2 of 'supercap2s-01a'
Submodel 'supercap2s-01b' is detail level 1 of 'supercap2s-01a'
Loading model 'TF-13_Kvasir.pof'
IBX: Found a good IBX to read for 'TF-13_Kvasir.pof'.
IBX-DEBUG => POF checksum: 0x7abef3e7, IBX checksum: 0xdd574d15 -- "TF-13_Kvasir.pof"
Loading model 'fighterCW-02t.pof'
IBX: Found a good IBX to read for 'fighterCW-02t.pof'.
IBX-DEBUG => POF checksum: 0x8141707d, IBX checksum: 0xad84eb2c -- "fighterCW-02t.pof"
ERROR: Invalid subsystem name.
In sexpression: ( when
( and
( not
( has-arrived-delay 1 "Checkpoint 1" )
)
( is-event-true-delay
"Levi: big damn rat"
6
)
( not
( has-arrived-delay 1 "Checkpoint 2" )
)
)
( send-message
"Indus"
"High"
"Indus: surrender"
)
( ship-subsys-guardian-threshold
( rand-multiple 85 95 )
"Indus"
"Engine01"
"Engine02"
"Engine03"
Freeing all existing models...
Whoa, uh, I'm surprised you made it that far...if this error is what I think it is, it should've manifested a little earlier in the campaign. Can you make sure your Blue Planet 1 and 2 asset VPs are up to date by redownloading them?
Where did you get the campaign from, and exactly what version of 3.6.14 are you running? RC4, RC5?
