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 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 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. ---- Listing some options of how to handle this: - Warning on load or render, the scenes-in-scenes are not rendered (return pink pixels or so). - Allow existing files to render, just disallow the operator in to add the scene to its self, so newly created files don't suffer the problem. - Do-version files so a new scene is created with only sequence editor data. The tricky part of this is splitting out animation data (drivers especially). So not sure its practical. Alternatives? or any preference for how to handle?

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. ---- Listing some options of how to handle this: - Warning on load or render, the scenes-in-scenes are not rendered (return pink pixels or so). - Allow existing files to render, just disallow the operator in to add the scene to its self, so newly created files don't suffer the problem. - Do-version files so a new scene is created with only sequence editor data. The tricky part of this is splitting out animation data (drivers especially). So not sure its practical. Alternatives? or any preference for how to handle?