GPU problem with camera position.
Closed, ArchivedPublic


System Information
Operating system and graphics card
Windows 10
6 x Nvidea sapphire

Blender Version
2.79a hash 5bd8ac9

Short description of error
I made a ~ 60mb animation, its a product demo (so i dont put it in public post here.)
I got only 1 camera, and the only part animated is its position and a focus point.
I have a track-to empty as a focus target, for the camera and the empty i made a key frame animation.

The OpenGL rendering of the frame is just as in the viewport (looks correct).
CPU rendering of the frame works OK
GPU rendering of the frame does go Wrong
With GPU in cycles the positioning of the camera is wrong. this happens in command mode and in GUI mode its as if it takes position from where i start rendering and then doesnt move anymore


Philipp Oeser (lichtwerk) triaged this task as Incomplete priority.May 31 2018, 12:35 PM

Sorry, but I'm afraid without a .blend file to reproduce, there is not much we can do here...
(cant reproduce from just your descriptions)

If you could strip down your file to exclude everything that is not contributing to the problem and post that here?
Even just the camera? Does this also happen if you append the camera into a new file?

Marking as incomplete for the time being...

Well i've signed contract not allowed to disclose the product idea.
Maybe i found a workaround, in this case...
Although i am not sure for how long this will work ( as the the first 1300 + frames, went OK ).

Now i have enabled "use spatial splits", and the camera seams back "on track" again. (its position got updated).

Its a bit strange because OPenGL works fine, and CPU works fine too.
I just wait and see if it happens again, its a huge render task about 15.000 frames, and this happened around frame 1300.

I'm not exactly sure what spatial splits does do, so i'm not sure if this is the solution, or that it is another error that comes after rendering a lot of frames.

Bastien Montagne (mont29) claimed this task.

I’m sorry, but we cannot investigate an issue we cannot reproduce, so will archive this report until someone can give enough elements to consistently reproduce it. Thanks for the report anyway.