How about remove 3D related and some other codes when integrating metal?

[zhangxm]

Yep, 3D part will be saved.

[piotrros]

cocos builder and cocos studio support codes

Please save these.

[zhangxm]

cocos studio will be saved since cocos2d-x tests depends on it. But i don’t think cocos builder reader need to be saved, it is not maintained a long long time ago. As i know, the cocos builder editor is not maintained too.

[piotrros]

Yes, I was talking about cocos studio.

[mars3142]

But can someone please update the flatbuffers dependency, because Cocos Studio uses it and I’m not able to verify if my changes worked, because I don’t have any data. Also see my topic for that.

[Guykun]

I’m deeply concerned that such a thread popped up without any notice. An email would have gone a long way to actually gather user feedback from a larger developer-base as opposed to those that just stumble across this forum from time to time?

I replied to points as I read this thread, reading the ending conclusion after voicing my concerns, so I apologize if it appears to argue an already decided point

Also, I just stumbled on this thread by luck. A great many users may not see it. It would be good to place some sort of warning on the main website, with maybe a link back to this thread.

I agree with this point deeply

And you (as team) should also focus on improving cocos documentation. The bad documentation is the most important reason for me to think about continue using cocos2dx/CocosCreator for future projects. Documentation should have first priority at all. it’s frustrating to search for solution for hours and hours abd find nothing!

This is also a critical point and has continued to be for the past few years.
The main things missing from documentation are proper definitions of:

• Expected inputs
• Expected outcomes
• Fringe/cases/ exception cases

for all functions.

You should take into consideration what percent of cocos developers are using 3D. My guess is its a very small percentage. If so how much do you delay the next version for this minority of developers.

What are the statistics on this? This thread is full of a lot of guesswork and there’s no actual metrics on the feedback in it. I for example maintain an application with tens of thousands of daily users which relies on the 3D features of cocos2dx and on csb parsing (Cocos Studio was still supported during development, and we still use it to this day)

A quick look at http://cocos2d-x.org/games/ I cant find any that make use of the 3D engine. I know some games like “Knife Hit” and “!Ball Chase” do - but they seem in the minority.

If I add the game that I work on that has a large playerbase and relies on 3D does this validate my claim there are large projects relying on it?

Yep, 3D part will be saved.

Thank god, finally some good news as I read this thread.

cocos studio will be saved since cocos2d-x tests depends on it. But i don’t think cocos builder reader need to be saved, it is not maintained a long long time ago.

Does this mean that csb parsing will still remain implemented? (CSLoader, Timeline etc)

[zhangxm]

Does this mean that csb parsing will still remain implemented? (CSLoader, Timeline etc)

Yep, you are right.

[Guykun]

Great news!

The only big remaining concern will be how easy (I presume not at all) it will be to switch out the renderer or to port a 3.X project to this… moving files to a new cocos2dx project isn’t really an answer for pretty entrenched game.

[zhangxm]

We will release alpha0 version quickly, you can take a look. I don’t think it is hard to do, especially if you don’t modify engine codes.