Timeout error trying to view old local replays

[en9dmp]

Hi all,

I'm no longer able to view old replays from last year of BlackOps games. It tries to update the patch filoes, but then seems to timeout giving the following error:
Update started at 2013-09-27 17:03:11
Using game path: C:\Program Files (x86)\Steam\steamapps\common\supreme commander forged alliance
Using appdata: C:\ProgramData\FAForever
Connected to update server at 2013-09-27 17:03:11
writeToServer(GET_FILES_TO_UPDATE, [FAF])
handleAction(LIST_FILES_TO_UP) - 324 bytes
Files to update: [ForgedAlliance.exe, init_faf.lua, init_ladder1v1.lua, GDFBinary.dll, SupComDataPath.lua, SupComDataPathFAF.lua, init_nonxt.lua]
writeToServer(PATCH_TO, [bin, init_nonxt.lua, 46d9008f6b77d2c60f96272a816e4227, 3618])
writeToServer(PATCH_TO, [bin, GDFBinary.dll, 3fc9e7684d150da5c51db71d2399f316, 3618])
writeToServer(PATCH_TO, [bin, init_faf.lua, 16da7063ae3309c154a2c544f559b3a9, 3618])
writeToServer(PATCH_TO, [bin, ForgedAlliance.exe, 678325b509098d3a108d721ad7773496, 3618])
writeToServer(PATCH_TO, [bin, SupComDataPath.lua, 55ac1ef97845f2291da64b830299331e, 3618])
writeToServer(PATCH_TO, [bin, SupComDataPathFAF.lua, 962c9d1327657d77184adcf358c628f1, 3618])
writeToServer(PATCH_TO, [bin, init_ladder1v1.lua, ea96ac9cec88af29c08556c96465acfe, 3618])
handleAction(VERSION_PATCH_NOT_FOUND) - 82 bytes
Error: Patch version 3618 not found for init_nonxt.lua.
writeToServer(REQUEST_VERSION, [bin, init_nonxt.lua, 3618])
handleAction(UP_TO_DATE) - 54 bytes
file : GDFBinary.dll
GDFBinary.dll is up to date.
handleAction(UP_TO_DATE) - 52 bytes
file : init_faf.lua
init_faf.lua is up to date.
handleAction(UP_TO_DATE) - 64 bytes
file : ForgedAlliance.exe
ForgedAlliance.exe is up to date.
handleAction(UP_TO_DATE) - 64 bytes
file : SupComDataPath.lua
SupComDataPath.lua is up to date.
handleAction(VERSION_PATCH_NOT_FOUND) - 96 bytes
Error: Patch version 3618 not found for SupComDataPathFAF.lua.
writeToServer(REQUEST_VERSION, [bin, SupComDataPathFAF.lua, 3618])
handleAction(UP_TO_DATE) - 64 bytes
file : init_ladder1v1.lua
init_ladder1v1.lua is up to date.
handleAction(UP_TO_DATE) - 56 bytes
file : init_nonxt.lua
init_nonxt.lua is up to date.
handleAction(UP_TO_DATE) - 70 bytes
file : SupComDataPathFAF.lua
SupComDataPathFAF.lua is up to date.
Updates applied successfully.
writeToServer(GET_FILES_TO_UPDATE, [FAFGAMEDATA])
handleAction(LIST_FILES_TO_UP) - 134 bytes
Files to update: [faforever.faf, faforever.nxt, lobby.nxt]
writeToServer(PATCH_TO, [gamedata, faforever.faf, d89cf6a29c996d05bccb0694021c6e34, 3618])
writeToServer(PATCH_TO, [gamedata, faforever.nxt, 4ea953fc92c8115cc1f2b42c2fa1b9e1, 3618])
writeToServer(PATCH_TO, [gamedata, lobby.nxt, 9e6521423cc955e2cfb821839d482226, 3618])
handleAction(UP_TO_DATE) - 54 bytes
file : faforever.faf
faforever.faf is up to date.
handleAction(UP_TO_DATE) - 54 bytes
file : faforever.nxt
faforever.nxt is up to date.
handleAction(UP_TO_DATE) - 46 bytes
file : lobby.nxt
lobby.nxt is up to date.
Updates applied successfully.
writeToServer(GET_FILES_TO_UPDATE, [blackops])
handleAction(LIST_FILES_TO_UP) - 82 bytes
Files to update: [init_blackops.lua]
writeToServer(MOD_PATCH_TO, [bin, init_blackops.lua, 102b6e4398f5c41407c02334e9416194, null])
TIMEOUT: UpdaterTimeout(('Connection timed out while waiting for data.',))
Disconnected from server at 2013-09-27 17:03:32

Would anyone know how to fix this error?

Thanks

[en9dmp]

Any chance someone can help me with this issue?

Was hoping time might fix it with the latest FAF lobby but I still can't view old BO replays.

It's pretty annoying, I've tried all the solutions offered in similar threads, such as removing init_blackops.lua and hosting a new game, but it always gives the same error when trying to view old replays...

It just sits trying to download some (old?) version of init_blackops.lua then times out.

There must be a proper solution to this?

Thanks

[Ze_PilOt]

Old BO replays are broken for some reasons, no idea why, sorry.

[en9dmp]

OK, is there a way to run an old version of FAF (e.g. as of Aug 2012) in order for it to work? Seems odd there's no way to trick the system into behaving how it did when the replays worked....