Can't publish due to "Experimental Features". Even though they're off

Summary

This is occurring in both maps I have tried to update today, after the update. When pressing the blue “Create Release” button on the Publishing page. At the bottom, it shows a red X next to “Experimental Features”. I have never used this setting on my map and double checked that they are toggled off.

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Publishing

Steps to Reproduce

Unknown. This occurred as of the last update. Nothing in my map has changed besides 1 texture update.

Expected Result

Publish just as normal.

Observed Result

Unable to publish due to false Experimental Features.

Platform(s)

PC

Island Code

2524-6026-4229

Upload an image


Same happening for me. Island Code: 0028-2305-8419 and 1854-3881-2050

Hey folks, could you get me your logs, please, so we can investigate?

How to get your Fortnite logs

FORT-985547 has been created and its status is ‘Unconfirmed’. This is now in a queue to be reproduced and confirmed.

The exact same thing happens to me, on my map and I only use entities.

This does not mean just experimental features from the project settings page this also includes Verse code so many functions have @experimental If you add any of these functions it will also flag. This is the confusing misconception.

Remove any of these verse () refs and itll work.

For example

If you use any of these it’ll flag up. There are more for ai ect just showing the @ tag so you see.

1 Like

@Flak my project yields the following warnings after local validation:

UEFNValidation: /project/GameFeatureData Validating asset
UEFNValidation: Warning: /project/GameFeatureData Project settings has experimental settings enabled which will prevent publishing.

I even tried to recreate the file, but it still results to this validation issue.

All experimental features are off and were always off.

Toggling them on and off also didn’t change anything.

1 Like

I managed to recreate this issue on completely new project by just enabling “One File Per Entity”.

1 Like

They can be found here: Logs

The Red Vs Blue 1854-3881-2050.zip (13.3 MB)

Pit Royale 0028-2305-8419.zip (12.9 MB)

Disabling one file per entity on my end fixed the validation warning.

Now my island has finished being on discovery (THE RED VS BLUE 1854-3881-2050) Island is now unpublished until issue is fixed. That way to prevent players playing a broken/buggy map without updates.

We are also having this issue, we are not attempting to publish. We have never used any experimental features and don’t use any Beta features either

The team is working on this. Thank you for the detailed info!

1 Like

Posting this in the known issue thread, even though all of you already know :wink:

We’re investigating an issue where creators may be blocked from publishing and receive an “Experimental Feature” flag, even when there are no experimental features on the island.

We’ll let you know when we have more information or a fix.

@flak Also hit with this… spent another weekend deleting half our project due to another update regression with no logs or direction given as to what it could be.

Turns out One File Per Entity is now flagged experimental.

Turning that off fixed it for us.

1 Like

Also experiencing this… ugh

Thank you for letting us know!

I just saw this Discord post and I’m not sure if it’s a direct answer to the general issue with experimental flag or only that specific case when using custom items.

My project was flagged because of “One file per entity” option (which is in beta - not experimental).
Turning it off helps only in getting rid of a warning about experimental features before pushing changes but I’m still not able to publish my map.