Trouble working with Effects on Sprite

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

Trouble working with Effects on Sprite

(13 posts) (6 voices)

Started 2 years ago by Wheeljack
Latest reply from araker

Tags:

No tags yet.

Wheeljack
Member

Hello!

I just started with Cocos2d, so bear with me.

I looked at this page:
http://www.cocos2d-iphone.org/wiki/doku.php/prog_guide:effects

Seemed straight forward.

So I put an image into my project, added the sprite to the spritemanager. Added it as a child so it shows on screen, that works great.

Then I do this, upon clicking that sprite as per the page, except I replace sprite 1 with the sprite I'm clicking on:
// execute a Waves action on sprite 1
id waves = [Waves actionWithWaves:5 amplitude:20 horizontal:YES vertical:NO grid:ccg(15,10) duration:5];
[sprite1 runAction: [RepeatForever actionWithAction: waves]];

I see the waves, but a few funny undesirable things happen:
-The whole background image does the wave
-No other image, other than the image I clicked and the background image, does the wave

I can't really imagine how to go about debugging this.

If you have any debugging tips for when dealing with effects, let me know. It's like the Wave effect purposely ignores everything else in the spritemanager, but then goes and hits other spritemanagers or the background itself too?

Also, bizarre, after I'm done with the above anomoly... , if I click on other images, the previous image I clicked on which has stopped doing the wave by now as I'm not "Repeating Forever", vanishes. hmm, nowhere in my code does it vanish.

So, something's totally off with my textures.

Are there any example projects with this effect going off?

Posted 2 years ago #
Mitch Lindgren
Member

Correct me if I'm wrong, but I believe that due to the way effects are currently implemented, any nodes with a z-order lower than the one you're calling the effect on will be modified by the effect as well. Changing this would require some heavy-duty modification to the effects code, I think. I believe a change is planned down the road but I don't know when.

Posted 2 years ago #
Wheeljack
Member

hmm, that's interesting

Something like that is definitely happening.

That makes it really difficult to use these effects to enhance a game. When I think of an effect, I picture something that affects a singular object.

If an effect modifies the whole screen, or everything under 1 object, all games would have to have black/empty backgrounds then and constantly play with Z-Ordering.

So, basically I'm not sure how to augment/improve my game using these effects. Perhaps the original implementation when it was put in the python version of Cocos2d was more to appease a transition effect and the crowd that likes to build GUIs which are screen transition-effect heavy?

Posted 2 years ago #
bradparks
Member

I don't know if this is a possibility, but in the docs for AtlasSprite:

http://www.cocos2d-iphone.org/api-ref/0.8.1/interface_atlas_sprite.html

it says:

"GridBase actions are not supported (eg: Lens, Ripple, Twirl)"

so maybe you can't do that with an AtlasSprite yet? Total guess though!

Posted 2 years ago #
Wheeljack
Member

good find, now i know why it didn't work in AtlasSprites

I used regular Sprite, and still ended up in the same situation that lindgrenM described. Just curious if that's an official statement? That it ALWAYS affects layers underneath?

Posted 2 years ago #
Mitch Lindgren
Member

Hm. I'm not so sure any more. This is the issue I was thinking of:

http://code.google.com/p/cocos2d-iphone/issues/detail?id=448

Reading it again, it says the effect can be applied to a texture and its children, which would seem to imply that it should only modify that sprite and its children, not things rendered before it. So perhaps I was wrong in my post above. Riq would know...

Posted 2 years ago #
Wheeljack
Member

I seem to see what I want to do, done in the "EffectsAdvancedTest" demo that comes with 0.8.1

Going to try and figure what was done there... and how I epically failed it myself ;)

Posted 2 years ago #
Wheeljack
Member

I fixed it! I used this:
// Use this pixel format to have transparent buffers
// BUG: glClearColor() in FBO needs to be converted to RGB565
[[Director sharedDirector] setPixelFormat:kRGBA8];

I compared my project against the cocos2d examples and found mine was missing that..!

Thanks lindgrenM, you made me question my code and search for ways to make it happen.

Posted 2 years ago #
Mitch Lindgren
Member

OH! I never would have thought of that. Good to know you figured it out though. Sorry I was wrong in my first post.

Posted 2 years ago #
spadict
Member

In case anyone has this issue as of of more recently (0.99.4 is wha tim using) the answer here is correct but the 'How" slightly changed:

For starters, it appears that "kRGBA8" is now "kCCPixelFormatRGBA8888" but both will work.

It's not going to let you set the pixel format after the Open GL has been initialized (Also says it's deprecated) and added to the window so I changed the setting in two other places:

CCDirector's init :

pixelFormat_ = kCCPixelFormatRGBA8888;

ALSO

ccMacro's CC_DIRECTOR_INIT():

EAGLView *__glView = [EAGLView viewWithFrame:[window bounds]
pixelFormat:kEAGLColorFormatRGBA8/* changed from default*/
depthFormat:0 /* GL_DEPTH_COMPONENT24_OES */
preserveBackbuffer:NO];

There may be a way to fix this without manually adjusting the defaults, and the first change in CCDirector may not be necessary but I wanted to be consistent.

Posted 1 year ago #
2cute4u
Member

I'm still getting this problem. Wheeljack's solution is causing me to get “SIGABRT”. and spadict's solution is giving me 'EXC_BAD_ACCESS'

is there an official solution, or at least one that works with 0.99.5?

Posted 1 year ago #
spadict
Member

Are you still having any issues? I'm probably porting my game over to 0.99.5 this weekend so I will be looking for an appropriate solution for this if I do, in fact, get an EXC_BAD_ACCESS

Otherwise, stay posted :)

Posted 1 year ago #
araker
Moderator

Cocos initializes a RGB565 backbuffer (no alpha channel) in the CC_DIRECTOR_INIT macro, to change to RGBA8 look at how to manually create the EAGLView in the documentation (link).

Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.