cocos2d for iPhone

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

1. 

   riq
   Key Master

   I am happy to announce that v2.0.0-alpha is available for download.

   Download:
   * http://cocos2d-iphone.googlecode.com/files/cocos2d-iphone-2.0-alpha.tar.gz

   Highlights:
   * OpenGL ES 2.0 support (shaders)
   * Better physics integration
   * Includes Box2d v2.2.1 & Chipmunk 6.0.1: Templates updated with new best practices
   * Much faster Motion Streak
   * Improved ProgressTimer
   * Much easier to create "Double Resolution" sprites in Retina Display
   * Retina Display code rewritten: double viewport instead of position. Everything is in points.
   * Improved profiling API
   * Simplified Sprite / SpriteBatch source code
   * and more

   API reference: http://www.cocos2d-iphone.org/api-ref/2.0.0

   Release Notes: http://www.cocos2d-iphone.org/wiki/doku.php/release_notes:2_0_0

   How to migrate to v2.0: http://www.cocos2d-iphone.org/wiki/doku.php/prog_guide:migrate_to_v2.0

   Documentation is still very incomplete. When in doubt, please read the tests source code as documentation.

   This is not an stable release. Use it with caution.

   I would appreciate if you could test it in your game and report any possible bug that might appear.
   Thank you.

   Posted 8 months ago #
2. 

   hm50
   Member

   Woot!!

   Posted 8 months ago #
3. 

   griga
   Member

   That's awesome!

   Posted 8 months ago #
4. 

   lerkan
   Member

   Awesome! Great job!

   If I update to cocos2d 2.0 and release a game update, will all people that previously downloaded the game, with devices that doesn't support openGL 2.0 be angry?

   Posted 8 months ago #
5. 

   slembcke
   Administrator

   @lerkan
   No, they won't be given the option to download it if you set your upgrade requirements in iTunes. If that makes them angry, I guess that's unfortunate but you don't really want people that demand free software updates forever from a $1-2 app for their obsolete device. Especially when the number of people with a non ES 2.0 compatible device is in the single digit percent range now.

   Also, why would you upgrade and release an existing project to an alpha release of a new major version that is not 100% API compatible? Is there any features you really need from 2.x or are you simply speculating to make a point?

   Posted 8 months ago #
6. 

   Bloxx
   Member

   Excellent!

   Posted 8 months ago #
7. 

   Leon
   Member

   Great job .
   A lot of migration work need to do now .

   Posted 8 months ago #
8. 

   zaaroth
   Member

   I dont think so. If your game works fine on 1.0 there is no point in migrating.

   Just move to 2.0 if you need some of the features it provides, otherwise stick with 1.0 since fixes are likely to be pushed on both (if not, just patch the code yourself).

   Posted 8 months ago #
9. 

   jandujar
   Member

   well done riq!!

   Posted 8 months ago #
10. 

    slycrel
    Member

    Hey, fantastic news! I'll have to give it a look.

    Does this mean that cocos2d 1.x releases will be by and large small features and bug fixes, with primary development in 2.0? I hadn't realized we were there yet, I'll need to do some mental shuffling...

    Looking forward to shaders, I hear they are the bees knees. =)

    Posted 8 months ago #
11. 

    Walzer
    Member

    Great job! Congratulations!

    Posted 8 months ago #
12. 

    lerkan
    Member

    @slembcke good point. thanks

    Posted 8 months ago #
13. 

    araker
    Moderator

    Nice Job Riq.

    @slycrel, I'm now working together with Riq on the 1.x branch. Besides bug fixes there will still be new features implemented, but the 2.x branch will be more actively developed. Riq's time is limited because he's working mainly on the 2.x branch and my time is limited, because I'm doing this in my spare time.

    Posted 8 months ago #
14. 

    MikeSz
    Member

    Cool ! Will check it out soon, maybe use it for the next project ? :)

    Anyways - there's an error in the CCProfiling

    CCProfiling.m:66:33: error: conflicting parameter types in implementation of 'releaseTimer:': 'CCProfilingTimer *' vs 'NSString *'

    in the header:
    - (void) releaseTimer:(CCProfilingTimer*)timer;

    In .m file:
    - (void)releaseTimer:(NSString*)timerName

    Posted 8 months ago #
15. 

    riq
    Key Master

    @MikeSz: Thanks. fixed. https://github.com/cocos2d/cocos2d-iphone/commit/d2e15e161d8b5bf07f3810081435a5cbca701371

    Posted 8 months ago #
16. 

    Ricardo1980
    Member

    Thanks a lot Riq.

    BTW, when you say "Documentation is still very incomplete.", do you mean this alpha release or also 1.0 release?

    Thanks.

    Posted 8 months ago #
17. 

    riq
    Key Master

    @Ricardo1980: I meant that the v2.0 related documentation is very scarce.

    Posted 8 months ago #
18. 

    Ricardo1980
    Member

    Thanks!

    Is there any doc or samples about we can now created using shaders?

    Posted 8 months ago #
19. 

    riq
    Key Master

    @ricardo1980:

    Yes, as I mentioned:
    [...] When in doubt, please read the tests source code as documentation.

    In particular, try the "ShaderTest"

    Posted 8 months ago #
20. 

    Ricardo1980
    Member

    Thanks riq, I'm at work and I will test it when I get home.

    Posted 8 months ago #
21. 

    Ricardo1980
    Member

    I was so impatient that I tested ShaderTest at my work.
    All demos run very slowly on my iPhone 4, between 5 and 10 FPS (similar in my iPad 1)
    Is that normal?
    I don't see any comment about this issue in source code.

    Posted 8 months ago #
22. 

    edz
    Member

    Thanks for the update Riq =) I have a quick question : since this uses OpenGL ES 2.0 code will cocos2d v2.0 not support iPhone 3G?

    Posted 8 months ago #
23. 

    ayt
    Member

    @edz:

    [FIX] Xcode: iOS 4 is minimun required to run

    Posted 8 months ago #
24. 

    ddeaco
    Member

    OpenGL ES 2.0 will not run on the -

    iPhone 2G,
    iPhone 3G,
    iPod 1st Gen,
    iPod 2nd Gen,
    iPod 8Gb 3rd,

    As they only support openGL ES 1.1

    David

    __________________
    http://iceflame.com

    Posted 8 months ago #
25. 

    edz
    Member

    @ayt @ddeaco:

    Thanks. Also from the migration guide

    iOS: OpenGL ES 1.1 is no longer supported

    which rules out support for those devices via coexisting 1.1 and 2.0 code.

    p.s The 3G will run iOS 4.2.

    Posted 8 months ago #
26. 

    slycrel
    Member

    @araker thanks for the explanation. For my projects going forward I'll see about pushing towards the 2.0 branch--I'm doing this in my spare time too, so my projects are at times maddeningly slow. 2.0 will likely be stable/usable by the time my next project is mostly complete, so that's good information to have. I'm happy helping with stuff in either, but it's good to know where the general focus is for the API. Thanks. =)

    Posted 8 months ago #
27. 

    wybielacz
    Member

    CCLabelTTF stopped loading external fonts. Only system fonts works now. Anyone has the same problem with cocos2d v2.0.0 ?

    Posted 8 months ago #
28. 

    rakkarage
    Member

    woohoo!

    Posted 8 months ago #
29. 

    toadkick
    Member

    @wybielacz: from the release notes:

    [NEW] Tests: FontTest uses “bundle” fonts instead of FontLabel
    [FIX] Xcode: FontLabel: Removed since in iOS 4 you can load custom TTF

    iOS 4.0+ supports external fonts. You have to list the external font filenames in your info.plist in an array with the key UIAppFonts (or "Fonts provided by application")

    Posted 8 months ago #
30. 

    wybielacz
    Member

    @toadkick
    ufff didn't notice that! Thanks for the solution :)

    Now I have to migrate my line drawing code to OpenGL ES 2.0, but as i noticed a lot has changed so it seems a lot of work for me :/

    Posted 8 months ago #

RSS feed for this topic

Reply »

You must log in to post.