Reference ID
7a21b429-47c1-61cc-08da-249d42494ea9
Please select what you are reporting on:
Unreal Editor for Fortnite
What Type of Bug are you experiencing?
Publishing
Summary
Made some major updates to an island today, including voice over work, and am now met with the following issue when trying to upload to a private version:
Module 63435fb8-4db8-c262-6caf-c08e81151ef7 v54 referenced by this project has safety_status failed_soft and cannot be loaded.
Based on the few posts about this that I have seen, it appears that it may be an auto-moderation issue. The Qty(5) audio files that I have added into the game are free of any foul language or anything that even sounds close. I really do not want to undo all of my work due to an auto-modā¦ Is there an appeals process that I can go through to have someone check the audio files out instead?
Otherwise perhaps it is something else entirely. Is there any way to tell from this error message (or something else) what is causing the issue?
Thank you for your time.
Steps to Reproduce
Unknownā¦ potentially caused by using personal voice over audio. Not my first time adding it to an island though.
Expected Result
Potentially getting the same error code?
Observed Result
Resulted in the error:
Module 63435fb8-4db8-c262-6caf-c08e81151ef7 v54 referenced by this project has safety_status failed_soft and cannot be loaded.
Platform(s)
windows
Island Code
5895-4324-6886
Additional Notes
Published version is 5895-4324-6886, but the private version that I was able to upload but not publish is 3577-4038-5787.
@HalcyonKnight96 You seemed to be a major part of the two other posts that I was able to find involving this issue. When you have time to take a look into this with me, I would greatly appreciate it!
Update:
I deleted all audio devices and removed the audio tracks from the one sequencer that included them, then force deleted all imported audio files, saved, restarted UEFN, and still am unable to move beyond this error.
To the best of my memory, this day of working on the island primarily involved placing hundreds of assets such as rocks and trees, adding some torches, a few terrain paint touch-ups, adding accolade and analytic devices, adding more collectible coins, and messing with a day sequence device to get it closer to working properly.
All assets and devices in this map are original to UEFN and have not given me issues in the past.
Hello,
Iāve seen that issue pop up many times with no firm solution.
One thing to try - Backup your project, then delete and recreate your āGameFeatureDataā data asset. (Located in the base of your Content folder)
My other theory is that this is caused by filetypes other than .uassets in the project directory. (Maybe from importing VO?)
Let me know if either of those solve it!
1 Like
@Astrotronic you are my hero.
Short version:
- Force deleting the āGameFeatureDataā from within UEFN, then copy/pasting the backed up version back into the file, restored it (although it has a red X next to itā¦) and I was again able to publish my map!
Longer/detailed version:
- My guess is that this issue came about from adding in the VO files, so the first thing I did was go and delete all devices using the imported audio files, then delete the audio files themselves. After closing and re-opening UEFN, I was able to āUpload to Private Versionā, but could not publish the map because something along the lines of āthis island contains data that was previously blockedā.
- After reading Astrotronicās idea, I went to: Documents>Fortnite Project>ProjectThatBroke and copied that entire folder and backed it up on my desktop.
- Opened UEFN and the project that broke.
- Found the āGameFeatureDataā Data Asset and deleted it.
- Opened the backed up folder to the following location: ā¦> ProjectThatBroke>Plugins>ProjectThatBroke>Content
- Found the āGameFeatureData.uassetā file and copied it, then pasted it into the same location in the original game folder. It immediately showed up in UEFN.
- Clicked āUpload to Private Versionā.
- Opened the creative portal and published it in the new current state to ensure it would let me get that far.
- Currently the project is āIn Reviewā like it normally would be - so things look good!
I plan to now re-import the audio files one at a time and try to upload to private version to see which of them causes the issue. I will report back on this thread if I find anything useful. Thank you again SO much!
Glad to hear it! Thanks for the thorough follow-up.
If you wanted to create a new GameFeatureData asset itās under Miscellaneous > Data Asset > āFort Game Feature Dataā
It will be interesting to know if adding those audio files again will reproduce it.
I re-added the audio files one at a time, and saw no issues this time around. Also added a few official Fortnite Music files, again with no issue. Re-worked my audio devices and published the game successfully!
So it would appear that this was just an odd bug. Thank you again for the advice on clearing it up!
If there is any further testing I can do help figure this out for others, please just let me know!
1 Like