Help to improve our Unreal Engine 4 For Unity Developers document

[zip]

I’m professionally don’t use Unity, but i read Unity forums and other sites where compering engines, so want to ask— why any of you guys don’t ask anything about 2d in general(good performance in low end mobile, smooth sprite animation(for character move for example), small build sizes)? 2d is a one main feature Of Unity(for me), Ue4 for now don’t have normal 2d unfortunately.

[Tomza]

@zip;344759

I’m professionally don’t use Unity, but i read Unity forums and other sites where compering engines, so want to ask— why any of you guys don’t ask anything about 2d in general(good performance in low end mobile, smooth sprite animation(for character move for example), small build sizes)? 2d is a one main feature Of Unity(for me), Ue4 for now don’t have normal 2d unfortunately.

I asked if there’s something like New UI in Unity 5.0, but I’m still not sure. I’m not personally interested in mobile development. I think Unity is probably better for mobile, but it can be changed in the future.

[Tomza]

@ShadowKindGames;340044

I’d highly recommend starting with blueprints first and then converting to code after (if you need to)… There are many reasons to do so, firstly because a lot of the tutorials seem BP orientated, a lot of the component systems are quite similar (Animation BP, AI Behaviour trees) and it’s easier to adapt to the API if you understand the flow in front of you.

Which in turn can make conversion to C++ much easier when you understand it in a more “pseudo format”.

For me the most difficult transition is general things like getting used to a new API, the “Spawn System”, how the UI / particle system works and general terminology. I still today keep looking for “raycast” :).

You are right.