Sorry, we don't support your browser.  Install a modern browser

Objects on top of a size 2 stack of custom tokens or models clip into stack#1530

Placing an object on top of a size 2 stack of custom tokens, will result in the object on top being clipped into the stack.

Brief Steps to Reproduce:

  1. Create a Stackable Custom Token, e.g using image:
    https://www.dropbox.com/s/uu7ewii0c1a48mn/Geld10.png?dl=1
  2. Clone the Token
  3. Stack the cloned token and original token
  4. Place an object on top of the stack (e.g. a die, a checkers chip, or another custom token)

Observe how the object on top clips into the 2-stack as if the height of the stack is equal to a single token rather than 2.

This is on Tabletop Simulator v13.1.1

A few observations:

  1. This only happens for stacks of size 2. Stacks of size 3 works as expected.
  2. This happens not just for custom tokens, but at least also for custom models (and possibly other custom objects)

This issue seems to occur 100% of the time when following the detailed steps below, and is pretty egregious. It prevents in game mechanics where e.g. an auction bid using coins of various denominations is stacked in a single stack, as the object clipping makes it impossible to read out the correct amount of money present in the stack.

Complete Steps to Reproduce:

  1. Create a new Custom Token (Objects -> Custom -> Token)
  2. Apply an image (e.g https://www.dropbox.com/s/uu7ewii0c1a48mn/Geld10.png?dl=1)
  3. Set Thickness to 0.1
  4. Check the Stackable option
  5. Import the token
  6. Create a Clone of the token
  7. Create a stack of the 2 tokens by placing the clone on top of the original
  8. Add a die to the table (Objects -> Components -> Dice -> Plastic -> D6)
  9. Place the die on top of the stack
2 years ago

I would like to add that Custom Tiles are affected by this as well.

In addition, if you stack a custom object to 3 and then remove 1, the stack of 2 will act normally. So it’s only when you initially create the stack of 2 does one side lose it’s collision it seems. Thickness seems to not affect whether this happens or not.

If you take a look at the image below, you can see that if the objects were flipped, they will clip through the object below as well… including the table! Thus this can easily lead to more confusion if the player(s) are determining things visually instead of reading the number when you put your cursor over the object.

Hopefully this gets fixed.

9 months ago