So I’m trying to follow along with the tutorial… Introduction to Third Person Blueprint game - 7 - Blend Spaces
on youtube. when I get to the part about putting the run anim at the top of the blend space graph ue4 will crash shortly after. This happenes everytime so far… 6/6 replicated.
It appears to be something to do with when you drag the assets from the box on the graph. it will crash 100% if you place the idle anim, then walk, then when placing the run anim, if the mouse touched the top border of the graph it’s insta crash. Tho it has crashed when just dragging the walk anim to the centre of the graph also.
upon further testing this is what I have discovered…
even if I place just one anim on the graph… I can then slowly move the mouse up the graph so that the orange ball moves upwards… then as soon as the orange touches the top of the graph it’s 'game over, man!..game over"
EDIT: on further investigation strange things become apparent. It seems to be connected to the blend space range. for example, if i set it to 0-349 i can play around all day and no crash. Change it to 0-350 however (or anything between 350-400) and it crashes as soon as you mouse over that orange ball at the top of the graph.
EDIT2: The crash only happens if you have the blend space graph displayed vertically. If you go with the default horizontal then everything seems to work fine. This is annoying as the Epic tutorial tells you to switch to vertical :\ otherwise I would have left it as it was and never found this problem. still… least now I can get on with stuff.
I have run a few tests and have been unable to reproduce this problem. In the attached image, you will see that I’ve tried to reproduce your issue by using both the vertical display mode as well 0-350 frames on a Windows 7 system in UE4.6.1.
In that case, when the editor crashed, the user pressed the copy callstack to clipboard button, pasted that into a doc and posted here, and then hit the submit button on the crash reporter pop-up window. -With all that information, our developers were able to isolate the issue and resolve it. However it may have been resolved for 4.7, which incidentally was released today.
Hence I recommend trying this with 4.7 or, if this is not possible, submitting the callstack and crash report as I’ve described above.
Thanks for the reply and trying to figure out the bug.
I’m happy to say that after updating to 4.7 i can no longer recreate the editor crash that I was experiencing.