Box/Capsule/etc Trace for Object Crashing Game

purezy · June 10, 2015, 1:51pm

Seeing this issue both in 4.7.6 and 4.8 Preview. I’m using a box trace for objects to find a physics object my character can pickup in the level. It works fine in editor window when I run a simulation but when I try to play stand alone it does not work, and if I package the game and try it there it completely crashes. Here is the log for the crash:

[2015.06.10-13.24.59:750][894]LogOutputDevice:Warning:

Script Stack:
TheifCharacter_C.ExecuteUbergraph_TheifCharacter
TheifCharacter_C.InpActEvt_Use_UniqueObjectNameForCooking_24

[2015.06.10-13.24.59:750][894]LogWindows:Error: Windows GetLastError: The operation completed successfully. (0)
[2015.06.10-13.24.59:945][894]LogWindows: === Critical error: ===
Assertion failed: Result [File:Runtime/CoreUObject/Public/UObject\Stack.h] [Line: 225]

KERNELBASE.dll {0x000007fefd8aaaad} + 0 bytes
UE4Game.exe {0x00000001400f0337} + 0 bytes
UE4Game.exe {0x000000014016ab38} + 0 bytes
UE4Game.exe {0x00000001401324e8} + 0 bytes
UE4Game.exe {0x00000001405da51b} + 0 bytes
UE4Game.exe {0x00000001405f214d} + 0 bytes
UE4Game.exe {0x00000001405d4494} + 0 bytes
UE4Game.exe {0x00000001405d626d} + 0 bytes
UE4Game.exe {0x00000001405a949e} + 0 bytes
UE4Game.exe {0x00000001405d626d} + 0 bytes
UE4Game.exe {0x00000001405547d1} + 0 bytes
UE4Game.exe {0x00000001405d58a2} + 0 bytes
UE4Game.exe {0x00000001412084e0} + 0 bytes
UE4Game.exe {0x00000001410aa91b} + 0 bytes
UE4Game.exe {0x00000001415e281b} + 0 bytes
UE4Game.exe {0x00000001415f8b83} + 0 bytes
UE4Game.exe {0x00000001415de4c4} + 0 bytes
UE4Game.exe {0x00000001415f889d} + 0 bytes
UE4Game.exe {0x00000001411f0341} + 0 bytes
UE4Game.exe {0x00000001409aa9fb} + 0 bytes
UE4Game.exe {0x00000001409bd620} + 0 bytes
UE4Game.exe {0x000000014029c555} + 0 bytes
UE4Game.exe {0x000000014029c76d} + 0 bytes
UE4Game.exe {0x00000001402bdbe3} + 0 bytes
UE4Game.exe {0x00000001401934f5} + 0 bytes
UE4Game.exe {0x0000000140a083ad} + 0 bytes
UE4Game.exe {0x0000000140a15cb6} + 0 bytes
UE4Game.exe {0x00000001413faf61} + 0 bytes
UE4Game.exe {0x000000014140058f} + 0 bytes
UE4Game.exe {0x0000000140c9764e} + 0 bytes
UE4Game.exe {0x00000001400a01f6} + 0 bytes
UE4Game.exe {0x000000014008fe0c} + 0 bytes
UE4Game.exe {0x000000014008fe5a} + 0 bytes
UE4Game.exe {0x00000001400a1f19} + 0 bytes
UE4Game.exe {0x00000001430e4b65} + 0 bytes
kernel32.dll {0x00000000777159cd} + 0 bytes
ntdll.dll {0x000000007784b891} + 0 bytes
ntdll.dll {0x000000007784b891} + 0 bytes

[2015.06.10-13.25.00:121][894]LogExit: Executing StaticShutdownAfterError
[2015.06.10-13.25.00:124][894]LogPhysics:Warning: PHYSX: …\PhysX\src\NpScene.cpp (2977) 8 : PxScene::unlockWrite() called without matching call to PxScene::lockWrite(), behaviour will be undefined.
[2015.06.10-13.25.00:124][894]LogPhysics:Warning: PHYSX: …\PhysX\src\NpScene.cpp (2977) 8 : PxScene::unlockWrite() called without matching call to PxScene::lockWrite(), behaviour will be undefined.
[2015.06.10-13.25.00:124][894]LogWindows: FPlatformMisc::RequestExit(1)
[2015.06.10-13.25.00:124][894]Log file closed, 06/10/15 09:25:00

I have also attached a screenshot of my character blueprint.

anonymous_user_e729f54e · June 10, 2015, 7:02pm

Hello ,

I was unable to reproduce this issue on our end. I have a few questions for you that will help narrow down what issue it is that you are experiencing.

Quick questions:

Can you reproduce this issue in a clean project?
If so, could you provide a detailed list of steps to reproduce this issue on our end?
Could you provide a more extensive screen shot of the blueprints involved?

purezy · June 10, 2015, 7:19pm

Yes, I created a new third person project and modified the third person character blueprint to add the box trace on key press, image is attached.
Launched engine version 4.7.6, create new their person template with no starter content, opened up third person blueprint and added box trace for objects node, see image.

Log from crash when using basic third person template: [link text][2]

anonymous_user_e729f54e · June 11, 2015, 2:10pm

Hello ,

I was still unable to reproduce this issue on our end. Would it be possible for you to provide a zipped down version of your project and/or a packaged version that you are seeing the crash with?

purezy · June 11, 2015, 2:20pm

Suere, here ya go: https://drive.google.com/file/d/0B8390trix2eOcUhla0RfVXYxTUE/view?usp=sharing

purezy · June 11, 2015, 6:41pm

Yes, that workaround worked perfectly, thanks!!

anonymous_user_e729f54e · June 11, 2015, 6:36pm

Hello ,

I was able to reproduce this issue on our end. I have written up a report (UE-16915) and I have submitted it to the developers for further consideration. I will provide updates with any pertinent information as it becomes available. Thank you for your time and information.

Possible workaround:

The issue derives from trying to get the location of the component of the character. I was able to avoid the crash by get the location of the actor. This may or may not be viable depending on your needs but I thought I would provide the information. I hope this helps.

Make it a great day

spinav · July 28, 2015, 2:03am

I figured it out on my end! I had traces using my arrow component, i switched it to the character capsule and it works! No crash

Anonymous_e5d5c0bf7d300728867097ff79906dbe · December 14, 2017, 11:37pm

I have the same issue on 4.16
And I need to use a Component location for trace,
may you help me to work this round ?