3 ms·
Yes. That was my point. The warning was for others like myself who might blunder into UE thinking it was an IDE, and not realizing it's really just "a bunch of
by russellbeattie 6y ago
Yes. That was my point.
The warning was for others like myself who might blunder into UE thinking it was an IDE, and not realizing it's really just "a bunch of scripts being called from a main loop".
- pjmlp 6y agoIt is an IDE, but whose main target are designers, artists, gameplay developers. Software developers in AAA are just putting the infrastructure in place, the real show is driven by others, so game development IDEs are tailored for those skillsets, not writing barebones C++ code.
- dogma1138 6y agoIt is an IDE but it’s just might be different than what you used too, although if you are used to visual component based IDEs like Visual Studio (not code) or Visual Basic it won’t be that unfamiliar. The whole point of blueprints is that the provide a visual interface to link the underlying classes together in a fairly easy manner you can actually make a game with using blueprints only now you’ll be limited in various ways from not having the exact functionality you want in a given blueprint to having performance issues if you are linking too many blueprints together to perform a relatively simple action but they serve their purpose and that is to detach much of the high level game/level design implementation from the low level code implementation.