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

Better collision info and object type integration? #1281

Open
vortexofdoom opened this issue May 18, 2016 · 4 comments
Open

Better collision info and object type integration? #1281

vortexofdoom opened this issue May 18, 2016 · 4 comments
Labels

Comments

@vortexofdoom
Copy link

@vortexofdoom vortexofdoom commented May 18, 2016

I've been getting to know this amazing tool better over the last few weeks, and am in awe of the power of the object type support now. However, I do think an improved Tile Collision editor could greatly improve it.

In addition to great suggestions like #1248, #799, and a couple others I saw but can't recall or find again atm, I think a great addition would be to make the Tile Collision Editor work more like the terrain editor. You would be able to view the entire tileset at once and see what colliders exist instead of clicking a tile to see an exact copy of that tile with collision info and then clicking back over to see a different one, etc.

I got the idea from the Tile Collision Editor loading by default with the tile at the default size and a lot of empty space. You would still create the tile collision objects on a per-tile basis, but you could freely move between them and see them all so that it's easy to tell if there's a tile you missed doing the collisions for.

The object types being applicable to the tile collision editor have the potential to be VERY powerful now for reducing redundant layers for tiles that will always work exactly the same way every time they're used, and I think that a little more ease of editing and viewing the per-tile object info along with more big picture things like making them visible and having more support for automatic type assignment would go a long way toward unleashing that power.

@bjorn
Copy link
Member

@bjorn bjorn commented May 19, 2016

I think it's a great idea and will definitely take this into consideration when moving the Tile Collision Editor dialog into the Tileset Editor that I'm working on in the wip/tilesetdocument branch. There, the editing of terrain information has already turned into an editing mode rather than a dialog, and it would be nice to do the same thing with the collision editor (as well as the animation editor)

@bjorn bjorn added the feature label May 19, 2016
@kheftel-old
Copy link

@kheftel-old kheftel-old commented May 19, 2016

oooh, +1 for not having terrain/animation in a dialog.

Super excited for all the great changes, @bjorn!

@DanielPower
Copy link

@DanielPower DanielPower commented Dec 21, 2016

The collision editor has become very important to my workflow, since some tiles (such as corner walls) require two boxes for accurate collisions. And placing an object for every collidable tile would be too much work. It would be extremely useful to be able to display tile collision boxes on the map in Tiled.

Looking forward to seeing the new tileset code. Thank you for all the hard work!

@bjorn
Copy link
Member

@bjorn bjorn commented Apr 19, 2019

@DanielPower Displaying tile collision boxes on the map is now implemented and available in the latest development snapshot.

The main suggestion by @vortexofdoom here is to improve the tile collision editor so that you can see the collision boxes of all tiles there and quickly switch between them, possibly removing the dedicated window entirely. While I think the last thing will be rather tricky with the current setup, rendering the collision shapes on all tiles in the tileset editor is definitely something I will try to include for the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants