@c13ply Okay, these files contain "previously viewed scenes that are designed to be skipped". Scenes not designed to be skipped cannot be skipped with SDF.txt. Try to skip final scenes in Al Farum or Nemrut by editing only SDF.txt, I think you will fail. And at least 2 people managed to skip scenes in Kelbegen and Ianna without editing this file and the code is very similar to what they should skip.
It worked and works on any patch.
No it doesn't.
I've been skipping cutscenes (Mines and the Temple of Ianna) in the steam version of the game
They have changed the code then.
There is no other explanation.
Actually @DeH4uK mentioned a few days ago when they scenes were first skipped. If we understand well the behaviour of the SDF file (what it seems), if you ever success to skip a scene, you can skip it until the end of time if the SDF file remains the same after that. In other words, the ability of a scene to be skipped is not only function of what you're doing in an actual level but also of what you've done before. So if you watch a run and someone is skipping the scenes in Kelbegen or Ianna, you cannot tell if it comes from a real manipulation which was done before or an edition of the SDF file. So if you can prove I'm wrong I'm listening, otherwise SDF file edition will be used and discussion is closed.
@c13ply Cubeface skipped a scene in mines long before the release of the steam version. We have 1 scene skip in the classic version and 1 scene skip in the steam version before I looked in SkipScript.py and SDF.txt. There is code in the maps indicating that these scenes were intended to be skipped, as these scenes have a SkipScriptStart call from SkipScript.py (when all non-skipped scenes don't have this). The vast majority of players may play >1000 times, but these scenes won't have time to be written to the file, but someone will only view them once and they will be written to SDF.txt, after which they will be skipped.
Another proof that the game can write these scenes to the file: When I first added these scenes to SDF.txt and tried to skip them, the game corrected the timing in that file itself. Most likely if the scene is already in the file, it takes less time to overwrite or the "wrong rewind" scene causes the call timing to work differently.
If we understand well the behaviour of the SDF file (what it seems)
As I said - it's serialized python dictionary. It's automatically generated and when you "first time" play the cut scene it will add corresponding value with "name" of the cut scene and its elapsed time.
If cut scene is meant to be skipped corresponding value will be added to a dictionary, serialized and saved in SDF.txt.
If it's not saved in SDF it's not meant to be skipped for some reason. Maybe they changed mind and wanted it to play in full and didn't remove all the code, just deactivated it. There is lot if deactivated, nonfunctional code in the game. A lot.
If you manually add, hardcode, corresponding vale to SDF then it may be skippable. It doesn't mean it was to be skipped.
These are all cut scenes from going through the map. There is no EscenaSuperEsp which is the last cut scene. It had not been added.
The conclusion is simple - EscenaSuperEsp, the last SOI cut scene is not automatically stored in SDF file and in GOG version, or Steam for that matter, it had been added manually, artificially, that's why it "works" to skip this cut scene. It's not standard feature. Even Tessaract, who knew so much about the game wasn't able to skip it.
Whether not including this cut scene was intended, or a bug is a different matter. It should be investigated.
