[Bf-committers] MSVC compiler optimize flags

[Ton Roosendaal]

Hi,

No this is a normal bug. :)
It's caused by gamma tables being used without initializing it (is  
skipped in non-OSA render). Render only_shadow_material.blend in OSA to  
see the effect.

Will take care of that one!

-Ton-

On 28 Nov, 2004, at 12:46, Peter den Bak wrote:

> Hi,
>
> Here is an other one.
>
> Start a fresh blender.
> Load form the 2.35 regression files the arealight file and press F12.
> Now press F1 and load the only_shadow_material file and press F12.
>
> The shadows are way too bright.
>
> Somehow things from the arelight file are left behind in memory  
> causing this
> to happen.
>
> When you load the only_shadow_material file in a fresh blender, it  
> looks
> fine.
>
> This happens with the windows build, don't know if it happens on other
> platforms as well.
>
> Regards,
>
> Peter
>
>
> -----Original Message-----
> From: bf-committers-bounces at projects.blender.org
> [mailto:bf-committers-bounces at projects.blender.org] On Behalf Of Ton
> Roosendaal
> Sent: Sunday, November 28, 2004 11:34 AM
> To: bf-blender developers
> Subject: Re: [Bf-committers] MSVC compiler optimize flags
>
> Hi,
>
> I think Brecht has found the offending unused variables. So it's no
> MSVC optimize bug after all. :)
>
> Related to this; I also heard the Windows version renders slightly
> brighter than Linux/OSX versions. Would anyone with both OSes available
> be able to test it? Maybe that's really related to optimize flags?
>
> -Ton-
>
>
> On 25 Nov, 2004, at 18:44, Peter den Bak wrote:
>
>> Hi,
>>
>> /O1 and /O2 also do the trick, and are slightly faster.
>>
>> Regards,
>>
>> Peter
>>
>>
>> -----Original Message-----
>> From: bf-committers-bounces at projects.blender.org
>> [mailto:bf-committers-bounces at projects.blender.org] On Behalf Of Ton
>> Roosendaal
>> Sent: Thursday, November 25, 2004 6:28 PM
>> To: bf-blender developers
>> Subject: [Bf-committers] MSVC compiler optimize flags
>>
>> Hi,
>>
>> While hunting a bug in the windows version, it appears that errors can
>> happenn with certain compiler flags, and only in MSVC7, not in MSVC6
>> (or so!).
>>
>> http://projects.blender.org/tracker/index.php?
>> func=detail&aid=1842&group_id=9&atid=125
>>
>> Peter found a compiler option (/Ox) that seems to solve this error,  
>> but
>> I'd appreciate an investigation what really goes on...
>>
>> - Are the default compile flags OK?
>> - Is nothing affecting floating point precision?
>> - Or maybe something that moves pointers to negative addresses?
>>
>> Thanks!
>>
>> -Ton-
>>
>>
>> ---------------------------------------------------------------------- 
>> -
>> -
>> --
>> Ton Roosendaal  Blender Foundation ton at blender.org
>> http://www.blender.org
>>
>> _______________________________________________
>> Bf-committers mailing list
>> Bf-committers at projects.blender.org
>> http://projects.blender.org/mailman/listinfo/bf-committers
>>
>> _______________________________________________
>> Bf-committers mailing list
>> Bf-committers at projects.blender.org
>> http://projects.blender.org/mailman/listinfo/bf-committers
>>
>>
> ----------------------------------------------------------------------- 
> -
> --
> Ton Roosendaal  Blender Foundation ton at blender.org
> http://www.blender.org
>
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at projects.blender.org
> http://projects.blender.org/mailman/listinfo/bf-committers
>
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at projects.blender.org
> http://projects.blender.org/mailman/listinfo/bf-committers
>
>
------------------------------------------------------------------------ 
--
Ton Roosendaal  Blender Foundation ton at blender.org  
http://www.blender.org