Forged Alliance Forever

Re: Replay in vault is faulty, but local is fine.

2015-01-24T13:27:45+02:00

Anti-Distinctlyminty wrote:
Hi,
I tried to watch a replay of a game that I just finished, but an error occurred:
Code:
**FAF Username:** Anti-Distinctly **FAF Version:** 0.8.53 **FAF Directory:** C:\ProgramData\FAForever **FA Path:** C:\Program Files (x86)\Steam\steamapps\common\supreme commander forged alliance **Home Directory:** C:\Users\Luke\Documents **Stacktrace:** {{{ Traceback (most recent call last): File "replays\_replayswidget.pyc", line 98, in finishRequest File "fa\exe.pyc", line 164, in replay File "fa\replayparser.pyc", line 51, in getVersion File "fa\replayparser.pyc", line 33, in __readLine error: unpack requires a string argument of length 1 }}}

The replays seem to have differing, yet complete headers, which is odd (see attached 7z file).
I know that not much can be done about corrupt replays, but if you need any more information from me then just let me know.

In fact, I've just remembered something that may be relevant. The non-functioning .fafreplay file header state that the teams are
{"1": ["StefanD"], "2": ["Vexy", "GFY_DePonny"]}
StefanD tried to start a game a few times, but just got a black screen. I'm wondering if the server allocated the UID to this game that never happened? Just a thought.

Hey,

Yes the server stores game information for every launched game, in the same place as normal games, we may be looking at some weird condition with somehow getting a stale game information object for use with the current replay.

Thanks for the report!

Statistics: Posted by Sheeo — 24 Jan 2015, 13:27

Re: Replay in vault is faulty, but local is fine.

2015-01-19T17:31:31+02:00

Yes it would be nice to be able to watch all replays. Are there any plans to fix it?

Statistics: Posted by ABSTRACT — 19 Jan 2015, 17:31

Replay in vault is faulty, but local is fine.

2013-07-08T21:54:39+02:00

Hi,
I tried to watch a replay of a game that I just finished, but an error occurred:

Code:: **FAF Username:** Anti-Distinctly **FAF Version:** 0.8.53 **FAF Directory:** C:\ProgramData\FAForever **FA Path:** C:\Program Files (x86)\Steam\steamapps\common\supreme commander forged alliance **Home Directory:** C:\Users\Luke\Documents **Stacktrace:** {{{ Traceback (most recent call last): File "replays\_replayswidget.pyc", line 98, in finishRequest File "fa\exe.pyc", line 164, in replay File "fa\replayparser.pyc", line 51, in getVersion File "fa\replayparser.pyc", line 33, in __readLine error: unpack requires a string argument of length 1 }}}

The replays seem to have differing, yet complete headers, which is odd (see attached 7z file).
I know that not much can be done about corrupt replays, but if you need any more information from me then just let me know.

In fact, I've just remembered something that may be relevant. The non-functioning .fafreplay file header state that the teams are
{"1": ["StefanD"], "2": ["Vexy", "GFY_DePonny"]}
StefanD tried to start a game a few times, but just got a black screen. I'm wondering if the server allocated the UID to this game that never happened? Just a thought.

Statistics: Posted by Anti-Distinctlyminty — 08 Jul 2013, 21:54