The missing DLL is declared as a runtime dependency of the DNxMXF module. It should be copied to Engine\Binaries\Win64 as part of the editor build steps. Looking at the code in FAvidDNxMediaModule::StartupModule, I see that this DLL is loaded after “DNxHR.dll” and both files are handled the same way, ie through the RuntimeDependencies property in their respective module. You should be able to find the DLL in the location I shared as I there should be another error in the log otherwise.
I was able to create an Installed Build with the following arguments locally. All the DNx dlls are present in Engine\Binaries\Win64 as expected and I have a Compressed DDC file part of the build.
Could the copy of the DLL be prevented by a virus\malware scanner on your end?
Please share the logs from a failed IB generation. You can find them in Engine\Programs\AutomationTool\Saved\Logs\. You will have to zip the entire folder as EPS only accepts one attachment per post.
As a workaround, you could manually copy the missing DLL in Engine\Binaries\Win64. Make sure that you are not using the Clean argument.
I don’t think that the answer is in the command line you shared. That being said, you do have some useless arguments (either wrong scope or deprecated).
-zenstore -cookincremental: Those are not required as compile or DDC arguments. They will do nothing
NoUBALocal has been deprecated a few release ago and folded into NoUBA.
NoUBA now refers to distributing work. The local executor will always be UBA with some tuning.
I would still recommend that you try a run without setting ExtraCompileArgs and ExtraDDCArgs.
I’m still working on getting the logs for this, but until then I can confirm the UAT arguments we use when building the engine (in case there is any smoking gun in there)