[Belisarius]

Hi guys

I installed the retail version of Freespace 2 and then downloaded the mv_complete.vp into the "mediavps" folder I've created in the FS2 main folder. After that I started the launcher and it told me that I need OpenALX or whatever it's called. I downloaded this as well, installed it and the launcher started. I choosed the fs2_open_3_6_10.exe via the browse button at the top and also choosed the mediavps folder as mod. After that I was setting up the features I wanted for playing the game. I was choosing only the features listed in the guide of the release thread. I added "-ambient_factor 35 -ogl_spec 20 -spec_exp 15 -spec_point 1.2 -spec_static 1.5 -spec_tube 1.5" (without the ") to the command flags line, pressed "Apply" and run, but then I got and still get following error message:

Error: mv_strings-lcl.tbm is corrupt
File: localize.cpp
Line: 608


Call stack:
------------------------------------------------------------------
------------------------------------------------------------------
 and the following:


Error: mv_strings-lcl.tbm(line 26:
Error: Expecting int, found [].

File: PARSELO.CPP
Line: 670


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


I have no idea what I could've done wrong, so could please tell me someone where the problem lies? If you need additional info, please let me know.

Thank you for help.

[Jeff Vader]

http://www.hard-light.net/forums/index.php/topic,58325.0.html

[General Battuta]

Hrm. I'm not that experienced at tech support compared to Lobo and the like, so I don't instantly recognize the error, but I bet it's something pretty easy to fix.

Could you run a debug build (select a 3.6.10 build ending in a -d), run it up to the crash, and then post the file called f2open_log (or something similar?)

EDIT: never mind, Lobo is really fast!

[Belisarius]

Thank you very much guys. I installed the hotfix and now the game runs as it's intended. But I wouldn't had to ask if that hotfix would be linked in the release thread of the 3.6.10 media vps.

[Jeff Vader]

Otherwise it would probably be there, but if I've understood correctly, there is a patch coming for the MediaVPs and it will include a fix for this issue as well.