UPDATE: ok so the old version plus me grafting on new Blueprints got me close enough to where I have an acceptable amount of rework left (and the bright side is I can build it up better than before with Interfaces! hahaha).
Next step: source control!
PLEASE ADVISE: this is still a very nasty bug, but I don’t need a workaround/solution. The bug is reported through the auto-report when it crashes. I’ve narrowed the files down to all the BPs that had that interface. Do I resolve this thread or keep it open? Sorry for the trouble!
Steps:
So I was experimenting with using Interfaces.
I was shooting in the dark adding all sorts of Events and function from the Interface in the same BP and others.
After cleaning the BPs up by removing any extra/duplicate nodes I compiled the BPs and got an error saying something like,
"there are more that one function being called, starting at .
However, I did a search in the all BPs and confirmed there was only one call to the event/function.
I even tried deleting all and the error then read something like, "there are more that one function being called, starting at NONE.
At which point I decided something got corrupted and hoped a close/restart would fix it.
The project booted up, but now I can’t open any level or blueprint that I have created. I can create a new BP and edit it.
So it appears just the files are corrupt somehow.
I updated the project to 4.8 in hopes it would fix it, but it doesn’t work there either.
The crashes I’ve been auto reporting are under:
MachineId:5AE863D74F05166DD54EAB911058125F
EpicAccountId:6ca7010a03604552a41016db395e4096
Please let me know if there is anything else I can provide to help resolve this issue. Going to my last backup will be painfully long ago, (I have now learned my lesson and will set up a better backup system=/ ), so I would like to avoid that.
Any work-around or fix would be greatly appreciated.
Can you post your crashlogs here from \Unreal Projects\PROJECTNAME\saved\logs. Additionally, can you list the specific steps you took before your most recent crash? Does this occur in a clean, blank project with no additional content or is this limited to one project?
I believe the file became corrupt while I was playing around with Interfaces. I was adding interface events and functions and connecting them willy-nilly. I only noticed corruption next time I opened the project.
Hope it helps. Let me know if you need anything else. Thanks again.
Can you post the corrupt asset? I’ll be happy to take a look. Do you remember what nodes you added before the crash occurred? What was the interface doing? Did you move anything in the content browser that is relevant to the interface or corrupt blueprint?
it says I can’t attach the .uasset because it is a not a valid type. File size is 3.9Mb. Please advise on uploading a .uasset
I think the action that broke it might have been connecting an Interface Event node to the same Interface function. That is the weirdest thing I did that I can think of. Is that bad? hahaha
We haven’t heard from you in several days. I am marking this thread as answered for tracking purposes. If you are still experiencing this error, please comment with the requested information.
If you go into your \Unreal Projects\Projectname\saved\backups\folder\ there may be a copy of the. uasset that is not corrupt. Additionally, if you have source control you should be able to revert to a previous version before the corruption occurred. However this does appear to simply be a corrupted file as opposed to a specific bug. Was this project updated between engine versions?
Yeah, i wasnt able to recover from the corruption. So there was a lot of redo, but now with source control and cloud backup! Haha i was giving this file to you (plus the loose steps that got it corrupt) in case it helped tracking down the cause.
To answer your question, no. It was fine on 4.7 and was corrupted on 4.7.
Lemme know what u would like me to do with this thread. Thanks again for the replies!
Ah I understand. Unfortunately in the case of corruption like this there isn’t going to be much I can do on my end. I’m happy to hear that you have since started using source control and have been able to work towards replacing the corrupted assets. For now, I will mark this as answered. If this happens to another asset, please comment back here with updated information and I’ll be happy to take another look.