[Becco_UK]

macray: Thank you very much.

Until the problem gets properly fixed I am fine using Maxwell 1.5 which I have reinstalled. The airscrew only moves about 10 degrees each frame which works in Maxwell 1.5. For further testing in 1.6 I also used no rotation and as soon as the motion blur tag was applied the part did not render.

In Maxwell 1.5 I once applied a real life rpm to a prop' and even that rendered in the correct place - although the shape rendered triangular which was probably due to insufficient sub steps being calculated. My 10 degree movement is a sort of compromise just to give the illusion of movement in a still image.

I too suspect that parts are somehow being rendered in the wrong place when looking at the studio scene grabs.

[Becco_UK]

An old 'in progress' render of motion blur working with Maxwell 1.5.

This didn't work in Maxwell 1.6 either using the Cinema plugin.

[Tyrone Marshall]

An old 'in progress' render of motion blur working with Maxwell 1.5.

This didn't work in Maxwell 1.6 either using the Cinema plugin.

Hello Becco and Macray,

Check your camera (Rotation) H, P, and B values, please let me know if those values are other than 0.

We are on the hunt for what may be an issue in this area of the plug-in. Please compare this value with the 1.5 and 1.6 plug-ins and let me know what you have your settings as far as the camera H, P, and B values.

If you both could post a simplified stripped down scene of the error, I would appreciate so I can take a closer look at everything in scene.

Thanks!

Thanks again.

[Becco_UK]

The camera values have changed since the problem test renders where produced. However, I typically use: camera H value of less than zero (ie: -130), camera P value (ie: 33), camera B value remains at 0.

May be worth mentioning that during in progress work the camera often get rotated several times as a result of working on the model. So for instance the camera H value could easily get to -1330.

It is extremely rare for my Cinema camera H and V values to remain at 0.

I have a render going at the moment with Maxwell 1.5. When that is finished I will reinstall Maxwell 1.6 and try a render with all camera values set to 0.

[Becco_UK]

Ok, this annotated scene is what I will use for comparison.

The airscrew is rotating at 18 degrees per frame. 3 frames have been created the airscrew has been keyframed and the second frame is used for rendering.

Motion blur rendered ok with Maxwell 1.5.1. Should the 1.6 version still not work I will zero the camera values.

[Becco_UK]

A coresponding screen grab of the Maxwell 1.5.1 generated mxs, loaded into Maxwell Studio.

[Becco_UK]

This is the same unchanged Cinema4D scene rendered with Maxwell 1.6 via the new Cinema plugin. The airscrew is not visible in the render.

[Becco_UK]

A coresponding screen grab of the Maxwell 1.5.1 generated mxs, loaded into Maxwell Studio. The differences are noticable without explanation from me. Next stop: zeroing the Cinema camera H,P and V values.

[Tyrone Marshall]

Becco,

Thanks for the screen grabs. I have another question. The only difference in your examples are the plug-in correct? You have kept the same version of Maxwell Render MXCL that came with the 1.6 distribution? Could you supply the version name of the 1.5 plug-in you use?

[Becco_UK]

With the Cinema camera rotation values all set to 0 the result was the same when rendered with Maxwell 1.6.

[Becco_UK]

The Maxwell is the one I dowloaded from the Maxwell download site a few hours after it was released. The version number of the plugin (downloaded at the same time) is cinemaxwell_1.6f (the zip file name).

[Tyrone Marshall]

The Maxwell is the one I dowloaded from the Maxwell download site a few hours after it was released. The version number of the plugin (downloaded at the same time) is cinemaxwell_1.6f (the zip file name).

This is very good BeccoUK, thank you for that important information.

Please make sure I understand you with the plugin version (You used 1.6 f for both the test with Maxwell Render 1.5 and 1.6?) and the only thing you changed for the motion blur to work correctly is your Maxwell Render MXST and MXCL version?

Thanks again, we are getting closer to the problem on this one.

This helps a lot!

[Becco_UK]

When I have rendered with Maxwell 1.5 I have used the last Maxwell 1.5 Cinema plugin.

I have only used the new 1.6f plugin with Maxwell 1.6 ( I assumed the Maxwell 1.5 Cinema plugin would not work with Maxwell 1.6?).

Since the last test I have removed the airscrew out of the object hiearchy removed all keyframes, set new key frames and again no success.

[Becco_UK]

Not really worth posting another image for this but to eliminate the airscrew as the source of the problem I used a similar sized Cinema cube with no material applied/ This cube was keyframed with the same values as the airscrew. The incorrect rendering was the outcome with a faint white trace of the cube - all these problem tests have shown the motion blur being incorrectly applied along the scenes X axis instead of rotatioanally. The test renders by mashium123 and macray also indicates a similar unwanted movement along a scene axis.

[Tyrone Marshall]

When I have rendered with Maxwell 1.5 I have used the last Maxwell 1.5 Cinema plugin.

I have only used the new 1.6f plugin with Maxwell 1.6 ( I assumed the Maxwell 1.5 Cinema plugin would not work with Maxwell 1.6?).

Since the last test I have removed the airscrew out of the object hiearchy removed all keyframes, set new key frames and again no success.

Thanks Becco_UK this is the information I am looking for, I will copy your confirmation so that it can be used to further zero in on this issue.