FC2.0 Corrupted

[Case]

My FC2.0 installation went corrupt. When running the single player I get the following error message:

Error:
..\blackshark\modules\me_options.lua:329: assertion failed!
Stack traceback:

->stack:..\blackshark\modules\me_options.lua in line 329 in func:
->stack:.\BlackShark\BlackShark.lua in line 266 in func:

which allows me to press 'OK', to get:

..\blackshark\modules\me_logbook.lua:147: attempt to index field 'country_by_id' (a nil value)

after which I can press 'OK' to kill the program.

 

It started after a multiplayer session where I might have gotten the stuck chat bug though I was not aware of it. I restarted the MP and SP versions of FC but TrackIR, HOTAS and keyboard do not respond, except for the ESC key.

 

After restarting the PC I get the error above.

 

My game is not modded except for having manually changed snapviews.

 

Any ideas what might cause this and how to fix it?

[Panzertard]

The crash/error files would certainly be helpful: TROUBLESHOOTING - Help us helping you.

[Case]

It seems only the MP version writes to temp/error.txt, which contains:

Failed to parse Error running \Scripts\server.lua: ./Scripts/Database/db_main.lua:12: module 'weapons_table' not found:
no field package.preload['weapons_table']
no file './LuaSocket/weapons_table.lua'
no file './Scripts/Database/../../Config/Weapons/weapons_table.lua'
no file './Scripts/Database/../../weapons_table.lua'
no file '.\lua-weapons_table.dll'
no file '.\weapons_table.dll'
no file 'C:\Program Files\Eagle Dynamics\LockOn Flaming Cliffs 2\bin\x86\stable\lua-weapons_table.dll'
no file 'C:\Program Files\Eagle Dynamics\LockOn Flaming Cliffs 2\bin\x86\stable\weapons_table.dll'

 

I did not install any mods so I have no problems reinstalling FC2.0, but I'll wait till tomorrow evening so I can perhaps get some more info on what might be causing this and how it can be fixed/prevented.

[Panzertard]

You've seem to have broken the references to lua - some files no longer have original content.

Either you have a bad file system or you must a have changed something - maybe without using notepad++?

I'd be warned enough to do a CHKDSK C: /F for C: D: etc.

But in all cases you could just do a reinstall - side by side, rename the old non working FC folder, then install another one - no activation required if it ends up in the same place.

[Breakshot]

I have a feeling the issue is indeed related to "MP Stuck Chat" bug!

 

The fact that no controls apart from ESC key responded point in that direction. Given the fact that you did not "fix" the chat bug (By hitting ALT+ENT or ALT-TAB), but rather decided to reboot the whole PC meant that some files must have gotten corrupted upon next load...

 

@ED: I have no idea how this chat bug slipped through beta testing, but this should be a BIG priority to be fixed in patch!

 

With that said, im backing up my FC2 as we speak to avoid the same fate as Case, because my chat gets stuck quite often...

[Panzertard]

I have a feeling the issue is indeed related to "MP Stuck Chat" bug!

 

The fact that no controls apart from ESC key responded point in that direction. Given the fact that you did not "fix" the chat bug (By hitting ALT+ENT or ALT-TAB), but rather decided to reboot the whole PC meant that some files must have gotten corrupted upon next load...

 

@ED: I have no idea how this chat bug slipped through beta testing, but this should be a BIG priority to be fixed in patch!

 

With that said, im backing up my FC2 as we speak to avoid the same fate as Case, because my chat gets stuck quite often...

No, it shouldn't be part of that - the only files being open when the chat is running, your game running is the files in the \temp folder.

Anyway it's Windows responsibility to close such files or to fix the problems of them being open after an applicaiton closes down.

 

The chat-bug can be fixed by tapping the midifier you used to activate it - it acts as a "stuck key". Basicly Windows thinks the key is still pressed.

So just tap your CTRL key a few more times and it's corrected.

 

As for the fact that it slipped through - well, we werent that friendly in MP testing - we had to keep chasing GGTharos in his F-15 :music_whistling: