About gaps between the sprites « cocos2d for iPhone

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

About gaps between the sprites

(24 posts) (8 voices)

Started 2 years ago by rolando
Latest reply from aramk

Tags:

rolando
Moderator

I'm positive this has been asked before (I did a search on the old group), but there was a reference on a post to riq where it was supposed to be fixed in a new version... But I'm still having the same problem.
[UPDATE]: I'm using cocos2d from svn trunk

When using TileMapAtlas, I get a small gap between the tiles. My tilesheet is a png 1024x1024 and the tiles with problems are not tiles in the border of the tilesheet, actually, those look just fine...

The gap seems to vanish if the sprites approach the middle of the screen... Any idea on how to fix this?

PS: here are some screenshots on the issue:

Thanks!
Rolando./

Posted 2 years ago #
riq
Key Master
if you set a 2d projection, does it work ?
```
[[Director sharedDirector] set2Dprojection];
```
also are you scaling the TileMap ?
Posted 2 years ago #
rolando
Moderator

yes it does!

I'm not scaling the TileMap, actually I'm using ShinyCocos's TiledMap, which is basically the same as TileMap, but using the Tiled (tmx) data format...

thanks!
rolando./

Posted 2 years ago #
patrickC
Member

Could somebody try and help me understand what I'm doing wrong here.
I have a tilemap, not scaled, using 2d projection, during camera movement I get horizontal line glitches (seems like a refresh problem).
It seems that it only happens on tiles that have neighbouring vertical lines of different colours (a group of grass like tiles is ok, but if below them I have a concrete tile, I get these horizontal glitches flickering).
I'm going insane here I've tried everything I can think of (different types of png and pvr, 2d and 3d projection, blending, depth values, etc...)
Please help me!
Thanks
Patrick

Posted 2 years ago #
rolando
Moderator

patrick: what version of cocos2d are you using?

Posted 2 years ago #
patrickC
Member

0.7.2

Posted 2 years ago #
rolando
Moderator

> patrickc says:
> 0.7.2
>
upgrade to the latest-stable (0.7.3) and let us know how it goes.

cheers,
--
Rolando Abarca M.

Posted 2 years ago #
patrickC
Member

Upgraded to 0.7.3 and made some tests, reported in next post :)

Posted 2 years ago #
patrickC
Member

Ok so after some experimenting I've made the following observation:
Moving the camera (using setCenter and setEye, also changing the Z value of the Eye) seems to make the flickering horizontal lines appear, but only in Landscape mode.
If I don't use Landscape mode the flickering mostly disappears, and is only visible (as grey lines, not white) when the camera is moving very fast.
If I don't change the Z value in setEye there is no flickering.
This is the code I'm using to move the camera:
[self.camera setCenterX:i centerY:i centerZ:0];
[self.camera setEyeX:i eyeY:i eyeZ:416+i];
(called every frame, with i incrementing by 1).
So I'm thinking I'm doing something wrong with moving the camera this way?
I need to change the Z value as I sometimes needs to zoom out, depending on how fast the player is moving.
All these tests were done on a blank project with 0.7.3, one layer and one tilemap and nothing else.
I tried enabling 2d projection but, once again, the camera movement seems to break that.
Anyone have any ideas?
Thanks as always!
Patrick

EDIT: It seems to be the Z value. A value of 416 seems fine, and so is 624 (416*1.5), but other inbetween values break the tilemap, is there a way of calculating correct Z values?

Posted 2 years ago #
riq
Key Master

yes, the camera might break things.
Probably you are using 3d projection.

The "trick" is to use a 2d projection.

Posted 2 years ago #
patrickC
Member

But what if I need to move the camera and change the Z value?
Is there a way to use 2d projection *and* use the camera in that manner?
If I use 3d projection and keep a valid fixed Z value then everything is fine.

Posted 2 years ago #
riq
Key Master
Are you using the orbitCameraAction ?
If you are using the camera to move in 2d (left,right,up,down) with a different z-values, then you can achieve the same behavior using:
- position: (left, right,up, down)
- scale: z-valuez
scale is the same as the z-value in the camera.
Posted 2 years ago #
mserougi
Member

I am having the same problem, only I don't see what I am doing wrong, bug with Cocos2D?

I am using 0.8.2 and when zooming in/out a TMX tilemap, I can see gaps/lines between any two tiles. I am using [[Director sharedDirector] setProjection:CCDirectorProjection2D]; since the other function is deprecated.

Posted 2 years ago #

riq
Key Master

another trick would be to do this:

in your layer add:

-(void) draw
{
   glTranslatef(0.5f,0.5f,0);
   [super draw];
   glTranslatef(-0.5f,-0.5f,0);
}

Posted 2 years ago #

mserougi
Member

Still the same problem.

I forgot to mention that doing [layer runAction:[ScaleTo actionWithDuration:1 scale:0.5]]; on the layer is when I see the problem, that is how I am doing some sort of zooming.

Posted 2 years ago #
GameBit
Member

uh, all over again...
cocos2d 0.9.3 My game looks great on iphone, but on iPad tiles not tiling (aka black lines) tried glTranslatef trick, tried _RENDER_SUBPIXEL, even my sprites is power of 2 and still got gaps ;(

anyone got reliable solution or advice on this?

Posted 1 year ago #
adityav89
Member

I too get the same flicker, im using cocos2d 0.99.5-rc1. I also put the sprites to a separate CCSpriteBatchNode and still see the flicker.I tried
1.RENDER_IN_SUBPIXEL
2.-(void)draw; //override

still see the gaps

anyone with a solution?

Posted 11 months ago #
riq
Key Master

Are you using a 2D projection ?

Posted 11 months ago #

adityav89
Member

Yes I am using 2D projection.

I have resolved the issue by:

incrementing the position of the camera with a rounded value

// In my Layer

[self runAction:[CCFollow actionWithTarget:followThis]];	

followThis.position = ccp(round(camposx), round(camposy));		//round to remove subpixel glitch

Thanks

Posted 11 months ago #

adityav89
Member

the round function has resolved the flicker issue but my player movement and camera are causing a frame delay of sorts(due to the round function). I hope they resolve this subpixel issue soon.

Posted 11 months ago #
araker
Moderator

@adityav89, you could try to round the position inside the CCFollow instead. This is a known problem for a long time and it depends on your implementation which method works best to solve it. Therefore cocos doesn't implement any of the fixes internally, since this could also lead to unexpected behavior (like rounding the positions of all objects).

Posted 11 months ago #

adityav89
Member

Wow, thanks a lot it actually works fine now!!!

This was what I did to the step function in CCFollow:

-(void) step:(ccTime) dt
{
#define CLAMP(x,y,z) MIN(MAX(x,y),z)

	if(boundarySet)
	{
		// whole map fits inside a single screen, no need to modify the position - unless map boundaries are increased
		if(boundaryFullyCovered)
			return;

		CGPoint tempPos = ccpSub( halfScreenSize, followedNode_.position);
		[target_ setPosition:ccp(CLAMP(tempPos.x,leftBoundary,rightBoundary), CLAMP(tempPos.y,bottomBoundary,topBoundary))];
	}
	else
	{
#define HACK_ROUND_CGPOINT(a) ccp(round(a.x),round(a.y))	// HACK insetred here!!! - works lol

		[target_ setPosition:ccpSub( HACK_ROUND_CGPOINT(halfScreenSize), HACK_ROUND_CGPOINT(followedNode_.position) )];
	}
#undef CLAMP
}

Posted 11 months ago #

aramk
Member

I know this is old, but the problem still keeps coming up. Thanks to the help on this forum, I think I've figured out a nice way of dealing with this:

http://ak.net84.net/iphone/gap-between-sprites-when-moving-in-cocos2d/

Posted 1 month ago #
aramk
Member

Hmm... I still get issues ONLY if I use [CCSprite spriteWithSpriteFrameName:]. However, using [CCSprite spriteWithFile:] and setting [[CCDirector sharedDirector] setProjection:CCDirectorProjection2D]; and using power of 2 dimensions. What I found was happening is that the edges of the sprite are bleeding out of their dimensions in the SpriteSheet. I put blue around the defined sprite in said spritesheet and as you can guess, the flickering gap turned blue... If I use my buffer (effectively rounds the pixels) then it works fine. Any suggestions? Also, I'm scaling my layer but it doesn't matter either way, the gap still appears.

Posted 1 month ago #

RSS feed for this topic

Reply

You must log in to post.