@Bracco #164 You are somewhere right sorry for creating a big issue.
@Karnik2009 #165 Don't be sorry, not a big issue at all, we are here to exchange ideas and opinions. The debate is welcome :-)
I'm sorry to get the same error again:
Game lost because I would have left the game. I thought the bug is well known. It's because my opponent gets a notification that I might cheat because I have more than one tab open.
Please fix it!!
Game lost because I would have left the game. I thought the bug is well known. It's because my opponent gets a notification that I might cheat because I have more than one tab open.
Please fix it!!
Is it possible to change the "Stabletime" in the LiveChess-Software? I cant find anything. Unfortunately it happened multiple times that I moved the pieces to slow and played e3 instead of e4 or a Rook to a field two fields before the field i wanted it to land on..
Maybe a stabletime setting could be implemented in the plugin? Something like "wait for 500 miliseconds, if no other move is received from the livechess api do the move"? I'm a dev myself so if i can help please let me know!
A workaround is to never slide the pieces and always lift them. but thats kind of akward :)
Maybe a stabletime setting could be implemented in the plugin? Something like "wait for 500 miliseconds, if no other move is received from the livechess api do the move"? I'm a dev myself so if i can help please let me know!
A workaround is to never slide the pieces and always lift them. but thats kind of akward :)
@phib #168
I am afraid that the "slide" of pieces instead of a "lift-and-place" manoeuvre is difficult to detect correctly, even by the DGT Technology genuine driver.
I have been using my DGT board since 2005. I mostly used it over FICS with an interface named "babaschess" which implements the genuine driver. I've personally experienced that the "slide" of a piece leads to unpredictable results. It's mostly a matter of board and pieces sensors detection. The timing is only one the factors that determine the reciprocal recognition.
Just to name some: distance of the piece from the board, a piece accidentally dropped, a piece going to be placed in a square while accidentally passed too close to the preceding square...
This is why DGT technology themselves always recommends to use a "lift-and-place" approach
I am afraid that the "slide" of pieces instead of a "lift-and-place" manoeuvre is difficult to detect correctly, even by the DGT Technology genuine driver.
I have been using my DGT board since 2005. I mostly used it over FICS with an interface named "babaschess" which implements the genuine driver. I've personally experienced that the "slide" of a piece leads to unpredictable results. It's mostly a matter of board and pieces sensors detection. The timing is only one the factors that determine the reciprocal recognition.
Just to name some: distance of the piece from the board, a piece accidentally dropped, a piece going to be placed in a square while accidentally passed too close to the preceding square...
This is why DGT technology themselves always recommends to use a "lift-and-place" approach
@andrescavallin
Could you please read the comment #167! I have the same problem.
Is there anything you can do to fix it?
What are the others‘ experience? Are you also losing games out of nothing. „... has left the game without resigning. Will get banned next time“
Could you please read the comment #167! I have the same problem.
Is there anything you can do to fix it?
What are the others‘ experience? Are you also losing games out of nothing. „... has left the game without resigning. Will get banned next time“
This topic has been archived and can no longer be replied to.