Editor 2D support

[jb-perrier]

Actually 2D game development is not the main goal of FlaxEditor, but with some effort we can greatly improve the "Flax"ibility of the editor in this direction.

For now, the easiest way to create 2D stuff is to use the UI system, but it's like driving a bicycle when you have a car.

The idea would be to adapt the editor, so it can setup a 2D environnement for us :

• Face the camera to the XY plane.
• Handling user input correctly for a 2D world.
• Rotate the grid gizmo.
• And so on ...

So i'm asking if 2D support can be at least a mini-feature* of FlaxEditor.

• not a full stack 2D editor

I can work on my own to implement this feature, in order to not add workload on the existing roadmap.

[aaronfranke]

If this were added, I don't know if anyone would actually use it. Why use 2D-in-3D when there are many great game engines out there that have real 2D support with 2D math and 2D rendering?

[stefnotch]

That's why the issue isn't asking for a full stack 2D editor, but rather something simpler. Lots of 3D games have little 2D things going on. (Biggest one here being the menus)

[honzapatCZ]

Necro bump, menus are almost impossible at this point, if there are stuff like sprite atlases, then proper UI is almost expected.

[Xrayez]

Why use 2D-in-3D when there are many great game engines out there that have real 2D support with 2D math and 2D rendering?

I recall trying to use the "pseudo 3D support in 2D engine" feature in some other engine. It didn't work well because such a game engine didn't implement it properly, and its 3D features were subpar compared to other more powerful 3D engines out there.

If you have enough experience, creating a 2.5D game with pseudo-depth and parallax effects can be relatively easy using 3D techniques. Simply moving 2D layers along the Z-axis can often achieve the desired effect. In contrast, in "2D" engines the complexity arises from the need to set up and update duplicate objects and properties between multiple layers, which is a major drawback that undermines the alleged usefulness of such a feature in a supposedly "2D" engine. These limitations could have been avoided by solely relying on 3D techniques from the beginning.