Re: [Bf-committers] Default for Raytracer Instancing
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 gigabytes! So not only takes much less memory and faster render times, it also avoid out of memory crashes! Cheers. 2011/1/28 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 conversation here :) > > holy crap... much faster now, cheers :) > Im still waiting for a reply in bf-commiters on my proposal > of making that feature on by default.. > nobody seems to care > I care - I would have assumes it would instance by default ! > 1 hr+ wasted :( > > similar goes on all the time > > cheers > > Daniel Salazar > ___ > Bf-committers mailing list > Bf-committers@blender.org > http://lists.blender.org/mailman/listinfo/bf-committers > ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Default for Raytracer Instancing
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 conversation here :) holy crap... much faster now, cheers :) Im still waiting for a reply in bf-commiters on my proposal of making that feature on by default.. nobody seems to care I care - I would have assumes it would instance by default ! 1 hr+ wasted :( similar goes on all the time cheers Daniel Salazar ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
[Bf-committers] Problem building blender from svn on mac os x 10.6
Hello all, We recently tried to build Blender from SVN on a new Mac, on 10.6 using the darwin-9.x.universal libs. We could build fine by checking out the PREV revision of libs (r 33298). We believe it is something to do with including ctype rather than cctype perhaps conflicting with the python headers. Our best guess is somebody removing the conditional specific to apple in include/python3.1/pyport.h an excerpt of the build error follows: [ 60%] Building CXX object source/gameengine/Converter/CMakeFiles/bf_converter.dir/BL_ActionActuator.cpp.o In file included from /Developer/SDKs/MacOSX10.6.sdk/usr/include/c++/4.2.1/ios:47, from /Developer/SDKs/MacOSX10.6.sdk/usr/include/c++/4.2.1/ostream:45, from /Developer/SDKs/MacOSX10.6.sdk/usr/include/c++/4.2.1/iostream:45, from /Users/mymese/research/git/BGERTPS/blender/source/gameengine/Converter/../../../intern/moto/include/MT_Stream.h:46, from /Users/mymese/research/git/BGERTPS/blender/source/gameengine/Converter/../../../intern/moto/include/MT_Tuple3.h:46, from /Users/mymese/research/git/BGERTPS/blender/source/gameengine/Converter/../../../intern/moto/include/MT_Vector3.h:47, from /Users/mymese/research/git/BGERTPS/blender/source/gameengine/Converter/../../../source/gameengine/Expressions/PyObjectPlus.h:39, from /Users/mymese/research/git/BGERTPS/blender/source/gameengine/Converter/../../../source/gameengine/Expressions/Value.h:200, from /Users/mymese/research/git/BGERTPS/blender/source/gameengine/Converter/../../../source/gameengine/GameLogic/SCA_LogicManager.h:45, from /Users/mymese/research/git/BGERTPS/blender/source/gameengine/Converter/BL_ActionActuator.cpp:36: /Developer/SDKs/MacOSX10.6.sdk/usr/include/c++/4.2.1/bits/localefwd.h:58:34: error: macro "isspace" passed 2 arguments, but takes just 1 /Developer/SDKs/MacOSX10.6.sdk/usr/include/c++/4.2.1/bits/localefwd.h:70:34: error: macro "isupper" passed 2 arguments, but takes just 1 -- Ian Johnson http://enja.org ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Default for Raytracer Instancing
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 all duplis, IMO > this option should be on by default (if optional at all) since, from > talking to Jaguarandy some time ago, it should not bring any problems > or speed increase in any case, to the contrary, the speed and memory > usage when using duplis gets much better. Also sadly many people > ignore this setting so they don't benefit from it. > > cheers > > Daniel Salazar > ___ > Bf-committers mailing list > Bf-committers@blender.org > http://lists.blender.org/mailman/listinfo/bf-committers > ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Volume Rendering Updates
On 27 January 2011 22:59, Matt Ebb wrote: > First, let me clarify, you are talking about the existing light cache > functionality inside blender right, not anything new you've coded? Yes, basically the light cache, but "radiance cache" is just the proper term, to what it is. I currently have a separate radiance cache for single and multiple scattering and build on top of this some artistic control, like blending between both caches and scaling single and multiple scattering radiance independently in a post process. More advanced radiance caching, as for e.g. in [Jarosz08] would be nice at some point, but also hard to do. I guess the trivial method, which I have implemented is a better starting point for now. > To be clear, it doesn't just cache per object, it caches independently > per object instance in the render - if you've got multiple instances > you want them to be lit differently. I suppose it may be an acceptable > limitation if you want to bake and save lighting that it doesn't work > with instances, but it's not too elegant. Yeah, that was also an issue, why I had no idea how to do this elegant. I guess it really should work for instances, tho it would be possible to just create copies, but then things start to get confusing. > Some alternatives could be: > a) baking radiance to a format that can be loaded back up in the voxel > data texture and rendered using that. That would at least reduce and > make clearer any non-standard behaviour like not being able to share > materials among objects, since it would then be explicit. Hm, I haven't thought of this, just baking to a texture and then doing volume ray casting without shading. That would work, but I also don't know if it is the best workflow. Another side effect is, that this would only work for the current isotropic radiance cache, but rules out any anisotropic caching, which could be implemented in the future. > b) perhaps you have an option to bake selected objects, and their > shaded grids get saved to a nominated folder, by name. Once it's > flagged as being baked (perhaps stored in the material), in a > pre-process per frame, the renderer looks in that folder for the right > files per object/objectinstance and loads up the data directly into > each objectinstance's light cache before rendering if the bake files > exist. If they don't exist, the light cache can remain null, and then > either get cached per frame as is done now, or left un-shaded, or > whatever. I guess this would be the most practical approach,... so I would just create files per object instance with an auto generated filename in the same directory, as the blendfile. And create those in a baking render pass. > I would also recommend that any kind of baking be done consistently > with other types of baking in blender, using the existing render > baking interface. It shouldn't have to introduce yet another > UI/workflow. That's the main thing I am concerned with. So to keep this consistent, I would need to introduce a new bake mode, "volume radiance"? And a special bake render pass for volumes, which then shades selected objects, saves the caches to those files and sets a flag in the material/object. I will try to come up with something, after I have finished multiple scattering. aurel ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
