Whenever I try to apply a texture or material, It freezes the Editor, which then doesn’t respond again. I am not sure if it is problem with my computer or the Editor. I am unsure how to find a crash log for it considering I have to force quit it. Any help would be much appreciated.
This almost certainly isn’t a crash - we have a crash-reporter GUI that pops when it crashes - the Editor is just busy & not being very informative.
Let us check the project logs to see what it was doing when you forced it to quit by uploading the logs from: /Users/[your-username]/Library/Logs/UnrealEngine/[your-project]
You can hold the Alt/Option key while clicking on Finder’s ‘Go’ main menu item to reveal a quick link to the Library folder if you can’t find it.
I suspect it may just be compiling shaders & textures which can leave the Editor unresponsive for some time. You’ll see ShaderCompileWorker instances in Activity Monitor.app if it is shader related & if it is texture compression then UE4 will consume all the CPU & memory it can get its hands on. Both processes just take some time.
Yeah sorry I didn’t mean to put crash on there. I just got Unreal, and every time I texture it just becomes unresponsive. It doesn’t come out of it, I even left it running for a few hours. I’ll upload the logs in a bit.
I have the same problem on W7, but it happens while I start dragging a material. It gets freezed for like 30s, then it start working again, but the material isn’t applied.
Yeah mine doesn’t even respond again. Are you on Mac too?
Also if it helps, not all textures produce this freeze.
Windows 7 Ultimate 64bits w/ Unreal Engine 4.7.2 (this didn’t happend in 4.7.1)
Only textures that are DXT compressed will cause the editor to become unresponsive for long spells, as uncompressed textures require far less processing. That is normal & expected behaviour.
The log shows the material being recompiled including the textures, but is then just cut-off suggesting that it was still busy doing something.
I suggest running the project again, while it is unresponsive open /Applications/Utilities/Activity Monitor.app which will show you all the running applications. Select the CPU tab, then sort the list by % CPU (greatest → lowest) so you can see what’s eating CPU time. If there are ShaderCompileWorker instances then it is busy compiling shaders so just leave it alone & it will eventually return. If UE4Editor is chewing CPU then click on its entry and then use the drop-down box with the gear symbol & select Sample Process. This log will show you what functions UE4Editor is calling & from there we can see what it is up to.
There will be an update in 4.7.4 which should dramatically improve texture compression performance on OS X, which should hopefully make a huge difference to you in these situations.