[CRITICAL ERROR] Fortnite Devices removed from content browser and Game due to Source Control Error / Repair Doesnt Work

[BubbleBunz]

CRITICAL ERROR RETURNS: FATAL ERROR - What do these mean?

[2024.03.20-03.40.42:930][837]LogWindows: Error: === Critical error: ===
[2024.03.20-03.40.42:930][837]LogWindows: Error:
[2024.03.20-03.40.42:930][837]LogWindows: Error: Fatal error!
[2024.03.20-03.40.42:930][837]LogWindows: Error:
[2024.03.20-03.40.42:930][837]LogWindows: Error: Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x00000138412c9de0
[2024.03.20-03.40.42:930][837]LogWindows: Error:
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7db580487 FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7e3767465 FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7e3768bd0 FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7db65900d FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7dbe74668 FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7dbe46041 FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7dbe45f68 FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7dbe45fea FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7db65900d FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7dbe78061 FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7dbe77e17 FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7db683a77 FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7db682d53 FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7dc131ea9 FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7dfb72304 FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7dcba66b3 FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7de640e8c FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7e120ae8b FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7e120bc42 FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7df51f068 FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7dd90a023 FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7dd909d9b FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7dd9099b7 FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7deca6566 FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ffd5■■■257d KERNEL32.DLL!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error:
[2024.03.20-03.40.42:957][837]LogExit: Executing StaticShutdownAfterError
[2024.03.20-03.40.42:960][837]LogWindows: FPlatformMisc::RequestExit(1, LaunchWindowsStartup.ExceptionHandler)
[2024.03.20-03.40.42:960][837]LogWindows: FPlatformMisc::RequestExitWithStatus(1, 3, LaunchWindowsStartup.ExceptionHandler)
[2024.03.20-03.40.42:960][837]LogCore: Engine exit requested (reason: Win RequestExit; note: exit was already requested)

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Stability

Summary

I closed my project. Verified Files using Epic Games application.
Opened my project and noticed all Fortnite assets and devices were removed from my content browser due to a bug.
In the Viewport, the Outliner, and Content Browser within all of my completed projects.
This randomly occured March 16, 2024, after “Verifying files” last night and opening the project.
UEFN Fortnite Assets, Devices, Prefabs, Galleries, and Materials and Textures are all missing from each and every one of my projects.
The worst part is when I Select Repair in the right panel above the Outliner window, all of my devices are gone, and it is unusable.
I just published my game prior to this.

These output logs do not seem to be explaining the culprit of the issues with Source Control and Repairing, or what caused this when I verified files, but I do know that it seems to be searching in a AssetSubsystem GetAssetClassInfo(InAssetData) on my D:\ Drive which I have no fortnite data in that Drive, and I am wondering how to force the engine not to seach for Fortnite Assets on my D:\ Drive.
I have never changed my drive letter path nor the project folders location to the D:\ Drive. This was automatically caused by just Verifying Fortnite and UEFN.

Class Selector For Example

Steps to Reproduce

To Reproduce unfortunately all I had done was launch a session, publish public, Fortnite client crashed repeatedly, then I closed the project, closed UEFN. Opened other projects and tested Fortnite client crash. Client did crash. Closed Project and UEFN. Opened Epic Games App. Verified Apps UEFN and Fortnite. opened projects, ALL 1900 Fortnite Assets and Devices were deleted from the outliner, content browser, and viewport without a trace. The Outliner error at the top of the window said Repair, then a loading task said Source control 0/100% then it completed, and said could not repair the issues.

Expected Result

I expect to be able to use UEFN again. And Hope that all Fortnite devices and content will return to the content browser and all of my projects.

Observed Result

There are no Fortnite assets, devices, materials, or textures at all in any of my projects.

Platform(s)

Windows

Island Code

7385-3224-0691

Additional Notes

This is a UEFN issue I just need help redirecting the AssetSubsystem to my C:\ Drive somehow, I have no idea what made it search for the D:\ Drive after verifying files with the Epic Games App. I am unable to work in UEFN until this is fixed.

Additionally when I synced to a previous Revision Control it made no difference. All Fortnite Assets are Missing from the Content Browser.

[BubbleBunz]

HEADS UP! One Day Later… a Project with no name was opened.

The Directory reverts to the C:\ Drive/, go long!? We have your best interest in mind?!

REST ASSURED!

[Hardcawcanary]

Wow what a nightmare for a day

[BubbleBunz]

@BubbleBunz

Haha! You couldn’t have said it better

Haha! You couldn’t have said it better

[BubbleBunz]

CRITICAL ERROR RETURNS

[2024.03.20-03.40.42:930][837]LogWindows: Error: === Critical error: ===
[2024.03.20-03.40.42:930][837]LogWindows: Error:
[2024.03.20-03.40.42:930][837]LogWindows: Error: Fatal error!
[2024.03.20-03.40.42:930][837]LogWindows: Error:
[2024.03.20-03.40.42:930][837]LogWindows: Error: Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x00000138412c9de0
[2024.03.20-03.40.42:930][837]LogWindows: Error:
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7db580487 FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7e3767465 FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7e3768bd0 FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7db65900d FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7dbe74668 FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7dbe46041 FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7dbe45f68 FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7dbe45fea FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7db65900d FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7dbe78061 FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7dbe77e17 FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7db683a77 FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7db682d53 FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7dc131ea9 FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7dfb72304 FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7dcba66b3 FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7de640e8c FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7e120ae8b FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7e120bc42 FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7df51f068 FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7dd90a023 FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7dd909d9b FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7dd9099b7 FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ff7deca6566 FortniteClient-Win64-Shipping.exe!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error: [Callstack] 0x00007ffd5■■■257d KERNEL32.DLL!UnknownFunction
[2024.03.20-03.40.42:930][837]LogWindows: Error:
[2024.03.20-03.40.42:957][837]LogExit: Executing StaticShutdownAfterError
[2024.03.20-03.40.42:960][837]LogWindows: FPlatformMisc::RequestExit(1, LaunchWindowsStartup.ExceptionHandler)
[2024.03.20-03.40.42:960][837]LogWindows: FPlatformMisc::RequestExitWithStatus(1, 3, LaunchWindowsStartup.ExceptionHandler)
[2024.03.20-03.40.42:960][837]LogCore: Engine exit requested (reason: Win RequestExit; note: exit was already requested)

[BubbleBunz]

update.

Verify Files using Epic Games Luancher broke the previously repaired Source Control
Fixed on its own, then broke again. All devices and Fnc content is removed from projects and engine.
Prior to the Verify Files In Epic games luancher, engine was Lagging and Freezing non PC GPU or CPU related.

All Devices Removed from Content Browser due to Failure. I selected Repair but no fix.

[Hardcawcanary]

… Thats rough

Do you have a couple of bad bits in your Hard Drive ?

[BubbleBunz]

I forgot to add, This happens after “Verifying files” with the Epic Games App.
It also occurs after a Fortnite update / then resulting in Graphics card update on Geforce Experience.
Then Engine itself is the only program that is lagging, pinging, chugging, all other programs and games ive tested do not have this issue. This bug occurs in all projects in UEFN, and not just one.

My hard drive runs at 42° C and is 96% lifetime health M.2 SSD
I have nvidia rtx 3050 TI
13 Gen i7 Processer 20 Cores
64 Gb ddr5 5600 mhz

I hope this helps.

[Tinkerbell1980]

How did this got fixed in the end? Going through the same thing, for almost a month, have made so many reports, but no answers. Seems to be connected to Fab content as well that everything disappears. How did you get this sorted? Any help would be much appreciated!!

[BubbleBunz]

It is a wierd bug for sure. When the option to repair appears above the outliner window/panel, I repair. The repairing takes place and shows the task 0/100% repairing source control. There does not seem to be a relevant error in the output log. besides the DAD and patch error in output log saying unable to patch 375/400 files which are irrelevant. I am 99% certain the error (After each Fortnite update and or verifying files) that says [Critical] Failure Fortnite is looking for some build.ini file in the Local Pc Directory (D:) Drive is corrupt might be the issue, when the engine build.ini files are on my C:\ drive, or how it is searching for Engine Files from the Fortnite folder in the wrong locations. It is likely that Updating / Verifying files via Epic Games App are the cause of this. However It began with severe lag, ping in UEFN when there was a Graphics Card update, and fortnite update, then the lag got worse to where i could not right click or the engine would Stall out continuously at 1 second active 5 seconds disactive. I restarted the computer, updated all drivers to be sure it was not those, the engine behavior was irratic still, i verified files, which made it worse, and then I had the error in not only one project, but all of my projects, that the World Contains Invalid Actors, Click Repair. The issue is I do not have referenced actors in all of my projects, and all devices in the FNC content browser are not showing up.

World Contains Invalid Actors, Click Repair.

After a day or two the engine when i open up the project seems to repopulate the FNC content browser devices. This bug occurs every one to two weeks since December 2023. It is scary and gives me extreme panic as well as limits production. Repeatable bugs that are catastrophic slow my map building times to 1 year, which would normally take me 3 months. I am constantly challenged by the same bugs.

There is no permanent fix at the moment.

[Tinkerbell1980]

I absolutely understand where you are coming from!! i have had this since a month now, i am so sorry to hear that you have had this since December ( in shock!!) The amount of reports i have made, and nothing is being done about this. I really do not understand what the whole D file is, i only have the C drive just like you. I was almost finished with two maps, started over 6 times. And i have nothing to publish this month!! so my income is going to hurt a lot!! we really need to scream at the top of our lungs to get heard here!! any ideas on how to beat this? And or to get heard?