cocos2d for iPhone

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

1. 

   Bill Hollings
   Moderator

   cocos3d 0.5.1-beta has been released. Highlights include:

   • Any visible 3D node can now respond to touch events, and the application can receive callbacks when a node is selected.
   • All 3D nodes now support the <NSCopying> protocol. Creating multiple copies of a 3D model is now simply a matter of invoking the copy method.
   • Fractional animation is now supported.

   Find out what's new here. And download cocos3d 0.5.1-beta here.

   Posted 1 year ago #
2. 

   fxy
   Member

   Great!
   Will cocos3d support Xcode 4 template in the near future?
   (after installed xcode4 GM, don't have xcode 3 any more)

   xy

   Posted 1 year ago #
3. 

   north
   Member

   Well that just made a good friday even better!

   Extremely happy to see the fractional animation capabilities and of course the touch enabling.

   Thanks for your great work!

   Posted 1 year ago #
4. 

   levi
   Member

   Yay for <NSCopying>!
   now I can rewrite all my duplicate methods :)

   Posted 1 year ago #
5. 

   estevez
   Member

   Hi Bill.

   I've just compiled the CC3DemoMashUp on my iPad with iOS 4.2 installed and the touch is not working. Any solution to this? I've looked the forums but haven't found any report of this.

   Thanks in advance

   Posted 1 year ago #
6. 

   Bill Hollings
   Moderator

   @estevez

   That's very strange. I have exactly the same environment (iPad with iOS 4.2), and have had no indication of touch not working properly with the demo app.

   Has anyone else experienced this?

   As a suggestion, you might try adding some LogDebug statements in the CC3Layer and CC3World methods that deal with touch handling to see how far the events get.

   Thanks...

   ...Bill

   Posted 1 year ago #
7. 

   estevez
   Member

   Sorry, my mistake, this iPad was upgraded to a beta. Will try on mine, with 4.2 at the office in a moment.

   Posted 1 year ago #
8. 

   fxy
   Member

   Hi Bill,
   I found one 'bug' in the 0.5.1 beta, when you touch anywhere, any transparent object will blink, like in the Demo app, the bouncing ball will blink even you didn't touch on somewhere else. Is that something related to rendering order?

   xy

   Posted 1 year ago #
9. 

   Bill Hollings
   Moderator

   @fxy

   Thanks for reporting the problem. We'll look into it.

   ...Bill

   Posted 1 year ago #
10. 

    fxy
    Member

    @Bill
    I'm an OpenGL beginner, I tried to looking into the touch problem. Basically, when you touch a transparent node, the painted color will pop out once, which make it looks like blink. When I looking into the code, I found out the way touch works is by color picking, and the unique color comes from the node tag, it only paints the touchable node. Then I tested it by changing the tag of one node, then the blink color changes too. I don't know how to fix it on the OPENGL color level, one way I bet it will work is to add the transparent node into another CC3Node, and make the parent node touchable.
    I hope it will help you to fix it.

    xy

    Posted 1 year ago #
11. 

    Bill Hollings
    Moderator

    @fxy

    Thanks for your research into the problem. I appreciate your input.

    We have been working on the problem as well. You are correct in that it is related to the color picking algorithm.

    To expand on your description, when a touch event occurs, the 3D scene is drawn twice in one frame. The color-picking algorithm colors each node with a unique color, picks the node based on the color at the touch point, and identifies the node from that color. Then the normal draw routine runs and draws the scene all over again in all its full material and texture glory. Because both drawing passes occur in the same frame, the user never sees the colors drawn by the picker.

    Except in the case of a translucent node. When it is re-drawn in full-glory on the second pass, a bit of the color used by the picking algorithm leaks through the translucency.

    Anyway...we've sorted it out, and the fix will be included in the 0.5.2 release due out at the end of this week.

    Thanks...

    ...Bill

    Posted 1 year ago #
12. 

    Herman
    Member

    @Bill V0.5.2 GREAT! Thanks for your support!!!

    Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.