I’ve recently switched to UE5 and there’s a difference between UE4 and UE5 in how comments on nodes (not comment boxes) are handled. Specifically, node comments appear to be completely ignored by the formatting algo.
In UE4 I usually had to manually refresh the node (via Shift+Ctrl+R) that I added comments onto for Format Selected (F) to work, but it did work and format according to the comment size. That no longer happens in UE5.1 (didnt test 5.0), which results in stuff like this:
I have another request that is more of a new feature: the ability to locally enable/disable the functionality of the plugin, without actually disabling the plugin.
We have some team members that prefer not using Blueprint Assist (clearly they are crazy but I’ll try not to judge them…), but the only way (that I know of anyway) to disable its functionality is to disable the plugin in the .uproject. On a source-controlled project, that isn’t a realistic solution because it forces you to keep the uproject file checked out, and at some point it will need to be reconciled and less-technical people might run into problems.
I had implemented this myself a few years ago on an older version of the plugin by modifying the source directly, but I feel like it would be useful as a built-in feature (and in a probably less hacky way than I had done it). I basically added a user-level (and not project-level) bool to the BPA settings that would early-return in the initialization of the plugin, effectively disabling without needing to actually disable it.
Nothing urgent, just something that would be nice if you get around to it.
The default privacy override for variables/functions is amazing and is something that should ship with UE, but the variable default privacy applies to Event Dispatchers since they are “variables”, and I feel like there should be an exception here since I don’t think that’s really ever a desired behavior (to have Event Dispatchers default to Private for example). Not sure if its possible for you to determine if its a normal variable or an Event Dispatcher and not apply the default privacy override in that case?
Thanks for letting me know, I’ll see what I can do about this.
Also did some testing, it seems like the access specifier label for EventDispatchers is always private, even if you untick private in the details. Is this the same for you?
The label still says Private yeah, which is weird. But there’s definitely a real difference between the Private checkbox ticked vs not in terms of being able to bind to that dispatcher.
Hi, thanks for reporting this. This seems to be a bug related to the setting Apply Comment Padding setting if you turn this off (you can do this in the Blueprint Assist toolbar settings), it will not cause it to be disconnected for this case.
Hard to say without seeing the build errors. If AddSymbolMenu.cpp was the last successful file to build then I am not sure, that file has not been changed for quite a while.
If you are not already, I suggest trying to compile the plugin by putting it in the Project/Plugins folder and compiling the plugin along with the project. It would be the easiest way of debugging issues.
That was in a project. I don’t know how to show more verbose output. And these builds are in parallel, so it may or may not be that file the issue.
I have tried different approaches like copy-pasting, restarting, deleting intermediates and etc. However, today I was able to build it. Therefore it was an unknown issue.
One of our devs ran into this issue where in ControlRig and AnimBlueprint editors, the D keyboard shortcut that is used as “disconnect pin link” is still active when that editor’s preview viewport is focused.
So if you have a pin highlighted and you go and WASD in the adjacent viewport, its going to disconnect that pin and you aren’t necessarily going to notice. The D input in the viewport is also just blocked unless you hold it for a few seconds.
For now we’ve disabled BPA in the ControlRig/AnimBlueprint types in the settings, but focusing the viewport in those editors should just remove any pin highlights. That is what happens in the Blueprint editor. I tested by re-docking the Blueprint Editor’s Viewport tab so that I would have a split view like in ControlRig/AnimBlueprint, and the highlight on the Frequency property in the example below will correctly disappear when I focus the viewport.
@BIGTIMEMASTER Hi, thanks for letting me know. I will fix this in the next update. Currently there is no built in method of deleting all groups. For now you can go into the json file located in your plugin folder:
The json file will be called %PROJECT_ID%.json. You can see your project id by going to your Project Settings and searching for project id.
Then you can search in the json file for the bugged blueprint by name. For example my blueprint BP_AIController will have a section /Game/Enemies/BP_FPAIController. You can delete this entire section from the json file.
