Looks like a classic Viewport 2.0 problem to me.
As a temporary band-aid, you can get 1.0 back by setting MAYA_ENABLE_LEGACY_VIEWPORT=1
before launching Maya. Other than that, you’re welcome to cry with the rest of us.
--
You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group.
To unsubscribe from this group and stop receiving emails from it, send an email to python_inside_maya+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/3e1965e9-b162-48b0-8d93-07b4646f00d3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Oh big shit!it's the MotionBlur of viewport 2.0 ! When I disable this option I don't have the problem
--
You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group.
To unsubscribe from this group and stop receiving emails from it, send an email to python_inside_maya+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/14e94c25-512e-4b22-afb5-c42ed0b500fc%40googlegroups.com.
It is not possible to give this setup because some nodes are the property of the studio. When I have a time a make a basic rig for reproduce this bug.How are you tracking this type of problem ?
--
You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group.
To unsubscribe from this group and stop receiving emails from it, send an email to python_inside_maya+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/7f62f141-7d70-4f48-b827-ec263d28df33%40googlegroups.com.