Topic: Additional savegame speed option: Backwards

Hello, while watching a savegame, I noticed, that although you can speed it up while it runs forward, and that you than also can slow it down again, the lowest point is "pause" - but why not making savegames able to get even more page down, so that after pause there comes "-1,0x", then "-2,0"x, and etc., just like it is with the speed on the forward running side. I would like that option, because when you see something interesting and then it is fast over again, I felt the need, to rewind the scene. This would make sense in my eyes, because a replay-savegame is just like watching a video from game, and videos, as we all know, cannot only be played forward and speed up forward and paused, but also played backwards and speed up backwards... Anyhow, I don't wanna say that that would be a sooooooooo important feature. I just thought it would be nice, if this option would exist, that's all. But of course there are way more imporant things to work on, I'm sure. It's just a thought which came to my mind.

Top

Quote

Big -1, rewinding time would be an enormous effort. Just not doable.

Video conversion could also be problematic, how would you pick which part of the map to render for every given frame? Rendering the whole map for every frame is possible in principle (that's sort of what an in-game screenshot does) but the resulting file would be gigantic.

Top

Quote

just to explain a bit further. During the game, all player actions are distributed over the network, so every client associated with a game gets this information. this is what makes our spectator function possible. for the replays this stream of actions is sved into a file. with the corresponding save file (created at the beginning of the game) you can watch the computer replaying all players in the game by just executing the player actions.

Top

Quote

hessenfarmer wrote:

with the corresponding save file (created at the beginning of the game) you can watch the computer replaying all players in the game by just executing the player actions.

Does it mean that stuff which is decided randomly by the game engine is not determistically replayed during a replay?

If so, this can result in different replays (in some cases even with huge differences), depending on where the engine during a replay chooses to route a scarce ressource to, chooses to decide if an exhausted mine still mines a bit, chooses which tree a tree cutter fells down, etc., up to the point where a recorded player action would just not be possible (because a tree is still there, or the own area has not been enlarged yet because the military building is not finished, etc.)

So, are not only player actions but all events recorded?

(empty signature.)

Top

Quote