Cocos Creator v2.0.7 released!

Cocos Creator v2.0.7 released!
0

#1

Cocos Creator v2.0.7 released!

Description of changes in this version:

  • Improve the font loading method on the web platform and fix the problem that individual TTF fonts must be loaded for a long time #3708
  • Fixed an issue where audio might not play after multiple reloads #3702
  • Fixed an issue where calling cc.view.setFrameSize does not take effect on the web platform

Also fixed the following new issues in 2.0.7:

  • Fix native platform WebView, VideoPlayer related issues
  • The rpk path of the debug platform window popped up after the Huawei small game platform clicks is inconsistent with the actual
  • If the fast game tool is not closed, the project will be opened after the project is switched.
  • Fixed an error caused by the failure of loading ttf in WeChat open data domain
  • Fixed a problem of not generating a web-mobile folder when building a web-mobile platform
  • Fix ios platform empty packet compilation error (ios)

Downloads

Cocos Creator 2.0.7 for Windows
Cocos Creator 2.0.2 for MacOS

Documentation

Cocos Creator 2.0.x Documentation


#2

i said before but just to remind again if we could update the creator from inside the creator without having to download again it would be much better thanks :heart_eyes:


#3

yeah, great idea. Hopefully :slight_smile:


#4

what about Cc system event editor bug? @Big_Bear promise that would be solved to the 2.0.7


#5

I am not sure if it is fixed yet or not. @Big_Bear can update us as to the status.


#6

2.0.7 had fixed this bug.


#7

Can anyone elaborate about this issue or where it was opened?


#8

@slackmoehrle Urgent. When build game using terminal ‘CocosCreator --build --path .’, custom extension were not loaded. This command line is working in Creator v2.0.5.

Custom extension were loaded properly when either --build or --path is specified, but not both. This is having a huge impact on progress since CI could not build automatically.

Can you please look into this?


#9

@zhiliangteoh I am asking the engineering team about this.

Update: The engineering team knows about this bug and a fix is coming in 2.0.8. Thank you for bringing this to our attention.


#10

Alright. Thanks