From ba44bf522cd098c8568a8dea4218b91b8d161191 Mon Sep 17 00:00:00 2001 From: Ton Roosendaal Date: Thu, 7 Apr 2011 15:48:33 +0000 Subject: Bugfix #26812 On anim-render, a click in timeline stopped render completely. The reason for this was a bit wacko code to cope with frame-step feature (steps of multiple frames). I thought of fixing that, but instead decided to block any operator in Blender to change a frame while a render is in progress. Both render engine and UI are accessing (writing to) the same data then, which is a bad conflict. Still a serious weakness of threaded render, but I'll keep trying to allow this as far as possible :) --- source/blender/editors/space_view3d/space_view3d.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'source/blender/editors/space_view3d/space_view3d.c') diff --git a/source/blender/editors/space_view3d/space_view3d.c b/source/blender/editors/space_view3d/space_view3d.c index 72d7977e132..a8cdc99645d 100644 --- a/source/blender/editors/space_view3d/space_view3d.c +++ b/source/blender/editors/space_view3d/space_view3d.c @@ -214,7 +214,7 @@ static SpaceLink *view3d_new(const bContext *C) v3d->lens= 35.0f; v3d->near= 0.01f; - v3d->far= 500.0f; + v3d->far= 1000.0f; v3d->twflag |= U.tw_flag & V3D_USE_MANIPULATOR; v3d->twtype= V3D_MANIP_TRANSLATE; -- cgit v1.2.3