Blueprint Assist Plugin

[fpwong]

Thanks @TheSilver812, I have confirmed this is due to some changed settings in the plugin. If you import the default settings here it should fix these issues (Editor Pref > Blueprint Assist > Import button in top right).
v4217-DefaultBlueprintAssistSettings.ini (5.8 KB)

You can see all the settings you have changed in your project here: BA Setting Diff - Diffchecker

The problematic ones are in BlueprintFormatterSettings where the padding is set to (75, 50). I need to put a warning for this setting, basically the y-padding cannot be less than the BlueprintKnotTrackSpacing(26) * 2 otherwise it thinks all the reroute tracks are overlapping.

The other setting is ExecutionWiringStyle and ParameterWiringStyle which are both set to MergeWhenNear. This seems to be triggering that “Badly linked reroute node” warning. I will look into why this is happening but I suggest you keep these as AlwaysMerge for now.

Hopefully that fixes all the problems you were having, do let me know if you find any other bugs!

[TheSilver812 (Silver812)]

As always, most of the problems come from the user changing things that they are not sure what they do . My bad…

I’ll be using those settings from now on. The only issue that persist is this weird behavior where some of the lines go under all the code. Like this:

Or here:

I guess this might be quite harder to debug so I wish you good luck with that.

Have a good day! And thanks for being so helpful!

[fpwong]

Hmm so I am not getting any of the formatting issues in the 1st screenshot but am able to recreate the issue for the 2nd screenshot.

Just to make sure we are on the same page, could you check you are on the latest version of the plugin (v4.2.17)?

[TheSilver812 (Silver812)]

Yes, I am on that version. All I can say is that having comments do have an impact on it. This is a comparison using left hand side style with and without comments:

[fpwong]

Previously someone else had posted a similar issue to this but I was never able to replicate it.

Could you see if you have the same problem? Specifically in this example:

Extra Reroute Nodes

[TheSilver812 (Silver812)]

Yes, I also have that bug now that you mention it. Here are a few examples:

This is using version 4.2.17, with your default settings and left hand side style.

[fpwong]

Hi again, I looked through the code and did see something which may be the cause of this (still unable to replicate on my machine).

I’ve sent you a test fix to your email and some instructions on how to get it working, please let me know if this fixes it.

[TheSilver812 (Silver812)]

Ok so good news, the “Extra reroute node” bug seems to be fixed. It went from this:

To this:

It still has the problem of the weird “Lower/Under reroute nodes” as you can see, but it’s definitely an improvement. Though I have no clue why you don’t see this behavior even with the same project.

[fpwong]

Hi @Silver812, sorry for the late reply. I just had another look at this.

Could you try adjusting the setting Parameter Vertical Pin Spacing from 26.0 to 30.0 and see if this issue (using the test hotfix I sent you earlier).

If this does fix it, can you check if changing this to 26.1 also fixes the issue?

[TheSilver812 (Silver812)]

No worries mate, you are helping so take all the time you need.

Both 30 and 26.1 do seem to fix most of the “Lower/Under reroute nodes”.

From this:

To this:

Or from this:

To this:

Although in this last example applying the fix seems to also propagate the issue to other green lines from the white ones.

Another problem is that it does not seem to fix the extreme edge cases where there’s a lot of nodes in one place, like here (see white line):

I see that a red line appears in this last example, so the system does know it’s not managing this case well.

Overall, I’d say it’s an improvement though, thanks!

[fpwong]

Hi @TheSilver812, I sent you another hotfix. Let me know if this one works!

[TheSilver812 (Silver812)]

Hello again @fpwong, the issue with the white lines seems to be resolved, for example you can compare the last picture in my last post with this one:

The bad news is that the “extra reroute node” reappeared. Here’s example of it, from this:

To this:

Before making any formats with the new build, I clicked on the “Reset to defaults” button on the settings, I hope that was okey. All parameter spacing values were back at 26.

[fpwong]

Hi @TheSilver812, sent you another hotfix. Hopefully this will be the last one

[TheSilver812 (Silver812)]

All bugs solved, thank you very much!

[fpwong]

Fix is live now (v4.2.18)

[fpwong]

@FroltBolt Hi I saw your question on the Blueprint Assist marketplace page. Seems to be a problem with that page, I am unable to reply there right now.

Question for context:

This is a bit tricky to describe, but hopefully i can get the point across.

When i have multiple nodes selected and i want to move them all by click + drag with the mouse this does not work when the location you clicked was the “left half” text/name of a variable.

I know that when you click the “right half” of the text/name, it will create a new wire, but UE5 default is that i can move multiple nodes when clicking on the left side text.

This might sound minor, but it’s pretty annoying when i want to drag my nodes and i lose my selection.

Looking at this example below: if you select all 4 nodes here, you are unable to click and drag to move them when you are hovering the green area in My Var?

If this is correct, I am not able to replicate this issue on my side.

Could you check you are on the latest version of the plugin (4.2.18)?

If you could also export your plugin settings, that would be very helpful. You can do this by going to Editor Pref > Blueprint Assist and in the top right corner there is an export button. Then also doing the same for Editor Pref > Blueprint Assist Editor Features.

[FroltBolt]

Hi,
thanks for the reply.
Hopefully the attached video explains it a bit better.
I can of course give you my plugin settings etc, by let’s just see if we agree that this is actually a bug and we know what we are talking about

[FroltBolt]

This is what the behavior is without the plugin.
Notice i can drag all nodes even when the drag starts at the node name, as long as it is in the “50% left part of the node”

[fpwong]

@FroltBolt Hi, fixing this issue will require quite a bit of a rework and a lot of testing, for now I am not going to look into this.

Basically I have an assumption in the plugin that if you select a pin you have ONLY that node selected too. So when you click a pin, it removes the other nodes from your selection, causing this issue.

---

A workaround (that is currently broken…) is binding a key to work as an Additional Drag Node. You can find this at Editor Pref > Blueprint Assist Editor Features > Additional Drag Nodes Chords. This should function the same as holding down LMB to drag except ignore any interactions you might get from clicking.

However testing this now, I realise that it suffers from the same problem – if you hover a pin it won’t drag correctly. I will push an update to fix this soon.

[FroltBolt]

That is understandable.

Not sure if the workaround requires me to use a different drag key than LMB, which would probably be more annoying than the current issue.

Anyway, thank you for looking into this, and I also have to say that the plugin is really fantastic.
Even though I only use a fraction of the features available, the ones I use are big time savers