BUILD FAILED. Errors unfixable.

Hi. I had a project which ran fine on an older version of engine 4.12. My computer broke and I got a new one. I have set up visual studio and unreal engine like usual, but when I try to package my game it fails both in 4.12.5 and 4.13.

In the log I see some possible causes, but the errors won’t go away even though I fix the problem in the code.

Ensure condition failed: AttachmentRules.LocationRule == EAttachmentRule::KeepRelative && AttachmentRules.RotationRule == EAttachmentRule::KeepRelative && AttachmentRules.ScaleRule == EAttachmentRule::KeepRelative [File:D:\Build\++UE4+Release-4.12+Compile\Sync\Engine\Source\Runtime\Engine\Private\C
omponents\SceneComponent.cpp] [Line: 1482]

AttachToComponent when called from a constructor is only setting up attachment and will always be treated as KeepRelative. Consider calling SetupAttachment directly instead.

I have tried to fix this by chaning AttachToComponent(DummyRoot, FAttachmentTransformRules::KeepWorldTransform) to SetupAttachment(DummyRoot), but the eror keep showing up when I try to build.

LogModuleManager:Warning: No filename provided for module ExampleDeviceProfileSelector
LogModuleManager:Warning: ModuleManager: Unable to load module 'ExampleDeviceProfileSelector' because the file 'C:/Program Files (x86)/Epic Games/4.12/Engine/Binaries/Win64/' was not found.

I have tried fixing this by disabling the ExampleDeviceProfileSelector plugin. I disabled it in the editor. I have also checked that it is infact disabled in my uproject file.

My question is why these errors keep showing up?

Many Thanks.

This problem first happend in 4.13.0. Then the same behaviour happend in 4.12.5. Upgrading the project to 4.13 fixed the problem again. Strange…

First error/warning gives you the fix - SetupAttachment()
SetupAttachment() should be used at construction.
AttachToComponent() should be used during runtime.
You must have a C++ class calling AttachToComponent() or similar in its constructor.

The ExampleDeviceProfileSelector I cannot answer, as we get it and have never been able to fix it :frowning: