Skip to content

C++ implemented, cocos2d like cross-platform game engine

License

Notifications You must be signed in to change notification settings

stubma/WiEngine

Folders and files

NameName
Last commit message
Last commit date

Latest commit

7e80641 · Apr 25, 2014
Feb 17, 2013
Feb 13, 2013
Feb 13, 2013
Feb 17, 2013
Aug 14, 2013
Sep 30, 2012
Dec 11, 2013
Jan 24, 2014
Jul 10, 2013
Jul 10, 2013
Sep 30, 2012
Sep 30, 2012
Oct 8, 2012
Jan 14, 2013
Jan 17, 2013
Sep 30, 2012
Apr 25, 2014
Jul 10, 2013
Dec 11, 2013

Repository files navigation

!!!!NOTE!!!!

This project is not in development and no more maintenance, please use cocos2d-x. Do NOT ping me if you have problem. Some features of WiEngine are ported to cocos2d-x, check out this repositories:

https://github.com/stubma/cocos2dx-better

WiEngine

C++ implemented, cocos2d-like cross-platform game engine. Any question, please visit our forum: http://wiengine.forumer.com/

Platform Supported

  • iOS(3.2+)
  • Android(2.0+)
  • Mac OS X(10.6+)
  • Windows (XP or above)

Main Features

  • Scene managing and transition effect
  • Texture and atlas (Supports png, jpg and pvr)
  • Advanced grid 3D effect, such as lens, ripple, wave, liquid, twirl
  • Particle system
  • Actions
  • Common UI controls, such as button, menu, cover flow, page control, etc.
  • Text rendering(TTF font, bitmap font, line wrap, etc.)
  • Tile map(TGA, Array, TMX)
  • Parallax
  • Motion streak
  • System events(touch, multi-touch, accelerometer, key, gesture)
  • Physics engine(Chipmunk, Box2D)
  • Lua script
  • Memory file system
  • Sound engine which is named "WiSound"
  • AFC(Animation, Frame, Clip) animation format support
  • Skeletal Animation support
  • texture color filter
  • Persistence support (preference, sqlite3)
  • flexible screen adaptation: by density, by base size
  • resource protection mechanism
  • JSON parsing

Tools Supported

When Submit Issue

When you submit an issue, I hope you provide:

  1. description, platform, OS version, WiEngine version, etc.
  2. log if it is a crash problem
  3. sample code to reproduce that problem. this is not mandatory but it will gain high priority if you can provide.

Documentation

We organize all documentation in github wiki.