cocos2d v2.0-beta released

19 Responses to “cocos2d v2.0-beta released”

---

• melvinng05

  November 30, 2011 at 3:03 am

  cocos2d v1.1 final release still coming soon or stopped? Thanks riq, good job!
• Dani

  November 30, 2011 at 12:51 pm

  What a surprise! Thanks for this new version. I have updated my shooter project and all is working fine and smooth.

  Thanks all cocos2d developers for such a hard work!
• Jugon

  December 3, 2011 at 11:23 am

  Hi guys,
  i tried to install templates but i got the message permission denied… any solution?

  sudo is not supported why?

  thanks
• Tim Knauf

  December 4, 2011 at 11:08 pm

  @melvinng05 The 1.x branch is still in active development, so yes, 1.1 is still coming. araker concentrates on the 1.x branch and riq now concentrates on 2.x.
• diadem_lee

  December 13, 2011 at 9:07 pm

  Been trying to implement shaders in this version, I cant get anything going.

  I decided to look at the tests to see if I could pinpoint the problem, but the shader tests appear broken to me (only the Blur shader appears) the rest throw endless errors:
  OpenGL error 0×0502 in -[CCSprite draw] 552
• riq

  December 13, 2011 at 10:41 pm

  @diadem_lee:
  It is already fixed on github, on the “gles20″ branch:
  https://github.com/cocos2d/cocos2d-iphone/tree/gles20
• diadem_lee

  December 14, 2011 at 5:15 pm

  @riq

  Thanks, got this working without issue!

  Any plans to do a little writeup on the openGL changes? They were challenging for me to adapt to, especially as a openGL noob trying to learn.
• riq

  December 14, 2011 at 6:15 pm

  @diadem_lee:
  I suggest reading this book: http://shop.oreilly.com/product/9780596804831.do

  It shows how to code both using OpenGL ES 1.1 and ES 2.0.
  You will learn a lot about openGL ES.
• diadem_lee

  December 14, 2011 at 6:42 pm

  @riq thanks for the book suggestion, i will check it out.

  What I was referring to was not pure openGL but more the wrapper/convenience functions Cocos2D has implemented. It has taken me a while to understand the specifics of how to get started in the Cocos2D environment. There are tutorials out there, but the recent changes seem to break them.

  Once I had the working version of the tests of course it was much easier to just read through the code. I guess I was just hoping for a blurb on the design goals/best practices to the changes, if that makes sense?

  For example, I am specifically having issue with ccGLBindTexture2D. I think its implementing a cache of some sort, but when I try to use it I am having problems. I have rolled back to using glBindTexture directly.

  Thanks!
• riq

  December 14, 2011 at 6:56 pm

  @diadem_lee:
  I think this guide might help you:
  http://www.cocos2d-iphone.org/wiki/doku.php/prog_guide:migrate_to_v2.0
• Ammar Al-Issa

  December 28, 2011 at 3:01 pm

  Hi,

  First of all, I would like to thank everyone worked on cocos2d, it is really a wonderful treasure of APIs.

  I tried cocos2d v2 beta, and noticed there is a problem while running the game for performance analysis from within Xcdoe, by choosing profile, and then pick any performance tool in the instruments, once start launching it gives error ‘failed to get task for pid xxx’ , it will only run if i started the instrument and run the game from there ?

  I tried the same game code, with the stable release v1.1 it is working perfectly.?

  Thanks once again, and looking forward to address this in the stable release, or if currently there is a solution, please let me know.

  Thanks.
• riq

  December 28, 2011 at 3:51 pm

  @Ammar Al-Issa: No idea
  What Xcode version are you using ?
• Ammar Al-Issa

  December 28, 2011 at 4:33 pm

  Thanks for replying, I discovered the issue, it was little bit strange, i just deleted the game, and deleted the provisioning profile, then run it once again, it worked perfectly.

  Thanks
• icanzilb

  January 1, 2012 at 6:30 pm

  Hi Riq, I’m trying out to migrate custom CCSprite#draw to cocos2d 2.0 beta … I followed the 1.0->2.0 migration guide but I keep getting EXC_BAD_ACCESS inside the CC_NODE_DRAW_SETUP() macro on the ccGLUseProgram( shaderProgram_->program_ ); line. I’m using the cocos2d beta download + ARC, would appreciate bit of help with this Marin
• riq

  January 2, 2012 at 9:28 pm

  @Marin

  Please, post the traceback and the exact code that you are using. Also I suggest using the latest code form github.
• icanzilb

  January 6, 2012 at 5:01 pm

  riq, I figured it out – in the migration guide it’s not mentioned you actually have to load the shader program and assign it to the class. (Wasn’t that obvious for me)

  Marin
• alekye

  January 13, 2012 at 3:09 am

  hi, in the b2ContactListener class, the virtual function may be [ virtual void EndContact(b2Contact* contact); ] not be called.
  ex: i create two sensor, and move one to the other, the BeginContact be called once, but the EndContact not be called when the two body divided. the first sensor run the reverse action, the BeginContact not be called
• Alessandro

  January 15, 2012 at 7:34 am

  Compiling for armv6 missed CCParticleSystemPoint
  Solved adding the one from v1 and including it in CCParticleExamples.h
• Jim

  May 15, 2012 at 9:14 am

  I’m trying to archive a distribution copy of my app for the App Store. At first it was complaining that I needed to add armv6 to the settings…but when I do that I get a lot of CCParticleExample errors…

  Is there a work-around or fix?

• cocos2d v2.0-beta | Alpapps
  Pingback on Jan 4th, 2012 at 4:03 pm