Coming back to Unity!

Hello!

After a year of developing with UE4, I am going to come back to Unity 3D. I see many things have changed for good! I will install Unity 3D on my computers: on Windows 8.1 (my client wants that) and then, after having bought a new powerful machine, I will install the Linux version! And we will probably buy a pro version what is a good info for Unity Team. Why not UE4? UE4 seems too big cannon for this project. Unity 3D is perfect. Again programming in C#. I look forward to trying the new Unity version.

1 Like

Are you referring to this awesome service they’re developing?

http://unity3d.com/services/collaborate

1 Like

No, but I wrote that in general. I have no idea of all the things that have been changed or appeared since the time I was using Unity 3D last time. I’ll be working with both engines (UE4 and Unity3D), making two projects simultaneously. There was so much to learn about UE4 that I almost lost contact with Unity3D. So thanks for showing me the service, Ryiah. Tomorrow, I will install the new version of Unity. I have yet downloaded the installer.

Why did you leave Unity in the first place?

Were you drawn by the shinies of UE4?

As I wrote many times on the Unity forum, before releasing 5.x, I used 4.x for my commercial demo project. I badly needed 64-bit version of engine that was why I started to use the 5.x Beta. It was a very risky step to upgrade my 32-bit project to 64-bit and with 5.x Beta. There were many problems and I lost a few months, fixing the problems by hand. But I was successful. My client wanted to get a very complex app. The Demo app seemed very slow for me, so I started to dream of using C++. This language is popular among game developers - more control in your hand, optimisation, etc. Therefore, I started to use UE4. Unity3D is perfect for smaller, 2D and mobile project, but for huge app, sorry, but the production app will be written with UE4. But at the same time, I have got a proposition to make a smaller app, so I come back to Unity. Now, I know both engines and it depends on the project I have to make. 15 years in programming, including 8 in game developing. That’s my story.

This seems to be the consensus over and over again. I wish Unity would accept this and focus their effort towards mobile. My Unity frustration of the week right now is that for iOS builds you have to choose between the game taking up massive storage on device (450mb on iOS vs 50mb on Android) or having the game look like garbage. There are a few ways to solve it but this feature suggested 5 years ago would’ve done the trick.

You should check out crunch texture feature in Unity. It’s actually better IMHO… it should support iOS if Unity’s ported the iOS PVR version over, not sure where the state of that is.

Re the whole UE4 Unity debate, lets not go there again in this thread. I’m not sure why OP felt need to announce he’s back or gone - it’s a free world. For example I enjoy both for different reasons.

2 Likes

People seem to do this quite a bit and it confuses me too. Learning a new game engine is almost the same situation as learning a new programming language. Once you’ve become familiar with one you can pick up additional ones much more easily. Therefore I see no reason why you can’t be productive with more than one engine at a time.

4 Likes

Crunch would be great but Unity doesn’t support it for iOS. Only Android.