Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wang tile coloring incorrect for isometric tiles of unusual dimensions #2101

Closed
BorisTheBrave opened this issue Apr 6, 2019 · 1 comment
Closed
Labels
bug Broken behavior.

Comments

@BorisTheBrave
Copy link

I have an isometric tileset with the following settings:

<tileset tilewidth="64" tileheight="192" ...
  <grid orientation="isometric" width="64" height="32"/>

In other words, the tiles extend upwards a lot beyond the flat surface of the map. I tried to set up wang tiles for this tile set, but it looks like the editor is using tilewidth / tileheight to draw the colors, rather than width / height.

Steps to reproduce

Download the tileset and accompanying image: tileset.zip

Open the tileset and add a wang set, and some colors. Hover or draw those colors anywhere over the tileset.

Actual Behaviour

The colors are drawn on the inside of a rhombus with size 64 / 192. This causes graphical glitches as it extends outside the rectangular bounds of that tile, and anything drawn there isn't cleaned up when the mouse leaves the tile.

image

(the mouse is over the top middle tile in this image)

Expected behaviour

The colors should be on the inside of a diamond with width 64 and height 32, like for a normal isometric tileset. The diamond should be oriented as it appears in the map editor, (i.e. respecting drawing offset). Additionally, there should be no graphical glitches when colors are drawn outside the bounds of the tile.

Other details

Tiled v1.2.3. Windows 10 64 bit

NB: All graphics come from https://opengameart.org/content/medieval-building-tiles
They are licensed to Clint Bellanger under CC-BY-SA.

@bjorn bjorn added the bug Broken behavior. label Aug 12, 2020
@bjorn
Copy link
Member

bjorn commented Aug 12, 2020

Can't reproduce on latest version anymore. Might have been a duplicate of #1943 which was fixed in 6c369e8.

@bjorn bjorn closed this as completed Aug 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Broken behavior.
Projects
None yet
Development

No branches or pull requests

2 participants