Weird behaviour, when trying to attach components to (yet unassigned) skeletal meshes in C++
While setting up a player character in C++ I was trying to attach some SceneComponents (in that particular case a CameraComponent) to a specific bone/socket of the characters skeletal mesh.
The problem was, that I didn't want to further specify my skeletal mesh in C++ but rather create a blueprint out of my C++ class and assign the mesh there (in order to keep my C++ code clear of any assets).
So I was basically trying to use a socket in my C++ constructer, that didn't exist at that point of time. It simply didn't work.
Things started to get weird when another user suggested to create a second camera (with identical properties) and attach it to my mesh as well.
It worked, both cameras behaved like originally intended and sticked to the assigned socket. I would just like to understand why so I can work around this problem in the future (allways creating spare-components isn't a solution). The user who suggested this workaround blamed this behaviour on an engine bug.
Could that be the case? Or did I cause this error?
If you need more details, feel free to take a look at the original quetion:
Thanks in advance!
Follow this question
Once you sign in you will be able to subscribe for any updates here