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

Some Improvements #6

Closed
GoogleCodeExporter opened this issue Jun 10, 2015 · 2 comments
Closed

Some Improvements #6

GoogleCodeExporter opened this issue Jun 10, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

Hi, I would just like to suggest a few features, and hope you can possibly 
implement them.

1. As you are allowed to create multiple bodies per assets, you could allow the 
creation of joints to link them together.

2. If I am not mistaken, I believe that you have to manually group your image 
together by yourself if you were to want multiple assets on the same area. 
Could we have an option to drag multiple assets at once upon the screen?

3. As there is support for loaders, how about having these loaders be able to 
display the direct code for creating the bodies as not all of us would like to 
use FixtureAtlas'?

Hope you are interested in some of these ideas,
Seth Sectioner

Original issue reported on code.google.com by senth...@gmail.com on 29 Nov 2011 at 1:08

@GoogleCodeExporter
Copy link
Author

Hello,

1. You're not allowed to create multiple bodies per asset, what is possible is 
multiple  shapes per body. In Box2D (and other engines), a body can be made of 
multiple shapes, but they still form a rigid body, and these shapes cannot 
interact dynamically with each other.

2. This time, such feature would allow multiple bodies to interact with each 
other, like in a real game. I'm considering this option, it would allow people 
to create complex objects made of multiple bodies, joined with custom joints.

3. Of course, the FixtureAtlas was just an example of how to create a (binary) 
loader for the editor files, anyone can reuse part of its code to create its 
own loader implementation. However, I'll try to create a generic java loader, 
that just let people access the vertices lists and build the bodies themselves, 
thanks for the suggestion ;)

Anyway, I'm really interested in point 2, it would allow some very powerful 
constructions. That's a lot of work (need to add a new canvas mode, joint 
creation, etc) but I'll update my twitter with the improvement status.

Thanks for the ideas ;)

Original comment by aurelien.ribon on 29 Nov 2011 at 1:29

  • Changed state: Accepted
  • Added labels: Type-Enhancement
  • Removed labels: Type-Defect

@GoogleCodeExporter
Copy link
Author

Work on all of this is started and will lead to 3.0 update with dynamic objects 
made of multiple rigid bodies and joint creation. Closing the issue.

Original comment by aurelien.ribon on 29 May 2012 at 8:39

  • Changed state: Done

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

No branches or pull requests

1 participant