Well title says it’s all:
LogShaderCompilers:Warning: Failed to compile Material /Game/Materials/MasterMaterials/MM_LashesSimple.MM_LashesSimple for platform PCD3D_SM4, Default Material will be used in game.
is that a big problem?
are you using a substance plugin material? If yes, that is the problem, the substance plugin is not compatible yet
No, I’m using simplest alpha map in the input, nothing else. Extremely simple material. Compiling for Windows x64
Hi Pirog,
I’ve tried to reproduce this with the full release of 4.11 and I’m not seeing the same issue. It doesn’t appear to be just this material that is causing the issue though.You’ve got several that I can see in the Log at the bottom that are not compiling.
Are you sure there is not some other settings you’ve maybe set in the Project Settings for Packaging?
Are you able to create a simple material in a blank project and apply to the floor mesh in the default map and package? If so, do you still get the error in the log.
The warning that is there is simply saying that it will not render in SM4 which is using OpenGL and DX10.
If you get it to reproduce in that simple blank project, can you upload that here in a zip file and I’ll have a look to make sure there isn’t anything strange going on in the settings or otherwise.
Thank you!
Tim
I’m getting the same problem in a blank project on Mac, and the error seems to indicate failure to compile for Metal (rather than DX or OpenGL). Seems this problem may be cross-platform.
One thing I noticed - at least on Mac - is that the preview for a simple Vector3 node (which should show a color) shows up as black regardless of the values. It shows up fine in the color picker, but does not update in the preview on the node nor does it update the material.
Actually, I found the solution last night from another post regarding Metal errors. Apparently shaders in 4.11 don’t compile properly on Mac without Xcode installed, which wasn’t made apparent in the release notes. After I installed Xcode it worked fine.
Can you post this as I think the second issue you’re seeing is a separate issue with Mac that needs its own post.
I had one of our guys on the support team try and reproduce this on El Capitan and Metal enabled, but no luck. Once posted this can be assigned and investigated further. Thanks!
If you have any additional information that I had requested I can look into this further.
Thank you!
Ah, I guess that would explain it since when it was tested we already had xcode installed on our test machine. Thanks for following up.