http://www.cocos2d-iphone.org/forum/tags/tilemap A fast, easy to use, free, and community supported 2D game engine en-US Sat, 31 Jul 2010 07:55:58 +0000 http://bbpress.org/?v=1.0.2 q http://www.cocos2d-iphone.org/forum/search.php http://www.cocos2d-iphone.org/forum/topic/8267/page/2#post-48475 Fri, 30 Jul 2010 21:21:44 +0000 CJ 48475@http://www.cocos2d-iphone.org/forum/ <p>@<a href='http://www.cocos2d-iphone.org/forum/profile/26'>Metric</a> I see your point. I started doing some testing based on Apple's GLSprite example here<br /> <a href="https://developer.apple.com/iphone/library/samplecode/GLSprite/Introduction/Intro.html" rel="nofollow">https://developer.apple.com/iphone/library/samplecode/GLSprite/Introduction/Intro.html</a></p> <p>I'm building up from that using the same texture and projection settings that cocos2d uses and manually adding support for texture atlas one step at a time until I can reproduce the issue. If I cannot reproduce the issue then it must be something else in cocos2d that is introducing the problem.</p> <p>Stay tuned... </p> http://www.cocos2d-iphone.org/forum/topic/8267/page/2#post-48462 Fri, 30 Jul 2010 19:43:33 +0000 Metric 48462@http://www.cocos2d-iphone.org/forum/ <p>@CJ: Yes, the texture can wrap, but it still doesn't make sense to put it at the center of a pixel. It shouldn't have artifacts when mapping from 0 to 1 in direct relation to the pixels. </p> <p>Basically, there is something else going on in the cocos2d engine dealing with creating the textures for the sprites / compressing / uncompressing. It could even be the hardware of the iphone interfering with compression / uncompression. However, I have a feeling it is more to do with the actual compression / uncompression / converting algorithms in cocos2D.</p> <p>What I am saying is, you are applying a fix, but not to the real issue behind the problem. Your fix is more of a bandage then a direct stitching of the real problem.</p> <p>You also should not have artifacts in the textures in the 3D Projection if the texture is being created properly / uncompressed. </p> <p>I have yet to experience this artifact issue / flickering in the Java version I am working on, on my desktop or laptop. It is still using the direct 0,0 to 1,1 mapping. Of course, I am using the built in bufferedImage object in Java when converting to ARGB, RGB, RGBA, RBG, etc. Also, I am using pngs to test with. </p> http://www.cocos2d-iphone.org/forum/topic/8267/page/2#post-48461 Fri, 30 Jul 2010 19:41:52 +0000 marcotronic 48461@http://www.cocos2d-iphone.org/forum/ <p>Thanks a lot, CJ. You are right. In my test project it actually works but in my "real" project this has no effect... I have to check the differences... (As it didn´t work in my real project I didn´t set it in my test project because I thought it just wouldn´t work...)</p> <p>Marco </p> http://www.cocos2d-iphone.org/forum/topic/8267/page/2#post-48457 Fri, 30 Jul 2010 19:17:23 +0000 CJ 48457@http://www.cocos2d-iphone.org/forum/ <p>@<a href='http://www.cocos2d-iphone.org/forum/profile/388'>marcotronic</a> I tested your project and it does show the artifact you describe. But upon setting the projection matrix to 2D (<a href="http://www.cocos2d-iphone.org/forum/topic/5760">as Steve Oldmeadow pointed out in that other post</a>) it solves the issue.</p> <p>So, just add this after you get a reference to the shared director in your app delegate:<br /> <pre><code>[director setProjection:CCDirectorProjection2D];</code></pre> http://www.cocos2d-iphone.org/forum/topic/8267/page/2#post-48451 Fri, 30 Jul 2010 18:53:23 +0000 marcotronic 48451@http://www.cocos2d-iphone.org/forum/ <p>@CJ: I´ve seen your posting after posting my example... Thanks a ton in advance for looking at it! That 2DProjector stuff didn´t help... In my little test project posted above I don´t use it.</p> <p>Marco </p> http://www.cocos2d-iphone.org/forum/topic/8267/page/2#post-48450 Fri, 30 Jul 2010 18:51:43 +0000 marcotronic 48450@http://www.cocos2d-iphone.org/forum/ <p>Hi,<br /> I´ve isolated the issue in a small project:</p> <p>The artifacts show like in my examples above:</p> <p><a href="http://www.marcotronic.com/forums/ArtifactTest.zip" rel="nofollow">http://www.marcotronic.com/forums/ArtifactTest.zip</a></p> <p>Any ideas? </p> <p>Thanks a lot...</p> <p>Marco</p> <p>PS: I know the framerate is very low (due to the sprite as background image) but in my "real" project I use that trick with placing an empty sprite first and adding a child with the actual backgorund image with speeds up the FPS again... But the issue shows either way... </p> http://www.cocos2d-iphone.org/forum/topic/8267/page/2#post-48449 Fri, 30 Jul 2010 18:48:01 +0000 CJ 48449@http://www.cocos2d-iphone.org/forum/ <p>@<a href='http://www.cocos2d-iphone.org/forum/profile/388'>marcotronic</a> The issue you describe sounds similar to this post:<br /> <a href="http://www.cocos2d-iphone.org/forum/topic/5760" rel="nofollow">http://www.cocos2d-iphone.org/forum/topic/5760</a><br /> But he said that setting a 2D projection fixed the issue. Can you upload a simple project that just replicates the issue? I'll take a look at it to try to fix it. </p> http://www.cocos2d-iphone.org/forum/topic/8267/page/2#post-48442 Fri, 30 Jul 2010 18:02:18 +0000 marcotronic 48442@http://www.cocos2d-iphone.org/forum/ <p>Hi,<br /> I don´t know if my problem is the same issue but even after updating to the latest development branch from git I´m still getting strange artifacts when using sprites. I want to display them crisp and clean, so I set the AliasTexture param for them:</p> <pre><code>[sprite.texture setAliasTexParameters];</code></pre> <p>I also changed that subpixel stuff (set it to 0) in ccConfig.h (for node and spritebatchnode). I tried </p> <pre><code>[CCDirector setDirectorType:CCDirectorProjection2D]</code></pre> <p>It all didn´t help. This is how my sprites look (normal and with artifacts, 2 x magnified to see the issue better)</p> <p><img src="http://www.marcotronic.com/forums/artifacts.png" alt="" /></p> <p>I also tried different positions on screen, different sizes. No matter what I do - nothing helps... I´m getting nuts...</p> <p>Thanks for any help!<br /> Marco</p> <p>PS: EDIT: Same issue with 0.99.5 beta - just tested some seconds ago... It really looks as if the sprites are resized a bit or something like that...</p> <p>PPS: Don´t know if it matters - it´s an iPad only project. So the issue displays on an iPad. </p> http://www.cocos2d-iphone.org/forum/topic/8267/page/2#post-48424 Fri, 30 Jul 2010 16:06:27 +0000 hm50 48424@http://www.cocos2d-iphone.org/forum/ <p>Thank you both! I will do! </p> http://www.cocos2d-iphone.org/forum/topic/8267/page/2#post-48415 Fri, 30 Jul 2010 14:20:37 +0000 riq 48415@http://www.cocos2d-iphone.org/forum/ <p>@<a href='http://www.cocos2d-iphone.org/forum/profile/1132'>hm50</a>: try downloading the latest "develop" branch:<br /> <pre><code>$ git clone git://github.com/cocos2d/cocos2d-iphone.git develop</code></pre> http://www.cocos2d-iphone.org/forum/topic/8267/page/2#post-48388 Fri, 30 Jul 2010 05:44:58 +0000 araker 48388@http://www.cocos2d-iphone.org/forum/ <p>@<a href='http://www.cocos2d-iphone.org/forum/profile/1132'>hm50</a>, CJ patched the development branch, that property doesn't exist yet in cocos 0.99.4. I assume it's support for rotated sprites in the new zwoptex version. So remove everything from the if (_rectRotated) { } and it will work brilliantly. </p> http://www.cocos2d-iphone.org/forum/topic/8267/page/2#post-48386 Fri, 30 Jul 2010 04:46:02 +0000 hm50 48386@http://www.cocos2d-iphone.org/forum/ <p>Using the patch provided by @CJ I get the following build error: 'rectRotated_' undeclared (in CCSprite.m).</p> <p>What other update would I be missing?</p> <p>Thanks! I can't wait to try this on my 'black line' issue!!</p> <p>Harv </p> http://www.cocos2d-iphone.org/forum/topic/8267/page/2#post-48383 Fri, 30 Jul 2010 02:54:07 +0000 CJ 48383@http://www.cocos2d-iphone.org/forum/ <p>@<a href='http://www.cocos2d-iphone.org/forum/profile/26'>Metric</a><br /> What you describe for mapping a rect of pixels texture coordinates in the range [0,1] is what we all assumed before. It does make logical sense that a rect of pixels (0,0,512,512) maps with tex coords (0,0),(1,1).</p> <p>But, in practice, that naive implementation doesn't work so well. The formulas I provided above simply change the sample point from the corner of a pixel (at the intersection of 4 pixels) to the center (where there is only one color available).</p> <p>Regarding your understanding of valid values for the u,v range... You are not required to keep them in the range [0,1]. Depending on the texture wrap setting, the texture may clamp or repeat. There is no need to manually clamp the values in your program code.<br /> Read: <a href="http://www.opengl.org/wiki/Texture#Edge_value_sampling" rel="nofollow">http://www.opengl.org/wiki/Texture#Edge_value_sampling</a> </p> http://www.cocos2d-iphone.org/forum/topic/8267/page/2#post-48359 Thu, 29 Jul 2010 21:39:02 +0000 Metric 48359@http://www.cocos2d-iphone.org/forum/ <p>Actually, in theory those formulas should not work at all that you presented.</p> <p>Texture mapping is essentially the image size ranging from 0,0 to 1,1 in 3D. You shouldn't have to times by 2 the rect position or size, or the atlas image size either.</p> <p>If you keep them all pixel based to begin with then there only needs to be one conversion to the range of 0 to 1.</p> <p>the rect x,y,width,height are all in pixels, and the atlasWidth and height are also in pixels</p> <p>If they are all pixel based and the maximum size is atlasWidth and atlasHeight then technically just dividing by atlasWidth and atlasHeight will results in a value of 0 to 1. However, it will only be 0 to 1 if the left side of the equation is &lt;= atlasWidth or atlasHeight and &gt;= 0.</p> <p>If we have an atlas of 512x512 and a rect of x=20,y=20,width=512,height=512. Then we have a problem, because the rect + either the x / y will cause the amount to be greater than atlasWidth or atlasHeight. Thus, you will get a value larger than 1. However if we have rect of x=0,y=0,width=512,height=512 then everything is fine a dandy because everything will stay within the range of the maximum atlasHeight and atlasWidth. Therefore everything will be 0 to 1.</p> <pre><code>float right = (rect.x + rect.width) / atlasWidth; // problem: if rect.x+rect.width &gt; atlasWidth then the result will be a value larger than 1 which is no go! The value for texels must be between 0 and 1! float left = rect.x / atlasWidth; //problem: if rect.x &gt; atlasWidth then the result will be a value larger than 1 which is a no go! The value for texels must be between 0 and 1! float top = rect.y / atlasHeight; // same problem as above float bottom = (rect.y + rect.height) / atlasHeight; // same problem as above //Another problem is the fact if someone gives a negative value for rect.x, rect.y or rect.width, rect.height. This is a no go either because it is less than 0! //Solution clamp the values to range from 0 to 1 top = clamp(top); left = clamp(left); right = clamp(right); bottom = clamp(bottom); /** * Simple Clamp function for 0 to 1 * @return float */ float clamp(float value) { if(value &gt; 1) { return 1.0f; } else if(value &lt; 0) { return 0.0f; } else { return value; } }</code></pre> http://www.cocos2d-iphone.org/forum/topic/8267/page/2#post-48354 Thu, 29 Jul 2010 20:59:34 +0000 hactar 48354@http://www.cocos2d-iphone.org/forum/ <p>Well a reduction from 4 to 1 pixel padding is still great! thanks cj for finding this holy Grail! Maybe @cj could have a look at issue 737, I wouldn't be surprised if they are linked...</p> <p>Anyway, well done! </p> http://www.cocos2d-iphone.org/forum/topic/8267#post-48344 Thu, 29 Jul 2010 19:53:50 +0000 abitofcode 48344@http://www.cocos2d-iphone.org/forum/ <p>@<a href='http://www.cocos2d-iphone.org/forum/profile/3916'>liquidfire</a> That'll be 'Angry jumping doodle zombie turbo birds'</p> <p>@CJ I think you've earned this, the fabled platinum sausage!</p> <p><img src="http://a.yfrog.com/img827/6929/us1.jpg" /> </p> http://www.cocos2d-iphone.org/forum/topic/8267#post-48336 Thu, 29 Jul 2010 19:25:41 +0000 CJ 48336@http://www.cocos2d-iphone.org/forum/ <p>hehehe, thanks guys :)</p> <p>@<a href='http://www.cocos2d-iphone.org/forum/profile/1222'>abitofcode</a><br /> Re <a href="http://www.cocos2d-iphone.org/forum/topic/762">Box2d vs Chipmunk</a>: They're both good. Choose the one that makes sense to you. Perhaps one has the joint types you need, or other features. :) </p> http://www.cocos2d-iphone.org/forum/topic/8267#post-48335 Thu, 29 Jul 2010 19:23:19 +0000 liquidfire 48335@http://www.cocos2d-iphone.org/forum/ <blockquote><p> @CJ while you're on a roll maybe you could provide the answer to the other great cocos2d forum question... Which is better chipmunk or box2d? ;)</p></blockquote> <p>Oooooh I want a shot at this:</p> <p>@CJ - What is a great app idea that will make me the most money? ;) </p> <p>Oooh if only it was that easy. </p> http://www.cocos2d-iphone.org/forum/topic/8267#post-48334 Thu, 29 Jul 2010 19:14:10 +0000 abitofcode 48334@http://www.cocos2d-iphone.org/forum/ <p>Oh yes!</p> <p>@CJ while you're on a roll maybe you could provide the answer to the other great cocos2d forum question... Which is better chipmunk or box2d? ;) </p> http://www.cocos2d-iphone.org/forum/topic/8267#post-48332 Thu, 29 Jul 2010 19:00:15 +0000 riq 48332@http://www.cocos2d-iphone.org/forum/ <p>I'm about to release v0.99.5-beta... are you OK if we called this version "no-more-artifacts-thanks-to-CJ" ?</p> <p>Updated:</p> <p>or: "CJ-the-artifac-fixer"</p> <p>or: "CJ-vs-the-artifacs"</p> <p>or... ? </p> http://www.cocos2d-iphone.org/forum/topic/8267#post-48330 Thu, 29 Jul 2010 18:46:43 +0000 abitofcode 48330@http://www.cocos2d-iphone.org/forum/ <p>cocos2d god of the week award goes to......</p> <p>CJ</p> <p>:D</p> <p>Nice find! </p> http://www.cocos2d-iphone.org/forum/topic/8267#post-48321 Thu, 29 Jul 2010 17:59:02 +0000 riq 48321@http://www.cocos2d-iphone.org/forum/ <p>@<a href='http://www.cocos2d-iphone.org/forum/profile/1750'>hactar</a>: Well, it doesn't fix that problem but it is really mitigated. "exact" and "1 pixel" are almost identical. </p> http://www.cocos2d-iphone.org/forum/topic/8267#post-48308 Thu, 29 Jul 2010 16:35:17 +0000 hactar 48308@http://www.cocos2d-iphone.org/forum/ <p>@riq, could you run it with the mipmaping problem (issue 737)? I'd be interested if this fixes the problem here too. I could save soo much texture space. </p> http://www.cocos2d-iphone.org/forum/topic/8267#post-48305 Thu, 29 Jul 2010 16:18:20 +0000 riq 48305@http://www.cocos2d-iphone.org/forum/ <p>following @CJ's idea, I've patched <code>CCTileMapAtlas</code>, <code>CCLabelAtlas</code> and <code>CCQuadParticleSystem</code><br /> <a href="http://github.com/cocos2d/cocos2d-iphone/commit/9e3132d8379b13db3c9a3943f0b8908a7e2bb509" rel="nofollow">http://github.com/cocos2d/cocos2d-iphone/commit/9e3132d8379b13db3c9a3943f0b8908a7e2bb509</a></p> <p>I've done some tests and there is no flicker when a <code>CCTileMapAtlas</code> is rendered using anti-alias, is moved and scaled at the same time. Nice! </p> http://www.cocos2d-iphone.org/forum/topic/8267#post-48280 Thu, 29 Jul 2010 13:28:23 +0000 riq 48280@http://www.cocos2d-iphone.org/forum/ <p>yes, cocos2d should be responsible for doing this. Zwoptex and any other tools (Hiero font editor, etc) should use pixel coordinates, and cocos2d should convert them to texture coordinates. </p> http://www.cocos2d-iphone.org/forum/topic/8267#post-48250 Thu, 29 Jul 2010 05:51:41 +0000 Robert Payne 48250@http://www.cocos2d-iphone.org/forum/ <p>@CJ Sounds good. It also saves texture memory by not requiring the user to add additional padding just to get around this issue. </p> http://www.cocos2d-iphone.org/forum/topic/8267#post-48247 Thu, 29 Jul 2010 05:07:51 +0000 CJ 48247@http://www.cocos2d-iphone.org/forum/ <p>@<a href='http://www.cocos2d-iphone.org/forum/profile/4542'>Robert</a>, I think zwoptex can safely continue using pixel coordinates as it makes the most sense and makes hand editing plists easier.</p> <p>I think it's best left to the rendering implementation (cocos2d) to translate the desired texture rect into texture coordinates. </p> http://www.cocos2d-iphone.org/forum/topic/8267#post-48242 Thu, 29 Jul 2010 04:38:57 +0000 Robert Payne 48242@http://www.cocos2d-iphone.org/forum/ <p>@CJ, @Riq</p> <p>I intended to eventually patch this into Zwoptex but perhaps it is better handled by the Cocos2d engine.</p> <p>IS there anything specifically Zwoptex should do to further support this? I'm still not just quite ready to do the full research and implementation on it but want to be made away of any fixes.</p> <p>-Robert </p> http://www.cocos2d-iphone.org/forum/topic/8267#post-48241 Thu, 29 Jul 2010 04:23:13 +0000 CJ 48241@http://www.cocos2d-iphone.org/forum/ <p>@<a href='http://www.cocos2d-iphone.org/forum/profile/22'>Codemattic</a> Oops, you are right. Good catch. I've updated the main post with the correct numbers.</p> <p>@everyone Happy to help. I must say that I highly recommend reading the book on oreilly:<br /> <a href="http://iphone-3d-programming.labs.oreilly.com" rel="nofollow">http://iphone-3d-programming.labs.oreilly.com</a> I would never have realized this without the diagram and explanation of texel space from that book. </p> http://www.cocos2d-iphone.org/forum/topic/8267#post-48218 Thu, 29 Jul 2010 01:07:29 +0000 Codemattic 48218@http://www.cocos2d-iphone.org/forum/ <p>CJ, Im trying to understand this example:</p> <blockquote><p> For example an atlas of size 256x256 that contains a sprite image at 10,10 with size 100x100 the correct texture coordinates for each vertex are as follows:<br /> <pre><code>21/256, 21/256 21/256, 219/256 219/256, 219/256 219/256, 21/256</code></pre> </blockquote> <p>should those 256s be 512s?</p> <p>Anyway - fantastic code CJ, thanks so much! </p>