I am an artist / designer. I did some scripting using QuakeC for Quake-based engine and DoomScript for Doom 3 based engine. Also did just a tad of C++ coding (nothing special; mostly reading through Doom 3 code and adding / fixing a few simple things).
I’ve been watching some videos on YouTube about Blueprints and I am having hard time understanding why and how I/O sockets on nodes plugged into another. Doesn’t seem to be logical in some instances.
Are there any tutorials that explain how to transition from scripting mindset to Blueprints mindset ? Thanks.
Its the exact same mindset. The tools are much the same, but prepackaged and sort of engineered taking into account some of th more common use cases typicaly. Its a bit of a give and take between ease of access and flexibility. Most of the “primitive” functions are also exposed so you can actually engineer functions/macros to your exact specifications with a bit more effort (in a sense exactly like scripting).
Input is function arguments, Outputs are the return value’s. Nothing more than that. The main wire in and out is the execution flow. It’s not a different mindset, it’s just a different way of visualizing it than text.