My UEFN is crashing when I try to open project that I have been working on for a weeks. Other projects open fine. I was testing some props yesterday and everything was fine, but it won’t open today.
Project is under Revision control. Is there a way form me to update project to previous checkin in Revision control?
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
I figured out what happened.
My project started crashing when opening after I added some jungle trees from Fortnite\Galleries folder.
I added the same trees to my new project, and my new project also started crashing.
Luckily, I am using git revision control for my new project so I was able to discard changes.
OK, now it started happening again.
Only this time I can open it if I open other project first.
Could it be because I always start my project using Tropical Island premade map?
Seems like if I add to many new props, Project starts crashing when opening.
Not sure if this is related but i had a similar issue. Some people could open the project and some not. People affected where usually people on older systems. Even the memory address of the exception was the same. In our case it was caused by this asset which im guessing is using some shader magic that certain graphics cards wont tolerate.
Tree Asteria Balsa Tree C
Hope it helps
1 Like
Thanx Ken.
My PC is pretty new. i7 13700, 64 Gb DDR4, Gigabyte Z790 Elite.
Only my GPU is old. GTX 1070.
That is the jungle tree I was playing with first 2 times I started getting crashes!
But last crash, the one that still let me open project from other project, I didn’t have that tree.
I’ll do some more testing by removing props.
1 Like
You are very welcome! I would suggest first looking at the jungle assets that looks to be using similar materials
This was tedious, but I figured it out.
So in my device code I was referencing Prop: Tinfoil ControlBox B from the picture.
@editable
BackWallProp : creative_prop = creative_prop{}
As soon as I removed that reference, project started opening directly again.
I’m so happy that this was an issue, not something else. I made so many changes in my classes organization last night. I have to keep in mind to reopen project more frequently while working on in.
1 Like
Glad to hear you found your issue!
Just out of curiosity, would the crashes reappear if you readded the reference?
Yes it would start crashing again.
1 Like
Is there any way to externally get rid of the asset through files? I didn’t do revision control’s ‘Check-In Changes’ thing and can’t access previous versions.
In theory, because unreal now saves every instance of actors and objects in a unique file, it should be possible.
I have not tried this myself and i have no idea what kind of issues it could create. If you try this definitly make a backup of the project first and expect to encounter some small issues after even if it does work.
Locate your project files, which should be in something like
“Fortnite Projects/YourProjectName/Plugins/YourProjectName/Content”
Theres two folders called ExternalActors and ExternalObjects which im pretty sure corresponds to the asset instances in your level. I would recommend deleting half of them and then trying to launch your project. If it doesnt work delete the other half. If it does work, keep halving the assets you delete, until you narrow down the issue.
Most likely the issue is in the ExternalActors folder imo.
Again i dont know if this works or not, use it as a last resort and only if you backup your project first.