Hello,
thanks for the fast response!
I did what you suggested and recreated the problem with a clean project.
1.: I opened a new TopDownTemplate; UE 4.9.2
2.: Added a socket on the TopDownCharacter.
3.: I opened the TopDownController and created a new function that takes in an actor and, via the “Attach actor to component” node, attaches it to the aforementioned socket on the mesh of the TopDownCharacter.
4.: I imported a sword mesh & textures, then set it up as an actor.
=> Blueprint: On BeginPlay, it enables the input on the actor. On the press on a button, it casts to the TopDownController and calls the function I’ve created, with itself as the actor to attach.
As far as I can see this worked absolutely fine…
5.: … until I tried to change the mesh of the TopDownCharacter to a custom mesh (which, in my original project, had functioning animations etc.). I created a socket on it’s skeleton and set the animation controller to “None”; so it’s sliding around in t-pose.^^ Now with my own mesh as the TopDownCharacter, the crashes returned instantly: Press “O” to attach sword to hand => complete system crashes down in a matter of seconds.
Right now I can’t even give you screenshots of the blueprints because I can’t reopen the project again - the crashes seem to have completely broken it. Tomorrow I’ll try to recreate the whole thing again, reopen a new project, provoke the crash and hope that it doesn’t fry my blueprints.^^
As about the call stacks: If you mean the error log that pops up after the engine “normally” crashes (which it does now and then…^^) - I don’t get one. The whole system just crashes and I have to hit the reset button on my pc. Or are there any other logs that I just don’t know about right now?
Thank you very much!