Maxwell Render | Official public forum

I read in the release notes for 2.5.1.4 that there have been some improvements to the plug-in when it comes to exporting an animation out of Cinema (great job BTW, the same filenames in both Cinema and Maxwell is going to help a great deal).
The changes might explain some strange behaviour I encountered last night when trying to output an animation:

Firstly, if I try to export an animation with "Use render settings" enabled, Cinema will crash. I have to disable the option and manually enter the values. I've tried changing the frame range in Cinema's "Render Settings" to no avail.

More unexpectedly, when I successfully export the animation frames, the first frame renders successfully, but the second and all subsequent frames render with the wrong camera. This is easily solved by deleting the offending camera and leaving the correct one, but has never happened before. I didn't knowingly animate which camera should be active.

One last thought: When I opened the exported MXS files to confirm that the wrong camera was selected, I saw that there was a camera for every previous frame, rather than just the current one, I've never opened an animation MXS previously to look, but is this normal behaviour?

Cinema R12, OSX 64 bit, Maxwell 2.5.1, plug-in 2.5.1.4

Thanks

Thanks for the detailed report, I'll check into it.

I have found the problem, which is that there is a logical error occurring when the Frame From & To numbers are the same. However, this does not square with your statement that:

I've tried changing the frame range in Cinema's "Render Settings" to no avail.

By render settings, I am referring to Cinema main menu > Render > Render Settings > Output > From, To, and Frame Step. Are you sure that you can reproduce this problem when the value of Cinema's From parameter is not the same as that of its To parameter?

In the meantime, I will try to reproduce your active-camera issue.

[edit: the camera issue was a simple one: the list of cameras built in one frame was not being cleared in preparation for the next frame]

Please note that I have posted links to a 2.5.1.5 release preview (see here) which addresses both of these (identical animation From & To values, and redundant camera export during animation) issues.