UEFN publishing blocked by Experimental editor settings despite all flags disabled

General Issues and Bug Reporting
, ,
1

Summary

UndergroundEmpire cannot be published: Creator Portal reports “Experimental Features - Experimental editor setting(s)” although every Experimental Access and Beta Access option is disabled. UEFN reports Ready to Publish, but the portal keeps Continue disabled. The staged ExperimentalSettings.json contains 10 settings, all with bIsEnabled=false. Latest private version: 3536-6310-9511. Please identify the exact setting or asset being flagged.

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Publishing

Steps to Reproduce

  1. Open UndergroundEmpire in UEFN 42.40.
  2. Disable every Experimental Access option, Scene Graph System, Custom Items and Inventory, Python Editor Scripting and UEFN MCP Toolsets.
  3. Build Verse successfully, upload a new private version and run memory calculation in the connected session.
  4. UEFN reports Ready to Publish, with no experimental issue and memory 20,876/100,000.
  5. Open Creator Portal > Publishing > Private Versions > Create release for 3536-6310-9511.
  6. Wait until the portal checks finish. Experimental Features remains red and Continue is disabled.

Expected Result

Creator Portal should pass the Experimental Features check when all staged experimental flags are false and UEFN reports no experimental issues. If an asset or setting is still invalid, the validator should identify it explicitly.

Observed Result

Creator Portal passes Version Type, Download Size, Memory Usage, Asset Status, Verse Validation and In-Island Transactions, but fails Experimental Features with “Experimental editor setting(s)”. Continue remains disabled. The same private version passes the UEFN Publishing Report. The error persists after disabling Python, MCP and Scene Graph and uploading a new private version.

Platform(s)

windows

Island Code

3536-6310-9511

Upload an image

msedge_pnJ0qV23Sa.png
msedge_pnJ0qV23Sa.png826×841 134 KB

2

Hi @Uilki1,

Thanks for reporting this - we’ve had issues like this reported previously and all of them had some deprecated device within the game.

I’ve sent this internally to be reviewed, as soon as I hear back what is blocking your publishing I’ll respond back

3

@Uilki1, I’ve got confirmation that this device is the issue:

Device_Skydome_V2_C_UAID_94BB43183B0F5F0E03_1098591340

You should be able to see this in your logs, it’ll look like this:

Saving object(Device_Skydome_V2_C_UAID_94BB43183B0F5F0E03_1098591340) will prevent publishing as it is marked as deprecated

So if you encounter the issue again in the future, look for anything marked as deprecated in the logs