Well the problem is, the Construction Script is not “easy” at all.
There is no plug and play version of it in C++.
I already tried that a few months ago. You need to actually remove your Instances again, before spawning new once.
The Construction Script handles that a bit different. All in all, that’s why no one can give you a clear and straight answer.
The Construction Script is not an actual function that you can call in your C++ Class and it will do the same stuff for you.
You could just create a function with the “AddStaticMeshComponent” stuff, and make it “BlueprintCallable”. Then let the
derived Blueprint Class call it in its Construction Script.
There is no shame in using a Blueprint as a last C++ Child Class. It’s even recommended to combine your C++ with Blueprints.
Question: Why exactly does your Solution from the other Thread crash? Do you have any Crashlogs and Errorlogs, which you could post?
Maybe it’s something simple.