[Closed] 4.13.2 - ResavePackagesCommandlet Null Material Function Inputs and Outputs
I have been trying to resolve null exception crash occurring when baking a level via the ResavePackagesCommandlet. I am executing the commandlet with the -map and -buildlighting params.
The exception occurs in UMaterialExpressionMaterialFunctionCall::Compile() Line 7314. I seeing all multiple Function Inputs and Outputs, however they are all null.
The flow as I see it is that the baking process hits a material that doesnt match the given shader in DDC decides to recompile a shader map. During compilation a material function is encountered. For some reason the Material functions Inputs and Outputs have the correct number of entries for the given material function, but they are all null. So far I have verified that the material in question is setup correctly with previews added to its inputs. It produces no errors on save. If I delete the material, it will crash on the next material function encountered.
Can you think of any reason that this would occur?
The question has been closed Jan 03 '17 at 09:47 PM by AndrewHurley for the following reason:
The question is answered, right answer was accepted
Would it be possible for you to try reproducing this in a new project with minimal assets and then privately sharing that with us? If you can pass us a reproduction case it should be much quicker to look in to as it definitely sounds like there's a bug there. We did recently fix a few material function issues for 4.14 so it could be related, but it's difficult to offer suggestions without getting the assert up in front of me.
answered Jan 03 '17 at 09:47 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here