Since October I’m experiencing very similar if not the same issue with all of my UEFN projects – of which most contain no Verse code. All of my three Windows 10 Pro 22H2 dev workstations appear to be having the same problem with plain vanilla installation that got auto-updated last year and now looks incomplete although Epic Game Launcher verification detects zero problems.
Yet, after launching UEFN is see these many (42) Load Errors that skip many /Game/Effect packages like:
While trying to load package /Game/Effects/Fort_Effects/Gameplay/Pickups/Effects/NS_Pickup_RareAmbient, a dependent package /Game/Effects/Niagara/DynamicInputs/TimeOfDay/FNTimeOfDayScalar was not available. Additional explanatory information follows:
FPackageName: Skipped package /Game/Effects/Niagara/DynamicInputs/TimeOfDay/FNTimeOfDayScalar has a valid, mounted, mount point but does not exist either on disk or in iostore. The uncooked file would be expected on disk at ‘C:/Epic/Fortnite/FortniteGame/Content/Effects/Niagara/DynamicInputs/TimeOfDay/FNTimeOfDayScalar.uasset’. Perhaps it has been deleted or was not synced?
Since then, I cannot enter any Live Edit or interactive project session in Fortnite as I run into two types of Asset Check issues (600+ in total) like:
LogValkyrieValidation: Error: Soft package /a8210d3a-42c7-90a6-1cc0-a0ae49ff81e0/Levels/Landscape is not referenced by any soft object path in asset …
LogValkyrieValidation: Error: Found disallowed object type /Script/Landscape.Landscape:PersistentLevel.Device_Collectible_Object_V2_C_UAID_3085A9982C48DAEB01_1534714704, Referenced by:content/externalactors/levels/landscape/9/5l/djkx2ltgdvn4drcjg63eou.uasset (Device_Tracker_V2_C),content/externalactors/levels/landscape/0/fo/j3rbhhnzp2wk5k6cvhyvg2.uasset (Device_AnalyticDevice_V2_C), Plugin mount point:/a8210d3a-42c7-90a6-1cc0-a0ae49ff81e0.
I suspect such error is throw for (virtually) all objects and devices in the scene. I puzzled how all my projects seem the have gotten inconsistent on the same date and upgrade of UEFN…
No response yet on these bug reports thus far: