After the recent pricing controversies, I am considering moving my 2D platformer project from Unity to Godot 4.3. How does the tilemap system and C# support compare in terms of workflow efficiency? Is the performance for sprite-heavy games on mobile platforms at par with what Unity offers currently?
3 answers
The transition to Godot 4.3 is smoother than ever, especially with the revamped TileMapLayer node which makes 2D level design much more intuitive than Unity's older Tilemap component. C# support via .NET 8 is incredibly fast, though you do lose some of the deep library integrations available in the Unity Asset Store. For sprite-heavy mobile games, Godot’s GLES3 renderer is very lightweight and often results in smaller build sizes, which is a huge plus for user acquisition. I moved a project in February and haven't looked back; the node-based architecture just feels more logical for 2D.
Have you run any specific stress tests regarding the "Forward+" renderer vs "Mobile" renderer for lights and shadows in a 2D space?
Godot’s dedicated 2D engine is actually a "real" 2D engine, unlike Unity which is 3D with a flat camera. This makes pixel-perfect layouts way easier to manage.
Exactly! Not having to fight with Z-axis issues or 3D physics quirks in a 2D game is a breath of fresh air. It simplifies the development cycle significantly.
Megan, for 2D, you almost always want to stick with the "Compatibility" or "Mobile" renderer. Forward+ is overkill for sprites and can actually cause issues with older Android GPUs. The performance gain on the "Mobile" backend for 2D lighting is very noticeable.