hiker {l Wrote}:There should be no need to press F10 twice (I am even wondering why this works). Just press ctrl-F10 should be all that's needed. If not, let me know.
Thanks for your feedback, Joerg. Right, Ctrl+F10 works fine, I was just trying different things and wondering whether saving a history file is important, so i posted this alternate route. As I have not looked up anything in the code, this was just some (time-) trial-and-error
hiker {l Wrote}:STK should try to open a replay file every time a track is loaded, and if it finds one, it is loaded.
True, that makes sense. I was just wondering why i had to restart STK to playback newly recorded replays... maybe that was related to recording in ghost mode, that sounds like a good scenario to trigger glitches
hiker {l Wrote}:We didn't finish this in time for 0.8 - it mostly needs [...]
That list of improvements looks very reasonable. Setting up new gui elements is probably a tedious thing to do. But hey, the feature is already impressive and very useful. I agree with Ancalagon, some indication for the use of skidding, nitro and zippers would be very appreciated. That does not have to be the visual effects, some on screen info about recorded key presses could be enough. That reminds me of demos in the title screens of old arcade games. Also: Ghost replay with some indication of key presses could be a useful aspect for future tutorials.
Other features that could be useful: An indicator for the ghosts position on the track outline and notifications about lap times, both just as for regular karts. Some trail for the ghosts could also be nice, much like skidding marks, but colored.
hiker {l Wrote}:We would also be interested in using replays for a challenge or two in story mode.
That sounds more tricky when interactions between multiple karts need to be recorded.