UEFN Crashing When Opening The Project That Worked Before

It all started after adding the jungle landscape to my project and now every time i try to open it i’m getting this crash report after 79% of the project being loaded, can anyone help me with that i can also provide crash log if needed

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000028

UnrealEditorFortnite_Win64_Shipping
UnrealEditorFortnite_Win64_Shipping
UnrealEditorFortnite_Win64_Shipping
UnrealEditorFortnite_Win64_Shipping
UnrealEditorFortnite_Win64_Shipping
UnrealEditorFortnite_Win64_Shipping
kernel32
ntdll

@Folevolt2 Thank you for your report! We would like to look into this further, would you be able to submit a bug report using the form available here? Fortnite Creative

1 Like

@Folevolt2 can you please confirm whether you sent us the crash report? Could you please reproduce the crash and send us the report again just in case? Thanks.

1 Like

I am also getting the same crash. However it happened when I was animating Klombo on my map. Now I can no longer open the island as it crashes every time. I have just sent a crash report.

1 Like

Hi I am Having the same issue, did you fix it? if so what did you do?

Copying my answer from another thread:

In case the forum urls are ever changed, In our case it was caused by the asset Tree Asteria Balsa Tree C. I had another person with a newer system open the project and remove the asset and redownloaded on my end.

1 Like

I have those trees on my map, i’ll try to remove them on other pc and see if it works ty

1 Like

I know it’s late but i sent report every time it crashed, so it should be there

Sadly no, but i think Kanneth found the solution

There is still no true solution, any sufficiently complex project will cause a crash on 10x nvidia cards

Currently working in a project with more than 15.000 manually placed actors and no issues on a 1080

still can’t open that same project on a laptop…

Are you using that jungle tree asset?

Nope, there is more than one asset which can cause that issue, I have seen at least three, and non of those are used in our map.

I was about to say. Only suggestion i can give you is to have another person who is able to open the map, make a copy of it. Then remove half the assets and check if you can open it. If not remove the other half. Keep halving the assets until you narrow down the asset that is causing issues. You can then remove it from your real map.
If you have multiple assets that cause problems youre probably going to have a bad time.

I have a feeling it’s going to be more than one asset, f*ck it, excuse my language. Does not look like Epic is on track to address it at all, I just had to invest in everything necessary to remotely power on and work on my home machine during travel, cause my laptop has 1060 in It which is affected by this bug.

sorry for the late replay but i tried to get the map in every way but sadly didnt manage to so i started the whole project from scratch i was at least able to transfter my verse code form island to island