Creator Portal incorrectly detects Experimental editor settings and prevents publishing my UEFN project.

[ElKevox]

Summary

My UEFN project cannot be published because Creator Portal reports “Experimental Features – Experimental editor setting(s)”, even though no settings under Experimental Access are enabled in UEFN.

The only enabled features are Scene Graph System and Custom Items and Inventory, which are listed under Beta Access, not Experimental Access.

I also verified all 25 Verse files in the project and found no experimental Verse APIs. Creator Portal confirms that Verse Validation compatibility checks are complete, Asset Status shows No issues, and all other publishing validation checks pass.

I also disabled Python Editor Scripting and UEFN MCP Toolsets and created a new private version, but the publishing validation still reports the same Experimental Features error.

Because the validation message only says “Experimental editor setting(s)” and does not identify the specific setting causing it, I cannot determine what is preventing the project from being published.

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Publishing

Steps to Reproduce

1. Open an existing UEFN project.
2. Verify that all settings under Project Settings > Experimental Access are disabled.
3. Keep Scene Graph System and Custom Items and Inventory enabled under Beta Access.
4. Build Verse successfully and verify that no experimental Verse APIs are being used.
5. Create and upload a new private version of the project.
6. Open the private version in Creator Portal and attempt to publish it.
7. Creator Portal passes Version Type, Download Size, Memory Usage, Asset Status, Verse Validation, and In-Island Transactions.
8. Publishing is blocked under Experimental Features with the message: “You can’t publish while these experimental features are enabled: Experimental editor setting(s).”
9. Creator Portal does not identify which editor setting is considered experimental.

Expected Result

Creator Portal should allow the project to proceed through publishing when no Experimental Access features or experimental Verse APIs are enabled. If a setting is preventing publication, the validation message should identify the exact setting that is considered experimental.

Observed Result

Creator Portal blocks publishing and reports “Experimental editor setting(s)” without identifying the setting, even though Experimental Access settings are disabled and Verse Validation passes successfully.

Platform(s)

Unreal Editor For Fortnite

Upload an image

[rhyan.smith (Rhyan)]

@ElKevox

Thanks for reporting this.
Wanted to know if you have ever turned on any of the experiments? Possibly camera components, animations or ability template experimental settings?

[ElKevox]

No, I’ve never activated any experimental feature; it’s always been exactly as shown in the image I attached.

[rhyan.smith (Rhyan)]

What’s the island code?

[ElKevox]

The public version is: 6234-7676-8241

[Flak]

Saving object (ControlInput_player_input) will prevent publishing since it’s deprecated.

[ElKevox]

@Flak

ControlInput_player_input

Thank you! That could be very relevant to my issue. Do you know where I can find ControlInput_player_input in UEFN, or how you identified which asset/object had it saved? My Creator Portal is blocking publishing with “Experimental Features – Experimental editor setting(s),” while ValkyrieValidator_ExperimentalSettings reports no invalid experimental settings.

[ElKevox]

Thank you so much for your help! Your comment about ControlInput_player_input was exactly what led me to the solution.

I checked my project and found that a Nitro Drifter Sedan Spawner was still saving the deprecated ControlInput_player_input component. I removed the vehicle, cleaned the remaining reference, validated the project again, and created a new private version.

It worked! The new version was approved and I can publish again with no Experimental Features error.

I had been troubleshooting this issue for quite a while, so your information was incredibly helpful. Thank you again for taking the time to point me in the right direction!

[Flak]

Awesome news! Thank you for the update.

I was coming back here to post this

In the Outliner → search NitroDrifter; the actor is Device_NitroDrifterSedan_C_UAID_28D0438346C5EDDA02_2144933490. Its Details should list a component ControlInput_player_input (validator shows its InputActionBindingData is empty/default, so nothing is lost). Delete the device, place a fresh Nitro Drifter Spawner, re-wire, save, upload a new version.

[Bug-Reporter]

FORT-1162114 is ‘Closed’ as ‘Fixed’. The issue will be addressed in 42.20.