[Bf-committers] MSVC official builds, optimisation and render errors

Simon Clitherow aphex at nildram.co.uk
Tue Aug 7 13:35:06 CEST 2007

Just did some more digging on this - the trunk version of blender 
doesn't have the problem at all (even with the old compile flags), but 
the stable branch does. I think stable might be missing an important 
commit somewhere but I'm not even close to guessing which one. And the 
fact that it doesn't appear as a problem on other platforms is just 
making it harder :)

I also noticed the problem in ray_blackdots.blend disappears if you turn 
off transparent shadows in the material options...

I'll keep digging, but if this is ringing any bells for someone - please 
let me know! :)



Matt Ebb wrote:
> On 8/7/07, *Simon Clitherow* <aphex at nildram.co.uk 
> <mailto:aphex at nildram.co.uk>> wrote:
>     Cheers for the heads-up, Matt.
>     RC1 had fixed the case shown in the bug report's blend file, but I had
>     no other render cases to check against.
> Oh, I see, that's interesting! I just isolated that test from one of 
> the files already mentioned on the tracker, after someone reported it 
> was a problem in RC1, as well.
>     Unfortunately, I don't know enough about the ray/rendering code,
>     so I'm
>     rather limited to trying different compiler flags options and
>     hoping for
>     the best.
> Yep, but just to confirm again, the file renders ok (albeit slowly) 
> here on my gcc/cygwin build. So at least it would seem to be something 
> that's being done differently by the compiler (whether that's the 
> compiler's or the code's fault might be hard to tell...)
> cheers and thanks
> Matt
> ------------------------------------------------------------------------
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers

More information about the Bf-committers mailing list