HarvestNodeConnections crashing the game

[glitchysparx]

I have a lot of problems with your plugin. Almost each time I open the asset (one same asset not all assets) I have a crash in the UE delegates implementation. However, if I will not open the asset in the Editor but in the Game, it will crash in the function HarvestNodeConnections:

because GetGraphNode() is not valid in the Node.

I press Validate and Save button in the Asset Editor but it doesn't help for next time I startup the project.

This asset is a root asset in the flow sequence:

[MaksymKapelianovych]

Can you provide more info about the problematic node? Which node type is this and how is it set up?

[glitchysparx]

@MaksymKapelianovych sure.

this root asset is a flow asset consists of subgraphs mainly.

but we don't even implement the FlowNode_Start. It's not our node

[glitchysparx]

@MaksymKapelianovych seems like verifying the validation of the GetGraphNode() would fix the crash but I don't know what logic do I need to implement in such use case (when it not valid) to not get another unlimited amount of new errors

[MaksymKapelianovych]

Okay, what do you mean by "open asset in the Game"?

[glitchysparx]

@MaksymKapelianovych "open asset in the Game" == "start the flow sequence". In such case I get that error above

[glitchysparx]

@MaksymKapelianovych when I open this same asset in the Editor I get another error:

[glitchysparx]

@MaksymKapelianovych so 2 different errors with the same asset in different running modes (Editor and Game). I would fix the asset or add some functionality, I just don't understand the nature of this error

[MaksymKapelianovych]

Are you talking about this? 🙂

[glitchysparx]

@MaksymKapelianovych nope. About PIE.

[MaksymKapelianovych]

It seems you have modified or outdated version of Flow, your line numbers on images do not match with repo

[MaksymKapelianovych]

Please update plugin to the last version and if this issue will persist, ping me, I will be able to help then.

[MothDoctor]

Hey, it seems this asset either has a fully created node (Flow Node itself added, but no Graph Node representation for some reason) or not-fully removed one. Hard to tell what caused it, as I haven't encountered such issues for years.

This shouldn't ever happen. I would recommend you temporarily add non-crashing null checks. Open asset, and copy-paste its graph to another asset. Remove the old asset, revert these null checks, and check if everything works fine. This might be the best approach as it's impossible to guess what might cause it.
Especially since a lot of graph processing code changed lately. It might be counter-productive to look into that further if an issue occurs only in a single asset.