Use C# to script in Unreal Engine 4 now, courtesy of

[lemmy101]

@;171819

But is exactly what the Blueprint system is for, and engine source is in C++. Blueprint is fast, it executes quickly enough, it compiles almost instantly so it’s perfect for prototyping. Most importantly, it’s understandable by virtually everyone who understands game logic. It’s artist friendly and powerful, sure it has a lot of bugs right now but I betcha it’s more bug-free than Mono integration. I also bet that Blueprint has more things from the engine exposed to it than C# does right now too, because it was integrated at day one.

C# only serves to mix up the flavours even more and add a third language to the mix, which in itself is going to have it’s own squirms and problems. C# will only ever serve as an interface between user and engine the same way Blueprint does, at which point I believe you are wasting time you could be spending learning new things, that will ultimately make the experience of working with the engine much smoother and you’ll have less roadblocks in the way too.

The only reason C# plug-in exists at all, is because Unity uses it, and somebody knows they can make money bringing it’s users over to Unreal. It’s nothing to do with the pros and cons of the language, you will always be better off using the native code of the engine. Either way, you’ll have to learn the engine, so why not experiment with C++ more too?

Disagree massively here. I did C++ for ten years and then took up C# and the simple fact is generation of languages allows you to create code so fast compared to C++. Just not having to deal with headers/libs/includes and the infinitely faster compiling, but not having to deal with memory overwrite crashes and missed deletes. No one will deny C++ is faster execution speed, but to say that someone equally skilled in both languages wouldn’t code significantly faster features in C#. Remember we’re talking properties, events, async, foreach, GC, and all those things that shave huge chunks of development time, particularly for those less experienced in C++ which is far from without its strange nuances, C hangovers and complicated build processes. It’s kind of ****** to say people who can code but find C++ intimidating should just make do with a visual scripting system like blueprints, and the more languages supported the better.

I’m dying for full C# bindings for reason. I’ve done plenty of C++ but there is no comparison. It’ll be the fastest of the three systems, blueprints due to their visual nature and simplicity for sake of artists / designers, it would take a lot longer to piece together a complex system for the game purely in blueprints when you’re placing constant nodes for calculations that could be typed in a few characters in code. After a certain level of complexity it’s a code thing, or you’d at least want power to create blueprint nodes with code driven functionality, C# and being able to liberally use List<String> and HashMaps and other things with nice inbuilt language features over stuff like boost or the stl. With simpler build process, it’s going to be attractive to many people.

I think C# support, even if third party, is a must in the long term to get indie devs on board, so very pleased to see .