Sorry to bump this old thread but I wanted to know if I understand something right. Besides the minor things that aren’t implemented in blueprints that were mentioned here, I watched an AI tutorial with Ian Shadden (think I have his name right) and he said for anything AI you eventually want to use blueprints because its less efficient and AI is constantly checking values many times a second.
Also, can someone explain what nativization is? It just creates c++ code from your blueprints is ? It also makes your project file larger? But I suppose it has those same limitations since if something hasn’t been implemented in blueprints, then there’s be no way to create in the first place to generate the nativized code. But I could use nativization to create c++ AI code?
I don’t mind learning c++ and I’ll get deep into it one day but for now I need to work on getting better at modeling and stuff first.
Also, I’ll search this but what are those limitations mentioned, file i/o and procedural mesh? So specific writing to files and creating/editing a mesh using math instead of your DCC app Are weak in BP?