3dsmaxbatch.exe 2026 crashes when Anima 7 is installed

I’m running into an issue when launching 3ds Max via Royal Render: Simply having Anima 7 installed is causing it to crash on launch with exit code -1073741819. Uninstalling Anima fixes the problem. Has anyone else run into a similar issue, and is there a fix or workaround beyond rolling back to Anima 6?

Hi @lynn_sisk

I’m not familiar with Royal Render, we don’t have licenses for it in our testing environment. That said, we indeed have tested Anima 7 with Backburner, Pulze, and Deadline, as well as running renders directly from the 3dsMax’s command line, and it works fine in all of them.

Have you tried rendering using the Anima Workstation installation mode and the Render Node mode? Or perhaps only using one or the other? If that is the case, could you please try to use the alternative installation mode provided in the installer and tell us the results?

To find out if the problem is actually not related to Royal Render but to your device, could you please try to render the same scene using any of those other render methods on that same device?

On the other hand, have you tried to contact the Royal Render support team? We provide both a full Anima trial version and a free Render Node version they can test on their side too.

Hello again @lynn_sisk ,

I just double-checked that 3dsmaxbatch.exe is working correctly with Anima 7 in both 3ds Max 2027 and 2026. I used a simple test script that loads and renders the maxstart.max scene:

Everything worked fine both when rendering a scene including Anima content and also without including any Anima content. Therefore, the problem you are experiencing is probably not related to Anima but to something else on your system setup.

In some cases we have seen random issues when having multiple plugins installed in 3dsMax that are not related to the plugins themselves but to how Windows loads DLLs. Sometimes, the installation order matters. In those rare cases, uninstalling some plugins and installing them back in a different order solved the issue. Perhaps you could try this workaround.