Warnings in WindForce uasset due to module dependencies

It seems that when a project references Engine/Plugins/FX/Niagara/Content/Modules/Update/Forces/WindForce.uasset the engine generates several warnings complaining about failing to load ChaosNiagara types.

It seems that ChaosNiagara loads in Default but Niagara and NiagaraCore load in PreDefault, moving ChaosNiagara to PreDefault fixes this for us.

2025.05.30-15.02.18:190][ 0]LogLinker: Warning: [AssetLog] C:\dev\MyProject\Engine\Plugins\FX\Niagara\Content\Modules\Update\Forces\WindForce.uasset: VerifyImport: Failed to find script package for import object 'Package /Script/ChaosNiagara' [2025.05.30-15.02.20:200][ 0]LogNiagaraEditor: Warning: Pin states that it is of class type, but is missing its class object. This is usually the result of a registered type going away. Pin Name 'Module.Physics Field' Owning Node 'NiagaraNodeParameterMapGet /Niagara/Modules/Update/Forces/WindForce.WindForce:NiagaraScriptSource_1.NiagaraGraph_0.NiagaraNodeParameterMapGet_10'. [2025.05.30-15.02.20:200][ 0]LogNiagaraEditor: Warning: Pin states that it is of class type, but is missing its class object. This is usually the result of a registered type going away. Pin Name 'None' Owning Node 'NiagaraNodeParameterMapGet /Niagara/Modules/Update/Forces/WindForce.WindForce:NiagaraScriptSource_1.NiagaraGraph_0.NiagaraNodeParameterMapGet_10'. [2025.05.30-15.02.20:200][ 0]LogNiagaraEditor: Warning: Pin states that it is of class type, but is missing its class object. This is usually the result of a registered type going away. Pin Name 'Module.Physics Field' Owning Node 'NiagaraNodeParameterMapGet /Niagara/Modules/Update/Forces/WindForce.WindForce:NiagaraScriptSource_1.NiagaraGraph_0.NiagaraNodeParameterMapGet_10'. [2025.05.30-15.02.20:200][ 0]LogNiagaraEditor: Warning: Pin states that it is of class type, but is missing its class object. This is usually the result of a registered type going away. Pin Name 'None' Owning Node 'NiagaraNodeParameterMapGet /Niagara/Modules/Update/Forces/WindForce.WindForce:NiagaraScriptSource_1.NiagaraGraph_0.NiagaraNodeParameterMapGet_10'. [2025.05.30-15.02.20:201][ 0]LogNiagaraEditor: Warning: Pin states that it is of class type, but is missing its class object. This is usually the result of a registered type going away. Pin Name 'Physics Field' Owning Node 'NiagaraNodeFunctionCall /Niagara/Modules/Update/Forces/WindForce.WindForce:NiagaraScriptSource_1.NiagaraGraph_0.NiagaraNodeFunctionCall_7'. [2025.05.30-15.02.20:202][ 0]LogNiagaraEditor: Warning: Pin states that it is of class type, but is missing its class object. This is usually the result of a registered type going away. Pin Name 'Module.Physics Field' Owning Node 'NiagaraNodeParameterMapGet /Niagara/Modules/Update/Forces/WindForce.WindForce:NiagaraScriptSource_1.NiagaraGraph_0.NiagaraNodeParameterMapGet_10'. [2025.05.30-15.02.20:202][ 0]LogNiagaraEditor: Warning: Pin states that it is of class type, but is missing its class object. This is usually the result of a registered type going away. Pin Name 'None' Owning Node 'NiagaraNodeParameterMapGet /Niagara/Modules/Update/Forces/WindForce.WindForce:NiagaraScriptSource_1.NiagaraGraph_0.NiagaraNodeParameterMapGet_10'. [2025.05.30-15.02.20:202][ 0]LogNiagaraEditor: Warning: Pin states that it is of class type, but is missing its class object. This is usually the result of a registered type going away. Pin Name 'Module.Physics Field' Owning Node 'NiagaraNodeParameterMapGet /Niagara/Modules/Update/Forces/WindForce.WindForce:NiagaraScriptSource_1.NiagaraGraph_0.NiagaraNodeParameterMapGet_10'. ...

Steps to Reproduce
Create a project that uses Engine/Plugins/FX/Niagara/Content/Modules/Update/Forces/WindForce.uasset

See warnings when starting editor.

Hi Diego,

Unfortunately I was not able to reproduce this bug. The things I tried were as follows;

I created a new empty project with starter content. After that I created a new Niagara system based on Blowing Particles template. This template has WindForce on it by default. The system was created fine, and after dragging it into the scene it displayed fine. PIE also worked properly, with no warnings. After this, I thought to close the editor and restart, with the default map set to my test with the effect in it. Everything was still working. I then made a second system based on the default system, and manually added WindForce to it, then repeated the same steps, and still no dice.

This all being said, I dug into some case history, and it seems you’re not the only person to have seen this. Here is a case logged just two days prior to your own that seems eerily similar.

[Content removed]

If there are any other details you can think of that would help get out a reproduction case, they would be much appreciated.