Hi any1 can help me solve this issue? i dont know how to read the crash report. thank you
Can you attach your crash logs to this thread as a txt file? Also, if you’re able to reproduce the crash, if you could copy and paste the info you have a pic of above as txt and not a picture that would be extremely helpful.
Thanks!
Also, there were many bug and crash fixes that made it into the 4.8 update, can you try making a copy of your project and attempting to reproduce your crash there? It is possible it may have been fixed in the interim.
Thanks!
here is my log, thx
Hi LTE,
From the logs, it looks like you might be running a 4.8 project (D:/Documents/GitHub/FpsGame2 4.8) in the 4.7.6 version of the editor (LogInit: Version: 4.7.6-2513093+++depot+UE4-Releases+4.7). Can you double check this?
Also, does this only occur when you play in editor? I’m unable to find this specific crash in the crash report tool, are you submitting this when the crash reporter shows up, the thing you took the screenshot of? Are you able to reproduce the crash at all?
I’m seeing two warnings repeated right before the crash occurs in your logs:
LogAnimation:Warning: Playing a Montage (FP_Fire_Montage) for the wrong Skeleton (SKL_Character_1p) instead of (EpicSkeleton) and
LogAnimation:Warning: Playing a Montage (FP_Reload_Montage) for the wrong Skeleton (SKL_Character_1p) instead of (EpicSkeleton)
so you may want to check those assets.
Good luck!
i revert it back to 4.7 using version control, i didnt change back the folder name
i got the log file from the folder from the link u gave me
if this is in response to my question about crash report tool, as you can see from the picture and then the log you posted, they’re two different things, the picture is of your call stack that is reported to crash reporter, whereas crash logs from the linked location are of what your project was doing immediately leading up to the crash. It’d be very helpful if I could find your crash in our reporter tool.
In the meantime, here’s something to try. Since you’ve moved forward and then backwards in versions, here is something to try.
In the Engine folder, delete the DDC
(Derived Data Cache). In your project,
delete the Intermediate, the Saved,
and the Binary folders.
When you next try to package it will take considerably longer as the shaders will need to newly compile, but this should get rid of any old or corrupted files that haven’t gotten deleted.
Other than that, have you checked out the assets I linked above?
Sry i dont get what u mean, all the file i looked inside the appcrash folder is not similar. And i found out the cause, its because of calling Destroy() in my Weapon.ccp. But how am i supposed to solve it?
isit this log? link text
No, it’s the one above, the crash log from the editor. That is the one with your call stack, thanks. I still can’t find your crash in our reporter tool, however, I was mainly wondering if you’re hitting submit when the crash reporter tool pops up. I assume that’s where you got the picture above?
Also, have you tried deleting the files I recommended? Have you tried altering or removing the weapon asset in case it has been corrupted?
yes i tried everything u said, I found out it was the Destroy in my Weapon.cpp, but I dont know to solve it
You can delete that asset and start over, or if you can’t get rid of it you can migrate your project to a fresh blank project and leave out that asset and rebuild it in the new project.