[Becco_UK]

Mihai: The airscrew example uses only 10 degrees of movement from one frame to the next. The 3DS motion blur example I earlier referred to looks as though it uses higher values.

Motion blur, which was once working with the previous Cinema plugin is not working with the new one.

[Tyrone Marshall]

Becco, I am not very happy with the claims you have made at every forum that you can log onto with this claim of a bug.

It may be that this is a windows plug-in specific bug, but making a claim that this is broken in the way that you have, before proper evaluation is something that is not acceptable.

Here I have tested this and it works, the quality could be better but it is not broken.

For your benefit, here is what I did to make this work:

The scene is a simple cylinder positioned above a plane object. The cylinder is set to rotate 360 degrees with key frames at frame 0 and frame 20. The cylinder has two things done to activate motion blur within Maxwell Render. A motion blur tag with value added to Cylinder object, and motion blur activated within the Maxwell Render Settings Object.


Shot at 2007-11-23

[Becco_UK]

The Moderator: Your happiness is not the issue I have raised at only two forums. You must have your own agenda why you make such wild claims about a long time user of Maxwell Render.

Back to the real issue of motion blur. If the Cinema plugin cannot translate a simple low value rotation blur to the mxs file then it is broken.

I am pleased another Maxwell user has also provided supporting evidence to save further ranting from you.

In case no one has informed you - the time of the Maxwell Render forum moderator bully has ended. If you cannot accept that you should respond to civilised posts in a civilised manner then please clear out your desk.

[mashium123]

If it's me, that is meant by 'another user', let me mention:
Please do not involve me in this thing that seems to be going on... here... among two personalities.

A nice plug is the thing I am interested in.

Thank you.

[Becco_UK]

mashium123: I too am interested in a working Cinema plugin which is why I am reverting back to Maxwell 1.5.

I am surprised Next Limit allow their Cinema moderator to have such a poor attitude towards customers.

[Becco_UK]

With the Cinema motion blur tag I removed all rotation of the airscrew. The part in question still does not render!

[Tyrone Marshall]

The thread has been unlocked. The goal here and I am sure you all know my intentions is for a better plug-in. Many of you do not know how much hard work has been done in testing and coding by our brilliant plug-in developer when others chose not to touch the plug-in at all.

From my test, I cannot find the problem with the motion blur. I tested it before the release personally and saw no problems. I retested again, due to this thread and again found no problems.

My latest test is a combination of object rotation and object movement to show the two combinations of object motion result in real physical motion blurring. I have no problems working to help everyone achieve the same.

As you can see, a new sticky has been created for FAQ's. I actively look to now find those issues which seem to be appropriate for this FAQ and have begun to add them. It looks like motion blur will be another candidate for this list.

Anyway the latest test:

I tested with both OSX plugin and the WIN version of the plug-in using the demo version of Cinema 4D 10.5



Please keep the thread in a more civilized tone so that we can all learn from each other.

[Becco_UK]

With Maxwell 1.5.1 reinstalled on my Windows XP system motion blur of the airscrew works.

Another great update to the Maxwell Render core let down by a poor Cinema plugin.

[Tyrone Marshall]

If anyone else has a problem with motion blur and the new plug-in please do not hesitate to ask, I'll be more than happy to help you.

[mashium123]

As you can see, a new sticky has been created for FAQ's. I actively look to now find those issues which seem to appropriate for this FAQ and have begun to add them. It looks like motion blur will be another candidate for this list.

Yes, great idea to have motion blur cleared up a bit with the help of a faq.

[Kabe]

Becco, I think we actually have a bug here. However, ranting doesn't help
to get this working.

I would please like to know how to get motion blur working again with the new Cinema plugin.

Ok, here's how:
Strip down your plane scene so you just have the problematic part in it - use a stand in if you can't give out the propeller.
Provide that for download.
Make an error description.

Doing that costs you less energy, gives better Karma, and speeds up developing a fix.

This is btw what the beta testers are doing for months now, some of them for years.

Kabe

[Tyrone Marshall]

Becco you have been warned. Leave out the pointed descriptions to individuals and post your problem and scene so that we may help. We really want to help get to the bottom of the issue with motion blur that you are experiencing and extend a hand out to help you with this problem.

But please understand that continued personal attacks will result in moderator action. By the way, your last post was deleted as you continue to launch personal descriptive attacks which are against the forum wide rules of conduct.

The forum rules quoted for your edification:

MAXWELL RENDER FORUM RULES

ALLOWABLE MATTER:

• Anything of a technical nature that directly relates to Maxwell Render is allowed.
• Please post in the appropriate sections of the Forum. For example, post plug-in related topics or questions in the appropriate plug-in sections.
• Do post your render tests, images, experiments, techniques, theoretical knowledge and questions related to Maxwell Render.

OBJECTIONABLE MATTER / OFF TOPIC:

• Any post of a non-technical nature, even if the post relates to Next Limit in general, is considered off topic and is either subject to removal or it will be transferred to the Off Topic forum section.
• Forum users who repeatedly post topics of a non-technical nature will be subject to a warning and/or eventual restriction or banning from the forum.
• Do not under any circumstances make inflammatory or belligerent remarks or comments against other forum users, against NL personnel or anyone else. Such posts will be subject to deletion and/or the offending user(s) will be subject to restriction or banning from the forum.


Please follow these rules to keep this forum friendly, organized and strictly informative for yourself and fellow Maxwell Render users. Thank you.


We have decided to enforce these rules more rigorously. Throughout the past months, we have tried to leave the forum to manage itself, but the huge amount of non-technical threads that break the rules have made this forum messy and unfriendly. We have had numerous emails from clients who are unable to find answers to their technical queries in the haystack of non-technical posts that is the Maxwell Render forum today.

This forum’s main intention has always been to provide technical information and help, and so we are returning to that intention by managing this forum more closely. This will hopefully lead to a more informative, well-organized and friendly forum.

[Tyrone Marshall]

I added a new quick step and checklist to the FAQ for motion blur.

ref: http://www.maxwellrender.com/forum/view ... 793#252793

[Becco_UK]

Tyrone Marshall: Thank you for the detailed list. That is exactly what I was doing in Maxwell 1.5 for many months with no problem.

With Maxwell 1.6 it simply does not work.

[macray]

I tried to see how this might work with me.

Following Tyrone's I set up 1 cube turning around it's center presented by a cylinder. Applied a cinema motionblur tag, strength untouched 100%.

Set the animation in maxwell....

rendered I can see motion blur, but not where I'd expect it. It is stretched in front of the cylinder in the normal direction of the cylinder. Very strange. The system is tanding in place, no movement except the rotation of the cube.

This is just 1/2 revolution per 20 frames. Can it be that your revolution is much higher and therefore stretched much further so you cannot see it? try to lower the amount of rpm's on your propeller, maybe this shows a result. This could also be an explanation for the strange studio behaviour. I couldn't check it with this model because cinema crashed when I wanted to render it another time and the mxs was misteriously empty, except for the material...

my test can be seen here: http://pics.livejournal.com/macray/pic/000frbhf