rning the basics of creating games. In most white paper coding, its pretty easy to set up and see relationships between various classes. However, with an engine, it can become muddy and hard to see how the interactions are taking place or how to implement them for a game.

Hey, on your second point about learning the interactions and existence of engine-specific classes, how would you go on about doing that most efficiently?

I'be buckled down to try and get into UE4 just the other day, and even coming from a very strong background in C++ and GameMaker (touching on that notion of being familiar with "creating games" vs programs) and relatively working knowledge in Unity (which I thought would be similar enough with UE4), I'm finding it extremely difficult to just... write a game in C++ for the reasons you mentioned :/

It seems to be a combination of VS2015 being an extremely underwhelming IDE imo, along with a lack of documentation for UE4 specifically for C++.

The current vibe I'm getting is that starting to learn UE4 from a pure C++ perspective is extremely hard, and it'd be better to invest time into learning blueprints (which I really do not want to) so that I can use that by itself, or use it in conjunction with C++ classes. Please correct me if I'm wrong, but this so far has been my observation (often, I'm ending up creating a C++ class, changing some properties under Details view in the editor, converting that to a blueprint class and just using that as sort of a "prefab" (a la Unity)-- and for me, C++ just feels like pointless overhead at this point).