[BUG] Crash due to TrashClass's property

Apparently I have an issue that took me an enitre weekend of tracking.

It started off with a really weird behavior. Whenever I compile a certain blueprint actor ( a char extended from Shootergame ) , simulating/playing the game would crash it WITHOUT fail. However, upon restarting it, I enjoy the saved change but doesn’t crash. Any change I make would crash it again. I look at the logs and I’m very positively sure it’s due to this line, because at every crash this appears.

[Line: 351]
‘AITestPawn_C_0’ is of class ‘AITestPawn_C’ however property ‘ObjectProperty_552’ belongs to class ‘TRASHCLASS_AITestPawn_198’

I continue tracking it ( all the way from behavior tree and to blueprint ) and I found that one specific function caused this. It’s a function that from a custom macro library.

Right now I have no idea how to replicate this. But I’ve manage to fix it by removing that custom macro library. Here’s the log and dump file to be examined.

link text

Hi ,

Did this start occurring after 4.2 or was it occurring before 4.2? If after 4.2, was the custom macro library function created before or after the 4.2 update? Thank you!

This is using 4.1.1. I am not using 4.2.

I did update to 4.2 but I did not make the project into 4.2 neither did am I running 4.2 editor

Hi ,

Is your project c++ or blueprints?

It’s from the shootergame. I’m testing the AI in shootergame

Is this an AI you built yourself or one that was already present in the shootergame example. If it was already present, please try deleting the shootergame content and get a new version that is up to date with 4.2, please let me know if this works for you. Thank you!

I am no longer getting this, but between then and now, there has been tonnes of changes.
I’m still on 4.1

If not, I will try to find the cause again if the crashed happen again .
But this is definitely NOT having anything to do with AI. Because I have tried on Empty AI Controller.

Either way, If nobody can tell anything based on the log, I will report again if it happens and try to diagnose it.