[zirael44]

when I click run:

Error: Strings.tbl is corrupt
File:D:\C++\Freespace\fs2_open 3.6.9 - BtRL\code\Localization\localize.cpp
Line: 612
[This filename points to the location of a file on the computer that built this executable]

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

[ This info is in the clipboard so you can paste it somewhere now ]


Use Ok to break into Debugger, Cancel exits.

[karajorma]

Sounds like your Strings.tbl is corrupt.

Where did you get your copy of FS2 from?

[zirael44]

i have original version

[Jeff Vader]

In that case your FS2 installation might be a bit broken. Try reinstalling FS2.

A quick search on the forums also suggests language problems. Do you have a non-English version of FS2?

[captain-custard]

when I click run:

Error: Strings.tbl is corrupt
File:D:\C++\Freespace\fs2_open 3.6.9 - BtRL\code\Localization\localize.cpp
Line: 612
[This filename points to the location of a file on the computer that built this executable]

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

[ This info is in the clipboard so you can paste it somewhere now ]


Use Ok to break into Debugger, Cancel exits.

mmmmm thats a btrl build doesnt it have some differences from a standard fs build

[zirael44]

i have polish version

[Jeff Vader]

Hmm. That would seem to be the cause, but I'm not completely certain of how to fix it.

Someone who knows more about this stuff: could this be fixed by delivering him the strings.tbl from an English FS2? And/or tampering with the registry?

[Wanderer]

Actually he might need polish section for the strings.tbl (possible via lcl.tbm)...

Tampering with the registry should work nicely though.

[karajorma]

i have original version

Oh no you don't.

As the others have pointed out you are using the .exe that came with Beyond the Red Line or The Babylon Project with FS2. Now there is nothing intrinsically wrong with that, it should work fine, but if you've managed to get the executable from a rather strange source it suggests that the same may be true of other things.

If the other advice already offered hasn't helped I'd suggest getting a 3.6.10 debug build from the nightly builds forum and running that. When it crashes post the FS2_Open.log you'll find in the data folder. That will help us a lot.