nasty message, but it is all false. A most of these errors were actually correct and compiling them didn’t resolve the issue, but that was only because they had references to blueprints that had a compile error that, after compiling, resolved themselves, and thus many other blueprints were resolved as well.
I do know that most of the errors were caused from , because compiling them resolved the errors in some of the other BP’s.
I have no idea why these would go wrong, seeing as Dice is an older BP and has been working fine since its inception, and just now its acting up even though nothing has changed.
It might be worth noting that this was once a 4.13 game that was transferred to 4.14, but even still, this problem had not happened immediately upon switching.
When you say startup, are you referring to when you launch the editor or when you attempt to play the game? The most likely issue is the couple of blueprints you pointed out as having issues () were referencing or were referenced by other blueprints. When a blueprint that is being referenced by another blueprint changes, the second blueprint also becomes dirty until the original is compiled.
When I launched the editor. And that was the case with a lot of them. About three errors would go away when I compiled only one blueprint.
Oddly enough, after a few times this problem just vanished. Normally when I get these bugs they do go away after a few start ups. Sorry I couldn’t go more into detail about what I thought was causing this.
