Please work with Xamarin to make Mono for UE a reality

[anonymous_user_a006f79c]

@;362613

People do “framework” as you saying yet they call it “engine”, specially when they reuse it in different game, because engine is what i said, fundaments of for a game and it can be reusable. And doing simple engines is not that hard as people talking, they think that if you do engine you need to do complex tools and giant code base and such, make it do everything, when majority of engines are done to power specific kind of games. If you looks on quake, it practically had editor as a sperete software, yet people call it a engine, not to mention that engine was made by single man. Speaking of editors, you are aware of fact that UE4 editor is build on top of UE4 engine it self and when you package a game you only building engine without editor modules?

I still think you incorrect and you don’t understand how UE4 is build and you won’t be able to master UE4 as long as you think that way, mark my words Again Unreal (unlike Unity which was made more like game maker) was made just for single game, it was initially not ment to be a “engine” of your definition “to provide content creation tools and make games”, initially it was just level editor for game called Unreal in your definition of “engine”. But again i only assume that, i don’t know if Epic really wanted to sell engine when they been building Unreal, or they just though they can do other business with what they made once Unreal was out, Jazz Jackrabit 2 also had nice editor, but it was more primitive. Also as i mention above if you grab UE3/UDK it feels you install some kind of empty game and build on top of it, because there was no project system at all, it’s actually new feature in UE4

I also think we kind of lost, but it all started with discussion in C# can do in UE4. To back that discussion, C# in UE4 sould be plugged to UE4 framework as much as possible, make it feel like you coding in similar way to C++, or other way around, text form of blueprint.

UE4 is built like every other engine out there is built, if you’ve been doing this a while you should know it’s all the same the same stuff different developer.! I’m not sure what there is to “understand”?

Simple as this, it’s whatever takes me the least amount of time to get to my end goal and keep the lights on. I don’t really care what’s in the engine if it speeds up dev, I have years worth of work without anything on top to deal with… If there is a problem I have the experience to fix it, it still doesn’t mean even as someone has worked on engines and messed around with them for years I’d ever dare attempt to dive to the centre. As soon as an engine starts becoming less cost efficient than a custom “framework” or Engine then I have to re-evaluate it’s purpose.

As much as I’d love to spend years noodling about with systems, in a commercial environment it’s not an option. Not to say I won’t fix core issues if I need to, or add tools if I require them… But for some indie’s even that could be too much of an ask…!

Personally, don’t see the point in C#… You can split and classify BP’s, get instant feedback and it’s not hard to convert. UE gives you less rope with GC and automation if for some reason you decide BP’s aren’t good enough.! I like OS, It’s allowing me to think about bolting on systems like Umbra, even though I’d prefer Unreal to sort a deal out :D, well it is in Unity.

Different engines, different workflows.!