(06-03-2015, 05:08 PM)Sath Wrote: Unity engine is sexy af, especially when combined with Freelancer, for all I know. Some guy made a bunch of small videos demonstrating.
With Unity you'll be drowning in bugs and arbitrary restrictions unless you shell out five digits money, whereas with UE4 you can do whatever you want. This is why none of these projects ever got anywhere, people take the easy way with Unity because it's the easiest.
(06-03-2015, 05:58 PM)Oldum Wrote: This makes ne suspect you're taking the hard way with Unreal cause you're badass
Also, thise vids are just awsome, I wish I cold do that kind of stuff
It depends. With Unity you'll be very well set for simple games or singleplayer games. Once you start throwing networking in, things tend to become very complicated with Unity and C# is not the best language you can pick when it comes to large scale multiplayer games. With UE4, things like instances are built in, whereas with Unity you have nothing at all.
I've been experimenting with creating my own blueprint components out of C++ classes, it's really useful as I just write a reusable chunk of code with definable parameters and can quickly iterate through them.
I wrote a simple communication interface that way and any of my blueprints can send requests to it. So far it creates the json but it doesn't send it anywhere yet.
Here's a pic, some HUD experimentation using that interface. The background is shamelessly stolen from the Matinee example project.