When comparing PlayCanvas vs Flax Engine, the Slant community recommends Flax Engine for most people. In the question“What are the best game engines for point & click adventure games?” Flax Engine is ranked 54th while PlayCanvas is ranked 60th. The most important reason people chose Flax Engine is:
Can be used for free until you hit a rather high revenue cap, at which point you have to pay royalties.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Real-time collaborative online editor tool
PlayCanvas has an online editor that lets you build scenes and work with other people in your team in real-time. This is all done through the web browser without having to install any additional software.
Pro Powerful assets pipeline
Assets and content delivery is very different on a web platform comparing to native. So PlayCanvas challenges best practices to allow developers decide how their content is delivered and in what form.
Async Assets download allows developers to load content as the app goes, instead of asking to download all assets in advance risking users to simply navigate away while staring at loading screens.
Formats for 3D models and textures support covers all the popular tools. And the workflow is as simple as dragging and dropping your files right into the Assets Panel. The cloud will do the rest of the hard work optimizing and converting your files into runtime-friendly and compressed data.
Pro Rendering engine runs on the browser
Has an advanced WebGL renderer that runs in the browser.
Pro Avoids having to download lots of textures for lightmaps
Lightmaps are an efficient way to deliver lighting to your scenes for a long time. But they come with the cost of large textures. PlayCanvas offers a unique solution for a web platform, it renders lightmaps when an app is loading in runtime.
This is faster than downloading MBs of textures. And it's much more convenient: simply switch your light sources to bake, and static models to be lightmapped, and the engine will do the rest.
Pro Friendly and active community
PlayCanvas has Feed as homepage for registered users, listing Dev Logs of other developers. This allows to socialize with other developers like yourself in a twitter-like environment.
More to that, there is also an active forum, where developers help each other to solve their challenges.
Developers of PlayCanvas itself are always looking forward to chat and help the community with any problems that may arise.
Pro Integrated physics engine
PlayCanvas lets users integrate physics in their game rather easily, using the powerful Bullet Physics Engine (ammo.js). Should also be noted that the physics engine is delivered as an optional library, so by default being disabled it does not add any extra download size to your apps.
Pro Has a free tier
Engine is free for projects under 200MB and with no more than 2 people on a team. The free tier has no engine restrictions.
Tools are totally free too. There are no special limiting features behind any paywalls, and free users have all the features as paid users.
There are no royalties associated with publishing your apps and games - you've made them, you own them.
It is free to publish to playcanvas.com as well, just by one click in Editor.
Pro Cross-platform support
PlayCanvas lets you build games that run in mobile, desktop browsers, and native mobile apps. PlayCanvas can even make games that can run inside mobile social media and instant messenger clients like Twitter and WhatsApp.
Pro Small app size
The engine itself weighs just under 150Kb, and it's always challenged to stay small. There is no extra weight that has to be carried with your app, just your assets and scripts in a runtime-friendly compressed form.
This allows users to engage with your content in matter of seconds, and even just under a second on a good connection.
Pro Open source
PlayCanvas is fully open source and is under active development.
Pro Very easy to use
Pro Loads extremely fast
Pro Has hot code reloading
Real-time link between your launched app and the editor allows the developer to preview and play with their scene without needing to refresh the game after every change in the code to see the updated result.
Pro Free
Can be used for free until you hit a rather high revenue cap, at which point you have to pay royalties.
Pro Powerful C# scripting
C# scripting is really well made, comparable to Unity, but without any of the legacy cruft.
Pro Multiplatform
Supports most platforms, including Windows, Linux, Android, Nintendo Switch, ...
Pro Modern rendering backend
Has a very modern, performant and beautiful rendering backend.
Pro C++ support
The entire core is written in C++ and it supports writing game code in C++. The interoperability between C# and C++ is also nothing to scoff at.
Pro Supports multiple IDEs
Works with any text editor and comes with proper support for Visual Studio, VSCode and Jetbrains Rider.
Pro Excellent documentation
The documentation is well written, up to date and accepts improvements from the community.
Pro Great and extensible editor
The editor is both powerful and simple. My favourite part is how easy it is to extend the editor with custom magic.
Pro Source code available
The entire source of the engine is available on Github, though not under an open source license.
Cons
Con Private projects are only available for premium users
The free tier does not support any private projects. Instead, all the code and assets will be hosted openly. While not a problem for open source games and for developers who intend to make an open source game, it can be a deal-breaker for teams who want to keep their code and assets private.
Con No collision offset
Con Not many tutorials
Con New software
As is standard with new software, not all of the bugs have been ironed out yet.
Con Few plugins
Unlike more mature engines, there isn't a vibrant ecosystem of plugins yet.
Con Not open source
While the source code is available, it's not quite open source
Con Not latest C# version
It uses Mono and is still on some variant of C# 7.
Con No OpenGL support
It only supports modern APIs, namely Vulkan and DirectX. This means that it won't run on very old machines.