Cocos2d Physics + tilemap IDE « cocos2d for iPhone

cocos2d for iPhone » Programming » Programming - Everything else

Cocos2d Physics + tilemap IDE

(41 posts) (11 voices)

Started 1 year ago by tato123
Latest reply from dany

Tags:

12 Next »

tato123
Member

I've started a Cocoa based project to essentially merge the tasks of designing physics in a work bench / IDE (similar to what is available in mekanimo) along with the task of generating tilemaps / level design. What I'm hoping to gain out of the project is an IDE that will allow developers to perform the following:

- Design, script, and preview physics objects within the workbench
- Export the objects as either c++ code (box2d) or an intermediate format such as xml
- Tile levels and the ability to drag the physics objects into the level
- Ability to configure all the physics bodies and planes directly on the tiles and have them mapped together

Please feel free to suggest any potential features.

I hope I'm not overstepping any boundaries on the forums given that there have already been a couple efforts for similar ideas. I come from a background of working with Unity3d and a couple other game editors. While they are great for 3d purposes, for the iphone they are slugs/overkill when it comes to strictly 2d, which is why I turn to cocos2d (the right tool for the job). I'm essentially looking to get a tool running that would allow me to more rapidly prototype and get running on coding games.

Thanks everyone!

Posted 1 year ago #
michaelm
Member

Sounds great.

Take a look at this http://www.splashdust.net/2009/10/box2d-mouse-drawing/
box2d and haxe code available.

Posted 1 year ago #
max9xs
Member

@tato123 . wonderful idea !
But I am concern with Memory management and frame-rates in device, How can we solve this problem ? any idea?

Cheers
Max

Posted 1 year ago #
Duckwit
Member

So is this tool going to be available to the public? Sounds absolutely awesome!

So is it pretty much similar to LevelSVG?

EDIT: Oh is it tilemap based? (Unlike LevelSVG...)

Posted 1 year ago #
tato123
Member

@max9xs

I will have to tinker around with this, after giving it some thought I believe I should be able to export as code rather than property files (except maybe in the case of large levels). This would remove an interpretation layer. I'm not sure if that's a great answer, but I will have more to say once I begin the export process. At the moment I'm working on mapping the box2d objects to my app.

@Duckwit

Yes, it will be available to the public. I love working with cocos2d, I'm hoping to simplify some of the tasks I know that are personally kind of time consuming (in terms of code / test).

It will be similar to LevelSVG but I'm taking an asset based approach, similar to working in Unity3d.

*1st update on the project

I've started development, I've taken a core animation approach for mapping the physics objects to my application. I don't work directly with box2d on the workbench for development (rendering will be separate) since most of that is just configuring properties. I figured this would allow me to decouple frameworks and eventually introduce support for chipmunk as well. The nice thing about taking a core animation approach is key value coding properties allows the framework to change without needing to rewrite large portions of code in the future.

Posted 1 year ago #
araker
Moderator

This sounds promising. Do you plan on making the tile map format the same as/compatible with the format used in tiled?

Posted 1 year ago #
Duckwit
Member

@tato123 How long do you estimate till this is ready? Excellent work and I am really looking forward to seeing how it turns out!
I am planning a platform game as my first game and was debating whether to spend all my money on LevelSVG..... if this turns out well it would save a big hole in my piggy bank!

Great work :D

Duckwit

Posted 1 year ago #
tato123
Member

@araker

Yes, I intend on supporting current standards but I intend to separate raw data from exported. This will allow me to support new standards or possibly provide my own optimizations when I start looking into it.

@Duckwit

I hope to have an alpha build ready within the next 6 to 8 weeks. It will probably only include the physics workbench in rough form and only box2d (once I finish box2d adding chipmunk support won't take long).

Posted 1 year ago #
Duckwit
Member

I'm planning on Box2d :) I really can't wait to start trying this out! I think you are dong an excellent job. It's gonna make it possible for me to make the game I want to :D

Posted 1 year ago #
tato123
Member

Ok I've made some progress over the weekend. I've added the project explorer, which feels familiar for anyone who's worked with Xcode. It will allow for grouping on multiple asset types (physics, particles, textures, tilemaps). I've started to divide the other key sections up. I'm using a tab approach to manage the workbench.

Physics is coming along, I've mapped the entire box2d framework. I'm still debating how exactly to provide editing of values. Whether I want to have a pop-under box that appears as you select objects within the workbench or a devoted view pane on the right hand side. I do know I want to provide the community a new feature. I'm proposing a node editor. Similar to anyone who has worked with material shader node editing. I think that could nicely display relationships on physics groups.

Posted 1 year ago #
max9xs
Member

But the IDE is for Box2d only ? Not for Chipmunk ? And the IDE is based on what ? means it will require Cocos2d or UIKIT ?

Posted 1 year ago #
tato123
Member

@max9xs

The IDE in the final version will support box2d, chipmunk, and (hopefully) jellyphysics. The IDE is being built from the ground up. In it's final form it will likely end up exporting a static library that can be linked in to an existing cocos2d project, essentially providing a set of assets that you've designed. The library will contain class files that you have access to for direct editing.

I've been looking into a couple efforts people have worked on of routing / tweaking uiview content to an NSview, so I may use cocos2d framework to provide preview rendering.

I'm not sure if that answers your question?

Posted 1 year ago #
Duckwit
Member

Jellyphysics, Awesome! :D I am sure that will open a lot of opportunity for cocos2d users.

Posted 1 year ago #
tato123
Member

Jellyphysics will take a little longer to implement, simply because I've worked with chipmunk and box2d already. They are both fairly easy and straightforward to implement. It's more the monkeying around (code -test -code - test) that drives me nuts when trying to create advanced shapes (which is why I started this project).

Jellyphysics is a little aggravating in that it is the opposite of chipmunk and box2, everything is represented as a softbody instead of rigidbody. In terms of objects, you can't have as many physics objects on the screen due to deforming but otherwise it's written very similar with the whole spatial hashing. If I had the time I'd honestly rather spend time tweaking box2d to support both soft and rigid bodies.

Given that chipmunk and box2d so easily translate between the two I could probably allow users to switch engines on code output (on whether they'd like to use chipmunk of box2d). That won't make it to version 1 though.

Well I"m gonna tackle the physics workbench view. I'm gonna see if I can finish up the gridview class tonight. The view will be responsible for managing a physics group on the screen.

[edit] here is a rough rough preview

Posted 1 year ago #
icanzilb
Member

Excellent idea indeed :) If it can remove the necessity to deal extensively with c++ code that would be just great. Looking forward!
btw: sounds like it's gonna take quite a lot of time to put a thing like that, reveal the secret where do you get it from ? :)

Posted 1 year ago #
icanzilb
Member

btw: do you knoq riq is porting the cocos2d for OSX? you can have live preview in the IDE I guess quite easily, check out this thread : http://www.cocos2d-iphone.org/forum/topic/8960

Posted 1 year ago #
tato123
Member

@icanzilb

It is my intention to hopefully speed up development time of complex physics objects. I have noticed that riq is working hard on a couple separate fronts including the Mac project as well as a world editor. As such I will be focusing the tool on the creation of complex physics objects and the ability to use multiple physics frameworks.

As for free time I usually devote an hour or two a day at minimum (with breaks some days to accommodate my gamefly subscription tehehe).

I will move project updates to a project blog, but feel free to continue to request updates, encouragement, or just things that you run across in the physics realm that would be great to have and I will add to my software roadmap as feasible.

I will post project updates in the project blog http://tato123.wordpress.com

Posted 1 year ago #
icanzilb
Member

@tato123 very very cool, I'll keep an eye on this thread! Another comment: have you seen what the guys at Corona SDK are doing? They are making using physics (Chipmunk eventually) very very easy, but all the programming trough their SDK is done in Lua :(
They provide the ability to attach event handler to the physic body itself and you can pre and post check collisions very easy as the coliding body comes as a param to the event handler ... all good stuff!

Are you thinking of providing something similar (in the sense of extending, making more easy, unifiying coding experience) also on the code side of the physics, or you'll be having just the IDE spitting out a file which you can import and the coding will be via standard c++ coding (asking cz I'm kinda hooked to Obj-c :) ?

Posted 1 year ago #
Duckwit
Member

Lua isn't that hard to learn, quite simple. I did a bit of Lua programming on the 3D design build and program game called Roblox (you guys should check it out, its 3D and its a MMO game) . When I looked into Corona it looked s bit too simple, not yet advanced enough. :/. But I liked the look of the physics. :)

Duckwit

Posted 1 year ago #
tato123
Member

I wish there was some way to track this topic with email updates! Sorry for the delay.

@icanzlib

I have considered adding support for some sort of scripting language. I'm not as familiar with embedding support for scripting languages but I can definitely look into it. At the moment I will be exporting (based on the option you select) the document model as xml or c++ extended class files (.mm) so that I can hopefully package as a static library.

I understand what you mean, I'm hooked on Obj-c as well but given my background I can switch between C and C++ just as easily. Given that, I hope that generated results are easy enough to follow that even if you are more familiar with objective-c you could follow and tweak if necessary.

One of the things I see as a downfall for the Corona SDK is that I would imagine although performance is fast, there is still an additional layer of complexity added by having an intermediate layer of lua scripting to objective c code.

On the road map I will support event handlers and defining animation sequences as well as visually creating them.

@Duckwit

In what ways do you feel it's not advanced enough? I'm interested in feedback on what types of things are missing / people are looking for. My hope is to end up allowing developers a way to rapidly get the physics objects they need for their games up and running - from idea to the actual model.

======
I've been able to make significant progress and still shooting for an alpha build in the next two weeks. I'm currently creating physics objects and building up all the IDE event handling (editing, sizing, positioning, etc...)

Posted 1 year ago #
dany
Member

i'm following progress, seem to be very interesting!. what about use twitter for updates?

Posted 1 year ago #
tato123
Member

I'm not opposed to twitter, I'd just have to find a way to be more concise about my updates to fit posting limits. I'll look into it though definitely. I will also get around to posting yesterdays progress update. Depending on how late I wrap up I end up writing the previous days progress the next day.

Posted 1 year ago #
dany
Member

Maybe write just the title more a short comment and tinyurl to post blog

Posted 1 year ago #
noocell
Member

@tato123
+1 for an easier way to add physics objects to Cocos2d projects.
Exciting project!

I would also be very glad with an easy-to-use objective-C wrapper for Box2d. Something as convenient as the Corona way: http://developer.anscamobile.com/content/game-edition-physics-bodies

Posted 1 year ago #
tato123
Member

@daniele1988

Twitter is up http://twitter.com/TatoGames. It's also referenced on the blog as well

@noocell

The IDE should be capable of generating most objects that can be created via code, along with simplifying the creation of complex objects. The IDE will easily expose all the options corona provides but in a visual manner. I'm not sure though if thats the answer you are looking for. I do intend to allow updating the model values via code but I haven't built out the script processor yet, it's in rough planning stage.

The only thing that would make me nervous with wrapping Box2d with objective c is framework changes. Thats kinda the catch 22 you run into, it's apparent with a lot of game editors out there right now. They simplify tasks but unfortunately changes in the primary framework require downstream changes to the wrappers.

One of the good things I've seen Unity3d do though is support Objective c via plugins. I could possibly create a lifecycle for the events that naturally occur within the physics lifecycle (object creation, prestep, step, post step, destroy ) and callback to any custom objective c code users want to plug in.

Posted 1 year ago #
noocell
Member

@tato123

When involving physics in a project, there two phases: a)the initial setup of the physics objects and b)the runtime changes on these objects (mostly their properties) that are being applied by the game logic.

The IDE you are working on would be excelent for the initial setup (something like Unity3D).

However, for phase b, the runtime objects update, the developer needs to access the objects by code, so that he can apply game logic on them. Unity exposes the required methods with Javascript/C#. Your project would greatly help the developer if it also provided an easy way to modify these objects without directly talking with C++ to box2d (e.g. for altering the gravity or increasing the friction of an object). Had the developer gathered all the knowledge to manipulate his physics objects directly with Box2d calls, he would have no strong motivation to go with an IDE just for the initial setup.

In other words, the project would be tremendously successful if it required no knowledge of box2d, for including physics to Cocos2d. This is what Corona and Unity both have achieved: they totally hide the physics engine in use and offer a more convenient way of working with physics objects.

Think about it in marketing terms too. Which message would be more appealing?
1) Use Tato2D to make easy physics initial setups with a graphical IDE!
2) Use Tato2D to work with physics without any knowledge of Box2d/Chipmunk!

Just my thoughts.. :)

Posted 1 year ago #
dany
Member

i think that "properties" (that you can manage on ide) include gravity, friction, etc...

Posted 1 year ago #
tato123
Member

@noocell

That does make a lot of sense. I intended to provide users the ability to retrieve the physics groups (collection of objects) and objects via a unique identifier configurable within the IDE and by key value coding style dot notation ( (tree name.){1,n}.key } ). Since I have already done work on unifying the frameworks to where I can switch between Box2d and chipmunk I could have the unifier generate a controller class during export based on the framework selected at the time of export. This would continue to allow me to abstract the frameworks away where version upgrades don't become an issue and take advantage of the mappings I've setup for each of the frameworks.

Essentially I had a doc brown moment and figured I could provide access to properties via objective c wrappers and fairly low cost translation between objective c and the respective framework. During initial rollout I intend to provide support however for chipmunk, box2d, and working towards adding jellyphysics.

Posted 1 year ago #
littlehiccup
Member

@tato123 what do you think about putting this code up on github? I've done a little bit of OSX development and if it was open source I would gladly contribute.

Posted 1 year ago #
max9xs
Member

@tato123, & @littlehiccup

I think ittlehiccup having wonderful idea.. either github or SVN !
What do u think..?

Actually I have made one wrapper of chipmunk which runs like, softBody Physics.(As described in Previous post).I think in this week it might be complete.

Posted 1 year ago #

RSS feed for this topic

12 Next »

Reply »

You must log in to post.