EDIT: I’ve spent more time playtesting this issue and have narrowed it down further. New, edited repro steps are as follows:
Repro:
Make a blank project
Add any Blueprint. (tested with “Actor”, “Character”) Blueprint window MUST be open in full screen mode for the bug to occur.
Add an input key event. (I’ve tested with “i”, “h”, “m”)
Add any other node but leave it disconnected. (Tested with “get” node and a few others)
Add another input key node
Editor crashes with no callstack available.
To sum up: with a blueprint in fulls screen, if you add an input key node, then another node that is not an input key, the next input key node you add to that blueprint will crash it.
I’m experiencing what I would term as general instability around adding nodes to a blueprint after adding an input key, in addition to the specific repro I’ve listed above. For instance, adding a comment after adding an input key is crashing it as well.
I’m trying to reproduce your crash and having a little trouble. Here are the steps I’m following.
Create a new blank project with no starter content on my D: drive. I name the project ‘HyperloopTesting’.
Right click in the Content Browser and click ‘Blueprint’ to create a new blueprint. I base it on Actor and name it TestBP.
I double-click on TestBP, which opens the Blueprint Editor. I maximize the Blueprint Editor.
In the Blueprint Editor, I right-click and type ‘h’, then select the ‘h’ input node.
I right click and type ‘get’, then select the ‘get’ array node.
I right click and type ‘f’, then select the ‘f’ input node.
It sounds like you’re getting a crash at this point, but I am not. I’m also on Windows 7, 64-bit. I’m using two monitors, but I also tried this without the second monitor.
Am I following your steps correctly?
(I also tried creating comments after creating input nodes, but I wasn’t able to reproduce that crash either.)
I realize now that there may be two ways to full screen that window - I am placing it in a tab within the editor by dragging it up to the top bar area.
Only other thing I can think to have you try is to add the same input key node in both steps (try “i” in step 4 and step 6 for instance).
I’m reproducing it consistently on my end even after restarting and re-installing 4.5.1 but maybe it’s some oddness specific to my system, or graphics driver. I’m using a Nvidia 560ti on a single monitor.
It first happened after I used the ‘load streaming level’ node, but I was able to repro it with any node after that so I concluded it was not anything to do with that particular node initially.
I did also notice that after it happened the first time, the launcher would hang and crash out when verifying the install, which is what led me to re-install. The crash persisted after the re-install though.
I’ve confirmed it does not happen in other versions of the engine for me, just 4.5.1
I’m still not able to reproduce the issue, but one of my coworkers is able to on his machine. We’ve reported it internally and will investigate the issue further.
As a side question, when you are creating an input node, do you see the ‘key event’ icons, or do you see a white box?
I’ll try to confirm your question about the icons when I get back to my workstation. I’m glad somebody was able to reproduce this, I was afraid I was goin’ nuts hehe.
