An error message will appear in the Message Log for "PIE", giving more info than before about the nature of the crash.
The infinite loop reporter is reporting every infinite loop by popping up a window for each problem loop.
So if you have an actor with 3 loops that trigger the infinite loop error and then you have 100 of them in a level, it will give 300 error messages. You can click one away, but they keep popping up until they are all done. The pop-up is a bad user experience by making them wade through text messages with no information.
Expected result:
We need one message that lists all infinite loops, what actors have them and where they are located.
1. Create an actor blueprint
2. Open the actor's event graph
3. Add a Begin Play event
4. Plug the Begin Play into a While Loop
5. Set the While Loop to true
6. Save and Compile
7. Add several of the actors into a level
8. PIE
Why does the REMOVE method of map container remove elements have memory leaks?
How do I set a material as a post-processing material?
UMG RichText not appear image when packaged
How to delete some elements correctly when deleting an array loop?
How does TextureRenderTarget2D get TArray<uint8> type data?
What is the difference between Camera and CineCamera?
How to implement springarm components to scale according to mouse position in spawn?
How does TArray loop correctly remove elements in blueprints?
There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-6812 in the post.
0 |
Component | UE - Gameplay - Blueprint |
---|---|
Affects Versions | 4.7 |
Target Fix | 4.8 |
Fix Commit | 2404786 |
---|
Created | Dec 17, 2014 |
---|---|
Resolved | Jan 14, 2015 |
Updated | Apr 27, 2018 |