Chaos Corona Forum

Chaos Corona for 3ds Max => [Max] Bug Reporting => [Max] Resolved Bugs => Topic started by: kumodot on 2013-03-25, 03:15:59

Title: MotionBlur Bug
Post by: kumodot on 2013-03-25, 03:15:59
I am rendering a animation of a little car entering the frame from right to left and away from the camera. On the first frames of the car, the object was "ripped" ? Looks like a Bug. I don´t know how to solve it. ;(

    There´s like a missing part of the object a huge part, like a horizontal rip.
    I will upload some sample images in some minutes. (I´ve deleted them and rendering again. But the error remains...)

     Here´s a print screen of the problem ->
   
Title: Re: MotionBlur Bug
Post by: Ondra on 2013-03-25, 09:32:15
I am not sure what I am seeing in the picture, can you post the scene?
Title: Re: MotionBlur Bug
Post by: kumodot on 2013-03-25, 15:05:18
Ok, it was rendering at that time.
   
    All the Red Area is missing, there´s a entire car body there with the MotionBlur turned of. The car was ripped of on the middle. I will send you more frames, in some minutes, so you´re gonna understand better. :)
   

     
   
Title: Re: MotionBlur Bug
Post by: maru on 2013-03-25, 18:32:02
Are you using displacement, morpher, or any other geometry-changing modifiers?
Title: Re: MotionBlur Bug
Post by: kumodot on 2013-03-25, 19:19:39
Nothing, it´s just a car. A Wolksvagen Bus entering the frame in "high Speed".

   Finally i have a Sample frame with and without motionblur (and "the bug")

     I´ve noticed that the only difference between the renders are the output resolution... sorry about the Red letters, the JPG ruined it. :(

     

     

   
Title: Re: MotionBlur Bug
Post by: Ondra on 2013-03-25, 19:58:11
ok, can you upload me the scene? (http://corona-renderer.com/upload)
Title: Re: MotionBlur Bug
Post by: kumodot on 2013-03-25, 20:26:04
I will try to reduce it´s size a bit, keeping the bug alive, cause it´s a job, and it´s "huge" file.
Title: Re: MotionBlur Bug
Post by: Ondra on 2013-04-28, 12:12:41
I've fixed a very similar bug, and dont have this scene, so I'm closing it