cocos2d for iPhone

A fast, easy to use, free, and community supported 2D game engine

1. 

   Questor
   Member

   Hi,

   I am new to cocos2d but I have been reading and experimenting with the examples code alot (of coco2d, denshion, box2d and a little chipmunk) and I had a couple of questions...

   1) When I tried the both the box2d and chipmunk templates (which I realize has alot in common): They create a program that allows you to drop boxes with letters (A,B,C or D) in them. Several times when trying these test programs (no mods just straight from the template and the RunAndBuild) they would work for a while and then simply exit at some point while I was dropping boxes. I saw no error/exception in the console, so I thought I should mention it. Since box2d is now based on the newer version (that uses fixtures as opposed to shapes) and that version is not an official release I was concerned that perhaps an issue may have crept in that would not be immediately obvious in the test bed. I was running the code in the 3.0 simulator. It doesn't happen every time, but it happens enough to make me curious if others have seen this behavior? And if it something I should report as a bug?

   2) When extracting part of the ParticleTest out into a new project (just to make a single particle test that would be easier to read) I kept running into the issue that "fire.png" was required even if it was not used anywhere in the program. I even blew away the new project once and started all over again....but once I got to the point of having an example that can run it will always seem to require fire.png. I have read that someone else experienced this behavior with fps_image as well. Is this a bug or simply an requirement of some internal cocos2d class that particle uses?

   Any insight into these issues would be appreciated.

   Thanks,
   Q

   Posted 2 years ago #
2. 

   xStoryTeller
   Member

   I cant help you on one since I dont use box2D or 0.9 yet for that matter.

   2 on the other hand I know what is happening, when you are using the standard particle effects they usually refer to fire.png, you can check this out in the particle.m file in your cocos2D folder, and if you dont want to use fps_image you can comment out the line for fast fps drawing in Director.m

   Posted 2 years ago #
3. 

   pabloruiz55
   Member

   not sure about 1, but about 2, fire.png is required by one of the particle systems, not sure which one, did you check that out?

   Posted 2 years ago #
4. 

   Steve Oldmeadow
   Administrator

   Re: 1 see this thread http://www.cocos2d-iphone.org/forum/topic/2206

   In future I think it is better to create separate threads for separate issues. Your point 1 belongs in the physics forum whereas point 2 belongs in the cocos2d forum. I will leave your post here for now. A more meaningful subject for your thread wouldn't hurt either.

   Posted 2 years ago #
5. 

   Steve Oldmeadow
   Administrator

   Re: point 1. I could reproduce what you described and it seems that it is an issue with OpenGL on the simulator so nothing to do with Box2d.

   Posted 2 years ago #
6. 

   Questor
   Member

   Sorry for the delay in posting back (holiday weekend and all).

   Thanks all for the comments. I will try to do better on the posting issues (title and category). Sorry about that.

   Glad to hear the 1st item is a simulator issue, it had me worried about stability. That is a relief.

   I found the code that had the fire.png file in it...it was CCParticleExamples.m...

   Thanks for the all the help and the quick replies.

   Best Regards,
   Q

   Posted 2 years ago #

RSS feed for this topic

Reply

You must log in to post.