Search in
Sort by:

Question Status:

Search help

  • Simple searches use one or more words. Separate the words with spaces (cat dog) to search cat,dog or both. Separate the words with plus signs (cat +dog) to search for items that may contain cat but must contain dog.
  • You can further refine your search on the search results page, where you can search by keywords, author, topic. These can be combined with each other. Examples
    • cat dog --matches anything with cat,dog or both
    • cat +dog --searches for cat +dog where dog is a mandatory term
    • cat -dog -- searches for cat excluding any result containing dog
    • [cats] —will restrict your search to results with topic named "cats"
    • [cats] [dogs] —will restrict your search to results with both topics, "cats", and "dogs"

Compiling Shaders Everytime

Yesterday while I was saving my project the GPU crashed and Unreal Engine closed. Ever since every time I open my project it Compiles the Shaders for about a minute.

When I package my project and run the game without editor, it does not compile shaders but still annoys when I open the editor.

Is my project gone corrupt or is there any way to fix this?

Product Version: UE 4.9
more ▼

asked Dec 03 '15 at 12:55 PM in Using UE4

avatar image

64 17 24 28

avatar image Logan Bailey ♦♦ STAFF Dec 03 '15 at 06:25 PM

Hello tongucci,

From what you describe it sounds as if there is some residual information that was carried over before your GPU crashed. Now when you open your project, UE4 has to calculate what was in your scene.

Make a copy of your project before doing this.

Delete your Intermediate, Saved, and Derived Data Cache directories from your project. This will force the editor to rebuild things like your shaders from scratch. It will rebuild when you open it the first time. Let that finish and save the copy of your project. Then close and reopen your project and see if that fixes your shaders compiling.


avatar image tongucci Dec 03 '15 at 07:45 PM

Hello Logan, I did exactly as you explained. Then it took about half an hour to open the editor the first time. When it opened it didn't compile shaders and worked fine. But when I saved, closed and reopened the project it opened fast but again compiled shaders.

avatar image Logan Bailey ♦♦ STAFF Dec 03 '15 at 08:52 PM

Would you provide your DxDiag please? I would like to start eliminating the list of possibilities to what could be causing this issue. Deleting the folders begins to eliminate project specific issues.

Do you have one large .fbx with many materials associated with it? Does this happen in a blank project with nothing else in it? Does this only happen in 4.9?

After I have this information I can start to narrow down the list of what is causing your shaders to compile.


avatar image tongucci Dec 03 '15 at 09:25 PM

I am sending my DxDiag. There is no large .fbx and this only happens to a single project. I forgot to mention a very important detail; just before this started happening I had some meshes vertex painted before saving, and now when the project is opened and while shaders are being compiled, those same meshes have no texture until compiling is done. But those meshes are parts of an asset pack from Marketplace and I had re-migrated them to my project but that didn't fix.

alt text

(comments are locked)
10|2000 characters needed characters left
Viewable by all users

1 answer: sort voted first

Thank you. So, we have determined that you computer is fully capable of handling large scale projects so it's not within any limitations of VRAM and graphics that would cause your project to load slower. You have also stated that this does not happen within a new project. At this point I believe you may be correct in your assumption that your project has become corrupt.

I highly recommend starting with a new project. If you have an older version of your project that you can fall back on this may be your best option.


more ▼

answered Dec 03 '15 at 09:41 PM

avatar image tongucci Dec 03 '15 at 09:45 PM

Ok, thanks Logan.

avatar image tongucci Dec 05 '15 at 08:07 PM

Today I started from my latest backup and the same issue started when I used a mesh with same material, as foliage. Nudging a node and saving the material again easily fixed the problem.

avatar image Luos Dec 06 '15 at 01:56 PM

Hello Logan, Tongucci

From a few emails I understood this problem occurs with my "Luos's modular rock/cave pack" which is on the marketplace. Apparently it occurs when using the props to paint meshes as foliage.

As I have no experience with that, (never needed any terrain related options so far) I would need to spend a lot of time to set it up. Time which I currently don't have, at least for another week. The shader I created is fairly complex, and if it needs recompiling it takes a long time doing so.

I have no idea if painting the meshes as foliage will cause this bug.

In the meantime, try going to your derived data cache, normally found at: C:\Users*username*\AppData\Local\UnrealEngine\Common\DerivedDataCache and clean those. It will force a recompile as well.

I know its a rather odd request, but Logan.. Do you have time to see if its the shader in my cave package combined with foliage painting that is causing this?

Cheers, Luos

avatar image Logan Bailey ♦♦ STAFF Dec 07 '15 at 03:03 PM

Hello Luos,

I will look into this as soon as I am able.


(comments are locked)
10|2000 characters needed characters left
Viewable by all users
Your answer
toggle preview:

Up to 5 attachments (including images) can be used with a maximum of 5.2 MB each and 5.2 MB total.

Follow this question

Once you sign in you will be able to subscribe for any updates here

Answers to this question