afedotov
commented
3 months ago Source version with debug is based on master branch and may have fixes that is not included in current release branch. But this should not be the case for current iCarry2 driver code, if only your browser somehow cached much older version release.
Actually iCarry2 has very buggy firmware (I suppose you update you cube to latest firmware v5.5) and this cube skipping moves so bad. This is somehow mitigated with corresponding lost move recovery protocol procedure, but there still exists some rare edge cases when move may be missed. Known case is when skipped move was last move before cube is solved. I'll think how to better avoid such edge case. But your case is very weird and should not happen, you can try latest beta version - https://cstimer.net/new/ and see if the problem occurs there too.
jscheidtmann
Dear cs0x7f,
sometimes when using https://cstimer.net and the Gancube 356i Carry 2 connected in Giiker, the recorded moves are incomplete, e.g. for a 58 s solve, only 20 moves and 8.65 s are recorded and stored in the solve. The Giiker Cube display before and after the solve are in sync with the cube.
I cannot reproduce this in debug mode (https://cstimer.net/src/?debug=1) and in non-debug mode there's no relevant logs. Please advise how I can help.
For the time being, I will be using the debug mode.