Collision object render data offset on the X axis for isometric maps

[maximveligan]

Rendering the collision objects for tiles doesn't seem to be working for isometric maps. They're offset in the negative X direction by what looks like is half the tile width. The collision objects also don't appear to be rendering correctly themselves, with parts of them being cut off when I scroll the map back into view.

Mousing over the mis-rendered tile fixes the missing collision rendering, but the X offset issue remains the same.

Here's what the collision object for the tile looks like:

Tiled version: 1.7.2, Windows 10

[bjorn]

Finally got around to looking into this. Turned out it was a silly regression in Tiled 1.7.2. :-/

Will be fixed in Tiled 1.8.3.