This repository has been archived on 2023-10-09 . You can view files and clone it. You cannot open issues or pull requests or push a commit.
e93a7aa849ddefee9a5fb9e97764502adff7f83c
Bugfix #25280 Image: sequence option was hardcoded to assume "first frame" was always picture "001". Made it impossible to have a sequence of images starting with picture like "000" Note that by allowing to render a first frame as 000 in Blender, things mess up a bit here. Things work now as follows: - Start Frame = 1 : Image 001 on frame 1 - Start Frame = 0 : Image 001 on frame 0 - Start Frame =-1 : Image 000 on frame 0 ;) This is of course the lack of proper control for image sequences. Definite something to work on; best idea I have now is a new setting that defines the Image Number to be "first frame". That way you can map that number on any Blender frame. Or it makes it more confusing? :) For the doc department: the proper meaning of "Start Frame" now is: "The blender frame a sequence starts playing, assuming the sequence starts with image #1" Tooltop was fixed accordingly (Also fixed 'remove doubles' to show more precision in toolbar)
Description
Archive of Blender with old branches
Languages
C
67.4%
C++
23.4%
Python
6.1%
CMake
1.5%
GLSL
1.1%
Other
0.4%