@BIGTIMEMASTER Will be added in the next version as ALT + End / Home, you can rebind these if you would like to.
Also in case you don’t already know, the thumb buttons on your mouse this will activate the hotkeys but there is no way to rebind this in the engine.
you’re the best, thank you!
@BIGTIMEMASTER Added in 4.2.11
Sorry for the stupid question, but how do we get the latest version? I just noticed that mine is 4.2.2, but the epic launcher does not prompt me for an update. I looked at the github but didn’t see any version downloads. Is it still yet to be released?
@BIGTIMEMASTER The marketplace only updates plugins for the last 3 versions of the engine so if you are on an older version, you can’t get updates.
The alternative is that you download the plugin for say UE5.3 and recompile for what engine version you are using.
You can also post your github username here (or pm me) and I will invite you to the source repo where you can grab the latest version.
Just bought the plugin and I have an issue where UE (5.3) freezes if I use e.g. ‘F’ shortcut to format nodes or try to create a new node with Tab. Everything becomes blurry and UE uses more and more memory (until I force stop it).
Before pressing ‘F’:
After pressing ‘F’:
The plugin version I’m using is 4.2.12. The issue didn’t crop up when I played around with just a couple of print string nodes (in the same BP the example crash appeared) but it seems to constantly crash the engine when I try to use it to anything more complicated.
Hi @Hemuli431, sorry about this. I’m pretty certain the size progress overlay is causing this. To get an accurate size of the nodes, the plugin needs to zoom in on each node on the graph, I temporary hide this by drawing an overlay of the graph while it is doing this process.
Could you try disabling the setting ShowOverlayWhenCachingNodes, you can find this setting by searching in the Editor Preferences.
This should show the graph jumping around for a very brief period of time when you press F and hopefully not freeze while doing it.
But this jumping process will only happen once per node since it will save the data for later use. To do it again for testing, you need to force refresh the node size by selecting the nodes and pressing CTRL + SHIFT + R.
Let me know if disabling this setting fixes the freeze. I suspect this is directly related to the way I’m drawing the graph onto the screen using a render target.
Thanks for the reply! I disabled the ShowOverlayWhenCachingNodes setting, but the crash still happens. The result is the same whether I just press ‘F’ or CTRL + SHIFT + R — it jumps around and freezes in a zoomed-in view.
before pressing F / CTRL+SHIFT+R:
after (when it no longer jumps and freezes):
I tried to disable other plugins that affect the BP graph view (auto size comments and advanced commenting) but unfortunately that didn’t fix the issue.
Hmm that is strange does the engine crash or just freeze up? If the size caching operation is getting stuck you can try pression ESC and it should cancel it. Although if you try format the nodes again I assume you’ll get into the same locked state.
Otherwise if the engine is actually crashing, do you get a crash report stating which line of code this is coming from?
It just freezes up, so there’s no crash report. Tried to press ESC but that didn’t do anything. Also just waiting didn’t help either.
I tested different combination of nodes. The freeze up happens when event beginplay is connected to set timer by event that is connected to a custom event. If any of these three nodes is not connected, there are no issues.
Replacing Event BeginPlay with a custom event also causes the issue. Connecting binary variable to Set Timer by Event’s Looping pin does not cause issues as long as the event pin is unconnected. Tried the ‘F’ on other blueprints that do not have Set Timer by Event and there were no issues. So I think the combination of event → set timer → event is the culprit. And it has to be an event connected to the timer, just connecting print string to it didn’t cause anything.
Testing this case with the 3 nodes on a fresh project does not cause this behaviour on my side.
Since you are unable to press ESC I assume it must be getting stuck in an infinite loop somewhere which is why your editor is completely freezing.
Now the question is whether it is in the formatting or the size caching logic.
Could you go your Blueprint, in the toolbar click on the BP Assist button (next to compile) then go to AutoFormatting and change it to Never auto format.
If you try to Refresh the node sizes with CTRL + SHIFT + R does it still crash?
If this avoided the crash, then it would be due to the formatting. If so: could you see if it is due to the delegate pin being linked to this external Custom Event? So on the SetTimerByEvent instead of using linking to Blinking, could you try linking this to a CreateEvent node?
With Never auto format, using CTRL + SHIFT + R does not cause the crash. With the CreateEvent connected to Set Timer by Event (like below) the crash does not happen whether or not the Never auto format is on or not.
Thanks for helping out, this narrowed it down a lot. I forgot to ask earlier, but could you post your plugin settings too just in case.
You can press CTRL+SHIFT+K to bring up the Open Window Menu then search for Blueprint Assist to open it in the Editor Preferences. Then clicking on the Export button in the top right will give you an ini file.
I think it is unlikely the other settings (in BA advanced / BA editor features) are causing this, so you don’t need to export those.
Will try to figure this one out asap.
Here is the ini file. No rush! I’ve been really enjoying the plugin a lot despite this issue.
Another setting that may help you is disabling the setting TreatDelegatesAsExecutionPins. I believe disabling this should also stop the crash and still allow you to link directly via delegate wires.
With this setting off, it basically ignores the delegate red wires. So in your screenshot with the timer, this will treat BeginPlay and Blinking as seperate and you will need to manage the “node trees” individually.
Yes, it fixed the crashes completely and I changed the other settings back to default and still everything is fine. Pushing a button a couple extra times when managing the branches is not a big deal to me. Thank you!
I cant find this options anymore…it started to insert nodes in the middle again.
How do I fix it?
this…changed the option again? it came back
Hi, these settings have moved to: Editor Preferences > Blueprint Assist Editor Features
I think the setting you want to disable is AlwaysConnectExecutionFromParameter
PSA if you have updated to 4.2.13:
There is an issue when using CTRL + LMB to disconnect a pin. I have submitted a fix for this, should be out in a few days.
In the meantime you can fix this issue by going to Editor Preferences > Blueprint Assist Editor Features and changing the hotkeys to CTRL + ALT + LMB / RMB like shown below:
Be careful not to remove the all the modifier keys, as this can cause issues (also fixed in the next update) you may need to manually fix your ini file to resolve this.
