I'm getting an error using this class with cocos2D version 99.5 beta.

"target" not declared

in the CCMoveTo+RoundedUpdate.m.

Edit:
Just change it to
target_
Seemed to fix it.

Awesome - this just fixed an issue that I had! I'd taken the example TileMap application from http://www.raywenderlich.com and applied a CCMoveTo to both my player and the viewport to smooth things out. That worked fine, but then I got the tearing problem, which this promptly removed! Thanks again!

I was having the same problem with flickering black lines appearing between my tiles on my TMX map when I moved the map layer around.

I found two different ways to solve it:

• Changing my spritesheet png to use a margin and spacing of 2 and then running the spritesheet-artifact-fixer.py on it.
• Using my original spritesheet and your code above. I like using the original spritesheet because I can fit more tiles on it with no spacing or margins.

Can someone comment on the preferred method? spritesheet-artifact-fixer.py or rounding? Are we losing anything important by rounding?

Just wanted to give a big thanks to you.
Ever since I've been testing on the device, I couldn't fix the lines no matter what trick I tired.
But when I tried your trick it worked like a charm.
Cheers.
Although if you try change the vertex value, the lines will be back.

thanks It works!!!

@psi thanks I was having the same problem but with CCMoveBy.

I decided to use a category to work-around this issue. Create a class called "CCMoveTo+RoundedUpdate" and add this code:

CCMoveTo+RoundedUpdate.h

//
//  CCMoveTo+RoundedUpdate.h
//
//	Category to rounded move any object and avoid gaps in tilemap.
//  --> Overrides "update" code from CCIntervalAction.m
//
//  Created by Markus Barta on 09.02.10.
//
#import <Foundation/Foundation.h>
#import "cocos2d.h"
@interface CCMoveTo (RoundedUpdate)
@end

CCMoveTo+RoundedUpdate.m

//
//  CCMoveTo+RoundedUpdate.m
//
//  Created by Markus Barta on 09.02.10.
//
#import "CCMoveTo+RoundedUpdate.h"

@implementation CCMoveTo (RoundedUpdate)
-(void) update: (ccTime) t
{
	//NSLog(@"Using category CCMoveTo+RoundedUpdate for movement -> rounded setPosition!");
	[target setPosition: ccp( round(startPosition.x + delta.x * t ), round(startPosition.y + delta.y * t ) )]; //Setting to a rounded pos avoids gaps in tilemap!
}
@end

Just add those two files to your project and compile. The gaps should be gone :)

Hope this helps!

Best,
Markus

I also have this problem with my map.
Only when scrolling along the x axis the lines appear.
I tried all the tips and nothing works.
When moving up and down, it's fine.

I tried adding in the tip/hack above in CCIntervalAction, but I got an error saying "shortens value from 64 bit to 32 bit"

Any suggestions?

You can create your own action, like MoveRounded, so you don't need to modify the cocos2d sources.

After trying a lot of different things in the last 10+ hours I have not been able to reproduce the problem in another project yet. It seems to have to do with my setup of the scene, as a simple Tilemap added to a scene, using the same tilemap GFX does not produce flicker at all - no matter what I set the projection, alias, subpixel settings to, I mentioned above.

The setup of the nodes in my real project is not quite trivial (lots of parent/child nodes...), so I will have to continue to build up the same structures in my test-app (called "mindTheGap" ;) until the gaps show up again.

In the meantime I came up with a little hack that "solves" my problem: In CCIntervalAction.m in line 535 I round the x and y position - and *boom* gaps/artifacts/lines are gone:

-(void) update: (ccTime) t
{
	[target setPosition: ccp( round(startPosition.x + delta.x * t ), round(startPosition.y + delta.y * t ) )]; //HACK: set to rounded pos to avoid gaps in tilemaps when scrolling around
}

The only thing is, I'm not quite comfortable with messing around in the cocos2d code. It gets frequently updated, so I will always have to change this when updating. I'm also not sure if this change might have other negative side-effects in the future - well, we'll see.

What do you think?

Best,
Markus

Will do so today. Hope to create a test project that shows the issue properly.

Could you open a bug attaching the code to reproduce the problem ?
The tests/TileMapTest.m seems to work OK without artifacts.

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