Feedbacks of v3.0-beta

cocos2d-x C++
#100

The texture iD issue was fixed at https://github.com/cocos2d/cocos2d-x/pull/5472 .
The texture ID was extended from 18bit to 32bit. It will resolve the problem.

#101

hi,when I use ControlPotentiometer,there are errors.

#102

since beta 2 I can not detect more than 1 touch, EventListenerTouchAllAtOnce looks not working,
the same code is working fine with beta 1

…
auto dispatcher = Director::getInstance()->getEventDispatcher();
auto listenerM = EventListenerTouchAllAtOnce::create();
listenerM->onTouchesMoved = CC_CALLBACK_2(CTouchManager::onTouchesMoved, this);
listenerM->onTouchesBegan = CC_CALLBACK_2(CTouchManager::onTouchesBegan, this);
listenerM->onTouchesEnded = CC_CALLBACK_2(CTouchManager::onTouchesEnded, this);
listenerM->onTouchesCancelled = CC_CALLBACK_2(CTouchManager::onTouchesCancel, this);
dispatcher->addEventListenerWithSceneGraphPriority(listenerM, mNode);
…
void CTouchManager::onTouchesBegan(std::vectorcocos2d::Touch* touches, cocos2d::Event* event)
{
…
int tSize=touches.size(); // tSize is always 1 :frowning:
…
}

Any idea? I read the same question from another guy without reply…

#103

another strange thing, with SpriteBatchNode I need to manually increase atlas capacity using increaseAtlasCapacity when adding a child to the batch node else
1/ app crache here
void SpriteBatchNode::swap(ssize_t oldIndex, ssize_t newIndex)
{
CCASSERT(oldIndex>=0 && oldIndex < (int)_descendants.size() && newIndex >=0 && newIndex < (int)_descendants.size(), “Invalid index”);
or
2/no crash but not rendered
Any idea?
Since i build all my project from beta1 to beta2 I’m really asking if it was a good idea to start a new project with V3 :frowning:
Please reply about this and previous question (EventListenerTouchAllAtOnce looks not working), I’m really afraid to continu my project.

Regards,

#104

the problem with beta 2 is:
when you reach atlas capacity and you add a sprite in the batchnode we have
cocos2d: cocos2d: SpriteBatchNode: resizing TextureAtlas capacity from [29] to [40]. -> this is normal
BUT
the sprite is not rendered because he has the same texture that the other one…

#105
#106

Hi Fabrice,
You received a solution? because I have exactly the same problem as you!
Thanks

#107

@fabrice I met this multi-touch problem (ios), that’s because no open multi-touch mode of the rootviewconctroller, you have to start it:[__glView setMultipleTouchEnabled:YES];

#108

Thank you I added in “appcontroler.mm”
[__glView setMultipleTouchEnabled:YES];
and now all is working fine !

#109

@ricardo @walzer @zhangxm In cocos2dx 2.x.x and cocos2dx 3.0 alpha,(CC)Sprite’s draw() function is different from 3.0 beta Sprite’s draw(),which cause this problem: “In old versions,if I wrote something like DrawSolidRect() in draw() function,and create a Sprite in that layer,the DrawSolidRect()'s effect would be covered by the Sprite.So we set the Sprite’s ZOrder to -1,and so it is smaller than zero(http://blog.csdn.net/crayondeng/article/details/12585479 ),which solved my problem. But now,I changed my platform to cocos2dx 3.0 beta2, the new Sprite’s draw() make that “ZOrder solution” doesn’t work any more. No matter how small the ZOrder is,DrawSolidRect() always be covered forever”.
I doubt that 3.0 beta’s Sprite new draw() is imperfect,although it’s neater than old draw(). I tried to understand the new draw() and fix it,but I don’t have time enough.So Anybody knows why? and how to solve the “DrawSolidRect() covered”'s problem in 3.0 beta.

#110

Hi guys, can some of u plz help me with my post, I’m newbie

#111

How to make DrawNode anti-alias?
And why drawQuadraticBezier draws not a curve but a shape with a line and a curve?

#113

@sophymax I have the same Z order problem: http://www.cocos2d-x.org/forums/6/topics/46970?r=47046#message-47046

#114

@naghekyan heh…The only thing we could do is to use order versions.I saw the new Sprite’s draw(),it seems too complex(over packed，like some frameworks in J2EE) to fix it ourselves and would waste much time.

#115

Assert failed: TextureID is greater than 2^18

03-20 14:34:27.503: D/cocos2d-x debug info(17488): Assert failed: ShaderID is greater than 2^10

03-20 14:34:27.503: D/cocos2d-x debug info(17488): Assert failed: TextureID is greater than 2^18

how to fix it

#116

cocos2d-x3.0 rc0 have this problem too
Assert failed: TextureID is greater than 2^18

03-20 14:34:27.503: D/cocos2d-x debug info(17488): Assert failed: ShaderID is greater than 2^10

03-20 14:34:27.503: D/cocos2d-x debug info(17488): Assert failed: TextureID is greater than 2^18

#117

@kyo9999
Which device did you test on?

#118

I’m facing the same problem as kyo9999 and it happens on Kindle Fire HD 8.9" 16GB and Samsung Galaxy Tab 2 7".

#119

Same error on cocos2d-x3.0 rc0 wth Galaxy Nexus

#120

I have the same error occurs on Android.

build: cocos2d-x-3.0 beta2
device: Samsung Galaxy Nexus (SHM-M420)

android logcat:
D/cocos2d-x debug info(16067): Assert failed: ShaderID is greater than 2^10
E/cocos2d-x assert(16067): /*/proj.android/…/cocos2d/cocos/2d/renderer/CCQuadCommand.cpp function:generateMaterialID line:64

D/cocos2d-x debug info(16067): Assert failed: TextureID is greater than 2^18
E/cocos2d-x assert(16067): /*/proj.android/…/cocos2d/cocos/2d/renderer/CCQuadCommand.cpp function:generateMaterialID line:66

This error is notified to every frame.