Welcome to mirror list, hosted at ThFree Co, Russian Federation.

git.blender.org/blender.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTon Roosendaal <ton@blender.org>2010-12-18 21:56:21 +0300
committerTon Roosendaal <ton@blender.org>2010-12-18 21:56:21 +0300
commite93a7aa849ddefee9a5fb9e97764502adff7f83c (patch)
tree67c3c5d1be7439e45e0ac13b20b63f3eb58fa773 /source/blender/blenkernel/intern/pointcache.c
parenta73e06775fbdcefffc6e9a567b7e3519abc9b4ca (diff)
FILTER="^\[[ 0123456789][ 0123456789][ 0123456789]\%] \|Linking \(C\|CXX\) static library\|Building \(C\|CXX\) object \|Built target "
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)
Diffstat (limited to 'source/blender/blenkernel/intern/pointcache.c')
0 files changed, 0 insertions, 0 deletions