there is a workaround for this issue, as i’ve run into this problem a lot using aiperception components as well as procedural mesh components. if you’re using blueprints, don’t add the component in the components tab (meaning don’t use the +add component button). instead, in the construction script, add the component using a node i.e. “add ai perception component” or “add procedural mesh component”. then, assign the returned value to a variable. use that variable to do all your logic stuff. this method seems to bypass all of the registration problems causing the fatal errors, and actually allows for a null value where you can check if the variable is valid anyhow. fractionally larger overhead, but it works.