[AV8R]

Just wanted to get some info on various errors I found in the debug logs for the two major Freespace campaigns (FSPort and FS2Open). I am using FSPort 3.4 with 3.6.12 media VPs and the 3.6.18 debug exe. Each has its own fresh pilot file (I know the new 3.7 exe has the new unified pilot code but I haven't downloaded it yet).

FSPort log errors:

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.

FS2Open log errors (actually crashes to desktop running with the dedug exe but not with the standard exe):

Same as above plus....
WARNING: "Cannot load hud ani: 2_rightarc1_fs1" at hudreticle.cpp:786


For FSPort, what do these table errors mean? For FS2Open, it looks like something in the HUD table file is preventing FS2Open from starting with the debug exe. Does anyone know to what line in the HUD table file this error is referring to?

[Yarn]

FSPort log errors:

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.

These are normal; you can ignore them.

FS2Open log errors (actually crashes to desktop running with the dedug exe but not with the standard exe):

Same as above plus....
WARNING: "Cannot load hud ani: 2_rightarc1_fs1" at hudreticle.cpp:786

Look in [your FS2 folder]\data\tables for "hud_gauges.tbl" and any files ending with "-hdg.tbm" and delete or move them. Do the same for [your FS2 folder]\mediavps_3612\data\tables, except instead of deleting them right away, open each of those files in a text editor such as Notepad and see whether the line $Reticle Style: FS1 (spacing and capitalization don't matter) appears near the top. If it does, delete or move that file.

If you still have problems, post your fs2_open.log (which is NOT the error message).

[AV8R]

Nothing in the first directory you mentioned. Here are the log file and HUD table from \GAMES\Freespace2\mediavps_3612\data\tables.

Thanks for your input.

[attachment deleted by ninja]

[Yarn]

The problem is that this appears in your HUD table:

Code: [Select]

+Weapon Linking:
Position: (806,453)

That is an FSPort-only gauge, so it should be removed. (Even better, get an updated table from August here.)

[AV8R]

Yep, removed the entry from the HUD table and no more crash opening FS2Open with debug EXE. You sir, are a genius.

Thanks for your input/help.