Has anyone found a work around for this problem from the CC3Layer documentation:

However, since the CC3Layer's background color and any background 2D nodes have already been drawn by normal cocos2d CCLayer behaviour and cannot be redrawn during 3D drawing, when a touch event is used to select a node, there is a very slight flicker on any translucent nodes that have nothing behind them except the layer's background color or 2D CCNodes. Opaque 3D nodes are not affected and do not flicker. Nor do translucent nodes that have 3D nodes behind them.

To remove this flicker on translucent nodes during touch event processing, make sure that translucent nodes do not appear directly over the background color of the layer, or over 2D CCNodes. In such cases, use a full 3D skybox in the 3D world instead.

I am attempting to use Cocos3d in an AR app, and the only thing behind the CC3Billboard is the video layer. So when the billboard which has some transparency is tapped the transparent parts of the sprite turn black for a split second. I'm fairly confident that this behavior that I am seeing can be explained by the CCLayer flickering explanation, I'm just not sure how to correct it in my case. It's an AR app, so putting a 3d object or a skybox behind (around) the sprites in the scene will now work for my purposes.

Any help will be greatly appreciated.

Hello Everyone,

One of my apps is experiencing a strange flickering only on the iPad 2. It works perfectly on my iPad (with iOS 4.3) and other devices (iPhone 4, iPhone 3G).

I've posted a video clip of the issue here:
http://freecloud.com/dl/iPad2Flicker.MOV

I'm not doing anything particularly complicated here. I create a CCNode called mcTray and then I add 2 CCSprites (the parts in the parts tray) to mcTray. Then I adjust the X position of mcTray to scroll it left and right.

Is anyone else experiencing any strange behaviors in their apps when running on an iPad 2? Any ideas on what's causing this?

Thanks!

Dan

Hi, I have a layer with several CCMenuItemSprite, the layer background is 1024 × 1499 pixels because I move it up and down when you tap on some of the menu items. I move the layer like this:

CCEaseOut *moveLayer = [CCEaseOut actionWithAction:[CCMoveTo actionWithDuration:0.8 position:ccp(0, 730)] rate:3.0];

While the layer is moving the menu items flicker and also all the running animations too :(

Any help please?
Thanks

All of a sudden my 0.99.5b3 game has the dreaded black frame on startup. It didn't have it yesterday. Everything has been working great since adding autorotation handled by the RootViewController.

I haven't made any changes to the RVC, but I did add the UILaunchImageFile key to Info.plist along with some device-specific Default.png files. This was to get around a problem where iOS 3.x devices would startup in Landscape Left by default, and iOS 4.x devices would start up in Landscape Right. By adding "~iphone" device modifiers, I can make sure that the right Default file is getting loaded. I don't see how this could have caused the flicker to return...

Currently, I see the flicker on the iPhone 4 w/ 4.1, iPhone 3Gs w/ 4.1, iPod touch (2G) w/ 3.1, iPhone 3G w/ 3.1.3, and all iPhone simulators. It DOES NOT happen on the iPad either on the device or simulator (except in LandscapeRight which is a separate, known bug).

I don't want to clutter up the forum by posting my entire app delegate, but if it would help, I can provide the relevant code.

Any advice for debugging, where to look, or whatever would be awesome.

I have to imagine that something with the new Default.png files or the Info.plist is conflicting with the startup. For the record, I have Default.png, Default~iphone.png, Default@2x~iphone.png, and Default-Landscape~ipad.png. Yet when I remove all the new files and revert the Info.plist file, I still get the flicker (even after cleaning all targets).

Ugh.

Hello,

I have the following problem with my cocos2d Mac app:
In fullscreen mode (set by setFullScreen:true of CCDirectorMac) I have flickering black rectangles exactly the position "above" the Mac OS dock.
It seems to be the system are updating the dock "under" the full screen app and it causes the flicker.
The black rectangles are appearing for approx. one frame when I move the mouse cursor and it looks flickering when I move the cursor continuously.
cocos2d 1.0.1, Mac OSX 1.6.8.

Thanks in advance

Hi Folks,

I am getting a flicker (artifacts?) on the iPad 2 during a CCTransitionPageTurn. I apply the following code before transitions to fix it:
[[CCDirector sharedDirector] setDepthTest:YES];

Moreover, I change the depthTest var back to 'NO' after the transition's complete, which fixed some other flickering issues. This snippet fixes the transitions until I try to transition to a scene which has a scaled/positioned layer. Here is a video showing a clean transition with the depthTest var set to true, and another scene set up exactly the same but with a scaled/positioned layer:

http://www.youtube.com/watch?v=PM1bdnCakQ0

I do the zooming with the following code:

self.bgLayer.scale = 1.8;

If I change the scale property to 1.0, there is no flicker. This is similar for positioning the layer. If I position the layer too far away from it's origin (centered in middle of screen), it will result in a flicker. What is even more weird is that I can zoom it to like 1.1, no problem.

Here is an example with no flickering (not scaled/positioned):
http://www.youtube.com/watch?v=QiXLdGFT-4g

Has anyone been in this particular situation?

I just tested the autorotation functionality of my app and discovered that on rotating the screen (using UIViewController to rotate in landscape mode) there is a short black flicker. So it starts rotating, flickers and then rotates without no other issues.

I have a CCLayer with some CCNodes on it that have personalized -(void) draw functions.

Didn't find a workaround yet because the startup flicker (http://www.cocos2d-iphone.org/forum/topic/10398) only appears on the startup and cares about "Default.png" not the whole scene. Do you know what's wrong?

title says it all, I am experience a flicker at start up (between Default.png & first scene) when using 16-bit mode. This doesn't occur when set to 0. Anyone have a fix for this? This occurs on iPad (1st & 2nd gen) and iPhone devices.

I'm getting a black screen flicker between my default.png and my first scene. I'm using 1.0.0-beta and have gone into the app delegate (removeStartupFlicker) and uncommented the necessary code to fix it but without luck. This is happening on an iPad 2 device with the app in Landscape mode. I've also tried to add the Default.png to the first scene but the black flicker still occurs. I know this topic has been discussed previously but I wasn't able to find a viable solution from prior discussions. Any suggestions or ideas of what I might be doing wrong?

here's a link to my app delegate code (didn't wanna clutter the thread): http://pastie.org/1878387

I recently migrated my project to 0.99x from 0.8x. I use transitions between scenes such as:

[[CCDirector sharedDirector] replaceScene: [CCFlipYTransition transitionWithDuration:0.5f scene:gs orientation:kOrientationUpOver]];

These transitions didn't cause me any problems in 0.8x. Even using UIKit elements, they worked fine. Now, in 0.99x, my sprites flicker as the transition effect occurs. I have tried all four directors; all have the same problem.

//[CCDirector setDirectorType:kCCDirectorTypeDisplayLink];
	//[CCDirector setDirectorType:kCCDirectorTypeMainLoop];
	//[CCDirector setDirectorType:kCCDirectorTypeNSTimer];
	[CCDirector setDirectorType:kCCDirectorTypeThreadMainLoop];

Has anyone else come across this?

Thanks!

Hi,

I've seen some similar discussion, but not quite sure if this is the same issue. Anyways, I get black lines when I use pvr.ccz images. I've tried setting both 2d projection and depthtest without luck. Below is a screenshot. I need help. Thanks

[director setProjection: CCDirectorProjection2D];
	[director setDepthTest: NO];

this occurs in both the simulator and the device. I have a sprite that is moving, its position being updated base on the physics of the game. The side in the direction of movement appears faded/slightly squished. Is there anything I can do to eliminate this effect? There's also a shimmering effect on the device, where the black edges of the sprite appear to flicker against the mostly white background.

Hello fellow cocos2d'ers,

We are a 3 man team and we are very delighted to present to you our first app that just got approved,
Flick It.

We started this app during the December holidays and decided to start with something simple, a whack-a-mole game. Reasons include not having to deal with physics, in app purchases and stuff...

Instead of the standard tap the screen to whack, we introduced a simple flick gesture as something unique.

Link to app in appstore

Here are some PROMO CODES! Post down below if anyone needs more! (:
PRMFRRL4FYK7
EAY9WHA94N9P
67WFFEYWTMLE
X473AK4YH6R6
EMHPAL3TRMH4

Do comment some love/hate on our game or even feel free to ask questions like how feature XXX is implemented! (We're keen to help as much as we can!)

Hello,

Even if I set a simple CCMoveTo action:

[player runAction:[CCMoveTo actionWithDuration:4.0f position:ccp([WinSize width], player.position.y)]];

This "player" CCSprite is flickering and getting blurred.

I also tried accelerometer movement based, with High-Pass filter and I still get flickering and blurring.
Most surprising is that it I'm getting flicker and blurring by just using CCMoveTo.

Details of what I'm using:
- 2D projection.
- kCCTexture2DPixelFormat_RGBA8888 and kEAGLColorFormatRGBA8
- cocos2d v0.99.5-rc1
- The sprite is being added over a CCColorLayer
- Running on an iPad 3.2.2

I also tried doing

[player.texture setAntiAliasTexParameters];
[player.texture setAliasTexParameters];

and got the same results.

Any tips?

Thanks.

Hello,

I am very new to iphone development started 1.5 months ago.
I am getting the hang of normal iphone apps building gradually.
Then, I have a new project of developing games using coco2d engine.
My apps is suppose to be like normal iphone apps inside which small games developed using coco2d engine will be inserted.
( maybe by tab bar button click or some kind of user response that will direct to play the game )

So I am wondering , integration is possible ?
I am not very much experience in developing apps. As far as I see , the application delegate is modified for coco2d to be launched currently.

I just want to make sure whether it's feasible before I learn and research more to do my project.

1. Is the integration is possible?
2. Any advise and tip on it is available ?

I am quite new to this forum also . Sorry if this has been asked before.
coco2d engine rocks!

Thanks all.

Hello,

I've migrated a project from 0.82 to 0.99rc.

Im' using this code to prevent flickering with the default.png in 0.82 :

// prevent flicker
CCSprite *sprite = [[CCSprite spriteWithFile:@"Default.png"] retain];
sprite.anchorPoint = CGPointZero;
[[sprite texture] setAliasTexParameters];
[sprite draw];
[[[CCDirector sharedDirector] openGLView] swapBuffers];
[sprite release];

Everythig was ok in 0.82.

But in 0.99rc, it seems to display a screen capture of the first scene, and not the default.png.

any idea ?

Régis

The gap is back...

After hours(!!) of fighting these pesky little black lines in my CCTilemapAtlas in the last release of cocos2d (0.9 beta2) I upgraded to the latest release (0.99 rc) yesterday and my beloved friends are back. *bitesHisTongue*

I followed all the tips and tricks I could find:

// 2D Projection:
[[CCDirector sharedDirector] setProjection:CCDirectorProjection2D];

// Alias textures
[myTilemap.texture setAliasTexParameters];

// Disable subpixel rendering in ccConfig.h
#define CC_COCOSNODE_RENDER_SUBPIXEL 0
#define CC_SPRITESHEET_RENDER_SUBPIXEL 0

With these tricks the gaps were gone in 0.9b2 but now they are back. I noticed it's again the subpixel rendering problem, as the black lines appear only if I use a CCMoveTo action, where I can not control the placement while the tilemap moves - or is this possible?! To clarify, I can place the tilemap at integer value coordinates - everything is fine (no gaps), but when moving around with an action those gaps show up again.

The tip regarding the "spritesheet-artifact-fixer.py" did also not solve my problems. I got the same flicker but a ruined texture. IMHO it does not work. It just doubles border pixels which looks simply BAD if you have to use tiles that perfectly align by pixel.

I really do not want to go back to 0.9b2 because the performance increased by 5-10 FPS for my game with the new release, so if anyone has another tip / trick to solve this problem I would be really grateful!

Thanks in advance for any help,
Markus

Hi,
I use TMX Tilemaps to draw a scene with 7 diffrent layers to get a nice parallax effect, but whats not so nice : the are flickering lines between the tiles. How to avoid them?
I tried to disable Subpixel rendering, but that would make it even worse.

I am running into a weird scaling problem on the iPhone 4.

The 1st scene seems to be initializing at scale 1 and then quickly changing to scale 2.

Here are some screenshots:

Bad start:

Good after:

Any thoughts?

I'm using 0.9-beta2. I backported from 0.99 the macros mentioned in http://code.google.com/p/cocos2d-iphone/issues/detail?id=735. Here's what I have:

CCSprite *sprite = [CCSprite spriteWithFile:@"Default.png"];
sprite.anchorPoint = CGPointZero;
CC_ENABLE_DEFAULT_GL_STATES();
[sprite draw];
CC_DISABLE_DEFAULT_GL_STATES();
[[[CCDirector sharedDirector] openGLView] swapBuffers];
[[CCDirector sharedDirector] runWithScene:scene];

Unfortunately, the flicker between Default.png and the intro scene is pretty noticeable on both my devices (old iPhone, iPhone 3GS). The [self mainloop] hack in Director didn't work. Anyone have any ideas of other ways to solve this problem?

I have several fullscreen (480x320) sprites positioned exactly next to each other. When the game scrolls horizontally over these sprites I get a flickering black vertical line between the sprites. I searched around on the forum and found several threads about similar problems. But nothing I have tried has fixed the issue.
I use regular sprites and not atlas sprites. I have set 2D projection. I have tried to add 0.5f to the position.
I'm using Cocos2d 0.8.2.

Hello there,
I'm adding a TMXTiledMap like this:

TMXTiledMap *map = [TMXTiledMap tiledMapWithTMXFile:@"Level1.tmx"];

		for( TMXLayer* child in [map children] ) {
			[[child texture] setAntiAliasTexParameters];
		}

		voidNode = [ParallaxNode node];
		[voidNode addChild:map z:0 parallaxRatio:ccp(0.0f,1.0f) positionOffset:CGPointZero];
		id goUp = [MoveBy actionWithDuration:1 position:ccp(0,-150)];
		[voidNode runAction:goUp];
		[self addChild:voidNode];

Where "Level1.tmx" is a 480x1600 pixels tilemap made with Tiled (16x16 tiles). The spritesheet is a normal 256x256 png file (I've tried putting blocks with no margin and space, and also with different values of margin and space, so I've tried them both).

The problem: if I use the anti-aliasing code, I get tiny black lines flickering between tiles which are both horizontal and vertical. And if I don't use anti-aliasing, there'll be long horizontal lines flickering over the whole map which are of course because of being aliased.

p.s. the whole screen is filled with tiles so there are a lot of them, not like the demos with long distance between tiles.

Thanks for your time,
Parsa

Hi!

We've noticed some random glitches in our game. Sometimes, on some phones, a part of the screen flashes black. It seems as if it only happens for one frame, but since it's black it's noticeable. It usually comes from the right side of the screen (landscape mode), covering the full height (320px), and going for about 30-75% of the screen. There doesn't seem to be a regular pattern for this, but it seems it happens most often on a particular screen, which is nothing special except for a few things that I can notice:

- it's a layer with a full-screen background image inserted on top of an existing scene
- there are about 4-5 Labels on the layer, very rapidly changing (it's a tally screen)

Could it have anything to do with those fast-changing labels? I know we're supposed to use AtlasLabels, but this has worked for us so far.

It's a very strange glitch and I really can't find anything that could be causing it (we don't even have any big black images loaded).

I'm using iPhone SDK 3.0 on Snow Leopard, but the app is built for 2.2. We and our publiher have been testing it on a variety of devices, from 2.0 to 3.1, 2g to 3gs and iPod Touches, jailbroken and non-jailbroken ones. It seems it doesn't happen on every device, but we can't find any relationship between the OS version or the device model and the glitch.

It feels like shooting in the dark here, but I was hoping someone could be able to help...

Thanks,
Ivan Galic
NightIrion
http://www.nightirion.com

In my game my first scene is an exact copy of the Default.png (with the addition of a loading animation). For some while it has annoyed me that there is a perceptible flash on the transition between the two. After some debugging it seems to me that the problem comes from the Director only scheduling its mainloop and then returning from runWithScene. By the time mainloop actually runs the window has refreshed with the empty back buffer(?). At least, I know that on leaving the application delegate the Default.png is still displayed, but when the mainloop is entered for the first time the screen is blank.

So as an experiment I added a call to mainloop at the end of startAnimation. Sure enough the scene gets visited before returning and the black frame is no more.

My question is: is this safe? Everything seems to run fine and I don't see any initialization happening after the inserted call, but I haven't spent a long time looking through Director so it leaves me a little uneasy.

For reference, I am not using FastDirector and I am attaching to a UIWindow, not a UIView.

Comments?