So i opened a copy of my 4.11 project with the 4.12.2 engine, and when i load the biggest level in my project, it loads just fine. However, when i enable the viewport in this specific level, the whole engine freezes and the engines CPU usage remains at 25% at all times. I’ve let me PC run for hours to load the level with no success, which usually just takes seconds.I have been upgrading this project since 4.8.3 from engine to engine and i have never had this problem ever.
Hello MassiveKrull,
Could you upload the logs from one of these sessions where the editor froze while attempting to open the Viewport? Although it most likely won’t show an error, it should be able to give some more information as to where it stopped and froze.
I believe I got the right ones but I could be wrong.
C:\Projects Data SSD\Unreal Projects\Breakout - Copy 4.12\Saved\Logs C:\Users\Krull\AppData\Local\UnrealEngine\4.12\Saved\Logs
I as hoping there would be more information but unfortunately it doesn’t seem like there is much. I’m assuming that when you say that you “enable the viewport”, you mean that you had the Viewport window closed and then opened it from the “Windows” menu. Is that correct?
As this seems like a content related issue, would it be possible to get a copy of the project itself, preferably one of the older versions that didn’t freeze? This way I can ensure that it worked previously before converting it and attempting to reproduce this issue. If you would like to keep it private, you could send a link to the project to me on our through a private message.
[1]:
Yes, it is exactly as you described it. I figured it would be less demanding on my system to load the level without the viewport open/enabled. I have pinpointed the problem now anyhow. The name of my level that has the issue is “Level01”, I will use this name often to avoid confusion.
How i pinpointed the problem
- I migrated the content from my 4.11 FPS_BP project into a new/clean 4.12 FPS_BP project.
- I launched the newly created 4.12 project and loaded “Level01”.
- I could load “Level01” and fly around in the editor without problems, but as soon as I entered a specific post process volume the editor froze.
- I singled out the Ambient Cubemap in the post process volume to be the option that caused the freezes.
- I disabled the Ambient Cubemap in the 4.11 project and then opened a new copy of it with the 4.12 engine; “Level01” was loaded successfully without any freeze.
Now to the newly introduced issue
I can’t use the Ambient Cubemap in a post process volume in “Level01” without a freeze.
- I created post process volumes in other levels with the Ambient Cubemap ON for testing, but with no errors upon entering the volumes.
- I also created a new post process volume with only Ambient Cubemap enabled in “Level01”, but I still get these freezes upon entering the post processing volume in “Level01”.
I’ve only used the cubemaps/textures that comes along with the engine. The editor gives me freezes no matter which texture I use or which value the intensity got.I have no idea what it could be related to or why it would happen in the first place.
Okay so I did some more testing. I tested this in both a blueprint project and a C++ project.
- Created new clean 4.12 project.
- Created 2 post process volumes.
- When transitioning to one post process volume from another that has a different cubemap to the prior, the editor freezes.
This is why my project was unable to load from the start, because the last location of the editors camera was inside one of the conflicting post process volumes. So upon loading the level, i would have a freeze.
So i guess there’s no need for me to send any project now as my problem isn’t specific to this project.
Now is this a known issue or is it only me? I have tried reinstalling the engine several times already and I have never had any issues with versions before 4.12.
I’m glad to hear that you’ve narrowed it down. Unfortunately I’m not getting the same results. Have you tried using the cubemaps included in the engine content or is this occurring with your own custom ones? You can find the engine content ones by selecting the View Options icon at the bottom right of the Content Browser and selecting “Show Engine Content”.
If it does only happen with your cubemaps, would it be possible for you to send those assets or the small project you created that is experiencing this freezing behavior?
Yes I have only been using the included engine content. I’ve uploaded the smaller project now anyhow, in case it will be of help.
Link to dropbox with the smaller project: Dropbox - File Deleted
Thank you for sending that reproduction project. While looking at the settings, I now see what I was missing. Firstly, I’ve never used Ambient Cubemaps so I wasn’t aware that the intensity needed to be activated for it to actually do anything. Secondly, I hadn’t be setting one of them to Unbound, so although they were overlapping in my scenario, the issue wasn’t reproducing.
After looking into it further, it seems that there was already a bug in for this particular freeze but it was originally thought to only be a conversion issue. Since we have reproduced it from a fresh project, I’ve updated that bug with the new information. For reference, the bug’s number is UE-31945.
Unfortunately I can’t think of a workaround at the moment other than simply going back to 4.11 as this seems to work correctly prior to 4.12. I’ll be sure to update you when any changes are made to the bug report.
After some additional testing on our latest internal build, the issue seems to have disappeared. It was never marked as fixed so I’m not yet sure when the actual fix happened. This means I’m not sure when it’ll be fixed in a Binary build but it should be coming.
Alright thanks for the heads up. I just installed the 4.12.4 hotfix and the freeze/hang no longer occurs!