I’m having problems when playing a level that has landscape and foliage in it. After playing for a few minutes inside the level a crash is generated but the crash reporter doesn’t show anything too specific. The crash reporter shows the following:
UCameraAnimInst::SetDuration()
ConvertQueryImpactHit()
RaycastSingle()
UWorld::LineTraceSingleByChannel()
UKismetSystemLibrary::LineTraceSingle()
UKismetSystemLibrary::execLineTraceSingle()
Many tests have been done to see if maybe line traces generated by characters are the problem, or physical materials in the landscape. All matinees and extra cameras have been deleted also but nothing seems to work. All other levels in the game are working except this one. Can anyone shed some light into what causes this strange crash.
Hey Kikimaru01,
Could you provide me with your full crash logs generated from the crash, as well as your ‘dxdiag’?
I would also need a way to reproduce this crash on my end in order to provide more insight into the issue.
Let me know if you have additional questions.
Thank you,
H.
Attached are the log and the dxdiag. I don’t exactly know how to reproduce this crash because I don’t know what is causing it. I’m hoping you could give me some insight as to what could possibly be the cause of the crash. That way I can fix it on my end. The crash report just seems to point out that there is something wrong with a function in the engine leading me to believe that this is a bug. But if this is something that has a logical solution I would like to know more about the nature of this crash.
The crash is always the exact same one. It only occurs if linetraces are drawn at any point during play but the crash isn’t generated immediately after drawing the trace. The only thing we know is that the crash is generated by the function UCameraAnimInst::SetDuration(). But we don’t have any camera animations anywhere in the level or anywhere at all for that matter.
Hi I am hear is the photo of the crash. We don’t now what it is and do not now if is replicate for other map out of ours, we have some system that envelop characters and there line trace that registered there step that interacts whit the physical material to make a sound but that is no it. We up date it to 4.12 to 4.16 can be anything in that migrant or in the engine that can be calling UCameraAnimInst::SetDuration()
and causing a crash ore some info about UCameraAnimInst::SetDuration()?
Thanks.
The only way I can give you direction is to have a repro case in order to understand the context in which the crash occurs. Solely reading the crash log will not give enough information to implement a fix, this is why we always need a repro steps on our crash bug reports. This way our engineers know how the crash is occurring and have a place to focus on when applying a fix.
What is it you are doing when the crash occurs, i.e. share with me any custom setup outside of the default behavior?
Cheers,
H.
Hey David,
So the general rule of thumb when upgrading your project between versions is to do them in iterations, and check each version to make sure things did not break or workflows have changed.
In order to report this issue internally, we need to have a way to reproduce this crash on our end. That way we can determine what is causing the crash, and use the context of the case to implement a fix.
We are marking this as resolved until more information can be provided. Once we have the necessary information to reproduce the crash, we can continue with the reporting process.
Thank you,