When comparing Starling vs Torque 2D MIT, the Slant community recommends Torque 2D MIT for most people. In the question“What are the best 2D game engines?” Torque 2D MIT is ranked 4th while Starling is ranked 78th. The most important reason people chose Torque 2D MIT is:
Torque 2D gives developers complete access to the source code. This removes all barriers one may hit when trying to extend and/or customize the engine they are working with.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Lightweight
Starling is just 12k lines of code and doesn't try to do everything — but what it does, as efficient as possible.
Pro Feathers User Interface Components
With Feathers, you can easily add great user interfaces to your games — or even create business apps with Starling.
Pro Free and open source
Starling is available for free with code available on GitHub.
Pro Strong community support
Forum is always active with knowledgeable developers and with lot of inside info, and post mortems.
Pro Works with Flash
With UI, you can design it in Flash Professional (powerful 2D editor), export to swf file, use GAF convert swf file to gaf file, finnally, load gaf file to Starling. GAF can convert a lot of file swf to one atlas. Alway use same resource in design files (fla) to optimize atlas size, avoid duplicate asset in atlas.
You can use flash to create animation for starling.
Pro Hardware accelerated rendering
Let the GPU do the rendering, the CPU has more important tasks to do.
Pro Cross Platform
It can be exported to web flash player, iOS, Android, Windows, and OS X
Pro Works with AIR's native extensions
Using AIR's native extensions any native code that can be written can be run and used by the game engine.
Pro Constantly updated
New features are added regularly.
Pro Better performance than most alternatives
Starling can run more animated display objects than Unity2D and many others frameworks at 60 fps.
Pro Extremely extendable and customizable
Torque 2D gives developers complete access to the source code. This removes all barriers one may hit when trying to extend and/or customize the engine they are working with.
Pro Cross platform
Torque 2D runs on Windows, OS X, iOS, Android, Linux, and Web.
Pro The scripting language is quite powerful
Torquescript is a fast and easy to use C++ like scripting language that ties all of the various elements of a project together. It supports a large complement of functions including math, physics, object manipulation, fileIO, and more. Torquescript features:
- Object-oriented programming
- Transparent interconnection with internal C++ objects
- Built-in fast 2D math (vectors, matrices, and quaternions with all corresponding functions)
- Well-documented standard library (hundreds of functions out-of-the box)
- Component system (aka Behaviors)
- Dynamic asset and module loading
Pro Highly performant
The engine utilizes a combination of batched rendering, asset management, and a module system that allows for high frame rates on all platforms.
Pro Box2D physics
Torque 2D MIT's utilizes Box2D for all physics calculations. Anyone with prior knowledge with Box2D by itself or through other engines can easily transfer their knowledge. Nearly all of the Box2D API is exposed to the scripting language, making it a quick process to port games to the engine without having to learn an entirely new system.
Cons
Con Poor text/font support
It supports only 4 features for text rendering:
- bitmap font with batching.
1.1. basic distance fields with support for outline and filters via MeshStyle.
1.2 the new multichannel distance field, the ultimate solution for bitmap font rendering. - Draw and upload texture in runtime
So every new text field required texture uploads or vertex/idnex buffer uploads.
skipUnchanchagedFrames keep the backbuffer static for scenes without changes between frames, leveraging a good rendering optimization.
Con Engine supported mainly by one man
Its open source but in most cases community features or pull request are canceled.
Con Project seems to be abandoned
Seems to not be developed/supported anymore.
Con Lacking documentation
The engine documentation is incomplete. Not all of the engine API is fleshed out and the number of tutorials is pretty small. All current and future documentation effort is up to the community, via the Torque 2D MIT GitHub wiki.