Change Details

While supported on a basic level, this ends up causing annoying problems especially relating to updating animated state and frame ranges. Examples of this are: - T52583 - where changing the render frame range also changes the scenes starting point in the sequence strip. - T50139 - again. - T42235 - seems related. - T38132 - again. - T33298 - again. - T30663 - again. This task is to see if its acceptable to remove this functionality in 2.8 to save headaches, users and devs wasting time on such useless and annoying behavior. The main down-side is existing blend files that use this wont render files that contain scene strips using themselves.

While supported on a basic level, this ends up causing annoying problems especially relating to updating animated state and frame ranges. Examples of this are: T52583 T50139 T44291 T42235 T38132 T33298 T30663... seems this is common annoyance, This task is to see if its acceptable to remove this functionality in 2.8 to save headaches, users and devs wasting time on such useless and annoying behavior. The main down-side is existing blend files that use this wont render files that contain scene strips using themselves.

While supported on a basic level, this ends up causing annoying problems especially relating to updating animated state and frame ranges. Examples of this are: - T52583 - where changing the render frame range also changes the scenes starting point in the sequence strip. - T50139 - again. - T42235 - seems related. - T38132 - again. - T33298 - again. - T30663 - again. T52583 T50139 T44291 T42235 T38132 T33298 T30663... seems this is common annoyance, This task is to see if its acceptable to remove this functionality in 2.8 to save headaches, users and devs wasting time on such useless and annoying behavior. The main down-side is existing blend files that use this wont render files that contain scene strips using themselves.