When comparing Flixel vs PlayMaker + Unity3D, the Slant community recommends Flixel for most people. In the question“What are the best 2D game engines?” Flixel is ranked 20th while PlayMaker + Unity3D is ranked 73rd. The most important reason people chose Flixel is:
Ports are available for Objective C, C# (XNA), HaXe and [Monkey X](https://github.com/devolonter/flixel-monkey).
Ranked in these QuestionsQuestion Ranking
Pro Many ports available
Ports are available for Objective C, C# (XNA), HaXe and Monkey X.
Pro Built-in pathfinding and following
Pathfinding just means figuring out how to (or if you can) get from A to B. FlxTilemap has a function FlxTilemap.findPath() which returns a FlxPath object, which is just a collection of "nodes", or FlxPoint objects.
Pro Camera system for split screen
Create effects like "split screen" views, or "picture in picture" style displays, or even mini-maps with FlxCamera. Each camera is an independent display object, with its own zoom, color tint, rotation, and scaling values.
Pro Record and play back replays
Replays are essentially a list of what keyboard keys were pressed, and what mouse inputs were given, during a specific time frame. Because Flixel is largely deterministic, you can use that information to recreate a gameplay session that someone else recorded, as long as you have the same SWF.
Pro Basic features provide a solid foundation
- Display thousands of moving objects
- Basic collisions between objects
- Group objects together for simplicity
- Easily generate and emit particles
- Create game levels using tilemaps
- Text display, save games, scrolling
- Mouse & keyboard input
- Math & color utilities
Pro Flixel Power Tools extend the functionality
Flixel Power Tools provide a set of classes and APIs that provide more functionality.
Pro Used to create Canabalt, game that started endless runner genre
Pro Easy to use
You'll need to put more time in learning Unity + Playmaker compared to something like GameSalad. But once get the hang of it and familiarize yourself with what it's possible to build with them, it's quite easy to use.
Pro Provides access to a huge list of assets through Asset Store
For those developers who can't afford an artist, or aren't skilled enough to create their own art, Unity features an Asset Store full of a wide variety of free and paid assets that can be easily added to your game. The Asset Store has more than just music and art. It also has code and modules that can be added to your game such as unique lighting or GUI systems.
Pro Third party plugins support
A lot of third party plugins have support for Playmaker. Playmaker team also invest time to add support for a lot of third party plugins.
Pro Elegant state-based visual scripting
Instead of a single "if this then that" event list which can become very cluttered beyond the most basic behaviors, PlayMaker gives each object a list of states where only certain events are triggered, and performing an action also changes state.
This allows for a clean, simple visual representation which helps break complex logical structures into smaller pieces, making them easier to understand.
It basically can do same things as scripting in Unity.
Con It is now obsolete
With Adobe Flash dead, Flixel is now unworkable.
Con Development has stopped
Seems like development for Flixel has stopped. The last commit on all of the branches of it's Github repository are from 2011.
Con Poor performance on mobile
Con Comparatively high learning curve
Con Limited tutorials
There are not a lot videos with Playmaker tutorials. Official text tutorials are also quite limited. Even not every action has a description on an official wiki.
Con Performance could be better for 2D
Performance can be a real issue with 2D games. Unity 3D is actually a 3D game engine, and drags a lot of overhead with it.
For mobile, one could never achieve the performance of more specialized 2D engines with Unity3D.