Algodoo

There seems to be a problem. As soon as I run the sim, all chess pieces disappear and only some weird pattern remains on each piece. Does anyone else have this problem?

Xray - When I get back (around 2hrs from now), I will put the texture back in the scene (I forgot that Algodoo does this)

Xray - Should be fixed now!

Nice work.

@ 42flowermaster -- I haven't spent much time with it yet, but so far it looks correct. Good job!

Thanks Xray and s_noonan

"Click the buttons on the left to disable/enable certain features."
What buttons?

I don't understand what you mean by "multiple piece possibilities". Do you mean consecutive moves by the same piece? Na2xb5 is not a valid move.

Why show "LEGAL MOVES" if it is not being used?

@s_noonan I'm sure that "Na2xb5" is just used as an EXAMPLE! I'm sure that it means: When 2 of any piece is on the same row / column("columns only" for pawns, as pawns only move forward/diagonal), different notation needs to be used to specify which piece was moved.

For the other 2 questions, here's my answer(Maybe not correct):
Q1 - "What buttons?"
A1 - Buttons that probably aren't in the scene yet.
Q3 - "Why show "LEGAL MOVES" if it's not being used?"
A3 - I can't even think of an answer

@CPJchute,

Thanks. If I understand you correctly, then the "x" in "Na2xb5" means "from". The added "xb5" would be to remove ambiguity if, before the move, (2) knights of the same color could move to "a2".

@42flowermaster,

I haven't looked into your code yet, but I'm thinking that legal move detection was not a trivial task.

s_noonan - I'm fairly certain that the "x" indicates capture. For example "Na2xb5" means Knight on a2 captured the piece on b5.

@CPJChute - (Q1) The buttons were in the scene, but algodoo crashed the moment I added them and decided not to go through all the work again.
(Q3) Legal moves were used, it worked but lagged the scene a lot everytime a move was played. If you want, I can add that feature again (there are definitely everything to fix)

@s_noonan - I used "Na2xb5" as an example because such a move notation would require legal move detection to determine the "a2" part because if this move were ever written it would require that the program determine that other knights on the a-file and 2-rank could move to the "b5" square. Since legal move detection is really slow, I decided not to implement this type of move notation.

I may consider completely deleting this scene and bringing it back in the future with (hopefully) faster move detection, this was just a test. Sorry for the confusion!

@Xray,
Thanks. I see you are correct. Algebraic_notation_(chess)

The reason for the mod in SAN is to disambiguate moves where two (or more) identical pieces can move to the same square. In my defense, I thought since "Na2" means knight moves to a2, that the added "xb5" was for disambiguation, which is wrong. In the “Na2xb5” case, the notation would be "Nb5" if there was not another identical knight that could move to b5.

Theres no clapping emoji so take these

how long did this take to code??

a_bored_coder - a long time

Ah yes. This scene is just like those types of scenes where the code is so complicated, it makes me wonder how they even do it. When I opened up the script menu of the pink rectangle on top, I'm amazed by the code. So many custom functions, so many variables... I have too many questions. Such as, how do you make the pieces snap to the grid? How do you understand all of this? Where did you learn all of this from??? You're not Albert Einstein, are you?

Anyway, I played the scene on the beta version, v2.2.0 b2, and it's not laggy at all. It runs smoothly. Good game!

@PizzaGuy22,

% of simulation time on my PC:

       sim.frequency
  Version  60   120
  ~~~~~~~~~~~~~~~~~~~~~~~
  v2.1.0   97   70
  v2.2.0 b2 93   30

PizzaGuy22 - Thanks for playing!

I had already attempted to make a chess engine a few times outside of Algodoo, so there was some code to replicate. The hard part was definitely translating all the bitwise operators and objects into Algodoo code, which is hard because it does not support those

The way the pieces snap to the grid was by transforming the cursor position into a square index (a function in the script), and then transforming the square index into a position that is centered on the grid.

For legal move detection, the 0x88 board representation was really helpful because it made out-of-bounds checks much more efficient

How to move?

ElleryDeku - Pieces drag-drop using mouse while the simulation is running (no move tool or anything, it is scripted)