This is another one of those minor problems that can be annoying. Just add it to the ever growing list. When you're watching a replay and you use the speed up/slow down functions then pause the replay the "paused" text on the screen (which is obviously there to tell you the replay is paused) flashes in accordance with your current viewing speed. So, for example, if you're viewing a replay on 0.25 speed it's really slow and if you're viewing it on 32 speed it flashes so quickly you could have an epileptic fit. I think it would be an improvement to have it flashing at the same rate irrespective of the viewing speed of the replay.

Yes, I agree with you. Sometimes, when I watch a replay very slow, I forget that the replay is paused because the frequency is slower.

Good solid suggestion. I never noticed this before as when I was racing actively I would discuss with teammates rather then review replays.

Someone get this man a cookie or something, he deserves one.

Never noticed it personally, either but it might be handy for those who use replays a lot so +1.

It's more like a bug. Actually I think this should be reported in the bug reports section of the forum instead of here.

na, its really more a "miss-conception" than a bug. If one uses that function everything in the game slows down, not only the simulation. Try watching a replay on slowest setting and than restart the race via Strg-R, it takes forever

Quote from ACCAkut :

na, its really more a "miss-conception" than a bug. If one uses that function everything in the game slows down, not only the simulation. Try watching a replay on slowest setting and than restart the race via Strg-R, it takes forever

That shouldn't happen, that's why it's a bug. It should only slow down the simulation, not everything else too.

For me the defiition of bug is, that something was programmed faulty. But in this case its the way the LFS simulation works, if you slow down the replay, it slows down the complete programm and its inner time management. I think it would be a hell lot of work to seperate these small functions from the main simulation core.

Your definition is programmed faulty.
No one programs faulty on purpose. Bugs just happen when the programmer doesn't notice all the things some piece of code changes. Just like in this case.

Besides I don't think it is that hard to fix really.