I couldn’t reproduce the problem that you have described in a newly created scene. Could you share some additional info like which frame are you rendering for the single frame test, etc. ? In fact, would it be possible to pack an archive and send it over to philip.shounev@chaos.com so we can troubleshoot ?
Thanks for the suggestion … Alas the camera and drone are not linked and are animated independently . the camera is imported as an alembic . the drone has its own little animation rig .
Thank you for providing a scene. We are currently testing a solution for this problem. So far, we have had positive results. Nevertheless, more testing will be needed before this solution finds a place in the next official release due to its complexity and involvement with other features.
@Philip_Shounev If you have identified a particular failing use case of motion blur could you please post the details of the issue so that the rest of us know what to watch out for?
Even if there is no current workaround we like to understand any bugs/issues so we can know what to expect is various situations.
This saves us users hours or days trying to find issues, and workarounds that may not exist and you have already tested.
The aforementioned difference in motion blur appears when a value of 0 is used for interval center. Until our fix for this case is complete and available the issue can be worked around by setting motion blur interval center to a value different than 0. In most cases a value greater than or equal to half of the duration value will suffice.
Excellent. Thank you. I have definitely seen some form of this. I thought it was the Phoenix particle shader at the time, but I don’t think I had time to test it thoroughly. ( and forgot to come back to it after the deadline. )
Great that somebody else narrowed it down and it is getting fixed; because in VFX we often need blur that is less than a 180deg shutter, and need control over the offset as well of course.