The new 'UncookedOnly' module type that was added in 4.24 is not visible to Blueprint nativization, and thus it does not know to exclude these module types from the generated Build.cs file when they are found to be a dependency of the Blueprint asset.
Current suggested workaround (from the forums):
To get around this you can manually set the package flags. PKG_EditorOnly or PKG_Developer should work. You can see where they're normally set under CodeGenerator.cpp I did this during module startup and it seemed to work without issue. Code: void FYourEditorModule::StartupModule() { const FString LongName = FPackageName::ConvertToLongScriptPackageName(TEXT("YourEditorModuleName")); if (UPackage* Package = Cast<UPackage>(StaticFindObjectFast(UPackage::StaticClass(), nullptr, *LongName, false, false))) { Package->SetPackageFlags(PKG_EditorOnly); }
For testing: See [Link Removed] (Expected result: Match3 should continue to be able to be packaged successfully with nativization enabled after this fix).
I am not able to find world outliner how to enable it?
How to achieve HLSL Multiple Render Target in Material blueprints?
Delay nodes occasionally don't fire the "Completed" output in a nativized build
How can i modify the param name in EQS node
How does TextureRenderTarget2D get TArray<uint8> type data?
Undefined sysmbol: typeinfo for AActor when cross-compile linux dedicated server on windows
How to convert the datasmith scene file to BluePrint. Create animations in BluePrint.
Why doesn't the collision diminish when the collision radius decreases?
There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-86099 in the post.
1 |
Component | UE - Gameplay - Blueprint |
---|---|
Affects Versions | 4.24 |
Target Fix | 4.25 |
Created | Dec 20, 2019 |
---|---|
Resolved | Jan 10, 2020 |
Updated | Mar 5, 2020 |