Replays don't work?

[DarrenTotalWar]

Hi there, wondering if anyone else had this problem:

I played a battle, on legendary, 1000 men vs 5000men. Sieging a settlement in the campaign.

I won the battle and was extremely pleased with both my performance and the AI (for once!) they actually blocked streets and stuff it was pretty cool.

I wanted to save the replay to make a video on it, but when I watched the replay back... I lost the battle. What the hell? None of my units acted correctly or anything. The timer had like 6mins left to go in the replay and it just said I lost.

Anyone else experience this?

[♠ Thomas Cochrane ♠]

This has been a problem throughout TW games. For some reason, replays work by recording the clicks, movements, attacks, orders etc from you and the AI. What it does NOT record is the actual effect of those orders. As arrows have a certain percentage chance to hit, in your game they may hit and kill, but in the replay they may miss entirely. The effect continues to the point where entire parts of the battle you played have different outcomes, and eventually you even lose the battle. Sometimes it's perfect though, so I'm not sure what's happening behind the scenes.

[rrgg]

I'm pretty sure it only records player commands, the AI still appears able to react normally any time replays start going alt-history. It also records the random number seed for the battle, the way that works is that all of those % hit chances and AI decisions are determined by a basically big long list of random numbers, so as long as you feed that exact same list back into the replay along with all of the same player commands you should get the exact same results every time. That's the ideal case, in practice all it takes is a getting single number in the list out of order for everything after that point gets completely screwed up. And, ds you can imagine with the size and state of Rome II, that seems to be happening quite a bit.

[Causeless]

I'm pretty sure it only records player commands, the AI still appears able to react normally any time replays start going alt-history. It also records the random number seed for the battle, the way that works is that all of those % hit chances and AI decisions are determined by a basically big long list of random numbers, so as long as you feed that exact same list back into the replay along with all of the same player commands you should get the exact same results every time. That's the ideal case, in practice all it takes is a getting single number in the list out of order for everything after that point gets completely screwed up. And, ds you can imagine with the size and state of Rome II, that seems to be happening quite a bit.

Arrow hit chance isn't determined by a random seed, it's determined by a simple simulation of the arrow. However, changes in fps can change the results of where an arrow actually hits, and who is there when it hits.

[DarrenTotalWar]

Oh that's weird, because I remember in Shogun 2, I saved a replay because 1 soldier killed a guy in a cool way toward the end of battle, and in the replay everything happened normally and the guy was still there behaving the same.It's really a shame, the battle was great. The AI actually blocked off streets to protect it's flanks as I tried to flank it, it was really cool. Shame

[perablenta]

They released the replay system broken in the same way they broke Shogun's 2 a while back with one of the patches.

Since they were able to fix Shogun's 2 replay system again, they will be able to fix Rome's 2 as well.