Tip: Do not runWithScene before attachInView or attachInWindow

cocos2d for iPhone » Programming » cocos2d support (graphics engine)

Tip: Do not runWithScene before attachInView or attachInWindow

(4 posts) (3 voices)

Started 2 years ago by Robert Payne
Latest reply from nash8114

Tags:

Robert Payne
Member

Hi All,

Thought I'd just share this. It isn't documented anywhere but in general avoid running a scene or allocing anything that uses OpenGL commands until the Director is attached into a window or view.

During the attaching process a lot of OpenGL parameters are setup and initialized. Without some of these it causes problems with gl commands. In particular if you add a texture through TextureMgr before attaching into a window/view the first texture will actually not be saved properly into the OpenGL state due to the glGetIntegerv command returning the minimum int value the first time through.

This could only be related to 3.1 or 3.0 but I think I've had this happen in 2.2.1 as well.

Posted 2 years ago #
natanavra
Member

Thank you for sharing the information, but don't we all attach in the appDelegate first and foremost?

Posted 2 years ago #
Robert Payne
Member

True I do as well but I was attaching it into the window/view after runWithScene. Not sure why I was doing it that way but just was and quite a headache trying to figure out what was causing the texture issues!

Posted 2 years ago #
nash8114
Member

I just found out the same. Apparently you can't even create a sprite before the director is attached in a view. This really bugs me :-(

Shouldn't there be a way to do the OpenGL setup before attaching in a view?
In my app I load an unload views, attaching the director to them. This doesn't really work well initially.

My workaround now is to create a UIView in the app delegate, then attach the director to it.

PS: is there any way to re-size the view the director is using?

Posted 2 years ago #

RSS feed for this topic

Reply

You must log in to post.