They appears right after i open my ingame Menu. After digging similar error posts and seeing what causes it, i am almost sure that Background Blur inside my Menu UMG widget causes that error (there is an option in my Menu which controls blur of Menu’s Opacity:)). So when that blur is 0 (disabled) - nothing happens. But when i move Blur slider and update settings (Save button) with it - i see those ugly red lines in Output Log window following with some freezees. It happens only 1 time per Game session and/or 1 time during PIE/Standalone play per Editor session. There is no PIE errors/crashes or any errors inside Message Log window. Also no crashes or something - only those error red lines and that freeze for about few seconds. I tried to find something similar here but found only that post ( Handled error: Ensure condition failed: CurrentDepthTexture - Programming & Scripting - Unreal Engine Forums ), where was said that it is possible caused by Translucent Material with Responsive AA enabled. I am a noob in UE and i wonder how it can be the same in my case, because i did nothing after moved to 4.18. And my Menu doesn’t use any materials at all, only some simple flat background textures. I don’t know what to do and where to catch that bug/error. Please help and sorry for my poor English:)
In theory i could try to reproduce this issue in a clean project, but i am still a noob, as i said before. So making the same conditions to reprodice it will possibly take a lot of time for me:) I have a fully functional Menu with a lot of settings and almost complete Player Character with movement and other possibilities. Nothing more serious.
I am almost sure that the cause of that issue is my Menu with Background Blur applied to its buttons and background. Buttons opens other widgets via one main Widget Switcher inside Main Menu Blueprint. Disabling “Set Blur Strength” Node or removing blue Target Nodes from it disables error messages too!
Maybe i can send you my project (800 megs zipped) with detailed steps to find and reproduce this issue on your end? If this is difficult or unacceptable for you i will try to make as you advice.
P.S. Sorry my possible stupidity but i am only half+ year in UE4 and my english is weak. Thank you!
If you would like to provide a project, you can do so via a google drive or dropbox link. As you suggested above, please provide steps to reproduce the issue in the provided project as well and I will be happy to take a look.
Thank you! I reduced project archive size to 180 megs (without Starter Content which i iamost not used). So you can choose wich one to download (they are the same, only *_Pure is without SC):
The steps to reproduce error is just written red on the floor of the default map:) But i repeat them here:
Open QualityMenu>HUD_UMG_Classic>‘WB_ClassicSettingsMain’ Blueprint. See red comments - there suspected Node is located - ‘Set Blur Strength’. If you disable it or remove blue Targets (Menu background and buttons) - no error anymore. So i am almost sure that this Blur is the case. To reproduce error - PIE or Standalone, press Enter to open Menu, wait untill game is unfreeze, then see Output Log for those ugly red lines. The exact location of that Blur option is inside Settings>Advanced>Menu Opacity Blur. If you set it to 0 then no errors happens (by default it is 0.33 so error occurs when you open the Menu itself).
I did nothing for this issue to happen. I just converted my project using “Convert In-Place” from 4.15.3 to 4.18 and got that error immidiately when i opened Menu in game for the first time. Also i did not any changes in Engine files. So i decides for myself that this is a bug related to new version:)
Please ask me everything if you need more info to reproduce error or something. Thank you!
P.S. Oh, i forgot to say that my movement is set to Arrows instead to WASD for current time of development (because i am on arrows myself). Also mouse Y is inverted. So if you want to make youself more comfortable you can rebind keys and setup mouse via Menu’s Settings>Control window. It’s working:)
We’ve recently made a switch to a new bug reporting method using a more structured form. Please visit the link below for more details and report the issue using the new Bug Submission Form. Feel free to continue to use this thread for community discussion around the issue.