Summary
For pre-40.0 projects, UEFN is forcing asset “resaves” that can break clean builds on edit session launches. Rollbacks fail because the resave overwrites committed settings, and edit sessions won’t launch without it. Private builds will play the game properly, but that means pushing private builds to test any changes at all.
This isn’t breaking every project, but it is breaking one with a significant codebase. My only current option is to record every setting on every device and then step through what changed with the “resave”
Please select what you are reporting on:
Unreal Editor for Fortnite
What Type of Bug are you experiencing?
Devices
Steps to Reproduce
- Load a project from pre-40.0.
- Rollback to a known working build.
- Press to launch edit session.
- Watch “resave” asset popup appear that forces user to save or edit session fails.
- “Resave” assets and proceed to edit session.
- Play edit session.
- Edit session gameplay is broken due to these “resaves” where nothing was actually changed by the user.
Expected Result
I expect to not need to resave any assets when nothing has changed. If these resaves are required, I expect the edit session to play similarly to published builds.
Observed Result
A variety of devices no longer function the way they did even a day or two ago.
Platform(s)
All platforms impacted since this is a UEFN edit session issue.
Island Code
Unpublished map