Bump. I am also looking for a solution to something similar to @codecowboy

You can use masking in Cocos2D. Here is an example
http://www.cocos2d-iphone.org/forum/topic/15890?replies=1#post-89757

I had a problem with progress bar rounded ends too.
When I used scaleX it looks really bad.
My solution is setTextureRect method:

CGRect barRect = [progressBar textureRect];
barRect.size.width *= progressYouNeed;
[progressBar setTextureRect: barRect];

Maybe it's late but this topic is top1 google so:

There is a simple way to do scrolling background.
You have to create two window size spirtes. One in the windows next just next to it (away from view).
Than in time just move both sprites and when the next background would fulify windows jump with invisible part of background on the another side of view. (you can modulo movement to make it slower).

ah use @selector to set scrolling for both.

i have put full answer in a new topic:
http://www.cocos2d-iphone.org/forum/topic/12598#post-70766

Hi crmagicxxx,

thanks again for your assistance!

BR,

Stefan

How should I change the loop to keep only 1 menu?

MenuItems are children of Menu, so you can add them with addChild like any other node

Btw - to add Buttons on a view, do I really have to use menus?

I suppose you mean Layer not View? But yes, you have to add Menu to Layer if you want to use cocos2d's Menu/MenuItem system. But you can always make your own buttons without menus, if you want to implement features that aren't covered with Menus...

Hi crmagicxxx,

thanks for your help and advice! How should I change the loop to keep only 1 menu? Btw - to add Buttons
on a view, do I really have to use menus?

Thanks again for your help and advice!

BR,

Stefan

Add tags to your buttons. For example, inside your loop you can do:

button.tag = i;

and then:

- (void) showSideMenu: (CCMenuItem *) menuItem
{
NSLog(@"Menu item called: %d", menuItem.tag);
}

And, unrelated to your question: Your loop seems to be wrong, as you're adding count number of menus. Instead you should only add menu items and keep only one menu.

Hi Folks,

I am new into Cocos2D and I am wondering how to add a Number to a CCMenuItemImage to fetch the button which has been pressed?

I am looping from 1 to 20 and adding images to my view like this:

CCMenu *menu;
		for (i=0; i < count; i++ ){

			if ((i != 0) && (i % 4 == 0)) row += 1;

		CCMenuItemImage *button = [CCMenuItemImage itemFromNormalImage:@"winziback.png"
														 selectedImage:@"winzi1.png"
																target:self
															  selector:@selector(showSideMenu:)];

		x = (i % 4) * 75 + 100;
		NSLog(@"x = %d", x);
		y = row * 75;

		menu = [CCMenu menuWithItems:button, nil];
		button.position = ccp(x-211, y-135);
		[self addChild:menu];

		}

Here I log the pressing:

- (void) showSideMenu: (CCMenuItem  *) menuItem
{
	NSLog(@"The first menu was called");
}

Thanks for any help and advice!

BR,

Stefan

@JohnM, I can confirm this works:

[[Director sharedDirector] openGLView].layer.magnificationFilter = kCAFilterNearest;
[[Director sharedDirector] openGLView].layer.contentsRect = CGRectMake(0.0001, 0.0001, 1, 1);

Put it just before you attach your first scene.

Just be sure you use this ONLY in iPhone 4 (will probably work as well in iPad but haven't tested there yet)

To detect device, sue something like this: http://www.cocos2d-iphone.org/forum/topic/8233#post-47883
Just be sure to replace NSUnicodeStringEncoding with NSUTF8StringEncoding

Actually the low resolution images in iPhone 4 are not exactly the same that old devices, I have tested that on few games. iPhone 4 will stretch the images and it is noticeable, similar effect than running the game in iPad in x2 mode.

I found a possible solution, I haven't tested yet, but take a look:

http://www.cocos2d-iphone.org/forum/topic/9264#post-53755

I believe you have to call this after all Director (or CCDirector depending of your version) and just before attach your first scene, but as I said, I haven't tested yet.

Thanks to @araker who pointed me on the right direction, there is more information here apple devforums

It's not pixelated and is the same as the older generation. The thing is that, people who got IPhone/IPod 4 get used to the new crisp display a lot which the older ones starts to look a little bit blurry ;).

Hi,

I believe it should not be so.

If Iphone 4 displays low resolution correctly, why would it be pixelated?

piexelated... annoying... makes me realise how beautiful the display really is...

You can find some cocos2d animation samples in below link ...
http://cocoabugs.blogspot.com/2010/09/creating-ccwaves3d-animation-for-iphone.html

Ok, forget my question, managed to alter the draw method on the AtlasSpriteManager.

Hi, sorry to jump on this old thread, but I am trying to do exactly the same, I'm finally porting all my sprites to a sprite sheet, before on my sprites subclass I overwrote the draw method so I could draw a bouncing box around, note I'm working with isometric so the default cocos2d debug bouncing box is not what I needed, I do draw an isometric 3d rectangle enclosing my objects so I could debug the collision and stuff, like the image:

So Steve, are you saying this is not possible to do? I am stuck on 0.8.2 so using old AtlasManager / AtlasSprite.

Hi,

I would like to run my game in low resolution (480x320) mode on Iphone 4.

I have following questions:
1. Does Iphone 4 display this low resolution clearly?
I know when we change resolution on LCD monitor, picture is not clear.

What are your experiences, is graphics clear or blurry?

I would like to avoid creating 2 graphics in game, as it takes more time and space in final build.

However, if it results in poor display, I will need to do support it.

Thanks in advance

I know this thread is ridiculously old, but I just had a problem with this. I decided to put all the Box2D stuff in a library, but then I was getting a HUGE number of "visibility" warnings.

To solve it, I just had to turn ON a flag in the Box2D library target called "Symbols Hidden by Default(GCC_SYBMOLS_PRIVATE_EXTERN)

Atlas sprites got folded into CCSprites together with normal sprites. Now the engine will make it an 'atlassprite' automagically if you define it from a sprite sheet, and a normal sprite if you define it from a standalone image, all behind the scenes.

edit: read this: http://www.cocos2d-iphone.org/wiki/doku.php/prog_guide:migrating_to_0_9

Specifically the 'Updating Sprites' section

So, if you could help me out a little bit, where did Atlas Sprites go? What happened to them, and should I be using CCSpriteBatchNodes over Atlas Sprites?

Yep, what @skyhawk said.

Using CCSpriteBatchNode is the preferred option if you have more than 10-20 sprites on the screen since it will do all of them in 1 OpenGL batch call.

For initial prototyping, though, I wouldn't worry about CCSpriteBatchNode just yet. It's extra complexity that you may not need.

You can probably get by with just using [CCSprite spriteWithFile:] until you run into performance issues, then switch over to using sprite batch nodes as needed.

CCSpriteSheet became CCSpriteBatchNodes

Alright, so I am just so confused. I've read a lot, but so far I haven't figured out how I should do sprites in my game. From what I gather, I have 3 options,

CCSprite
Atlas Sprites
Sprite Sheets

However, when I was starting my new project, I was given a warning saying:

CCSpriteSheet *sheet; //This is deprecated

Well, in that case I can't use that. Which must mean Atlas Sprites are the way to go. But in the cocos2D test project, I didn't see the AtlasSpriteTest at all... and looking at some other tests (like the touches test) they just create a CCSprite using the Texture Cache.

So I am very confused at this point. What is the best practice for making Sprites? I've been using CCSprite for a while, but if Atlas Sprites are the better decision, where did the test file go? Where can I learn about them to use them, because I don't know where to start. Thanks.

You get 24MB for texture memory. This site has some tips of texture optimization. According to that article, your 5 sprite sheets will be using 10MB total. You can check the actual texture memory usage of your app with the OpenGL ES profiler tool.

Hi,

I have 5 spritesheets, each of 1024x1024 size, with 16bit graphics. All graphics will be in memory at same time.

1. How much IPhone 3G has available memory for graphics? So I am asking for slowest Iphone model and IPod 2nd generation.
2. Will I have an issue since graphics is spread out on 5 large spritesheets.

Thanks

I was able to use 32 x 32 tiles without any editing by rounding the animation calculation to the nearest pixel. Solution here:

http://www.cocos2d-iphone.org/forum/topic/4219

Read the documentation..

Hi,

Making graphics for tmx maps can be teddious job.
Moreover, I have read that some artifacts can happen.
For example, we have tile size 32x32.

I have read that graphics picture must be adjusted, so that actuall size will be 34x34 and this one pixel from each side is added to prevent artifacts in game.
1. How to prepare graphics for tmx map. Is there some easy solution? For example I have graphics in texture 1024x1024. Is there some way to automatically fix it?
2. Do I have to manually edit each tile in png graphics and add this 1 pixel (so that I copy neighbouring pixels) or there is some automatic way to do it easily. If all has to be done manualy, it is painful process.
3. This above questions were for game background. What about with sprites that are not part of tmx map graphcis? Are they also need to be fixed same way?

As far as I understand, this is very painfull process in preparing graphics for the game.
Could you give some guidance in this and enlight the way how to do it?

Thanks

I've been reading a lot of threads and come across lots of great info, but haven't been able to come up with a workable solution.

I have sprites from 2 different sprite sheets which need to be ordered in relation to eachother. Since they're children of different nodes, i'm going to have z-ordering issues.

Everything was fine initially because I was using normal CCSprites, not CCSpriteSheets but was having severe performance issues. The performance issues got addressed by porting everything to the CCSpriteSheet, but now I have ordering issues :)

According to this site -
http://allseeing-i.com/Performance-tips-for-Cocos2d-for-iPhone

I can play around with the vertexZ property in a CCNode to affect the actual render order of the sprites, but I'm guessing this isn't recommended. I don't have any weird transparency though. (I did try to play with changing the vertexZ of a few random sprites, but it didn't appear to actually do anything)

My question is, given the ordering requirement I have, what are (if any) my options besides using CCSprites or CCSpriteSheets? If it makes any difference, I'm using v0.99.3 of cocos2d. I haven't really explored AtlasSprites yet, mainly because I don't think I understand how they differ from CCSpriteSheets.

As always, thanks in advance!