Meta wrote:
You are right that there is a timing issue. The checkpoint is triggered too early.
If I am not mistaken, the spider checks the existence of a scorepoint (CueEvent CID_ScoreCheckpoint) after one turn, namely, processing everything caused by a player move. On the other hand, the engine will handle a scorepoint immediately after seeing a scorepoint (command Score Checkpoint), even when it is in the middle of a turn.
...
The engine (as part of the game) is already doing what it is supposed to do, sending the correct move list to the spider. On the other hand, the engine (as part of the spider) did not handle the scorepoint correctly.
Therefore, although this is an engine bug, any (straightforward) engine fix would require the spider to switch to the new engine code, which could be either very easy to do, if the engine is dynamically linked to the spider, or difficult otherwise. There are some workarounds, but all those workarounds I can think of require much more effort.
...
Let us wait for Mike and let him confirm how much of what we suspect is correct.
I appreciate the investigation into this admittedly opaque issue. I read carefully through these posts and I think I followed the discussion, but I'm not sure whether a root cause has been identified (please correct me if I missed it).
I'm happy to collaborate on identifying, developing, and deploying a fix. Now that the TLP project is officially done, my time investment into that project is generally completed except for ongoing support and the like, and I can focus my attention on point issues like this one, one at a time. I also have texture updates and additions next on my radar.
From my reading of this thread, my intuition is that there's some de-sync between game engine versions, but my intuition could be wrong. I understand the latest Steam version is 1.2.7.330, while the latest Caravel version is 1.2.7.316. However, from the dredges of my memory, IIRC, the only differences between the two are Steam-specific fixes. This assertion may not be correct.
To get me up to speed on the current state of this issue, can someone help with answers to these questions, to ensure I'm on the same page as to what you are experiencing?
Q1: The Caravel build (316) is submitting high scores for 'Neatherhood?
Q1a: The Caravel scores are being rejected for this scorepoint?
Q2: The Steam build (330) is submitting high scores for 'Neatherhood?
Q2a: The Steam scores are being rejected for this scorepoint?
Q3: Do we think there's a difference between the Caravel and Steam versions in submitting or accepting high scores for score points like this one, or is this issue present for both the Steam and Caravel game engine builds?
Is there value in me providing y'all a new Caravel test executable of v330 to experiment with, to see if the issue is resolved in that build?
Are the steps listed in Kieran's post from 01-10-2016 above to reproduce the issue still valid in the latest Caravel build?
____________________________
Gandalf? Yes... That's what they used to call me.
Gandalf the Grey. That was my name.
I am Gandalf the White.
And I come back to you now at the turn of the tide.
[Last edited by mrimer at 08-18-2020 02:19 PM]