[Snail]

This is just unavoidable now. Every time I try to do something with tables from retail and make it into FS2_Open, something crops up along these lines:

Error: ships.tbl(line xxx:
Error: Expecting xxx, found [xxx].

File:C:\temp\fs2_open_3_6_9.t\code\Parse\PARSELO.CPP
Line: 638
[This filename points to the location of a file on the computer that built this executable]

Call stack:
------------------------------------------------------------------
------------------------------------------------------------------

This is completely unavoidable, and cannot be fixed unless you completely remove the changes you made. Anyone getting this should rise up and post here, because this table error should not be happening, because this same table works with retail (I'm using a normal build, not debug). This is also the reason I had to stop working on one of my mods. And now it's killed another. Something is amiss here. And it's got nothing to do with ND either.

Effected are 2 of my own mods, a modified INFR1 (mine), NTV: Emergence (old NTV demo) and the BWO Demo.

And I don't know if its been reported so i'm not going to mantis it yet.

So, any one else getting this abomination of an error.

[karajorma]

I doubt it's a code error. It's an error with your tables most likely.

FS2_Open is a lot stricter about what it expects you to do with your tables. This is a good thing. Sloppy tables can and have caused crashes in the past.

Add your mods one at a time so you know which one is causing the problem. Then post the first couple of errors along with the table entry. Those error messages are actually very informative if you know how to read them.

[Dark Hunter]

You know what, Snail? Those errors aren't unavoidable. 

Really. It likely just means there's an extra entry somewhere on the table. For example: in the ships tables for retail there are a bunch of $ND lines. FSOpen doesn't use those and so doesn't expect them. Deleting them removed practically %80 of my table conversion blues.

Ditto what Kara said about reading the error messages, too. Just remember that the line it gives you won't match up with the line in Notepad, though generally it's somewhere close.

My strategy: in the line it tells you: "Expecting xxx, found [xxx]", use Ctrl-F on the [xxx] part. It usually takes you right to the error. If not, cycle through the entries with Ctrl-F until you find an inconsistency, such as an extra semicolon or a missing parentheses.

[karajorma]

Just remember that the line it gives you won't match up with the line in Notepad, though generally it's somewhere close.

They should if you use this version of FRED. The fix has been in CVS for a few days now but no one had released a build until now AFAIK.