Page MenuHome

Multcam selector, sequencer and rigid body simulation are acting weird together when choosing a different scene start &end value
Closed, ArchivedPublic

Description

System Information
Linux64, 16gb ram 2*gtx 560ti oc

Blender Version
Broken: All I've tried

Short description of error
The renderer gets another frame to render than what is displayed in the viewport.

Exact steps for others to reproduce the error
I've attached a blend file to illustrate the problem.

First I created a scene from frame 1 to 1200, baked the rigid body sim and inserted the scene in the vse. Then I applied a cam selector and switched the camera at certain frames. All worked well.
When I now increase the scene start value to (f.e.) 125 and the end value to (f.e.) 423, all seems to work well - until I render the scene. Because then, the scene start frame is added to the point cache and delivers an offsetted image to the renderer. Even worse is that it's not communicated to the user that the scene length in the vse actually changed. You can only see that if you're changing the trim duration (hard) at one of the scenes...

As a user, I would like to render out the scene exactly as I see it in the viewport...so I would consider that as a bug.

Thanks to Sergej Reich for investigating the issue partly..

Greetings, Thomas

Event Timeline

A few notes.
This is not really related to simulations.
What happens is that when you change the start frame of the scene the strips appear to have an offset.
This is very confusing when you use the scene as a strip in the sequencer becase now the 3d view is out of sync with the render result.

Not sure if you would call this a bug but it's confusing to have the scene start frame also be the sequencer start frame in this case.

Attached a much simpler scene with an animated cube.

A big problem (and bug) here is that it's not communicated well to the user what's going on. If you look at my scene, you'll see that the scenes are still as long as the original scene was - and that is clearly not what the data is underneath (because there we have the clipped scene data).

You'll see the real problem not until you change properties of the scene strips in the vse - because then, the scene strips are changed in size accordingly.

Brecht Van Lommel (brecht) lowered the priority of this task from 90 to 50.Nov 22 2013, 8:25 PM
Sergey Sharybin (sergey) changed the task status from Unknown Status to Unknown Status.Jan 2 2014, 7:17 PM

This is actually a known TODO issue: http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Tools#Sequence_Editor

It's happening because your scene does have start frame offset. Strip in the sequencer will use that scene frame as the first frame of the sequence.

This runs into conflicts when you're using the scene itself in it's sequecer -- it looks like a doubled frame offset. Workaround would be to use separate scene for VSE edit. Real solution would actually require VSE rewrite to avoid such a crappy things..

Thanks for the report, but it's a TODO..

Hi Sergey,

thanks for making me aware of the Todo List...didn't know that it existed! :)
When it's a todo then it's sad but fine... maybe I found my blender area to work on now ;)

Many greetings, CU in IRC