Re: [Bf-committers] Default for Raytracer Instancing

2011-01-28 Thread Doug Hammond
It has benefitted me - once told it needed turning on! +1 for on by default please :) Cheers, Doug. On 21 January 2011 10:39, Daniel Salazar - 3Developer.com wrote: > There's an option in the Performance panel in Render Properties called > Instances, it allows the raytracer to memory instance

Re: [Bf-committers] Default for Raytracer Instancing

2011-01-28 Thread Daniel Salazar - 3Developer.com
Since there has been no reply by the decision makers, consider this a formal bump. There is confusion over instancing in blender and people *are wasting hours* on this. I propose to get rid of this option in the interface and make it on for every file, old or new. Quoting a piece of IRC conversati

Re: [Bf-committers] Default for Raytracer Instancing

2011-01-28 Thread Agustin Benavidez
Even to avoid bug reports! Right now i am working on a heavy scene with raytracing, it sucks about 500 Mbytes with instancing on, and with instancing off it simply CRASH because it doesn't have the enough memory to build the tree! You can see it in the task manager, even in a 64bits with 8 gigabyte

Re: [Bf-committers] Default for Raytracer Instancing

2011-01-30 Thread Randall Rickert
When I read the post about instancing being off by default, I was in the middle of a big project with raytracing and lots of instancing. I can turn on instancing to save some rendering time, right? Wrong! Turning on instancing gave me longer render times, and it also made a small but visible diffe

Re: [Bf-committers] Default for Raytracer Instancing

2011-01-30 Thread Bassam Kurdali
I have noticed this too, turning on instancing, in scenes with lots of instances, sometime leads to longer render times. In the past it has been faster, too, so I don't know what's going on, or why it should have these results. On Sun, 2011-01-30 at 10:00 -0800, Randall Rickert wrote: > When I rea

Re: [Bf-committers] Default for Raytracer Instancing

2011-01-30 Thread Daniel Salazar - 3Developer.com
bassam/randall you do know that instancing will only work on duplis? and not on shared mesh objects? I wonder how your scene is setup Daniel Salazar www.3developer.com 2011/1/30 Bassam Kurdali : > I have noticed this too, turning on instancing, in scenes with lots of > instances, sometime leads

Re: [Bf-committers] Default for Raytracer Instancing

2011-01-30 Thread Matt Ebb
On Mon, Jan 31, 2011 at 7:45 AM, Bassam Kurdali wrote: > I have noticed this too, turning on instancing, in scenes with lots of > instances, sometime leads to longer render times. In the past it has > been faster, too, so I don't know what's going on, or why it should have > these results. It's p

Re: [Bf-committers] Default for Raytracer Instancing

2011-01-30 Thread Daniel Salazar - 3Developer.com
Matt instancing speeds up in orders of magnitude when a scene uses instances Daniel Salazar www.3developer.com 2011/1/30 Matt Ebb : > On Mon, Jan 31, 2011 at 7:45 AM, Bassam Kurdali > wrote: >> I have noticed this too, turning on instancing, in scenes with lots of >> instances, sometime leads

Re: [Bf-committers] Default for Raytracer Instancing

2011-01-30 Thread Brecht Van Lommel
Hi, When you enable instancing, it will only do it for objects that have more than one instance. So for that there should be no performance regression. It can degrade performance due to the overhead of the ray transforms, and because of lower BVH tree quality. Also when instancing meshes with only

Re: [Bf-committers] Default for Raytracer Instancing

2011-01-30 Thread Thomas Dinges
Hi Brecht, that would be awesome and will speedup things a bit :) Thomas Am 30.01.2011 23:19, schrieb Brecht Van Lommel: > I still have raytracing > optimizations to port over from the render branch, will look at > getting those into trunk, since they shouldn't change any results. > > Brecht. __